Re: waiting for mswincontext

[Wolfgang Schuster <schuster.wolfgang@googlemail.com>]

On Thu, 20 Sep 2007 15:18:45 +0200
"Mojca Miklavec" <mojca.miklavec.lists@gmail.com> wrote:

> On 9/20/07, Taco Hoekwater wrote:
> > Hans Hagen wrote:
> > > Mojca Miklavec wrote:
> > >> On 9/19/07, Hans Hagen wrote:
> > >>> btw,
> > >>>
> > >>> pdftex --ini &plain \\pdfoutput=1 \dump
> > >>>
> > >>> can do the same for you, but as said .. if the minimals would have plain
> > >>> formats they would default to dvi anyway so it would be of no help to you
> > >> pdftex.fmt and mpost.mem would be perfectly fine. No need for
> > >> plain.fmt (I guess). (And maybe xetex.fmt as a sugar, although that
> > >> one might need some additional files.)
> > >
> > > pdftex --ini -fmt=pdftex plain.tex \\pdfoutput=1 \dump
> > >
> > > probably does that, but as said, everyone wants his/her own variant
> > > (patterns to start with -)
> >
> > There is no doubt that plain is useful. I always create the plain
> > Knuth format for luatex and pdftex by hand, and while it would be nice
> > to have it done automatically, it is not that much work, and all real
> > input files are there (.ini's are a commandline convenience).
> 
> (In case of XeTeX, it's slightly more that a single line to be typed :)
> 
> > If I understood correctly, plain xetex really needs something extra?
> > If that is so, than perhaps that file should be added. Mojca, what's
> > up with that?
> 
> xetex.ini looks like that:
> 
> \catcode`\{=1 \catcode`\}=2 \catcode`\#=6 \catcode`\^=7 \catcode`\@=11
> 
> \input unicode-letters
> 
> \let\s@vef@nt=\font
> ... some stuff here
> \lowercase{\def\sk@pf@nt\preloaded=#1^^A{\endgroup}}
> 
> \input etex.src
> 
> % restore the \font command and undefine other stuff
> \catcode`\@=11
> \let\font=\s@vef@nt
> ... some more stuff here
> 
> \dump
> \endinput
> 
> So one additionally needs:
> - (possibly modified) xetex.ini itself
> - unicode-letters.tex (could be replaced by enco-utf.tex, though I
> just figured out that there's more in unicode-letters than in
> enco-utf, but in that case enco-utf is that one which should be fixed)

this is not possible with the 0.997dev version because it presets
charclasses (a new feature in XeTeX) for a few CJK characters 

> - etex.src (btw: why is that one only used in xetex, but not in pdfTeX?)

this is also used for the pdftex format in w32tex 

> - tex-text.tec (which was missing until now but needs to be added anyway)
> - hmmm ... no idea about what is needed for hyphenation (but I guess
> that patterns from ConTeXt could be used as well)
> 
> I will test once I have the rest, but it would be really handy to have
> the three plain formats (pdfTeX, XeTeX and mpost available; plus
> luatex if needed).
> 
> > On dev-context, I have already proposed the removal of a number of
> > binaries, so I can make that request :-)
> 
> ;) 3-times hurray for Taco :)
> 
> Mojca

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
___________________________________________________________________________________