Re: [NTG-context] m-letter.tex -- backslash interpretation error
Rob Ermers wrote: Thanks for your quick reply. I adapted the file, according to your suggestion. The letter now comes out right! Thank you for that. I immediately tried an items list, which also works! Still, if there is any \ code in the xml file, it does not seem to work. Changing \e to in Drie\eenheid makes the disappear. contact ... ... pLaan der Drie\eenheid/p ... /contact comes out as: ... Laan der Drieeenheid ... I also found out that \usemodule[m-letter] works much better than \usemodule[letter], which is not evident from the way is Context set up. maybe your local m-letter-re gets loaded otherwise Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] New ConTeXt cz interface installation problem
Dear friends, I apologize that I have recently sent message to this list only when I've got some problems. Nontheless I need to keep this tradition. :-( I tried to install the newest ConTeXt over the TexLive 9/2003. All was perfect except the Czech interface. I've got a strange error. What should I do to improve it? My system is this: * SuSE Linux 9.1 * TeX Live + CTAN 9/2003 * pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2) * ConTeXt ver: 2004.12.06 fmt: 2005.1.11 int: english mes: english * TeXExec 5.2.3 - ConTeXt / PRAGMA ADE 1997-2004 The excerpt from the log file is this: language : patterns for cz not loaded language : patterns for hr not loaded language : patterns for pl not loaded language : patterns for sk not loaded encoding : coding fde is loaded (/usr/TeX/texmf/tex/context/base/enco-fde.tex unprotect 3 language : language specific options [default-de] seamless appended language : language specific options [default-de] seamless appended language : language specific options [default-de] seamless appended encoding : coding pdfdoc language : language specific options [pdfdoc-de] seamless appended encoding : coding ec language : language specific options [ec-de] seamless appended encoding : coding texnansi language : language specific options [texnansi-de] seamless appended protect 3)) language : patterns en for en loaded (n=1) (/usr/TeX/texmf/tex/generic/hyphen/hyphen.tex) language : no hyphenations en for en (n=1) language : patterns de for de loaded (n=2) (/usr/TeX/texmf/tex/generic/hyphen/dehyphn.tex New German Hyphenation Patterns `dehyphn' Rev.31 2001-05-07 (WaS)) language : no hyphenations de for de (n=2) encoding : coding il2 language : patterns sk for sk loaded (n=3) (/usr/TeX/texmf/tex/generic/hyphen/skhyph.tex (/usr/TeX/texmf/tex/csplain/t1code.tex Font encoding set to Cork.) The \^, \`, \', \v, \ and \r expands to characters by Cork. (/usr/TeX/texmf/tex/csplain/skhyphen.tex)) language : no hyphenations sk for sk (n=3) encoding : coding ec language : patterns sk for sk loaded (n=3) (/usr/TeX/texmf/tex/generic/hyphen/skhyph.tex (/usr/TeX/texmf/tex/csplain/t1code.tex Font encoding set to Cork.) The \^, \`, \', \v, \ and \r expands to characters by Cork. (/usr/TeX/texmf/tex/csplain/skhyphen.tex ! Duplicate pattern. l.29 a1 I am quite desperate so I will be thankfull for any hint. Your sincerelly Michal Kvasnicka ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New ConTeXt cz interface installation problem
Michal Kvasnicka wrote: I apologize that I have recently sent message to this list only when I've got some problems. Nontheless I need to keep this tradition. :-( I tried to install the newest ConTeXt over the TexLive 9/2003. All was perfect except the Czech interface. I've got a strange error. What should I do to improve it? My system is this: * SuSE Linux 9.1 * TeX Live + CTAN 9/2003 * pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2) * ConTeXt ver: 2004.12.06 fmt: 2005.1.11 int: english mes: english (/usr/TeX/texmf/tex/generic/hyphen/skhyph.tex (/usr/TeX/texmf/tex/csplain/t1code.tex Font encoding set to Cork.) first of all, fetch a context zip from our website (or grab the minimal context distribution for linux, you can use that one alongside other trees if needed) The \^, \`, \', \v, \ and \r expands to characters by Cork. (/usr/TeX/texmf/tex/csplain/skhyphen.tex ! Duplicate pattern. l.29 a1 I am quite desperate so I will be thankfull for any hint. the integration of czech/slovak patterns in tex live is a mess, and among the reasons for problems you will find: - files not in the right places (generic hyphen paths) - using non standard names (*hyphen where oithers use *hyph) - combined with a latex depency (in the *hyph ones) in spite of what you may think, tex distributions are not upward compatible, and fonts and patterns are among the troublemakers. In your case: locate [cont-usr or so] where context tries to load czhyph and replace that by czhyphen; same for sk* (so, contrary to other languages, czech/slovak had the pattersn in the *hyphen files); in your current setup something t1code.tex is loaded and i don't even want to think about what interference can come from that -) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[Fwd: Re: [NTG-context] m-letter.tex -- backslash interpretation error]
-- - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ---BeginMessage--- [EMAIL PROTECTED] wrote: Rob Ermers wrote: I also found out that \usemodule[m-letter] works much better than \usemodule[letter], which is not evident from the way is Context set up. Hans Hagen comments: maybe your local m-letter-re gets loaded otherwise No, I have renamed the file m-letter-re back to m-letter.tex. The only adaptations in that file are the Dutch salutations and greetings which I want to have automatized rather than redefine them in a local file. So now, with \usemodule[m-letter], everything works fine. (Apart from the diacritics in the xml address file, that is.) If I write \usemodule[letter] a general tex file /letter.tex is loaded. Someone else already pointed that out. I'm not at home now, so I cannot check it, but it seems to me that it is this file: \texmf\tex\plain\base\Letter.tex. Context gets stuck at this and generates an error. this is weird, since the order of loading is: m- p- s- x- t- and only when that fails, the raw name btw, you can say \usemodule[m][letter] to force m over something else (handy for local modules); so, it looks like tex cannot find your m-letter module; does kpsewhich --progname=context m-letter.tex report something? did you do a mktexlsr ? Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ---End Message--- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New ConTeXt cz interface installation problem
Michal Kvasnicka wrote: Many thanks for your answer. I will try to follow your advices. As for TeX distributions, I'm getting desperate. I had to switch to TeXLive from teTeX, because 1) it didn't work with tha last version of ConTeXt I tried to install, and 2) in SuSE 9.1 mktexlsr doesn't work in the teTeX. Now I can see that the TeXLive is not better at all. Moreover, I don't understand why there are three different texmf directories. :-( What distribution of TeX should I use? Does your minimal TeX distribution support plain/LaTeX (for those rare cases I need to use them)? Well, I will see at the night. :-) in that case, just download the minimal context distribution for linux, you can rsync that one of needed (some 25 meg zip initially) in there, there is setuptex, run that one (with the tex root as arg) and make the formats texexec --make --all will give you all languages, including czech Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New ConTeXt cz interface installation problem
David Antos wrote:
just a comment. In TeXlive2003, czhyph.tex contains first
\ifx\addlanguage\undefined
\errmessage{This file can be used only in babelised formats!}
\fi
Well, I forgot to say that I commented these lines. :-) As for the rest,
I think ConTeXt is as superior to LaTeX as an herd of buldozers is to a
child trowel in digging. :-)
Many thanks to you both for your help.
M.K.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New ConTeXt cz interface installation problem
David Antos wrote: The path of least resistence is probably to make cont-usr.tex to point directly to the actual position of czhyphen.tex directly :-(, sigh... indeed, sigh ... a problem is that users keep their own cont-usr file and changes in names like that are then up to the user; i could add this to the kernel \definefilesynonym [czhyph.pat] [czhyphen.tex] % safeguard \definefilesynonym [skhyph.pat] [skhyphen.tex] % safeguard but then we end up with all kind of fuzzy code similar problems showed last year when the us hyphen filename was changed, (on some systems the alias file handled that, but who knows about that one) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] can I upgrade yet?
Some months ago I stopped upgrading ConTeXt. Here and there I saw references to new file hierarchies, and something about installation scripts ... if I remember correctly. I didn't want to break my system, so I just stopped upgrading, and stopped reading those messages (which I didn't understand, anyway). I'm currently using MikTeX. 1.) Concerning file hierarchy: did something monumental indeed ocurr that I ignored? 2.) If so, is it safe to upgrade? 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? 4.) Have I misinterpreted, and nothing much has changed? Sorry about this. I really want to avoid getting my system into some strange state, and spending hours unraveling the mystery. Done that too many times in my life. -gary ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Gary wrote: Some months ago I stopped upgrading ConTeXt. Here and there I saw references to new file hierarchies, and something about installation scripts ... if I remember correctly. I didn't want to break my system, so I just stopped upgrading, and stopped reading those messages (which I didn't understand, anyway). I'm currently using MikTeX. 1.) Concerning file hierarchy: did something monumental indeed ocurr that I ignored? enc and map files as well as scripts are now in new locations, i assume that miktex has been adapted to that 2.) If so, is it safe to upgrade? miktex has a good reputation or upgrading 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers 4.) Have I misinterpreted, and nothing much has changed? thing shave changed, e,g, the pdftex cfg file is gone now; no real problem for context since it never depended on that; the danger is in partially upgrading: a new pdftex will not work in an old tree Sorry about this. I really want to avoid getting my system into some strange state, and spending hours unraveling the mystery. Done that too many times in my life. i do my best to avoid problem sfo rusers, but some things are out of my control Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? I'm on MikTeX as well. I've kept my system up to date via the MikTeX Update Wizard. But just to see if unzipping cont-tmf.zip over my \texmf would break anything, I just tried it. No problem. That said, I updated my installation via the wizard only a few weeks ago ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Hans Hagen wrote: Gary wrote: [...] Sorry about this. I really want to avoid getting my system into some strange state, and spending hours unraveling the mystery. Done that too many times in my life. i do my best to avoid problem sfo rusers, but some things are out of my control Hans Understood and appreciated. I am *not* annoyed, and I apologize if I sounded annoyed. Thanks for the upgrade tips. -gary ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Hans Hagen wrote: Gary wrote: [...] 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers ok, here's what I did: 1. Upgraded MikTeX 2. Unzipped the latest cont-tmf.zip (from pragma-ade.com) into c:\tex\localtexmf 3. ran textools --fixtexmf --force (what does that do?) 4. checked c:\tex\localtex\context\config. texexec.ini is newer than texexec.rme, so I left it alone. 5. ran texexec --make en nl (do I need nl? I'm exclusively English. I guess it can't hurt.) 6. noticed that cont-en.efmt was automatically relocated to c:\tex\localtex\miktex\fmt but cont-nl was not. 7. moved cont-nl.efmt to c:\tex\localtex\miktex\fmt 8. renamed them both to *.fmt (per a note in the contextgarden wiki. Is this necessary?) 9. ran texexec --make metafun 10. moved metefun.mem to c:\tex\localtex\miktex\mem 11. ran mktexlsr So far, everything seems to be fine. Are all of these steps necessary? or advisable? Did I forget anything? Is there an shorter method that I've missed? (not that this is long or difficult) Thanks again, -gary ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Gary wrote: Understood and appreciated. I am *not* annoyed, and I apologize if I sounded annoyed. i was not annoyed at all -) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] can I upgrade yet?
Gary wrote: Hans Hagen wrote: Gary wrote: [...] 3.) Is there some other way besides my traditional method of unzipping cont-tmf.zip file into /localtexmf ? Do I need to rebuild the file system? no, you can unzip, run textools --fixtexmf --force, regenerate the database, and cross your fingers ok, here's what I did: 1. Upgraded MikTeX 2. Unzipped the latest cont-tmf.zip (from pragma-ade.com) into c:\tex\localtexmf 3. ran textools --fixtexmf --force (what does that do?) if needed it moves you rlocal enc/map files to their new locations, not needed if you have no commercial fonts 4. checked c:\tex\localtex\context\config. texexec.ini is newer than texexec.rme, so I left it alone. 5. ran texexec --make en nl (do I need nl? I'm exclusively English. I guess it can't hurt.) 6. noticed that cont-en.efmt was automatically relocated to c:\tex\localtex\miktex\fmt but cont-nl was not. 7. moved cont-nl.efmt to c:\tex\localtex\miktex\fmt 8. renamed them both to *.fmt (per a note in the contextgarden wiki. Is this necessary?) 9. ran texexec --make metafun 10. moved metefun.mem to c:\tex\localtex\miktex\mem 11. ran mktexlsr texexec --make (--all if you want all patterns) is normally enough, apart from moving the fmt and mem files (aren't those put at the right spot by miktex?) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] \godown to an absolute position
Hello. I have a style request that I haven't come across before and
don't know how to handle in ConTeXt.
I need the first line of text following a chapter title to always start
15 picas from the top edge of the text area. In other words, no matter
how little space the title takes up, the first line after it should
always start at the same vertical point.
Something like
--
\chapter{Chapter title}
\godown[to=15pc]
Start of the text of the chapter...
--
would be ideal, but of course \godown starts from the current point and
doesn't offer a to= option! I'm not sure that layers are the answer
because as soon as I have moved down I'm into the running text of the
chapter.
Can anyone help? Thanks very much.
Duncan
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \godown to an absolute position
Duncan Hothersall wrote:
Hello. I have a style request that I haven't come across before and
don't know how to handle in ConTeXt.
I need the first line of text following a chapter title to always start
15 picas from the top edge of the text area. In other words, no matter
how little space the title takes up, the first line after it should
always start at the same vertical point.
Something like
--
\chapter{Chapter title}
\godown[to=15pc]
Start of the text of the chapter...
quick and dirty:
\setuphead[chapter][before=\vbox to 10cm\bgroup,after=\vss\egroup]
\starttext
\chapter{test} \input tufte
\chapter{test\endgraf test} \input tufte
\stoptext
there are other solutions (synchronizing stuff) but that's more complex
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] ConTeXt dont work with fonts after last miktex update
After the last update ConTeXt has problems with fonts unter miktex.
from the log:
[1.1{original-empty.map}{texnansiOSFSC-adobe-cronospro.map
Warning: pdfetex (file texnansiOSFSC-adobe-cronospro.map): invalid entry
for `texnansiOSFSC-raw-CronosPro-Bold': invalid font file name
the entry in the map-file:
texnansiOSFSC-raw-CronosPro-Bold 4 CronosPro-Bold.pfb texnansiOSFSC.enc
Before update all worked fine. Nothing has changed. The .enc files are
under fonts/enc and in the miktex.ini the path is set on it (under
pdfetex). ConTeXt/pdfetex don't find any font file (but under LaTeX all
is o.k.). I red that there are have to changed any variables, but I
don't know how I have to do this under miktex (miktex.ini looks well for
paths). Why it doesn't work now?
Thanks in advance, Matthias
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt dont work with fonts after last miktex update
On Wed, 12 Jan 2005, Matthias C. Schmidt wrote:
After the last update ConTeXt has problems with fonts unter miktex.
from the log:
[1.1{original-empty.map}{texnansiOSFSC-adobe-cronospro.map
Warning: pdfetex (file texnansiOSFSC-adobe-cronospro.map): invalid entry for
`texnansiOSFSC-raw-CronosPro-Bold': invalid font file name
the entry in the map-file:
texnansiOSFSC-raw-CronosPro-Bold 4 CronosPro-Bold.pfb texnansiOSFSC.enc
Please remove the blank after the :
texnansiOSFSC-raw-CronosPro-Bold 4 CronosPro-Bold.pfb texnansiOSFSC.enc
Is it working then?
I'm guilty for this change (anywhere else this blank is missing, but it
was definitively allowed as i see now -- an undocumented feature).
What is the origin of file texnansiOSFSC-adobe-cronospro.map? Is it from
somewhere distributed or written by yourself?
Regards, Hartmut
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
