From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xetext-pdftex differences
Date: Wed, 11 Apr 2007 19:22:39 +0200 [thread overview]
Message-ID: <461D195F.8070500@wxs.nl> (raw)
In-Reply-To: <6faad9f00704110844x377d61dao3f5cad8d433707cb@mail.gmail.com>
Mojca Miklavec wrote:
> LuaTeX will probably support those old encodings, but you would want
> to use "uc" (unicode) encoding for both engines, otherwise it makes no
> sense to use XeTeX instead of pdfTeX at all.
>
luatex itself has still the pdftex machinery around, so you can use map
files to handle things when you use for instance type one fonts.
ttf and otf are supported as wide fonts, but of course one needs to make
sure that the unicode to glyph mapping is ok
in context mkiv i will intercept the encoding-prefixed fonts
(texnansi-mojca-regular) so this is transparent for users by using some
lua glue code but mainly because i read afm files instead of tfm files
(so, texnansi-mojca will in fact use mojca.afm); non prefixed names will
use the tfm file (this is pretty safe because the texnansi-* names were
only there when proper afm files are also there; i mainly provide this
features for existing typescripts)
in general, encodings are not something to worry about
not even uc as encoding is needed in mkiv
> All of your questions mentioned here belong to the ConTeXt mailing
> list (XeTeX mailing list is mostly for XeLaTeX and low-level XeTeX
> discussions) since it's really about the ConTeXt user-interface. The
> only thing you could ask for on the XeTeX list is the question of
> supporting ec/texnansi-encoded fonts (I prefer to wait for luaTeX than
> to bother about those "soon-to-become-obsolete" additions).
>
indeed, there is no need to mess up xetex with obsolete encoding stuff;
luatex will still have much pdftex code around so there the penalty is
less, but eventually users have to move on
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
-----------------------------------------------------------------
next prev parent reply other threads:[~2007-04-11 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 20:16 Steffen Wolfrum
2007-04-10 19:27 ` Mojca Miklavec
2007-04-11 9:09 ` Steffen Wolfrum
2007-04-11 15:44 ` Mojca Miklavec
2007-04-11 17:22 ` Hans Hagen [this message]
2007-04-12 7:37 ` Steffen Wolfrum
2007-04-12 10:41 ` Hans Hagen
2007-04-12 7:53 ` Steffen Wolfrum
2007-04-12 10:46 ` Hans Hagen
2007-04-12 13:53 ` Steffen Wolfrum
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=461D195F.8070500@wxs.nl \
--to=pragma@wxs.nl \
--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).