Re: [NTG-context] New Release Winedt WORKS with MKIV!!
Update on using MikTeX 2.9, ConTeXt MKIV, Winedt 6.?!!! First let me thank Mojca, Aditya, Ulrike and Hans for looking into this. I received a suggestion to remove Miktex Full and install Miktex basic. That did NOT work as I like lucida and lucida math which will not function correctly using Miktex basic. So here is what I did to make it all work: 1. uninstall Miktex 2.9 basic 2. Install Miktex 2.9 complete 3.Go to Miktex\doc\latex\circuitikz and rename context.tex some other name. For some reason known only to Christian Schenk Miktex searches until it finds that sample and attempts to use it. So renaming that file allows luatex to kick in and start processing. Finally success! now all I need to do is figure out how to invoke bibiliographies in MKIV using bibstyle econometrica. Thanks to all!!! ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
Am Tue, 23 Nov 2010 19:43:13 +0100 schrieb Mojca Miklavec: limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ... I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users. The limited utf-8-support has been there for years. And it is really very limited: WinEdt is not capable to handle utf-8 documents that require more than one code page (eg. a mix of Russian and French). I don't care very much as I'm not using other scripts. In the few cases I need access to chars from other codepages I can use -notation. Or use emacs. -- Ulrike Fischer ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
On Thu, Nov 25, 2010 at 11:01:17AM +0100, Ulrike Fischer wrote: Am Tue, 23 Nov 2010 19:43:13 +0100 schrieb Mojca Miklavec: limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ... I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users. The limited utf-8-support has been there for years. And it is really very limited: WinEdt is not capable to handle utf-8 documents that require more than one code page (eg. a mix of Russian and French). I've seen all sorts of limited unicode support, but that one is really retarded, I can't actually imagine how such thing would be coded! Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
Am Thu, 25 Nov 2010 12:31:05 +0200 schrieb Khaled Hosny: limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ... I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users. The limited utf-8-support has been there for years. And it is really very limited: WinEdt is not capable to handle utf-8 documents that require more than one code page (eg. a mix of Russian and French). I've seen all sorts of limited unicode support, but that one is really retarded, I can't actually imagine how such thing would be coded! It is a simple mapping to a 256 codepage: To quote from the documentation: However, WinEdt can transparently convert Unicode (UTF-8) documents into ACP when they are loaded and back to UTF-8 when they are saved. This makes it possible to work with UTF-8 documents as long as they can be converted into ACP (Ansi Code Page). -- Ulrike Fischer ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
On Sun, 21 Nov 2010 02:03:33 -0700, barney schwartz barndog1...@gmail.com wrote: New build of WinEdt 6.0 (Build: 20101121) has been uploaded to www.winedt.com This build contains macros that work with the latest ConTeXt Mark IV (previous versions were designed for older version of ConTeXt). If you are upgrading from older version of WinEdt make sure that the executable for ConTeXt in WinEdt's Execution Modes is set context.exe (instead of old texexec.exe)... I used winedt for years, and turning it into a full-fledged dedicated ConTeXt editor would not be hard ... I had to leave it because there was no utf-8 or bidi support. limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ... otherwise the best dedicated tex editor I've ever used... Best wishes Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shiʿi Studies Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
2010/11/23 \Idris Samawi Hamid ادريس سماوي حامد\ wrote: I used winedt for years, and turning it into a full-fledged dedicated ConTeXt editor would not be hard ... I had to leave it because there was no utf-8 or bidi support. limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ... I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users. It's not that he made it default on his own machine - it is now default with every installation of WinEdt (it might be that they made that on his request). Mojca ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
On 21-11-2010 10:03, barney schwartz wrote: Just thought I would post this here for other Winedt users. ah, good. thanks, Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] New Release Winedt WORKS with MKIV!!
On Sun, Nov 21, 2010 at 10:03, barney schwartz wrote: New build of WinEdt 6.0 (Build: 20101121) has been uploaded to www.winedt.com This build contains macros that work with the latest ConTeXt Mark IV (previous versions were designed for older version of ConTeXt). If you are upgrading from older version of WinEdt make sure that the executable for ConTeXt in WinEdt's Execution Modes is set context.exe (instead of old texexec.exe)... Just thought I would post this here for other Winedt users. Thanks a lot for this notice (and thanks to Ulrike for debugging). This is indeed very nice to know (it used to be my favourite editor a while ago). I always thought that supporting ConTeXt needs heavy hacking of WinEdt. Mojca (I'm still confused about whether it really doesn't/won't support UTF-8 until version 7 since it is then almost useless for any non-English speaking user for XeTeX and ConTeXt MKIV that are now available in drop-down menu by default.) ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] New Release Winedt WORKS with MKIV!!
New build of WinEdt 6.0 (Build: 20101121) has been uploaded to www.winedt.com This build contains macros that work with the latest ConTeXt Mark IV (previous versions were designed for older version of ConTeXt). If you are upgrading from older version of WinEdt make sure that the executable for ConTeXt in WinEdt's Execution Modes is set context.exe (instead of old texexec.exe)... If you (really!?) want to use old ConTeXt Mark II you will have modify the menu item for ConTeXt to call: ConTeXt_old.edt instead of ConTeXt.edt News.txt gives the details (read it!) In the meantime another build 2010 had been available (but never announced on the list). Since then WinEdt takes care of environment variables MIKTEX_EDITOR and TEXEDIT that define the editor response for e in MiKTeX and TeX Live. You can install the latest build over the old version of WinEdt 6.0 and then read What's new in the Help menu (if you want to take advantage of certain changes such as new items in the Maintenance Menu designed to load customized scripts etc...). Best regards, alex Just thought I would post this here for other Winedt users. barney ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
2007/12/5, Thomas A. Schmitz [EMAIL PROTECTED]: Oops, I was too fast upgrading... luatex fails to produce format files on my system: luatex --version This is LuaTeX, Version snapshot-0.20.0-2007120515 luatools --ini --compile cont-en LuaTools | creating initialization file cont-en LuaTools | using library path : /usr/local/texlive/texmf-local/tex/ context/base LuaTools | using lua libraries: l-string.lua l-table.lua l-boolean.lua l-number.lua l-unicode.lua l-md5.lua l-os.lua l-io.lua l-file.lua l- dir.lua l-utils.lua l-tex.lua luat-lib.lua luat-inp.lua luat-tmp.lua luat-zip.lua luat-tex.lua LuaTools | using compiled initialization file cont-en.luc LuaTools | using lua initialization file cont-en.luc LuaTools | running command: luatex --ini --lua=cont-en.luc /usr/ local/texlive/texmf-local/tex/context/base/cont-en.tex \dump Error in lua file loading: ?:0: attempt to call field '?' (a nil value) LuaTools | LuaTools | runtime: 0.37 seconds Taco, Hans? All best Thomas Hi Thomas, the new release did work for me with LuaTeX but the mkii part give a error message in conbination with XeTeX., only a short error message but it should be also fixed. Line 53 in regi-ini.mkii use in a message for XeTeX \m!regime as messageconstant and not \m!regimes. Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
Wolfgang Schuster wrote: the new release did work for me with LuaTeX but the mkii part give a error message in conbination with XeTeX., only a short error message but it should be also fixed. Line 53 in regi-ini.mkii use in a message for XeTeX \m!regime as messageconstant and not \m!regimes. i will probably post an updated zip later today, i noticed that in base mode kerns got lost (has to do with using an optimized otf table in the cache; i never adapted the base code to 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
That particular line: # Error in lua file loading: ?:0: attempt to call field '?' (a nil value) is often the sign of mismatching luatools and ConTeXt version :-) Arthur ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
Arthur Reutenauer wrote: That particular line: # Error in lua file loading: ?:0: attempt to call field '?' (a nil value) is often the sign of mismatching luatools and ConTeXt version :-) indeed, make sure that luatools --generate is run; many new files ... - 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
On Dec 6, 2007, at 8:26 AM, Arthur Reutenauer wrote: That particular line: # Error in lua file loading: ?:0: attempt to call field '?' (a nil value) is often the sign of mismatching luatools and ConTeXt version :-) Arthur Yes, thanks for your help, now it works wonderfully. On a related note: this big new release had me waiting in anticipation, so would it be possible to just tell us in a sentence or five or six what the big changes are? I guess with the right switches it can cook my dinner, but would be curious to learn a bit more... Thanks Thomas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
Hi Thomas, Thomas A. Schmitz wrote: On Dec 6, 2007, at 8:26 AM, Arthur Reutenauer wrote: That particular line: # Error in lua file loading: ?:0: attempt to call field '?' (a nil value) is often the sign of mismatching luatools and ConTeXt version :-) Arthur Yes, thanks for your help, now it works wonderfully. On a related note: this big new release had me waiting in anticipation, so would it be possible to just tell us in a sentence or five or six what the big changes are? I guess with the right switches it can cook my dinner, but would be curious to learn a bit more... Well, I have two detail pages in the wiki ... but it is pretty hard to come up with a consise list of improvements. Mostly, mkiv is just faster and better than it was already. :-) http://wiki.contextgarden.net/Context_2007.12.05 http://wiki.contextgarden.net/Context_2007.12.06 Best wishes, Taco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] new release
Oops, I was too fast upgrading... luatex fails to produce format files on my system: luatex --version This is LuaTeX, Version snapshot-0.20.0-2007120515 luatools --ini --compile cont-en LuaTools | creating initialization file cont-en LuaTools | using library path : /usr/local/texlive/texmf-local/tex/ context/base LuaTools | using lua libraries: l-string.lua l-table.lua l-boolean.lua l-number.lua l-unicode.lua l-md5.lua l-os.lua l-io.lua l-file.lua l- dir.lua l-utils.lua l-tex.lua luat-lib.lua luat-inp.lua luat-tmp.lua luat-zip.lua luat-tex.lua LuaTools | using compiled initialization file cont-en.luc LuaTools | using lua initialization file cont-en.luc LuaTools | running command: luatex --ini --lua=cont-en.luc /usr/ local/texlive/texmf-local/tex/context/base/cont-en.tex \dump Error in lua file loading: ?:0: attempt to call field '?' (a nil value) LuaTools | LuaTools | runtime: 0.37 seconds Taco, Hans? All best Thomas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] new release
Hans Hagen wrote: texmfstart --verbose --unix --stubpath=yourbinpath --make all That is a cool feature. But it does not set executable bits on the stubs yet, could you fix that? Regards, Christopher ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Christopher Creutzig wrote: Hans Hagen wrote: texmfstart --verbose --unix --stubpath=yourbinpath --make all That is a cool feature. But it does not set executable bits on the stubs yet, could you fix that? if you tell me what magic code is needed ... 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 release
hmm, on Tue, May 16, 2006 at 01:06:26AM +0200, frantisek holop said that
your texmf.cnf file should contain:
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
as long as we have no uniform map file syntax, progs needs to be able to
find their own map files
i just did:
# rm -r /usr/local/share/texmf-local/fonts/map/dvipdfm/context
# rm -r /usr/local/share/texmf-local/fonts/map/dvips/context
# texhash
aren't these files awfully old anyway? are they needed?
as cont-lm is not needed anymore i thought these are obsolete files...
btw. http://live.contextgarden.net/ is suffering from this also:
from the texexec output:
[1.1{/opt/context/current/texmf/fonts/map/dvipdfm/context/original-empty.map}{/
opt/context/current/texmf/fonts/map/dvipdfm/context/original-base.map
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `fmvr8x': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmat11': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmbt11': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xyeuat11': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xyeubt11': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmat12': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xycmbt12': font file missing
Warning: pdfetex (file /opt/context/current/texmf/fonts/map/dvipdfm/context/ori
ginal-base.map): invalid entry for `xyeuat12': font file missing
and pdftex could be updated there also :-)
-f
--
can't have everything. where would you put it?
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
hmm, on Tue, May 09, 2006 at 03:11:23PM +0200, Hans Hagen said that
Warning: pdfetex (file
/usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
invalid entry for `fmvr8x': font file missing
It works if i remove (or rename) the dvipdfm directory.
What can i do to have ruby thing working, and pdftex fonts used instead of
dvipdfm ones?
your texmf.cnf file should contain:
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
as long as we have no uniform map file syntax, progs needs to be able to
find their own map files
i just did:
# rm -r /usr/local/share/texmf-local/fonts/map/dvipdfm/context
# rm -r /usr/local/share/texmf-local/fonts/map/dvips/context
# texhash
aren't these files awfully old anyway? are they needed?
as cont-lm is not needed anymore i thought these are obsolete files...
-f
--
light doesn't emit energy; it emits little dark eaters
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New release and XeTeX - XeConTeXt
Otared KAVIAN wrote:
sudo texexec --make --xtx en
(/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-de.pat
! Bad \patterns.
\unknownchar -{
\hbox {\vrule \!!width .5em\!!height 1ex\!!depth \zeropoint }}
l.114 .ge
s6
?
Same for me. The problem is that in line 113, we have
.ge5rö
in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.
Has anyone encountered this error? Is there a solution?
I only have a nasty hack: In the patterns directory, run (in bash)
for file in *.pat *.hyp
do iconv -f iso-8859-1 -t utf-8 $file $file-u
done
and in mult-sys.tex, change the lines reading
\definefileconstant {patternsextension} {pat}
\definefileconstant {hyphensextension} {hyp}
to
\doifundefinedelse{XeTeXversion}
{\definefileconstant {patternsextension} {pat}
\definefileconstant {hyphensextension} {hyp}}
{\definefileconstant {patternsextension} {pat-u}
\definefileconstant {hyphensextension} {hyp-u}}
There probably is a much better place for this change, but cont-new.tex,
afaik, is not read when generating formats and I don't know where the
code really should go. It mayalso be possible to fix the behaviour by
some regime switchting in the .pat and .hyp files, but I know very
little about those commands and haven't tested it.
Still, XeConTeXt does not work as expected in the current version:
The plain TeX file
\font\myface=Hiragino Mincho Pro W3
\myface
こちらはテストです。日本語のテストです。
\bye
works like a charm, but
\definetypeface[myface][rm][Xserif][Hiragino Mincho Pro W3]
\setupbodyfont[myface,14pt]
\starttext
こちらはテストです。日本語のテストです。
\stoptext
produces an output containing only a lot of accented latin characters,
see attached file.
Best regards,
Christopher
jap.pdf
Description: Adobe PDF document
This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) (format=cont-en
2006.5.9) 13 MAY 2006 22:52
entering extended mode
(/usr/local/teTeX/share/texmf.local/web2c/natural.tcx)
**jap.tex emergencyend
(./jap.tex
ConTeXt ver: 2006.05.08 12:59 fmt: 2006.5.9 int: english mes: english
language: language en is active
protectionstate 0
system : cont-new loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
color : palette rollover is available
)
system : cont-old loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system : cont-fil loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
system : cont-sys.rme loaded
(/usr/local/teTeX/share/texmf.local/tex/context/user/cont-sys.rme
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex))
bodyfont: 12pt rm is loaded
language: patterns en-ec:ec-1-2:3 uk-ec:ec-2-2:3 de-texnansi:tex
nansi-3-2:3 de-ec:ec-4-2:3 fr-texnansi:texnansi-5-2:3 fr-ec:ec-6-2:3
es-ec:ec-7-2:3 pt-texnansi:texnansi-8-2:3 pt-ec:ec-9-2:3 it-texnansi
:texnansi-10-2:3 it-ec:ec-11-2:3 nl-texnansi:texnansi-12-2:3 nl-ec:ec-
13-2:3 cz-il2:il2-14-2:3 cz-ec:ec-15-2:3 sk-il2:il2-16-2:3 sk-ec:ec
-17-2:3 pl-pl0:pl0-18-2:3 pl-ec:ec-19-2:3 pl-qx:qx-20-2:3 loaded
specials: tex,postscript,rokicki loaded
\openout2 = `jap.tui'.
system : jap.top loaded
(./jap.top
specials: loading definition file tpd
(/usr/local/teTeX/share/texmf.local/tex/context/base/spec-tpd.tex
specials: loading definition file fdf
(/usr/local/teTeX/share/texmf.local/tex/context/base/spec-fdf.tex)
specials: fdf loaded
)
specials: fdf,tpd loaded
)
\openout0 = `jap-mpgraph.mp'.
\openout0 = `mpgraph.mp'.
systems : system commands are disabled
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
Re: [NTG-context] New release and XeTeX - XeConTeXt
On 5/13/06, Christopher Creutzig [EMAIL PROTECTED] wrote: Still, XeConTeXt does not work as expected in the current version:Hi Christopher,I tried the file you suggest with the latest version of ConTeXt and generated a new XeConTeXt (ConTeXt ver: 2006.05.11 10:30 fmt: 2006.5.13, on MacOS X 10.4.6) and I didn't have any trouble with the following%% begin japanese.tex\starttext\font\Myface=Hiragino Mincho Pro W3 at 14 pt\Myface こちらはテストです。日本語のテストです。%\bye\blankworks like a charm, and so does the ConTeXt way of defining a typeface:\definetypeface[myface][rm][Xserif][Hiragino Mincho Pro W3]\setupbodyfont[myface,14pt] こちらはテストです。日本語のテストです。\stoptext%% end japanese.texthe japanese text is typeset identically with \Myface (defined with the good old Plain TeX way) and \myface (defined in ConTeXt way).Nevertheless still I encounter other problems with the new version of ConTeXt and I am reporting them in another thread. Best regards: OK ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New release and XeTeX - XeConTeXt
Christopher Creutzig wrote:
(/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-de.pat
! Bad \patterns.
\unknownchar -{
\hbox {\vrule \!!width .5em\!!height 1ex\!!depth
\zeropoint }}
l.114 .ge
s6
?
Same for me. The problem is that in line 113, we have
.ge5rö
in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.
Has anyone encountered this error? Is there a solution?
how old is your context
the latest version uses utf patterns for both pdftex and xetex so no
special tricks are needed
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New release and XeTeX - XeConTeXt
Hans Hagen wrote: Same for me. The problem is that in line 113, we have .ge5rö in Latin-1 encoding, but XeTeX tries reading the file in UTF-8. how old is your context Indeed, that was stone age: 2006.05.08 12:59 - more than five days old. :-) the latest version uses utf patterns for both pdftex and xetex so no special tricks are needed Thanks for the pointer. Strangely enough, I still can't typeset simple Japanese, but right now I don't have the time to investigate this further. Best regards, Christopher ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] New release and XeTeX - XeConTeXt
Christopher Creutzig wrote: Hans Hagen wrote: Same for me. The problem is that in line 113, we have .ge5r� in Latin-1 encoding, but XeTeX tries reading the file in UTF-8. how old is your context Indeed, that was stone age: 2006.05.08 12:59 - more than five days old. :-) for xetex indeed, but if we proceed in the way we do now, we will have reasoable stable xetex support soon 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 release
Johannes Graumann wrote:
Hans Hagen wrote:
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\starttext
\startXMLdata
document/document
\stopXMLdata
\stoptext
You catch my folly as usually. Thanks. While I get the solution above to
work, the alternative 'ruby
~/texmf/scripts/context/ruby/texexec.rb --pdf --environments=PhD-Thesis
../XML/main.xml'
doesn't. Error is:
User file 'cont-sys.tex' not found, 'cont-sys.rme' has been used instead.
has nothing to do with ruby, just copy cont-sys.rme to cont-sys.tex in
tex/context/user; i ship the rme as example and fallback so that it does
not overwrite you rlocal copy
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Johannes Graumann wrote: If you cannot figure it out, try posting a few extra lines from the log, just before 'cont-err loaded'. I append the log region around the 'cont-err loaded' part. It looks to me like context found a cont-err.tex when it should not have. At the end of a job, ConTeXt looks for a file named cont-err.tex, in the directory path that is set by the \setupsystem command in jobname.tmp. This file itself is generated by texexec, and the directory value is based on setuppath). In your case, it looks like this directory entry is either incorrect, or there is a bug in context, because it finds and then loads the file while XML mode is still active. I do not know how to proceed from here. Hans? Cheers, taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Am Donnerstag, 11. Mai 2006 00:21 schrieb Hans Hagen: (concerning the path ... what is the path separator on osx?) The normal unix path separator '/'. On OS9 it was ':'. Uwe ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
nico wrote:
On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz
[EMAIL PROTECTED] wrote:
Yes, that's strange. I just checked, and everything is golden on a linux
system (gentoo, but I gues the same is true for other linux distros). So
I really don't see why OS X should behave differently. Is there any
debugging info that I could provide? How 'bout the other OS X users (I
seem to recall there were quite a few of them): do you get the same
error?
Strictly speaking it's not OSX, but i've a FreeBSD distro, which is close,
and it works fine.
Are you sure you have the permission to write in any of these paths?
BTW, i find dangerous to do (kpse.formatpath method):
# locate writable path
if ! formatpath.empty? then
formatpath.split_path.each do |fp|
fp.gsub!(/\\/,'/')
# remove funny patterns
fp.sub!(/^!!/,'')
fp.sub!(/\/+$/,'')
fp.sub!(/unsetengine/,if enginepath then engine
else '' end)
if ! fp.empty? (fp != '.') then
# strip (possible engine) and test for
writeability
fpp = fp.sub(/#{engine}\/*$/,'')
if FileTest.directory?(fpp)
FileTest.writable?(fpp) then
# use this path
formatpath = fp.dup
break
end
end
end
end
# needed !
begin File.makedirs(formatpath) ; rescue ; end ;
If none of the paths from formatpath is valid, we keep the whole concat
path in this variable... that then is used to create a directory tree.
Thomas, maybe that you have ugly directories created starting with an
hidden directory named .:. You should check that.
i can make the fallback '.' in that case, not that it helps much
if ! formatpath.empty? then
done = false
formatpath.split_path.each do |fp|
fp.gsub!(/\\/,'/')
# remove funny patterns
fp.sub!(/^!!/,'')
fp.sub!(/\/+$/,'')
fp.sub!(/unsetengine/,if enginepath then engine
else '' end)
if ! fp.empty? (fp != '.') then
# strip (possible engine) and test for
writeability
fpp = fp.sub(/#{engine}\/*$/,'')
if FileTest.directory?(fpp)
FileTest.writable?(fpp) then
# use this path
formatpath, done = fp.dup, true
break
end
end
end
formatpath = '.' unless done
end
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 release
Thomas A. Schmitz wrote: On May 11, 2006, at 12:21 AM, Hans Hagen wrote: i'm uploading a coupls of zips with fixes for xetex but i'm not sure if they solve your problem (concerning the path ... what is the path separator on osx?) Hans Nope, still get the same bizarre result. Path separator is a : btw, concerning the texmfstart script itself: - on unix it's indeed best to make a symlink from texmfstart - texmfstart.rb in the whatever-tree it resides in - on windows, one can associate the .rb suffix with ruby and add the context ruby path to the bin path, or use the 'exe' variant which can be located anywhere (texmfstart uses a few libe but when they are not found, it will enter stupid-mode and lack some features that probably go unnoticed) 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 release
Taco Hoekwater wrote:
Johannes Graumann wrote:
If you cannot figure it out, try posting a few extra
lines from the log, just before 'cont-err loaded'.
I append the log region around the 'cont-err loaded' part.
It looks to me like context found a cont-err.tex when it
should not have.
At the end of a job, ConTeXt looks for a file named cont-err.tex,
in the directory path that is set by the \setupsystem command in
jobname.tmp. This file itself is generated by texexec, and the
directory value is based on setuppath).
In your case, it looks like this directory entry is either
incorrect, or there is a bug in context, because it finds and
then loads the file while XML mode is still active.
I do not know how to proceed from here. Hans?
in core-sys.tex, replace:
\ifx\disableXML\undefined \let\disableXML\relax \fi
\def\loadsystemfiles
{\reportprotectionstate
\readsysfile\f!newfilename
{\showmessage\m!systems2\f!newfilename}%
\donothing
\readsysfile\f!oldfilename
{\showmessage\m!systems2\f!oldfilename}%
\donothing
\loadallsystemfiles\f!filfilename
\donothing
\loadallsystemfiles\f!sysfilename
{\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
\doglobal\appendtoks
\bgroup
\disableXML
\loadallsystemfiles\f!errfilename\donothing
\egroup
\to\everygoodbye}}
and let me know if that works ok
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 release
On May 11, 2006, at 12:21 AM, Hans Hagen wrote: i'm uploading a coupls of zips with fixes for xetex but i'm not sure if they solve your problem (concerning the path ... what is the path separator on osx?) Hans Nope, still get the same bizarre result. Path separator is a : echo $PATH /sw/bin:/sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/tas/bin:/usr/ local/bin:/usr/lib/portage/bin:/usr/local/teTeX/bin/powerpc-apple- darwin-current:/Developer/Tools:/usr/X11R6/bin So maybe Gerben's guess is right, and it's some hard-coded path thing in kpsefast? texmfstart texexec --make --all TeXExec | using search method 'kpsefast' TeXExec | updating file database mktexlsr: Updating /usr/local/teTeX/share/texmf/ls-R... mktexlsr: Updating /usr/local/teTeX/share/texmf.gwtex/ls-R... mktexlsr: Updating /usr/local/teTeX/share/texmf.local/ls-R... mktexlsr: Updating /usr/local/teTeX/share/texmf.tetex/ls-R... mktexlsr: Updating /var/tmp/texfonts/ls-R... mktexlsr: Done. TeXExec | using tex engine pdfetex TeXExec | using tex format path .:/Users/tas/texmf/web2c//:!!/usr/ local/teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/ share//share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/ web2c//pdfetex As you can see: while mltexlsr find the corret paths for updating, the format path given by TeXExec uses default values. Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release (Modified by Gerben Wierda)
btw, doesn't gwtex set the TEXMFCNF env variable? It does not get a useful value. TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is ignored for obvious reasons. The compiled-in version shows my compile environment which differs from the install environment on people's system. Try kpsewhich -expand-var=\$TEXMFCNF in a Terminal window. I had to do this if I wanted to make my TeX install relocatable and I had to make it relocatable to enable the option that people who do not have sysadmin privileges can install the TeX i-Package in their home directory and still work with it. In short: everything in TeX is relocatable at run time except the location of texmf.cnf. G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release (Modified by Gerben Wierda)
Gerben Wierda wrote: btw, doesn't gwtex set the TEXMFCNF env variable? It does not get a useful value. TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is ignored for obvious reasons. The compiled-in version shows my compile environment which differs from the install environment on people's system. Try kpsewhich -expand-var=\$TEXMFCNF in a Terminal window. I had to do this if I wanted to make my TeX install relocatable and I had to make it relocatable to enable the option that people who do not have sysadmin privileges can install the TeX i-Package in their home directory and still work with it. In short: everything in TeX is relocatable at run time except the location of texmf.cnf. but how then does it locate texmf.cnf, relative to the bin path of kpsewhich? 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 release
Hans Hagen wrote:
in core-sys.tex, replace:
\ifx\disableXML\undefined \let\disableXML\relax \fi
\def\loadsystemfiles
{\reportprotectionstate
\readsysfile\f!newfilename
{\showmessage\m!systems2\f!newfilename}%
\donothing
\readsysfile\f!oldfilename
{\showmessage\m!systems2\f!oldfilename}%
\donothing
\loadallsystemfiles\f!filfilename
\donothing
\loadallsystemfiles\f!sysfilename
{\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
\doglobal\appendtoks
\bgroup
\disableXML
\loadallsystemfiles\f!errfilename\donothing
\egroup
\to\everygoodbye}}
I have appended this to core-sys.tex (just before the final '\protect
\endinput'; latest version of 11.5.) and used 'texexec.rb --make'.
I get the same error - even for a document containing nothing but this:
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\startXMLdata
document/document
\stopXMLdata
How do we proceed from here?
Joh
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Johannes Graumann wrote:
Hans Hagen wrote:
in core-sys.tex, replace:
\ifx\disableXML\undefined \let\disableXML\relax \fi
\def\loadsystemfiles
{\reportprotectionstate
\readsysfile\f!newfilename
{\showmessage\m!systems2\f!newfilename}%
\donothing
\readsysfile\f!oldfilename
{\showmessage\m!systems2\f!oldfilename}%
\donothing
\loadallsystemfiles\f!filfilename
\donothing
\loadallsystemfiles\f!sysfilename
{\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
\doglobal\appendtoks
\bgroup
\disableXML
\loadallsystemfiles\f!errfilename\donothing
\egroup
\to\everygoodbye}}
I have appended this to core-sys.tex (just before the final '\protect
\endinput'; latest version of 11.5.) and used 'texexec.rb --make'.
I get the same error - even for a document containing nothing but this:
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\startXMLdata
document/document
\stopXMLdata
How do we proceed from here?
a minimal test file showing the problem; as taco said, maybe some
interference with xml processing
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 release
Johannes Graumann wrote:
Hans Hagen wrote:
in core-sys.tex, replace:
\ifx\disableXML\undefined \let\disableXML\relax \fi
\def\loadsystemfiles
{\reportprotectionstate
\readsysfile\f!newfilename
{\showmessage\m!systems2\f!newfilename}%
\donothing
\readsysfile\f!oldfilename
{\showmessage\m!systems2\f!oldfilename}%
\donothing
\loadallsystemfiles\f!filfilename
\donothing
\loadallsystemfiles\f!sysfilename
{\loadallsystemfiles{\f!sysfilename.rme}\donothing % new, fall back
\doglobal\appendtoks
\bgroup
\disableXML
\loadallsystemfiles\f!errfilename\donothing
\egroup
\to\everygoodbye}}
I have appended this to core-sys.tex (just before the final '\protect
\endinput'; latest version of 11.5.) and used 'texexec.rb --make'.
I get the same error - even for a document containing nothing but this:
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\startXMLdata
document/document
\stopXMLdata
How do we proceed from here?
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\starttext
\startXMLdata
document/document
\stopXMLdata
\stoptext
does that work ok? in your example, you stay inside a group and then end the
doc
\starttext
\processXMLfilegrouped{somedoc}
\stoptext
is ok, as is
texexec somedoc.xml
which wraps the xml processing in a run file
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 release (Modified by Gerben Wierda)
On May 11, 2006, at 17:16, Hans Hagen wrote: Gerben Wierda wrote: btw, doesn't gwtex set the TEXMFCNF env variable? It does not get a useful value. TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is ignored for obvious reasons. The compiled-in version shows my compile environment which differs from the install environment on people's system. Try kpsewhich -expand-var=\$TEXMFCNF in a Terminal window. I had to do this if I wanted to make my TeX install relocatable and I had to make it relocatable to enable the option that people who do not have sysadmin privileges can install the TeX i-Package in their home directory and still work with it. In short: everything in TeX is relocatable at run time except the location of texmf.cnf. but how then does it locate texmf.cnf, relative to the bin path of kpsewhich? The first texmnf.cnf it tries is indeed located that way: ../../texmf.cnf This is the only reason my precompiled TeX distro is relocatable. G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Hans Hagen wrote:
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\starttext
\startXMLdata
document/document
\stopXMLdata
\stoptext
You catch my folly as usually. Thanks. While I get the solution above to
work, the alternative 'ruby
~/texmf/scripts/context/ruby/texexec.rb --pdf --environments=PhD-Thesis
../XML/main.xml'
doesn't. Error is:
User file 'cont-sys.tex' not found, 'cont-sys.rme' has been used instead.
Hints?
Joh
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Not sure what settings you need, but I think I know that you take the
cont-sys.rme and rename it to cont-sys.tex and go from there.
On May 11, 2006, at 5:46 PM, Johannes Graumann wrote:
Hans Hagen wrote:
\defineXMLenvironment
[document]
{\starttext}
{\stoptext}
\starttext
\startXMLdata
document/document
\stopXMLdata
\stoptext
You catch my folly as usually. Thanks. While I get the solution
above to
work, the alternative 'ruby
~/texmf/scripts/context/ruby/texexec.rb --pdf --environments=PhD-
Thesis ../XML/main.xml'
doesn't. Error is:
User file 'cont-sys.tex' not found, 'cont-sys.rme' has been used
instead.
Hints?
Joh
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Johannes Graumann wrote: Trouble with tex/context/base/cont-err.tex: system : cont-err loaded (/home/balin/texmf/tex/context/base/cont-err.tex Runaway argument? on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC. ! Paragraph ended before was complete. to be read again \par l.13 Can't find anything wrong though ... just to be sure, i use version 2006.05.09 23:03 i looks like you're ignoring comments how does the tex file look that you process? 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 release
Johannes Graumann wrote: Trouble with tex/context/base/cont-err.tex: system : cont-err loaded (/home/balin/texmf/tex/context/base/cont-err.tex Runaway argument? on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC. ! Paragraph ended before was complete. to be read again \par l.13 Can't find anything wrong though ... This is the very top of cont-err.tex, the 'module header'. If that does not look broken, then probably the file that loads it does so while some really strange catcode settings are in effect. The most likely cause is that you have an invalid zip file or an error has occured during extraction. If you cannot figure it out, try posting a few extra lines from the log, just before 'cont-err loaded'. Cheers, taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Hans, do I need to re-report that format generation with texmfstart newtexexec --make is still broken on OS X (I'll check on my linux box later)? I still get these monstrous paths like TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// pdfetex Best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Hans, This ruby stuff has me confused to no end. I'm compiling this document (which compiled just fine with the last release - no changes since) with the following command: ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex For trying to figure out the version I do: ruby ~/texmf/scripts/context/ruby/texexec.rb --check And get TeXExec | current distribution: web2c TeXExec | context source date: unknown TeXExec | format path: TeXExec | start of analysis /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart texexec --help /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart texutil --help /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart ctxtools --help TeXExec | end of analysis TeXExec | TeXExec | TeXExec | TeXExec | Which is mostly related to the UNIX stubs not working no? How do I now actually figure out what I'm running and whether it all got rebuild correctly? Thanks, Joh Hans Hagen wrote: Johannes Graumann wrote: Trouble with tex/context/base/cont-err.tex: system : cont-err loaded (/home/balin/texmf/tex/context/base/cont-err.tex Runaway argument? on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC. ! Paragraph ended before was complete. to be read again \par l.13 Can't find anything wrong though ... just to be sure, i use version 2006.05.09 23:03 i looks like you're ignoring comments how does the tex file look that you process? 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 release
Johannes Graumann wrote: Hans, This ruby stuff has me confused to no end. I'm compiling this document (which compiled just fine with the last release - no changes since) with the following command: ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex For trying to figure out the version I do: ruby ~/texmf/scripts/context/ruby/texexec.rb --check And get TeXExec | current distribution: web2c TeXExec | context source date: unknown TeXExec | format path: TeXExec | start of analysis /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart texexec --help /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart texutil --help /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart ctxtools --help TeXExec | end of analysis TeXExec | TeXExec | TeXExec | TeXExec | Which is mostly related to the UNIX stubs not working no? cp texmfstart.rb samepathaspdftex/texmfstart chmod 755 samepathaspdftex/texmfstart How do I now actually figure out what I'm running and whether it all got rebuild correctly? so, no stub for texmfstart, just a copy (althoughj you may want to call it indirectly 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 release
Thomas A. Schmitz wrote: Hans, do I need to re-report that format generation with texmfstart newtexexec --make is still broken on OS X (I'll check on my linux box later)? I still get these monstrous paths like TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// pdfetex strange, since i suppose that linux and osx behave the same (don't call it newtexexec any more) 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 release
Thomas A. Schmitz wrote: Hans, do I need to re-report that format generation with texmfstart newtexexec --make is still broken on OS X (I'll check on my linux box later)? I still get these monstrous paths like TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// pdfetex btw, i cannot test the mac here since the machine is broken (does not start up and i already wasted half a day on it) 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 release
Yes, that's strange. I just checked, and everything is golden on a linux system (gentoo, but I gues the same is true for other linux distros). So I really don't see why OS X should behave differently. Is there any debugging info that I could provide? How 'bout the other OS X users (I seem to recall there were quite a few of them): do you get the same error? Best Thomas On Wed, 2006-05-10 at 19:10 +0200, Hans Hagen wrote: strange, since i suppose that linux and osx behave the same (don't call it newtexexec any more) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Thomas A. Schmitz wrote: Yes, that's strange. I just checked, and everything is golden on a linux system (gentoo, but I gues the same is true for other linux distros). So I really don't see why OS X should behave differently. Is there any debugging info that I could provide? How 'bout the other OS X users (I seem to recall there were quite a few of them): do you get the same error? i'm uploading a coupls of zips with fixes for xetex but i'm not sure if they solve your problem (concerning the path ... what is the path separator on osx?) 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 release
Hans, I linked texmfstart.rb to texmfstart in my local bin directory (which is in the path) and issued 'chmod -R +x ~/texmf/scripts'. If I call 'ruby ~/texmf/scripts/context/ruby/texexec.rb --check' now, I get this error free (but not informative) output: TeXExec | current distribution: web2c TeXExec | context source date: unknown TeXExec | format path: TeXExec | start of analysis TeXExec | end of analysis TeXExec | TeXExec | TeXExec | TeXExec | Any ideas what I might be doing wrong? Joh Hans Hagen wrote: Johannes Graumann wrote: Hans, This ruby stuff has me confused to no end. I'm compiling this document (which compiled just fine with the last release - no changes since) with the following command: ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex For trying to figure out the version I do: ruby ~/texmf/scripts/context/ruby/texexec.rb --check And get TeXExec | current distribution: web2c TeXExec | context source date: unknown TeXExec | format path: TeXExec | start of analysis /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart texexec --help /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart texutil --help /home/balin/texmf/scripts/context/ruby/base/kpsefast.rb:659: command not found: texmfstart ctxtools --help TeXExec | end of analysis TeXExec | TeXExec | TeXExec | TeXExec | Which is mostly related to the UNIX stubs not working no? cp texmfstart.rb samepathaspdftex/texmfstart chmod 755 samepathaspdftex/texmfstart How do I now actually figure out what I'm running and whether it all got rebuild correctly? so, no stub for texmfstart, just a copy (althoughj you may want to call it indirectly 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 release
On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz
[EMAIL PROTECTED] wrote:
Yes, that's strange. I just checked, and everything is golden on a linux
system (gentoo, but I gues the same is true for other linux distros). So
I really don't see why OS X should behave differently. Is there any
debugging info that I could provide? How 'bout the other OS X users (I
seem to recall there were quite a few of them): do you get the same
error?
Strictly speaking it's not OSX, but i've a FreeBSD distro, which is close,
and it works fine.
Are you sure you have the permission to write in any of these paths?
BTW, i find dangerous to do (kpse.formatpath method):
# locate writable path
if ! formatpath.empty? then
formatpath.split_path.each do |fp|
fp.gsub!(/\\/,'/')
# remove funny patterns
fp.sub!(/^!!/,'')
fp.sub!(/\/+$/,'')
fp.sub!(/unsetengine/,if enginepath then engine
else '' end)
if ! fp.empty? (fp != '.') then
# strip (possible engine) and test for
writeability
fpp = fp.sub(/#{engine}\/*$/,'')
if FileTest.directory?(fpp)
FileTest.writable?(fpp) then
# use this path
formatpath = fp.dup
break
end
end
end
end
# needed !
begin File.makedirs(formatpath) ; rescue ; end ;
If none of the paths from formatpath is valid, we keep the whole concat
path in this variable... that then is used to create a directory tree.
Thomas, maybe that you have ugly directories created starting with an
hidden directory named .:. You should check that.
Regards,
BG
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Taco Hoekwater wrote:
This is the very top of cont-err.tex, the 'module header'.
If that does not look broken,
then probably the file that
loads it does so while some really strange catcode settings
are in effect. The most likely cause is that you have an
invalid zip file or an error has occured during extraction.
I went back and looked at the file - nothing obvious. I repeated my install
from the pragma server ... no changes.
The document in question compiled just fine before the update.
If you cannot figure it out, try posting a few extra
lines from the log, just before 'cont-err loaded'.
I append the log region around the 'cont-err loaded' part.
Thanks for any help, Joh
chapter : - About this Document
publications: warning: cite argument knuth:86 is unknown on 80
publications: warning: cite argument hagen:01 is unknown on 80
publications: warning: cite argument lamport:94 is unknown on 80
publications: warning: cite argument thanh:98 is unknown on 80
publications: warning: cite argument knuth:84 is unknown on 80
publications: warning: cite argument adobe:04 is unknown on 80
Overfull \hbox (4.7209pt too wide) in paragraph at lines 4--4
[]\*modern12ptrmtf*: This doc-u-ment was type-set in Com-puter Mod-ern
(Xxx
xxx, ), us-ing ConT[]Xt
\hbox(8.82599+3.0)x438.77812, glue set - 1.0
\kern-0.432 (left margin)
\hbox(0.0+0.0)x0.0
\*modern12ptrmtf*: T
\*modern12ptrmtf*: h
\*modern12ptrmtf*: i
etc.
publications: warning: cite argument graumann:04 is unknown on 80
publications: warning: cite argument yergeau:04 is unknown on 80
section : - References
)
structure : end of sectionblock backmatter
[175.162]
systems : end file PhD-Thesis at line 77
system : cont-err loaded
(/home/balin/texmf/tex/context/base/cont-err.tex
Runaway argument?
on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
! Paragraph ended before was complete.
to be read again
\par
l.13
? s
OK, entering \scrollmode...
Overfull \hbox (42.98929pt too wide) in paragraph at lines 1--13
\*modern12ptrmtf*: Sys-tem Files, %D sub-ti-tle=Just A warn-ing, %D
au-thor=Han
s Ha-gen, %D date=\currentdate,
\hbox(8.82599+3.0)x438.77812, glue set - 1.0
\*modern12ptrmtf*: S
\*modern12ptrmtf*: y
\*modern12ptrmtf*: s
\discretionary
.\*modern12ptrmtf*: -
\*modern12ptrmtf*: t
etc.
)
Runaway argument?
} \writeline \par \endinput
! File ended while scanning use of \xparseXMLelement.
inserted text
\par
to be read again
\relax
\dodoreadfile ...\preprocesssuffix \or \fi \relax
\the \everyafterreadfile
\loadallsystemfiles ...ssage \m!systems 2{#1}}{#2}
\else \def
\doloadsystemfi...
\finalend ...se \the \everybye \the \everygoodbye
\global \everybye
\emptyto...
l.77 /document
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release (Modified by Gerben Wierda)
On May 10, 2006, at 19:13, Hans Hagen wrote: Thomas A. Schmitz wrote: Hans, do I need to re-report that format generation with texmfstart newtexexec --make is still broken on OS X (I'll check on my linux box later)? I still get these monstrous paths like TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/ teTeX/share//share/texmf-local/web2c//:!!/usr/local/teTeX/share// share/texmf/web2c//:!!/usr/local/teTeX/share//share/texmf-dist/web2c// pdfetex btw, i cannot test the mac here since the machine is broken (does not start up and i already wasted half a day on it) It seems like not the real paths are taken but only the main path and texmf-local, texmf-dist and such are hard coded subdirectories. This is one reason why I do not use the standard directories (like texmf-local and texmf-dist, but texmf.local, texmf.gwtex, texmf.tetex), to catch path `hard coding' errors as soon as possible. Another possibility (also a type of hard coding error) is parsing the wrong texmf.cnf file yourself instead of asking for the right paths by using kpsewhich. G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote: Hi, Today i'll upload a new release. Got big problems with the fonts that are no more found when using the ruby stuff. Since the unix stubs are crappy, I do this: ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb texexec.rb --pdf typefile.tex What's wrong? Here is the log: This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=cont-en 2006.5.8) 8 MAY 2006 19:55 entering extended mode (/usr/local/share/texmf-local/web2c/natural.tcx) **typefile.tex emergencyend (./typefile.tex ConTeXt ver: 2006.05.08 12:59 fmt: 2006.5.8 int: english mes: english language: language en is active protectionstate 0 system : cont-new loaded (/usr/local/share/texmf-local/tex/context/base/cont-new.tex systems : beware: some patches loaded from cont-new.tex color : palette rollover is available ) system : cont-old loaded (/usr/local/share/texmf-local/tex/context/base/cont-old.tex loading : Context Old Macros ) system : cont-fil loaded (/usr/local/share/texmf-local/tex/context/base/cont-fil.tex loading : Context File Synonyms ) system : cont-sys loaded (/usr/local/share/texmf-dist/tex/context/user/cont-sys.tex (/usr/local/share/texmf-local/tex/context/base/type-exa.tex) (/usr/local/share/texmf-local/tex/context/base/type-syn.tex) (/usr/local/share/texmf-local/tex/context/base/type-enc.tex) (/usr/local/share/texmf-local/tex/context/base/type-siz.tex) (/usr/local/share/texmf-local/tex/context/base/type-map.tex) (/usr/local/share/texmf-local/tex/context/base/type-spe.tex) (/usr/local/share/texmf-local/tex/context/base/type-akb.tex)) bodyfont: 12pt rm is loaded language: patterns nl-texnansi:texnansi-1-2:3 nl-ec:ec-2-2:3 fr- texnansi:texnansi-3-2:3 fr-ec:ec-4-2:3 de-texnansi:texnansi-5-2:3 de-e c:ec-6-2:3 it-texnansi:texnansi-7-2:3 it-ec:ec-8-2:3 pt-texnansi:texna nsi-9-2:3 pt-ec:ec-10-2:3 hr-ec:ec-11-2:3 pl-pl0:pl0-12-2:3 pl-ec:e c-13-2:3 pl-qx:qx-14-2:3 cz-il2:il2-15-2:3 cz-ec:ec-16-2:3 sk-il2:i l2-17-2:3 sk-ec:ec-18-2:3 sl-ec:ec-19-2:3 en-ec:ec-21-2:3 uk-ec:ec- 22-2:3 us-ec:ec-23-2:3 agr-agr:agr-24-2:3 da-ec:ec-25-2:3 sv-ec:ec- 26-2:3 af-ec:ec-27-2:3 no-ec:ec-28-2:3 deo-ec:ec-29-2:3 es-ec:ec-3 0-2:3 ca-ec:ec-31-2:3 la-ec:ec-32-2:3 ro-ec:ec-33-2:3 tr-ec:ec-34- 2:3 fi-ec:ec-36-2:3 hu-ec:ec-37-2:3 loaded specials: tex,postscript,rokicki loaded \openout2 = `typefile.tui'. system : typefile.top loaded (./typefile.top specials: loading definition file tpd (/usr/local/share/texmf-local/tex/context/base/spec-tpd.tex specials: loading definition file fdf (/usr/local/share/texmf-local/tex/context/base/spec-fdf.tex) specials: fdf loaded ) specials: fdf,tpd loaded ) \openout0 = `typefile-mpgraph.mp'. \openout0 = `mpgraph.mp'. (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) (./typefile.tuo) systems : begin file typefile at line 146 (/usr/local/share/texmf-local/tex/context/base/pdfr-ec.tex) verbatim: file ./test-001.tex does not exist verbatim: file joke does not exist fonts : resetting map file list fonts : using map file: original-base fonts : using map file: ec-public-lm fonts : using map file: ec-base fonts : using map file: 8r-base fonts : using map file: t5-base fonts : using map file: original-ams-base fonts : using map file: original-ams-euler fonts : using map file: original-public-lm [1.1 Warning: pdfetex (file original-empty.map): cannot open font map file Warning: pdfetex (file original-base.map): cannot open font map file Warning: pdfetex (file ec-public-lm.map): cannot open font map file Warning: pdfetex (file ec-base.map): cannot open font map file Warning: pdfetex (file 8r-base.map): cannot open font map file Warning: pdfetex (file t5-base.map): cannot open font map file Warning: pdfetex (file original-ams-base.map): cannot open font map file Warning: pdfetex (file original-ams-euler.map): cannot open font map file Warning: pdfetex (file original-public-lm.map): cannot open font map file ] [2.2] systems : end file typefile at line 167 ) Here is how much of TeX's memory you used: 1168 strings out of 58787 21094 string characters out of 563686 4585586 words of memory out of 5529308 39652 multiletter control sequences out of 1+10 75349 words of font info for 38 fonts, out of 50 for 2000 232 hyphenation exceptions out of 1000 47i,18n,54p,252b,773s stack positions out of 1500i,500n,5000p,20b,5000s PDF statistics: 10 PDF objects out of 30 0 named destinations out of 131072 5 words of extra memory for PDF output out of 65536
Re: [NTG-context] new release
nico wrote: On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote: Got big problems with the fonts that are no more found when using the ruby stuff. Since the unix stubs are crappy, I do this: ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb texexec.rb --pdf typefile.tex this should be ok in this mornings version What's wrong? maybe you need to run 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On May 8, 2006, at 1:04 PM, Hans Hagen wrote: Hi, Today i'll upload a new release. Highlights: Hans, another (big) problem with the new release. Unfortunately, I can't really say what breaks, but when I compile a file under the new release, I get hundreds of overfull boxes. I get hyphenation, but TeX doesn't seem to find the same break points as before. The same file compiles wonderfully with version 2006.04.27. Can I send a logfile or something? Hope this message makes it to the list... Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen [EMAIL PROTECTED] wrote: nico wrote: On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote: Got big problems with the fonts that are no more found when using the ruby stuff. Since the unix stubs are crappy, I do this: ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb texexec.rb --pdf typefile.tex this should be ok in this mornings version Seems that the unix texmfstart stub is missing. What's wrong? maybe you need to run mktexlsr Doesn't help, and the required map files are here for a while (eg: kpsewhich ec-base.map gives /usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map). I tried to use the perl version, and now it tries to find stuff in dvipdfm fonts, which plants: Warning: pdfetex (file /usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map): invalid entry for `fmvr8x': font file missing It works if i remove (or rename) the dvipdfm directory. What can i do to have ruby thing working, and pdftex fonts used instead of dvipdfm ones? Regards, BG ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Thomas A.Schmitz wrote: On May 8, 2006, at 1:04 PM, Hans Hagen wrote: Hi, Today i'll upload a new release. Highlights: Hans, another (big) problem with the new release. Unfortunately, I can't really say what breaks, but when I compile a file under the new release, I get hundreds of overfull boxes. I get hyphenation, but TeX doesn't seem to find the same break points as before. The same file compiles wonderfully with version 2006.04.27. Can I send a logfile or something? Hope this message makes it to the list... can you send some example hyphenatable words? 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 release
Thomas A.Schmitz wrote: On May 8, 2006, at 1:04 PM, Hans Hagen wrote: Hi, Today i'll upload a new release. Highlights: Hans, another (big) problem with the new release. Unfortunately, I can't really say what breaks, but when I compile a file under the new release, I get hundreds of overfull boxes. I get hyphenation, but TeX doesn't seem to find the same break points as before. The same file compiles wonderfully with version 2006.04.27. Can I send a logfile or something? Hope this message makes it to the list... btw, there was a problem with the german patterns for a while; let me check it 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 release
nico wrote:
On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
Got big problems with the fonts that are no more found when using the
ruby
stuff. Since the unix stubs are crappy, I do this:
ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb
texexec.rb --pdf typefile.tex
this should be ok in this mornings version
Seems that the unix texmfstart stub is missing.
indeed; the fastest method is:
cp texmfstart.rb .../bin/texmfstart
or make a stub that directly points to your copy of texmfstart
What's wrong?
maybe you need to run mktexlsr
Doesn't help, and the required map files are here for a while (eg:
kpsewhich ec-base.map gives
/usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
I tried to use the perl version, and now it tries to find stuff in dvipdfm
fonts, which plants:
Warning: pdfetex (file
/usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
invalid entry for `fmvr8x': font file missing
It works if i remove (or rename) the dvipdfm directory.
What can i do to have ruby thing working, and pdftex fonts used instead of
dvipdfm ones?
your texmf.cnf file should contain:
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
as long as we have no uniform map file syntax, progs needs to be able to
find their own map files
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 release
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote: Hi, Today i'll upload a new release. Highlights: - some fixes/extensions discussed the last few weeks What about fixing this one (http://archive.contextgarden.net/message/20060430.190029.2f68d437.en.html)? Regards, BG ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
On Tue, 09 May 2006 11:09:43 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
On Mon, 08 May 2006 13:04:58 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
Got big problems with the fonts that are no more found when using the
ruby
stuff. Since the unix stubs are crappy, I do this:
ruby /usr/local/share/texmf-local/scripts/context/ruby/texmfstart.rb
texexec.rb --pdf typefile.tex
What's wrong?
maybe you need to run mktexlsr
Doesn't help, and the required map files are here for a while (eg:
kpsewhich ec-base.map gives
/usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
I tried to use the perl version, and now it tries to find stuff in
dvipdfm
fonts, which plants:
Warning: pdfetex (file
/usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
invalid entry for `fmvr8x': font file missing
It works if i remove (or rename) the dvipdfm directory.
What can i do to have ruby thing working, and pdftex fonts used instead
of
dvipdfm ones?
your texmf.cnf file should contain:
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
as long as we have no uniform map file syntax, progs needs to be able to
find their own map files
Ok, thanks, modifying texmf.cnf as you say fixes the path precedence. Now,
is there a ruby debug mode to see why the paths are lost with texexec.rb?
Or tests I could do to find out what happens?
Regards,
BG
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
What's wrong?
maybe you need to run mktexlsr
Doesn't help, and the required map files are here for a while (eg:
kpsewhich ec-base.map gives
/usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
I tried to use the perl version, and now it tries to find stuff in
dvipdfm
fonts, which plants:
Warning: pdfetex (file
/usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
invalid entry for `fmvr8x': font file missing
It works if i remove (or rename) the dvipdfm directory.
What can i do to have ruby thing working, and pdftex fonts used instead
of
dvipdfm ones?
your texmf.cnf file should contain:
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
For the ruby issue:
if I remove the TEXFONTMAPS environment setting from tex.rb, it works on
my machine. I don't know if it can be a fix working on any platform:
def fixbackendvars(backend)
if backend then
report(fixing backend map path for #{backend}) if
getvariable('verbose')
ENV['backend'] = backend ;
ENV['progname']= backend unless validtexengine(backend)
#ENV['TEXFONTMAPS'] =
.;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//
else
report(unable to fix backend map path) if
getvariable('verbose')
end
end
Regards,
BG
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
nico wrote: Ok, thanks, modifying texmf.cnf as you say fixes the path precedence. Now, is there a ruby debug mode to see why the paths are lost with texexec.rb? Or tests I could do to find out what happens? --verbose gives some info 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 release
nico wrote:
On Tue, 09 May 2006 15:11:23 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
What's wrong?
maybe you need to run mktexlsr
Doesn't help, and the required map files are here for a while (eg:
kpsewhich ec-base.map gives
/usr/local/share/texmf-local/fonts/map/pdftex/context/ec-base.map).
I tried to use the perl version, and now it tries to find stuff in
dvipdfm
fonts, which plants:
Warning: pdfetex (file
/usr/local/share/texmf-local/fonts/map/dvipdfm/context/original-base.map):
invalid entry for `fmvr8x': font file missing
It works if i remove (or rename) the dvipdfm directory.
What can i do to have ruby thing working, and pdftex fonts used instead
of
dvipdfm ones?
your texmf.cnf file should contain:
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//
For the ruby issue:
if I remove the TEXFONTMAPS environment setting from tex.rb, it works on
my machine. I don't know if it can be a fix working on any platform:
def fixbackendvars(backend)
if backend then
report(fixing backend map path for #{backend}) if
getvariable('verbose')
ENV['backend'] = backend ;
ENV['progname']= backend unless validtexengine(backend)
#ENV['TEXFONTMAPS'] =
.;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//
else
report(unable to fix backend map path) if
getvariable('verbose')
end
end
i wonder why this does not work
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 release
On Tue, 09 May 2006 17:16:38 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
#ENV['TEXFONTMAPS'] =
.;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//
i wonder why this does not work
Unix likes column separator (and often cannot stand windows one ;-). If i
change ';' into ':' it works. BTW, why is this set? Isn't it up to
texmf.cnf to configure this (like for texexec.pl)?
Regards,
BG
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
nico wrote:
On Tue, 09 May 2006 17:16:38 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
#ENV['TEXFONTMAPS'] =
.;\$TEXMF/fonts/map/{#{backend},pdftex,dvips,}//
i wonder why this does not work
Unix likes column separator (and often cannot stand windows one ;-). If i
change ';' into ':' it works. BTW, why is this set? Isn't it up to
texmf.cnf to configure this (like for texexec.pl)?
as usual, it takes a while before such changes end up in the mainstream
distributions
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 release
Trouble with tex/context/base/cont-err.tex: system : cont-err loaded (/home/balin/texmf/tex/context/base/cont-err.tex Runaway argument? on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC. ! Paragraph ended before was complete. to be read again \par l.13 Can't find anything wrong though ... Joh Hans Hagen wrote: Hi, Today i'll upload a new release. Highlights: - some fixes/extensions discussed the last few weeks - xetex support adapted to using xdvipdfmx - ctxtools --update which will update your local context - an update feature in scite (can be used a example for other editors) - an integrated mpto (more robust that the binary approach) (btw, use textext instead of btex .. etex when possible) Taco will undoubtely give mnore details later. Keep in mind that you need to change the stubs: - preferable use texmfstart to launch scripts - texmfstart itself can be stubbed if needed - there is a ../scripts/context/stubs path in the zip 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 release and XeTeX - XeConTeXt
Dear all,
After upgrading to the latest release (that is TeXExec 5.4.3, and
ConTeXt ver: 2006.05.08 12:59 fmt: 2006.5.9 int: english mes:
english), when I tried to generate the format with XeTeX (that is to
generate XeConTeXt), with the command
sudo texexec --make --xtx en
I get the folllowing error message:
language: patterns de for de loaded (n=3,e=texnansi,m=texnansi)
(/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-de.pat
! Bad \patterns.
\unknownchar -{
\hbox {\vrule \!!width .5em\!!height 1ex\!!depth \zeropoint }}
l.114 .ge
s6
?
Has anyone encountered this error? Is there a solution?
Many thanks for your help: Otared K.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] new release
Hi, Today i'll upload a new release. Highlights: - some fixes/extensions discussed the last few weeks - xetex support adapted to using xdvipdfmx - ctxtools --update which will update your local context - an update feature in scite (can be used a example for other editors) - an integrated mpto (more robust that the binary approach) (btw, use textext instead of btex .. etex when possible) Taco will undoubtely give mnore details later. Keep in mind that you need to change the stubs: - preferable use texmfstart to launch scripts - texmfstart itself can be stubbed if needed - there is a ../scripts/context/stubs path in the zip 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 release
Hi Hans, just downloaded the new release and regenerated the formats. Will play with it later. For the time being just one question: the stubs in scripts/context/stubs/unix and .../mswin seem to be identical; is that what you meant? I doubt that many unixoid systems will be at ease with .bat executables and c: paths... Best Thomas On Mon, 2006-05-08 at 13:04 +0200, Hans Hagen wrote: Hi, Today i'll upload a new release. Highlights: - some fixes/extensions discussed the last few weeks - xetex support adapted to using xdvipdfmx - ctxtools --update which will update your local context - an update feature in scite (can be used a example for other editors) - an integrated mpto (more robust that the binary approach) (btw, use textext instead of btex .. etex when possible) Taco will undoubtely give mnore details later. Keep in mind that you need to change the stubs: - preferable use texmfstart to launch scripts - texmfstart itself can be stubbed if needed - there is a ../scripts/context/stubs path in the zip 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 mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Hans et al, I don't understand the word stub. What are ctxtools? What is meant by an update feature in Scite? Where are context features in scite discussed? For example, Hans let me knoow about Ctrl +F12 for compiling my figure library, but that's not on any of the menus of scite. What else is cool but hidden? On May 8, 2006, at 4:04 AM, Hans Hagen wrote: Hi, Today i'll upload a new release. Highlights: - some fixes/extensions discussed the last few weeks - xetex support adapted to using xdvipdfmx - ctxtools --update which will update your local context - an update feature in scite (can be used a example for other editors) - an integrated mpto (more robust that the binary approach) (btw, use textext instead of btex .. etex when possible) Taco will undoubtely give mnore details later. Keep in mind that you need to change the stubs: - preferable use texmfstart to launch scripts - texmfstart itself can be stubbed if needed - there is a ../scripts/context/stubs path in the zip 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 mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Mon, 8 May 2006, Hans Hagen wrote: (btw, use textext instead of btex .. etex when possible) Some naive thoughts Do people still use draw string infont fontname Is it possible to provide a metapost package so that defaults to textext? For most graphics, I want TeX to do the typesetting. Using btex ... etex or textext(...) for everything makes the source look ugly. Something less drastic. Is it possible to define macros, say LABEL such that LABEL(a string, origin) is same as label(textext(a string), origin) I do not understand metapost well enough to know if a macro can handle all the cases like LABEL(a string scaled 1.5, origin) and so on. Aditya ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
David Arnold wrote: Hans et al, I don't understand the word stub. look in scripts/context/stubs they are small bat files put in the bin path and launch rograms What are ctxtools? ctxtools pdftools xmltools textoosl tmftools are goodies that ship with context What is meant by an update feature in Scite? Where are context features in scite discussed? For example, Hans let me knoow about Ctrl +F12 for compiling my figure library, but that's not on any of the menus of scite. What else is cool but hidden? in the new big windows zip there is a scite that has a menu entry (under tools) for updating your context 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 release
Thomas A. Schmitz wrote: Hi Hans, just downloaded the new release and regenerated the formats. Will play with it later. For the time being just one question: the stubs in scripts/context/stubs/unix and .../mswin seem to be identical; is that what you meant? I doubt that many unixoid systems will be at ease with .bat executables and c: paths... hm, i will check 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
Re: [NTG-context] new release
Thomas A. Schmitz wrote: Hi Hans, just downloaded the new release and regenerated the formats. Will play with it later. For the time being just one question: the stubs in scripts/context/stubs/unix and .../mswin seem to be identical; is that what you meant? I doubt that many unixoid systems will be at ease with .bat executables and c: paths... a typo indeed, you can correct it with: texmfstart --verbose --unix --stubpath=yourbinpath --make 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] new release
On Feb 1, 2006, at 9:07 PM, Thomas A. Schmitz wrote: No, that's not the point, updating works. I just see that in my $HOMETEXMF, I now have a directory web2c/pdfetex where format files are stored. This directory has been created on Jan 25, at one of the latest updates. I haven't changed my texmf.cnf, so the behavior of texexec --make has changed during one of the last releases, I guess 2006.01.16. And I'm just wondering if I can have the old behavior back as I prefer it. I downloaded the latest release from yesterday, and it doesn't create a web2c directory in my $HOMETEXMF anymore, so either a problem has been fixed, or I did something wrong to get this result. Sorry for the noise. Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Thomas A. Schmitz wrote: On Feb 1, 2006, at 6:37 PM, VnPenguin wrote: Which commands have you used for updating ? I follow the page http://wiki.contextgarden.net/TeTeX_3.0_installation , it works perfectly for me. No, that's not the point, updating works. I just see that in my $HOMETEXMF, I now have a directory web2c/pdfetex where format files are stored. This directory has been created on Jan 25, at one of the latest updates. I haven't changed my texmf.cnf, so the behavior of texexec --make has changed during one of the last releases, I guess 2006.01.16. And I'm just wondering if I can have the old behavior back as I prefer it. There are no pertinent changes to texexec (going back to 20051218) so if you are right about the date, it has to be something in your local environment that has changed. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Jan 31, 2006, at 7:46 PM, Taco Hoekwater wrote: On the subject of fixes: Hans' new ConTeXt release is now available for download, and it includes fixes for \eqalign and \startalign. The release notes are here: http://wiki.contextgarden.net/Context_2006.01.31 I'll do a formal announcement and CTAN upload tomorrow. Cheers, taco Just a quick question about the new release(s): I've seen that formats are now installed in $HOMETEXMF instead of $TEXMFLOCAL. Is there a reason for this change, and is it possible to have them installed in the old place? I preferred that way because it keeps everything in one location. Best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
Thomas A. Schmitz wrote: Just a quick question about the new release(s): I've seen that formats are now installed in $HOMETEXMF instead of $TEXMFLOCAL. Is there a reason for this change, and is it possible to have them installed in the old place? I preferred that way because it keeps everything in one location. Depends on your tetex/texlive setup, I think. afaik, texexec calls kpsewhich to decide on the path to use. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On 2/1/06, Thomas A. Schmitz [EMAIL PROTECTED] wrote: Just a quick question about the new release(s): I've seen that formats are now installed in $HOMETEXMF instead of $TEXMFLOCAL. Is there a reason for this change, and is it possible to have them installed in the old place? I preferred that way because it keeps everything in one location. Which commands have you used for updating ? I follow the page http://wiki.contextgarden.net/TeTeX_3.0_installation , it works perfectly for me. -- http://vnoss.org Vietnamese Open Source Software Community ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new release
On Feb 1, 2006, at 6:37 PM, VnPenguin wrote: Which commands have you used for updating ? I follow the page http://wiki.contextgarden.net/TeTeX_3.0_installation , it works perfectly for me. No, that's not the point, updating works. I just see that in my $HOMETEXMF, I now have a directory web2c/pdfetex where format files are stored. This directory has been created on Jan 25, at one of the latest updates. I haven't changed my texmf.cnf, so the behavior of texexec --make has changed during one of the last releases, I guess 2006.01.16. And I'm just wondering if I can have the old behavior back as I prefer it. All best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] new release
On the subject of fixes: Hans' new ConTeXt release is now available for download, and it includes fixes for \eqalign and \startalign. The release notes are here: http://wiki.contextgarden.net/Context_2006.01.31 I'll do a formal announcement and CTAN upload tomorrow. Cheers, taco Matthias Weber wrote: Great, this works now! That was definitely the easiest fix of the day. Thanks a lot. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] New release
Hi all, Hans has issued a new release of ConTeXt yesterday (2005.01.13). Highlights: * The distribution now contains Taco's bib module and related files * The TeXShow program now uses the XML versions of the interface definition files, the .tws variants have been removed * Math font definitions (esp. lucida/euler) are completed and improved, resulting in more robust mixed math usage More details on the Wiki, http://contextgarden.net/Release_Notes Greetings, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
