From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Ancient Greek
Date: Sun, 22 Aug 2004 09:07:28 -0600 [thread overview]
Message-ID: <20040822160728.24043@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <a06002002bd4e2f9bdad2@[62.134.73.248]>
Steffen Wolfrum said this at Sun, 22 Aug 2004 13:10:28 +0200:
>As far as I understood I order to typeset text in xetex you have to use
>basically plain TeX-commands.
XeTeX is another TeX engine. So it responds to (plain) TeX commands.
LaTeX and ConTeXt are macro packages that are written in TeX. So your
LaTeX or ConTeXt commands are eventually just translated into TeX
commands as well. MacOSX LaTeX people already have xelatex going. It's
not terribly hard to get "texexec --tex=xetex" to work, either. (Hint: do
"xeinitex cont-en" and use the resulting cont-en.xfmt file.)
Colors, graphics, and transformations need \specials, and there are some
font quoting tricks to do, as well.
>So, when you say you're working on XeTeX drivers for ConTeXt does that
>mean that I can write normal context code but typeset with XeTeX instead
>of pdfeTeX?
Exactly.
>That would be great. Because my aim is to include polytonic greek quotes
>in my context document, and I setup an ideal context environment for my
>publications already and don't want to start with plain TeX again.
:)
>So if my understanding is right, when do you think XeTeX will be
>available for us ConTeXt users?
Ah, that would be why I asked about *your* requirements and timeframe.
This is an avocation for me--I have a PhD thesis to write soon, so I
don't want to commit to a timeframe for a side (albeit interesting)
project. I can help you get started, and I will concentrate on the
features you want most, but to do that, I need your requirements.
I think Hans will agree that real users drive things forward, and that's
what I see xecontext needing.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay atl@comp.lancs.ac.uk
Computing Dept, Lancaster University +44(0)1524/594.537
Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-08-22 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 11:10 Steffen Wolfrum
2004-08-22 15:07 ` Adam Lindsay [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-23 13:12 Steffen Wolfrum
2004-08-23 15:25 ` Hans Hagen
2004-08-20 18:57 Steffen Wolfrum
2004-08-21 18:04 ` Adam Lindsay
2004-08-18 20:57 Steffen Wolfrum
2004-08-20 15:52 ` Idris Samawi Hamid
[not found] ` <a06002008bd497194fc9d@[62\.134\.77\.121]>
2004-08-21 22:29 ` Giuseppe Bilotta
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=20040822160728.24043@news.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).