November 2006 - ntg-context - NTG Mailing Lists

register with align is justification ?
by Steffen Wolfrum 22 Nov '06

22 Nov '06

Hi, once again I am in despair of the register/index. I assumed the syntax below gives a register in align=justification. But it doesn't. (It pretends to, but not good.) Is there a way to *force* justification? (Even with the space between words gets a bit large, to *some* extend.) Steffen \showframe \usetypescript[postscript][\defaultencoding] \setupencoding[default=texnansi] \mainlanguage[de] \enableregime[mac] \setupbodyfont[postscript,10pt] \setupinterlinespace[line=12pt] \definestartstop[kleiner][before={\startcolumns[n=1]\setupindenting [1em,yes]\switchtobodyfont[9pt]\setupinterlinespace[line=11.9pt] \setupwhitespace[3pt]},after={\stopcolumns }] \setupregister[index][pagestyle=normal,indicator=no] \starttext \startkleiner \placeregister[index][file=TestTuo] \stopkleiner \stoptext

1 0

on \setupindenting
by Pablo Rodríguez 22 Nov '06

22 Nov '06

Hi, after trying to get hanging indenting for standard paragraphs (or what you get in TeX writing \hang\noindenting at the beginning of the paragraph) and not being able to get this (without \star...\stop lists), I wonder whether it would be possible to add a "command=..." option to the \setupindenting command. I would need this to set up a bibliography where standard paragraphs should have hanging indentation (but at margin, not in margin). Thanks for your help, Pablo

1 0

problem with \startnarrower (?)
by Alan Bowen 22 Nov '06

22 Nov '06

There seems to be a change in latest ConTeXt (ver: 2006.11.20 09:49 MK II fmt: 2006.11.20 int: english/english) that has broken my definitions for setting extracts in the body text. \defineblank[extractdistance][3pt] \definestartstop[extract][ before={[extractdistance] \setupnarrower[left=1.5pc,right=1.5pc] \startnarrower[left,right] \noindent}, after={\stopnarrower \blank[extractdistance] \indenting[yes]}] \starttext Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Morbi commodo, ipsum sed pharetra gravida, orci magna rhoncus neque, id pulvinar odio lorem non turpis. Nullam sit amet enim. Suspendisse id velit vitae ligula volutpat condimentum. \startextract Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Morbi commodo, ipsum sed pharetra gravida, orci magna rhoncus neque, id pulvinar odio lorem non turpis. Nullam sit amet enim. Suspendisse id velit vitae ligula volutpat condimentum. \stopextract Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Morbi commodo, ipsum sed pharetra gravida, orci magna rhoncus neque, id pulvinar odio lorem non turpis. Nullam sit amet enim. \stoptext fails with the message: ! Undefined control sequence. <argument> \dosinglenarrower \redorepeatwithcommand [#1]#2->#2 {#1} \dodorepeatwithcommand ...repeatwithcommand [#1]#5 \else \dododorepeatwithcom... \next1 #1,->\docommand {#1} \doprocesscommaitem <argument> \relax left, right \doprocesscommalist ...aitem \gobbleoneargument #1 ,]\relax \global \advance ... ... l.14 \startextract If I comment out \startnarrower[left,right] and \stopnarrower in the definition of \definestartstop[extract], the text is set (though not as I should like). Any suggestions? Alan

2 2

please add support for Korean language in unic-cjk.tex
by Dohyun Kim 22 Nov '06

22 Nov '06

Hi. Recently I have tried to support typesetting UTF-8 Korean language along with context-beta. I have uploaded related files to a temporary server for your reference (3.5Mb): http://210.94.201.157/~nomos/KTUG/context-korean-test.tar.gz But as the current unic-cjk.tex does not cover Korean Hangul Syllables area and CJK Compatibility Ideographs area, I have to edit that file every time I upgrade context. It is so an annoying thing to do it every time that I suggest adding those areas in unic-cjk.tex file, like this: %%% Hangul Syllables \dostepwiserecurse{172}{215}{1}{\expanded{\defineunicodecommand {\recurselevel}} {\lookaheaduchar}} %%% CJK Compatibility Ideographs \dostepwiserecurse{249}{250}{1}{\expanded{\defineunicodecommand {\recurselevel}} {\lookaheaduchar}} Additionally, I here report some possible bugs of context-beta related to CJK (especially Korean language) support. First, unintended space is inserted when I change font family. This disappears if I add a comment sign in \enableunicodefont command in font-uni.tex. \def\enableunicodefont#1% {\definefontsynonym[\s!Unicode][\getvalue{\??uc#1\c!file}]% \def\unicodescale {\getvalue{\??uc#1\c!scale}}% \def\unicodeheight {\getvalue{\??uc#1\c!height}}% \def\unicodedepth {\getvalue{\??uc#1\c!depth}}% \def\unicodedigits {\getvalue{\??uc#1\c!conversion}}% \def\handleunicodeglyph {\getvalue{\??uc#1\c!command}}% \doifnot\currentregime{utf}{\enableregime[unicode]}% % the following \relax's are realy needed \doifvalue{\??uc#1\c!interlinespace}\v!yes \setupinterlinespace\relax \doifvalue{\??uc#1\c!strut}\v!yes {\setunicodestrut\unicodeheight\unicodedepth}% <- HERE {\resetunicodestrut}% \getvalue{\??uc#1\c!commands}\relax} Secondly, to deal with special commands in pdf bookmarks, "\simplifycommands" should be added to \sanitizePDFuniencoding command in spec-tst.tex. \long\def\sanitizePDFuniencoding#1\to#2% {\enablePDFunicrlf \simplifycommands % <- HERE \let\unicodechar\relax % prevent further expansion \retainlccodes\lccode32=255 % slooow \lowercasestring\PDFunicodetrigger#1\to#2% \edef#2{\expandafter\doPDFuni#2\empty\empty}} % slooow Thirdly, "\definefileinsertion{tpd}{mps}" in spec-dpx.tex seems to be a typo. I think this should be corrected as follows: \definefileinsertion{dpx}{mps} In fact, as an unsubscribed user I have posted a similar message to the context mailinglist a few weeks ago . But I did not obtain any response then. Now being subscribed, I repost it. Best Regards, -- Dohyun Kim http://people.ktug.or.kr/~nomos/

2 2

using cmbright and hfbright fonts
by M.J. Kallen 21 Nov '06

21 Nov '06

Hi all, I couldn't find anything on using the Computer Modern Bright font together with the Type1 versions (hfbright) so I experimented a little myself. I consider myself a ConTeXt novice, so I hope others can help me improve it. Attached are two source files: cmbr.tex and textfragment-context.tex. The latter is the text used to test fonts in the free font survey (http://www.tug.org/tex-archive/info/Free_Math_Font_Survey/survey.html) loosely adjusted for use in ConTeXt. The first file contains my attempt at defining typescripts for CM Bright and compares regular modern with CM Bright. I have a pdf output available for those who do not have the necessary font files. I'm particularly interested in CM Bright/hfbright, because of the sans serif math font which I believe is a good candidate for use with other sans serif fonts (like the Verdana example in This Way #9). Besides fixing any mistakes in my typescripts and setting things like bold math and encodings up correctly, the one thing that remains to be done (I think) is to define the math collection for cmbr. I'm not sure if something elaborate like math-ams.tex is required. hfbright has two files hfbras10.afm and hfbrbs10.afm, which look very similar to msam10.afm and msbm10.afm so maybe there's an easier way (font synonyms?) of using the hfbright AMS symbols instead of the regular AMS symbols? I think this would be a nice addition (perhaps in the form of a module) to ConTeXt. Any suggestions and help are greatly appreciated! Maarten-Jan ____________________________________________________________________________________ Sponsored Link Mortgage rates near 39yr lows. $310k for $999/mo. Calculate new payment! www.LowerMyBills.com/lre

1 0

Re: [NTG-context] Problems with \fillinfield
by Fredrik Sjunnesson 21 Nov '06

21 Nov '06

Hans Hagen wrote: > > Fredrik Sjunnesson wrote: > > > > Hi, > > > > PDF fields created with \fillinfield lose their filled in values as > > soon as they lose focus. > > > no, this is an acrobat thing ... you need to click in the field which > makes it stay > Thank you Hans, The main reason why I didn't suspect acrobat to start with is that everything else in the mwidget-s.pdf seem to work flawlessly. Since \fillinfield, as far as I understand, use the same underlying mechanisms as other kinds of fields I find it somewhat surprising that these fields are not affected by this missing configuration. Anyway, what is the name of the option that I have to use, I just can't seem to find it. /Fredrik

1 0

Missing \endcsname in the latest current
by Aditya Mahajan 20 Nov '06

20 Nov '06

Hi Hans, There is a missing \endcsname in the latest ConTeXt ver: 2006.11.20 11:37 MK II fmt: 2006.11.20 int: english/english %----------------------------------------- \definehead[Topic] \starttext \Topic{test} \stoptext %----------------------------------------- gives me ! Missing \endcsname inserted. <to be read again> \@@kosection <argument> \??se \@@sectie \s!start \letgvalueempty ...al \expandafter \let \csname #1 \endcsname \empty \@@setsectionnumber ...ueempty {\??se #1\s!start } \setcounter {\??se #1}{#2}... \dosetupheadnumber ...tionnumber \@@sectie {#2#3}} \egroup \findsectionnumber ...r [#1][\foundsectionnumber ] \setupheadnumber [#1][-1] ... l.6 \Topic{test} ? Aditya

2 2

Problems with \fillinfield
by Fredrik Sjunnesson 20 Nov '06

20 Nov '06

Hi, PDF fields created with \fillinfield lose their filled in values as soon as they lose focus. I have tried several different documents, including mwidget-s.pdf, with the latest Acrobat Reader on both Linux and Windows but I always get the same result. Any others with similar problems? Regards, Fredrik

2 1

Non-bold marker in bold head?
by Steffen Wolfrum 20 Nov '06

20 Nov '06

Hi, I need a non-bold (roman) footnote-marker even when the footnotes are in bold section heads. But the suspected syntax below doesn't work. Any other idea? Steffen \starttext \definehead[MySection][subsection] \def\MySectionStyle {\switchtobodyfont[rm,10.75pt]\setupinterlinespace [line=12pt]\bf} \setuphead[MySection][style=\MySectionStyle] \MySection{Bold text {\switchtobodyfont[rm,9.5pt]\rm\footnote{non- bold, roman footnote marker?}}} \stoptext

1 0

\write \getvariable and expansion
by Aditya Mahajan 19 Nov '06

19 Nov '06

Hi, Can someone explain what should be the correct order of expansion here. I want to enter the date entered as a variable to a file. \setvariables [test] [date={d=11,m=11,y=2006}] \starttext The date entered was \expanded{\date[\getvariable{test}{date}]}. \immediate\openout \scratchwrite test-001 \immediate\write \scratchwrite {The date entered was} % None of these work. % \immediate\write \scratchwrite {\expanded{\date[\getvariable{test}{date}]}} % \expanded{\immediate\write \scratchwrite \date[\getvariable{test}{date}]}} \immediate\closeout\scratchwrite \stoptext Thanks, Aditya

2 2