Taco Hoekwater wrote:

Hans Hagen wrote:

...

Hi,

it's upto taco to write the usual announcement -)

expect some delays. The diff -r file has 33846 lines :-)

lucky you, it's mostly patterns -) 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 -----------------------------------------------------------------

See http://contextgarden.net/Context_2005.05.25 for a rather detailed list of changes. My apologies: the formatting is not very pretty and perhaps I've been a bit too brief here and there, but after two days of this I'm a bit bored with it. Perhaps I will fix the pages later. Greetings, Taco Taco Hoekwater wrote:

Hans Hagen wrote:

...

...

expect some delays. The diff -r file has 33846 lines :-)

lucky you, it's mostly patterns -)

All those patterns are just one line, I'm afraid:

Only in 20050525/tex/context: patterns

looks like there is quite a lot of .map activity going on though. Anyway, I'll take me a few days to sort this through.

_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

On Fri, 2005-05-27 at 17:07 +0200, Taco Hoekwater wrote:

See

http://contextgarden.net/Context_2005.05.25

for a rather detailed list of changes.

Thank you. Very helpful. In particular, I'd missed the SVG support announcement, and I'm excited to play with that. Thanks to everyone that contributed to this new release. -- Stuart Jansen Guru Labs, L.C.

Idris Samawi Hamid wrote:

\definefonthandling [highquality] [hz,normal]

ok, added

which is why I named it `highquality'-)

And thnx 4 all your hard work!

sorry for your suffering in updates [i'm considering letting context write a map file that you then can use in dvipdfmx] 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 -----------------------------------------------------------------

Idris Samawi Hamid wrote:

On Wed, 25 May 2005 17:34:24 +0200, Hans Hagen wrote:

...

Hi,

I posted a new version of context.

Does the multi-format engine work now? :-)

it should; just try the latest texexec --make --engine=aleph --all texexec --make --all (The new texexec will provide more status info about what is generated) 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 -----------------------------------------------------------------

Adam Lindsay wrote: (i cc to karl who knows more about the detry details of path expansion than i do)

Hans Hagen said this at Wed, 25 May 2005 17:34:24 +0200:

...

the next (main) release will probably have a new texexec (ruby version, smoother, faster, more clever, no ini file etc)

Hmm. I hand-updated to the latest, and now texexec wants to rebuild the format on every run.

I'm not used to seeing this, anyone have any hints on where to poke around?

(the format is in texmf.local/web2c/ and in a pdfetex subdir. I've texhashed, too.)

since engine support is either broken or not implemented in kpse/tetex, i need to sort it out myself; this is done in: sub checktexformatpath { # engine support is either broken of not implemented in some # distributions, so we need to take care of it ourselves my $texformats ; if (defined($ENV{'TEXFORMATS'})) { $texformats = $ENV{'TEXFORMATS'} ; } else{ $texformats = '' ; } if ($texformats eq '') { if ($dosish) { $texformats = `kpsewhich --expand-var=\$TEXFORMATS`.chomp ; } else { $texformats = `kpsewhich --expand-var=\\\$TEXFORMATS`.chomp ; } } if ($texformats !~ /web2c[\/\\].*\$ENGINE/) { $texformats =~ s/web2c/web2c\/{\$ENGINE,}/ ; $ENV{'TEXFORMATS'} = $texformats ; print " fixing texformat path : $ENV{'TEXFORMATS'}\n"; } if (! defined($ENV{'ENGINE'})) { if ($MpEngineSupport) { $ENV{'ENGINE'} .= $MpExecutable ; } ; $ENV{'ENGINE'} = $TeXExecutable ; print "fixing engine variable : $ENV{'ENGINE'}\n"; ## just added } } how i hate this naming; when -long ago- i started using local trees, i adopted the texmf-local naming that i noticed in those days, and look what we have here:

fixing texformat path : .:{/Users/atl/Library/texmf,!!/usr/local/teTeX/ share/texmf.local,!!/usr/local/teTeX/share/texmf.gwtex,!!/usr/local/ teTeX/share/texmf.tetex,!!/usr/local/teTeX/share/texmf}/web2c/{$ENGINE,}/{,}// 0

well, this magic line will append web2c/{$ENGINE,} to each path, including the share/texmf.local path so i'm puzzled; one complication is that kpse is not able to report the path that will be used (probably for good reason); so the format should end up in: !!/usr/local/teTeX/share/texmf.local/web2c/pdfetex/cont-en.fmt could it be that the /{,}// is playing tricks? can you try to add $texformats =~ s/\{\,\}\/\/// ; i.e. get rid of the trailing crap so that th eend looks like /web2c/{$ENGINE,}/ can you check at what value texexec sets $ENGINE ? (setting TEXFORMATS at the shell level will also work; that is what i normally have) watch this mix of teTeX and tetex and Users and Library vs share; if i would not know better, i'd think it was a blob of tricky perl code -) last time i tried it on the mac it worked, so i must try again the file should end up in web2c/pdftex

fmtutil: running `pdfetex -ini -jobname=cont-en -progname=context

forget about fmtutil, it cannot and will not handle engines 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 -----------------------------------------------------------------

Adam Lindsay wrote:

Hans Hagen said this at Fri, 27 May 2005 01:29:30 +0200:

...

well, this magic line will append web2c/{$ENGINE,} to each path,

Okay, that's part of the problem: your code isn't detecting the presence of $ENGINE in my path... It's there already! (Thanks, Gerben.) The line from texmf.cnf:

TEXFORMATS = .;$TEXMF/web2c/{$engine,}//

However:

% kpsewhich --expand-var=\$TEXFORMATS .:{/Users/atl/Library/texmf,!!/usr/local/teTeX/share/texmf.local, !!/usr/local/teTeX/share/texmf.gwtex,!!/usr/local/teTeX/share/texmf.tetex, !!/usr/local/teTeX/share/texmf}/web2c/{,}// ^^^ But:

% kpsewhich --engine=pdfetex --expand-var=\$TEXFORMATS .:{/Users/atl/Library/texmf,!!/usr/local/teTeX/share/texmf.local, !!/usr/local/teTeX/share/texmf.gwtex,!!/usr/local/teTeX/share/texmf.tetex, !!/usr/local/teTeX/share/texmf}/web2c/{pdfetex,}//

there is also code like: if (($UseEnginePath)&&($EngineDone)) { $FormatPath = `$kpsewhich --engine=$EnginePath --show-path=fmt` ; } else { $FormatPath = `$kpsewhich --show-path=fmt` ; } what does --show-path=fmt reports? ----------------------------------------------------------------- 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 -----------------------------------------------------------------

Adam Lindsay wrote:

...

the next (main) release will probably have a new texexec (ruby version, smoother, faster, more clever, no ini file etc)

what does texmfstart newtexexec --make --all do? 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 -----------------------------------------------------------------

Adam Lindsay wrote:

Interesting... It builds the formats (not engine aware in terms of where it puts the .fmt files--at least it uses different switches compared to what I'm used to), but (old)texexec did that too.

What's interesting is that it doesn't insist on rebuilding the format on a normal (--pdf) run. (And it's fast: does it buffer the terminal output?)

in summary: texexec --make --all Builds the formats. texexec --pdf myfile fails to find the format, builds it, runs the file texmfstart newtexexec --make --all Builds the formats. texmfstart newtexexec --pdf myfile finds the format correctly, runs the file quickly.

texmfstart newtexexec --make --xtx --engine en Builds a XeTeX format, but leaves it in the web2c directory texexec --make --xtx --engine en Builds a XeTeX format, and correctly puts it in web2c/xetex

hmm. Honestly, I personally didn't have any complaints with the operation of the previous version of texexec.

well, i had complaints -) lin win and mac all behave differently, party due to differences in distribution (on our machines i set texformsts explicitly so there is no real problem there) \ can you try texmfstart newtexexec --make --engine=xetex en 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 -----------------------------------------------------------------

Peter Münster wrote:

On Fri, 27 May 2005, Adam Lindsay wrote:

...

Hans Hagen said this at Fri, 27 May 2005 01:34:57 +0200:

...

what does

texmfstart newtexexec --make --all

do?

Interesting... It builds the formats (not engine aware in terms of where it puts the .fmt files--at least it uses different switches compared to what I'm used to), but (old)texexec did that too.

What's interesting is that it doesn't insist on rebuilding the format on a normal (--pdf) run. (And it's fast: does it buffer the terminal output?)

Hello, I have the same problem on Linux, but I don't have texmfstart... Are there other solutions or is texmfstart now needed to run texexec? Cheers, Peter

you do have texmfstart, just copy texmfstart.rb to texmfstart in one of your bin paths (texmfstart is one of the core components of the context scripts, being the only way i can guarantee upward compatibility when drastic changes take place in the tds/distributions) (there is a manual on the website) 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 -----------------------------------------------------------------