From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: waiting for mswincontext
Date: Thu, 20 Sep 2007 15:18:45 +0200 [thread overview]
Message-ID: <6faad9f00709200618h1077af37q4abb381040e98afb@mail.gmail.com> (raw)
In-Reply-To: <46F21A40.70204@elvenkind.com>
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)
- etex.src (btw: why is that one only used in xetex, but not in pdfTeX?)
- 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
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-09-20 13:18 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1190023202.9795.ntg-context@ntg.nl>
2007-09-17 14:30 ` Recommendations for Speed? Duncan Hothersall
2007-09-18 20:33 ` waiting for mswincontext Vyatcheslav Yatskovsky
2007-09-19 7:46 ` Hans Hagen
2007-09-19 14:25 ` Idris Samawi Hamid
2007-09-19 16:33 ` Joel C. Salomon
2007-09-19 17:08 ` Idris Samawi Hamid
2007-09-19 18:02 ` Hans Hagen
2007-09-19 17:24 ` Mojca Miklavec
2007-09-19 14:40 ` Wolfgang Schuster
2007-09-19 14:45 ` Taco Hoekwater
2007-09-19 17:13 ` Idris Samawi Hamid
2007-09-20 7:01 ` Taco Hoekwater
2007-09-19 17:25 ` Wolfgang Schuster
2007-09-19 19:19 ` Idris Samawi Hamid
2007-09-19 19:53 ` Hans Hagen
2007-09-19 22:19 ` Aditya Mahajan
2007-09-19 23:22 ` Arthur Reutenauer
2007-09-20 7:06 ` Taco Hoekwater
2007-09-20 7:47 ` Hans Hagen
2007-09-20 17:24 ` Joel C. Salomon
2007-09-20 19:15 ` Aditya Mahajan
2007-09-20 7:36 ` Hans Hagen
2007-09-20 7:37 ` Hans Hagen
2007-09-19 17:26 ` Mojca Miklavec
2007-09-19 17:54 ` Hans Hagen
2007-09-19 14:45 ` Hans Hagen
2007-09-19 17:22 ` Wolfgang Schuster
2007-09-19 18:00 ` Hans Hagen
2007-09-19 18:31 ` Mojca Miklavec
2007-09-19 19:19 ` Hans Hagen
2007-09-20 6:59 ` Taco Hoekwater
2007-09-20 13:18 ` Mojca Miklavec [this message]
2007-09-20 18:22 ` Wolfgang Schuster
2007-09-20 20:21 ` Mojca Miklavec
2007-09-20 20:41 ` Hans Hagen
2007-09-21 7:37 ` Wolfgang Schuster
2007-09-21 12:40 ` Hans Hagen
2007-09-21 18:15 ` Wolfgang Schuster
2007-09-22 10:34 ` waiting for mswincontext / injecting Hans Hagen
2007-09-23 11:52 ` Wolfgang Schuster
2007-09-23 17:45 ` Mojca Miklavec
2007-09-23 17:49 ` Arthur Reutenauer
2007-09-23 18:00 ` Hans Hagen
2007-09-23 18:18 ` Idris Samawi Hamid
2007-09-23 20:01 ` Hans Hagen
2007-09-23 20:19 ` Idris Samawi Hamid
2007-09-23 18:24 ` Hans Hagen
2007-09-19 16:14 ` waiting for mswincontext Joel C. Salomon
2007-09-19 16:58 ` Hans Hagen
[not found] ` <6faad9f00709190257x35bd3495p1a5ee0de51f2a150@mail.gmail.com>
2007-09-19 15:00 ` Vyatcheslav Yatskovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6faad9f00709200618h1077af37q4abb381040e98afb@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).