From: Hans Hagen <pragma@wxs.nl>
Subject: Re: XeTeX working on Windows as well !!!
Date: Tue, 06 Jun 2006 21:46:51 +0200 [thread overview]
Message-ID: <4485DBAB.9020600@wxs.nl> (raw)
In-Reply-To: <6faad9f00606061102v42a7e08fj8ffd12df7008d8b4@mail.gmail.com>
Mojca Miklavec wrote:
> On 6/6/06, Hans Hagen wrote:
>
>> hm, i didn't try that fc stuff yet
>>
>
> One of the most important things about XeTeX :(
>
>
> While talking about fonts: do you have any suggestions about (old)
> Type1 (ec-encoded) fonts? The problem is that XeTeX handles them as if
> they were Latin1/Unicode-encoded (if you type in Yen, you'll get
> whatever glyphy is present at that slot independint of font encoding),
> so the only way to get other characters from EC encoding is to:
> a) "redefine" (make active) some parts of Unicode (\def�{\ccaron})
> b) extend XeTeX, so that it knows which glyph is "hidden" on which slot
> c) forget about support for Type1 fonts
>
> Another thing to adapt is (again :) the \enableregime macro (see
> http://wiki.contextgarden.net/Encodings_and_Regimes_in_XeTeX for some
> notes about that), so that regimes will work with XeTeX as well. Two
> possibilities are:
> a) \XeTeXinputencoding "somename" for native XeTeX handling, but with
> the same problems with EC fonts as above
> b) \XeTeXinputencoding "bytes" + loading the regime definitions with
> exactly the same behaviour as in pdfTeX, but without the support for
> non-latin regimes
>
here i get the right characters when i say:
\starttext
\XeTeXinputencoding "utf8"
It works! [\eacute][\rawcharacter{233}][é]
\yen
\XeTeXinputencoding "bytes" % \enableregime[ec]
It works! [\eacute][\rawcharacter{233}][é]
\yen
\stoptext
Do you have an example that fails?
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
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
prev parent reply other threads:[~2006-06-06 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 15:31 Mojca Miklavec
2006-06-06 16:59 ` Hans Hagen
2006-06-06 17:19 ` Hans Hagen
2006-06-06 17:31 ` Mojca Miklavec
2006-06-06 17:33 ` Hans Hagen
2006-06-06 18:02 ` Mojca Miklavec
2006-06-06 18:53 ` Hans Hagen
2006-06-06 21:45 ` Mojca Miklavec
2006-06-06 19:46 ` Hans Hagen [this message]
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=4485DBAB.9020600@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).