- ntg-context - NTG Mailing Lists

german sharp s in Metapost Labels
by Lutz Haseloff 12 Jan '04

12 Jan '04

Hi all, if i use another Font as cmr to typeset labels in MetaPost the german sharp s is typeset with wrong width. The same text direct typeset by tex (pdfetex) without MetaPost looks right. Is this a bug in tex or in metapost (i dont believe) or is it a font problem? Greetings Lutz My File: \setupoutput[pdftex] \setuppagenumbering[state=stop] \useencoding[win] \mainlanguage[de] \starttext \startMPgraphic verbatimtex \useencoding[win] \mainlanguage[de] etex; draw fullcircle scaled 4cm; label(btex Hans Maaß, Berlin etex(center currentpicture)); \stopMPgraphic \loadcurrentMPgraphic \placeMPgraphic Hans Maaß, Berlin \startMPgraphic verbatimtex \usetypescript [berry][ec] \definetypeface [palatino] [rm] [serif] [palatino] [default] [encoding=ec] \definetypeface [palatino] [mm] [math] [palatino] [default] [encoding=ec] \setupbodyfont [palatino, 10pt, rm] \useencoding[win] \mainlanguage[de] etex; draw fullcircle scaled 4cm; label(btex Hans Maaß, Berlin etex(center currentpicture)); \stopMPgraphic \loadcurrentMPgraphic \placeMPgraphic \usetypescript [berry][ec] \definetypeface [palatino] [rm] [serif] [palatino] [default] [encoding=ec] \definetypeface [palatino] [mm] [math] [palatino] [default] [encoding=ec] \setupbodyfont [palatino, 10pt, rm] Hans Maaß, Berlin \startMPgraphic verbatimtex \setupencoding [default=ec] \usetypescript[berry][ec] \definetypeface [postscript] [rm] [serif] [times] [default] \definetypeface [postscript] [ss] [sans] [helvetica] [default] [rscale=..9] \definetypeface [postscript] [tt] [mono] [courier] [default] [rscale=1.1] \setupbodyfont [postscript, 11pt] \useencoding[win] \mainlanguage[de] etex; draw fullcircle scaled 4cm; label(btex Hans Maaß, Berlin etex(center currentpicture)); \stopMPgraphic \loadcurrentMPgraphic \placeMPgraphic \setupencoding [default=ec] \usetypescript[berry][ec] \definetypeface [postscript] [rm] [serif] [times] [default] \definetypeface [postscript] [ss] [sans] [helvetica] [default] [rscale=..9] \definetypeface [postscript] [tt] [mono] [courier] [default] [rscale=1.1] \setupbodyfont [postscript, 11pt] Hans Maaß, Berlin \stoptext

3 4

Mac Way: Apple Symbols
by Adam Lindsay 11 Jan '04

11 Jan '04

Hi again. The Mac-specific followup to the Unicode Symbols My Way is now up on my site. http://homepage.mac.com/atl/tex/ This Mac-specific My Way documents some fonts available exclusively on MacOSX 10.3, "Panther," and makes them available to Mac users with fairly minimal installation effort. I do not distribute the fonts themselves. These include Mac-specific support files for the below Unicode Symbols package. It depends on Mac fonts, but might be interesting to other folks. If anyone finds this useful or interesting, I could use some help completing the naming of the other symbols. adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay atl(a)comp.lancs.ac.uk Computing Dept, Lancaster University +44(0)1524/594.537 Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

Number formating in MetaFun
by Nigel King 11 Jan '04

11 Jan '04

For the MetaFun Experts, Section 9.2 of the MetaFun manual gives vlogtext.bot(0, 10, 9, 10cm, "@3e") ; The formating of the numbers is controlled by "@3e". I have been trying to find the command which control this number formating without success. Please could somebody point me in the right direction. TIA Nigel King

2 2

Argument of \next1 has an extra }.
by Peter Münster 11 Jan '04

11 Jan '04

Hello, I would like to write a twoside document with a title page, so I wrote the following file: \setuppagenumbering[alternative=doublesided] \starttext \startstandardmakeup bla \stopstandardmakeup \stoptext But when processing \stopstandardmakeup, I get the error "! Argument of \next1 has an extra }." ConTeXt ver: 2003.12.12 Could someone help please? TIA, Peter -- http://pmrb.free.fr/contact/ ------------------------------------ Film Search site: http://f-s.sf.net/

2 2

unicode and out-of-box usability
by Adam Lindsay 11 Jan '04

11 Jan '04

Hi, folks, I've been struggling through, trying to learn Unicode in ConTeXt. It's been instructive, at least. (Hope to make a MyWay about it...) There are a few weird things that made it difficult to learn, and I was wondering if someone could help explain why things are the way they are. In unic-ini: \chardef\utfunihashmode=0 % 1 = enabled Actually, if I understand things correctly, '1' means "disabled", which is what I preferred, having not yet created any unicode vectors. So the internal documentation there seems wrong, and I would argue the default case (0) makes it harder for beginners. More confusingly, in font-uni: \def\enableunicodefont#1% {\definefontsynonym[\s!Unicode][\getvalue{\??uc#1\c!file}]% \def\unicodescale {\getvalue{\??uc#1\c!schaal}}% \def\unicodeheight {\getvalue{\??uc#1\c!hoogte}}% \def\unicodedepth {\getvalue{\??uc#1\c!diepte}}% \def\unicodedigits {\getvalue{\??uc#1\c!conversie}}% \def\handleunicodeglyph {\getvalue{\??uc#1\c!commando}}% %%%%%%%%%%% NEXT LINE \enableregime[unicode]% the following \relax's are realy needed \doifvalue{\??uc#1\c!interlinie}\v!ja\setupinterlinespace\relax \getvalue{\??uc#1\c!commandos}\relax} The \enableregime[unicode] runs in direct opposition with the \enableregime[utf] that normally goes at the start of (some of my) documents. As it stands, with the regime hard-coded, users have to put an \enableregime[utf] *after* the font declaration. That's awkward. The last proposed change/complaint is back in unic-ini, and came from my attempts to match the main body font with the unicode font. \def\utfunifontglyph#1% {\xdef\unidiv{\number\utfdiv{#1}}% \xdef\unimod{\number\utfmod{#1}}% \ifnum#1<\utf@i %%%% \unicodeasciicharacter\unimod \char\unimod % \unicodeascii\unimod \else\ifcsname\@@univector\unidiv\endcsname \csname\doutfunihash{\unidiv}{#1}\endcsname \else % so, these can be different fonts ! \unicodeglyph\unidiv\unimod % no \uchar (yet) \fi\fi} Basically, I'd like to use the \unicodeasciicharacter hook with this definition: \def\unicodeasciicharacter{\uchar{0}} (I'm not certain the above is release-quality code, but I've been testing it with a stripped down \utfunifontglyph that should be functionally equivalent.) Working with the unicode code makes me appreciate that it's really powerful part of ConTeXt. Thanks, Hans! gelukkig nieuwjaar, adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay atl(a)comp.lancs.ac.uk Computing Dept, Lancaster University +44(0)1524/594.537 Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 9

endnotes: ! Dimension too large. ??
by Steffen Wolfrum 10 Jan '04

10 Jan '04

Hi, when using \setupfootnotes[way=bychapter,location={text,none}] I get the following ERROR: <snip> ! Dimension too large. <recently read> \@@vn+footnote \placenotesasnone #1->\ifdim \ht #1 >\zeropoint \noteparameter \c!voor \setno... \dodoplacenotes ...tesintext \localpostponednotes \fi \fi \else \ifdim \ht \... \next1 #1,->\doprocessnotes {\dodoplacenotes }{#1} \doprocesscommaitem \doprocesscommalist ...item \gobbleoneargument #1, ]\relax \global \advance \... \doplacenotes ...2} \processnotes \dodoplacenotes \egroup ... l.8315 ? H I can't work with sizes bigger than about 19 feet. Continue and I'll use the largest value I can. <snip> OK, I have more than 700 footnotes - but when using "location=page" everything works fine. I was trying to find whether there is something missing when I just continue, and I found the TableOfContent is cut. But the text and the footnotes as well seem to be OK. Is there a patch helping me to avoid this error? Thank you, Steffen

2 1

bold small caps
by Peter Münster 09 Jan '04

09 Jan '04

Hello, I just tried the Latin Modern font, but there are no bold small caps available, as in the EC fonts. Is it possible to add EC support to ConTeXt? TIA for any hint, Peter -- http://pmrb.free.fr/contact/ ------------------------------------ Film Search site: http://f-s.sf.net/

1 0

extended ascii characters
by Gonçalo Morais 09 Jan '04

09 Jan '04

I would like to know how I may use extended ascii characters in context, for example character number 167. Thanks in advance Gonçalo -------------------------------------------- IPLNet WebMail http://www.mail.ipl.pt -------------------------------------------- "Campus Virtual" do IPL - Já Aceite ! http://www.net.ipl.pt/index.html#WIRELESS --------------------------------------------

9 18

arabtext in Context
by R. Ermers 09 Jan '04

09 Jan '04

Hi Context users, A number of flaws in the ArabicTeX support for ConteXt (working under Miktex) have kept me from migrating to Context thus far. I guess I am not the only one. I sincerely hope that they can be fixed! Kind regards. Robert Ermers

3 4

Re: footnotes are lost!! endnotes don't work ?
by Steffen Wolfrum 09 Jan '04

09 Jan '04

Uff ... Hans, thank you very much for this super-fast help! This was really first aid. Steffen Hans Hagen <pragma(a)wxs.nl> wrote: > At 18:23 09/01/2004, you wrote: > >Hi, > > > >as the commands "location=text" and "\placefootnotes" seemed to be > >unproblematic I decided to edit a book in ConTeXt with footnotes as > >endnotes - at the end of each chapter. > > > >Unfortunately there seems to be a bug: > >My first chapter has 57 footnotes. > >The first 17 footnotes fit (touching the bottom edge) on the first page > >(after the chapters end) > >and the following 40 are lost! > > > >Is this a known bug? > > > >Does anybody know what to do? > > For the moment use: > > \setupfootnotes[location={text,none}] > > \starttext > > \dorecurse{100}{test \footnote{test} \endgraf} > > \placefootnotes > > \stoptext > > else the notes get boxed and treated as a whole (so that they can have > backgrounds and so). > > Hans

1 0