October 2004 - ntg-context - NTG Mailing Lists

Font sizes.
by Dirar Bougatef 11 Oct '04

11 Oct '04

Hi, I have 2 questions: 1. When you say something like : \definebodyfont[10pt][rm][tfe=lbr at 36pt] Do i have to provide the 36pts font files at first and install them or does context adapt a font file with another size to the 36pt size ? 2. I have installed a font which i got with a .pfb and a .afm file. When i make the following calls: \pdfmapfile{+texnansi-rubicon-karatmedium.map} \font\Myfont=texnansi-raw-KAMN \setupbodyfont[Myfont] \starttext This is roman, {\bf bold}, {\it italic}, {\bi bold-italic}, {\tfa bigger} and {\tfx smaller}. \stoptext Which size is going to be displayed ? Thanks. Dirar.

1 0

Undefined control sequence. <argument> \c!gebied
by Thomas A.Schmitz 11 Oct '04

11 Oct '04

OK, I tried several things to fix the error "Undefined control sequence. <argument> \c!gebied," but it persists. I wiped out my entire texmf.local tree and started from scratch because I thought the c!gebied was residing in some older file that ha dnot been overwritten. But even starting from scratch wouldn't amend the situation; after regenerating the format, I get the same error. However, grepping for "c!gebied" in the newly created tree gives only this result: grep -r 'c!gebied' ./* ./tex/context/base/cont-sys.ori:% \setupexternalfigures [\c!gebied={e:/fig/eps,t:/mine/figs}] ./tex/context/user/cont-sys.rme:% \setupexternalfigures [\c!gebied={e:/fig/eps,t:/mine/figs}] So this shouldn't be the problem since these two lines in cont-sys.rme are commented out. Does anybody have an idea where the error is coming from? There must be some old config file re-introducing it into the format file, but I can't seem to find it. Baffled Thomas

3 4

cygwin/tetex or miktex?
by rb 11 Oct '04

11 Oct '04

Is one of these two preferable when running ConTeXt on windows? Thank you --

5 5

Re: [NTG-context] Re: cygwin/tetex or miktex?
by rb 11 Oct '04

11 Oct '04

"Patrick Gundlach" <patrick(a)gundla.ch> writes: > Hello rb, > >> Is one of these two preferable when running ConTeXt on windows? > > please don't use the subject alone, it is confusing. Hello Patrick, Good point, thanks for the reminder and thanks for the suggestions. > You can also use fptex (or texlive). I'd prefer fptex over miktex over > tetex/cygwin. But I am not the person to ask, since I haven't seen a > windows system in a while. Just my impression from reading some > mailing lists and news groups. You might think of posting your > experience to this list. If I have any experiences worth sharing, I shall certainly do so. Thank-you --

1 0

Nightmare after upgrading
by Sun Minchao 08 Oct '04

08 Oct '04

Hello Hans, run into trouble again... yesterday I've upgraded MikTeX to 2.4, by the way I've upgraded ConTeXt to the newest version too, but after that I can texexec nothing more. I first tried some chinese texts, but texexec always reported: TeXExec 5.0 - ConTeXt / PRAGMA ADE 1997-2004 current path readonly : E:/Temp changing to path : C:\Temp executable : pdfetex format : cont-en source path : E:/Temp dummy file : test.run inputfile : test output : pdftex interface : en current mode : none TeX run : 1 This is pdfeTeX, Version 3.141592-1.20a-rc4-2.1 (MiKTeX 2.4) output format initialized to DVI entering extended mode (test.run ConTeXt ver: 2004.10.07 fmt: 2004.10.7 int: english mes: english systems : eTeX version 201 -> too old (bugs) language : language en is active <protectionstate 0> system : cont-new loaded (D:\CTeX\texmf\tex\context\base\cont-new.tex systems : beware: some patches loaded from cont-new.tex! color : palette rollover is available system (E-TEX) : [line 966] system (E-TEX) : [line 1021] ) system : cont-old loaded (D:\CTeX\texmf\tex\context\base\cont-old.tex loading : Context Old Macros ) system : cont-fil loaded (D:\CTeX\texmf\tex\context\base\cont-fil.tex loading : Context File Synonyms ) system : cont-sys loaded (D:\CTeX\texmf\tex\context\user\cont-sys.tex) bodyfont : 12pt rm is loaded language : patterns en->default:default->1->2:2 de->default:default->3->2 :2 fr->default:default->4->2:2 es->default:default->5->2:2 it->default:default- >6->2:2 nl->default:default->7->2:2 loaded specials : tex,postscript,rokicki loaded system : test.top loaded (./test.top specials : loading definition file tpd (D:\CTeX\texmf\tex\context\base\spec-tpd.tex specials : loading definition file fdf (D:\CTeX\texmf\tex\context\base\spec-fdf.tex <unprotect 3> <unprotect 4> system (E-TEX) : [line 2256] \ifcsname <protect 4> <protect 3>) specials : fdf loaded <unprotect 3> <protect 3>) specials : fdf,tpd loaded ) fonts : needs map file: ec-public-lm.map fonts : needs map file: original-base.map systems : begin file test at line 1 (E:/Temp/test.tex system : macros of module chinese loaded (D:\CTeX\texmf\tex\context\base\s-chi-00.tex (D:\CTeX\texmf\tex\context\base\./type-pre.tex) bodyfont : variant chi is loaded (D:\CTeX\texmf\tex\context\base\font-chi.tex loading : Context Font Macros / Chinese encoding : coding chi is loaded (D:\CTeX\texmf\tex\context\base\enco-chi.tex encoding : coding big5 encoding : coding gbk ) ! Undefined control sequence. <argument> \c!richting =\v!links \xprocesscommaitem #1,#2->\if ,#1 ,\@EA \xprocesscommaitem \else \if ]#1\@EAE... <argument> \c!richting =\v!links , \c!balanceren =\v!nee , \c!n =\v!passend ... \xdogetparameters #1]->\xprocesscommaitem #1 ,],\@relax@ l.418 \c!afstand=1.5\bodyfontsize] ? ! Emergency stop. <argument> \c!richting =\v!links \xprocesscommaitem #1,#2->\if ,#1 ,\@EA \xprocesscommaitem \else \if ]#1\@EAE... <argument> \c!richting =\v!links , \c!balanceren =\v!nee , \c!n =\v!passend ... \xdogetparameters #1]->\xprocesscommaitem #1 ,],\@relax@ l.418 \c!afstand=1.5\bodyfontsize] No pages of output. then I tried some english texts, they can be compiled, but in fact nothing has been written to the disk. before upgrading I've backup-ed the configurations ( texexec.ini, font-chi.tex, cont-system.tex, cont-usr.tex ) and just after extracting new files I've put them back, succeeded with "initexmf -u" and a new "texexec --make", but context just didn't work, though it worked fine before ( with same test files ). I've never thought it could be such a big problem. after several unsuccessful tries I decided to restored the old version, but I even couldn't go back! it seems that context has kept "memory" somewhere to trace the version changes. after 3 hours tired struggle I've lost all the patience and all the hope... I've also heared similar stories from other people, but I just wonder how it could be a trouble to upgrade a package like context? Best regards, Minchao

3 3

Re: website
by Thomas A.Schmitz 08 Oct '04

08 Oct '04

Very tasteful new look, I like the colors (except for the "links" page, the mauve doesn't go very well with the rest). One has to get used to the idea that a website is presented like a pdf document in sequential order, but the clean look is quite beautiful. Of course, I was impatient and downloaded the latest version, and now I get a couple errors when processing, but I hope can straighten that out. Congratulations, Hans, wonderful work! Best Thomas

5 10

supp-mps
by Vit Zyka 08 Oct '04

08 Oct '04

Hi, there is an additional space in the end of the line 653 in supp-mps.tex (latest alpha): \immediate\write\MPwrite{verbatimtex \MPinputtranslation etex ;} It causes e.g. wrong left bbox border in --------------------- \startuseMPgraphic{c} draw fullsquare scaled 2cm; \stopuseMPgraphic \startTEXpage \useMPgraphic{c} \stopTEXpage ---------------------- Vit Zyka (I sent it to the dev-context list in 19.9. but with no success.)

1 0

Context release differences
by Taco Hoekwater 08 Oct '04

08 Oct '04

Hi, For those of you that are interested in such things, I've created a new item on the wiki for the current ConTeXt distribution. It's not as detailed as usual, because the amount of changes is staggering. http://contextgarden.net/Release_Notes Greetings, Taco

1 0

Entities names instead of characters in header texts
by kopszak＠mnw.art.pl 06 Oct '04

06 Oct '04

Hello, I am having problems with setting up header texts based on source xml utf-8 coded. When I use: \useXMLfilter [utf] \defineXMLargument [imie-i-nazwisko] \title \setupheadertexts[title] I get the title right, e.g.: Maria Giżbert whereas the header text is: Maria Gi"zdotaccent b ert I attach the necessary files (without graphic files of course). Piotr -- Piotr Kopszak, Ph.D. Polish Art Gallery, National Museum in Warsaw -----------------------------> http://kopszak.mnw.art.pl/

2 5

Re: [NTG-context] first element in radio field
by Peter Rolf 06 Oct '04

06 Oct '04

Moin! First of all thanx to Hans and Willi for testing. It seems that I have to update my (pdf)etex to a newer version. No bug: lucky Hans, unlucky me ;) Willi Egger wrote: > Hi Peter > > I tried your example wit the alpha version: > This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2c 7.5.2) > ... > ConTeXt ver: 2004.10.1 fmt: 2004.10.2 int: english mes: english > > Indentation as mentioned in your mail I can not see. -- however there > are three things I do not really understand: > > 1. Though the frames are turned off for the unselected buttons, there > are left and righthand lines along the buttonboxes. a result of \showmakeup (struts?) > 2. When pointing on the first botton it turns correctly into the gray > area but with changing the text into "InAreaX", but this text can not > be selected in order to have it remaining. the names are not well choosen.... the prefix "X" in the button name means, that this button is inactive (X-ing off); only one button can be active in a radio field > 3 When clicking on the second button the contents of the first butten > changes into the value "NormalX" ... > > May be I do not get the idea of the radio-button ... > maybe this is not a good example for learning radio fields :) > Willi > > Hans Hagen wrote: > >> Peter Rolf wrote: >> >>> Hello all! >>> >>> This is my first attempt with fields, so I am not sure if this is a bug >>> in context or my fault :) >>> Anyway, the first element of my radio field is indented, while the >>> following >>> elements are ok. This is the case in horizontal and vertical >>> arrangment. >>> I added a minimal example... >>> >>> ConTeXt ver: 2004.10.1 fmt: 2004.10.3 int: english mes: german >>> systems : pdfTeX version 111 -> please update >>> systems : eTeX version 201 -> too old (bugs) >> >> >> >> >> it looks ok here, do others have the same problem? >> >> (\showmakeup may not be that handy in such cases) >> >> > \noindent >> > \vbox{% >> > \field[Button1] >> > \field[Button2] >> > \field[Button3] >> > } >> >> >> may better be: >> >> \noindent \vbox{\forgetall ....} > > ..... Greetings, Peter

1 0