From: "Yue Wang" <yuleopen@gmail.com>
To: "Jonathan Kew" <jonathan_kew@sil.org>
Cc: Jin-Hwan Cho <chofchof@ktug.or.kr>, Hans Hagen <pragma@wxs.nl>,
Taco Hoekwater <taco@elvenkind.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: different behavior between xetex and luatex
Date: Tue, 23 Dec 2008 10:15:34 +0000 [thread overview]
Message-ID: <68bfdc900812230215n30f2f9e0me662fc38454c7fde@mail.gmail.com> (raw)
In-Reply-To: <D7D06F30-5A56-4215-9899-F46E77C8480D@sil.org>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
Hi, Jonathan:
Thanks for the analysis! Now I replace the trk with TRK, and xetex
output is right.
>
> In the LuaTeX case, I don't think *any* ligatures are enabled by default, so
> the language is irrelevant; notice that there's no "ff" ligature in your
> output either, even though this should be expected.
The input file is not right. here is the right one: luatex do not
enable kerning and ligatures by default, users should specify them or
just using the "default" feature. Sorry for the noise.
Yue Wang
[-- Attachment #2: luatex.pdf --]
[-- Type: application/pdf, Size: 3193 bytes --]
[-- Attachment #3: a.tex --]
[-- Type: application/x-tex, Size: 1102 bytes --]
[-- Attachment #4: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-12-23 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 4:26 Yue Wang
2008-12-23 8:08 ` Jonathan Kew
2008-12-23 8:42 ` Mojca Miklavec
2008-12-23 10:08 ` Yue Wang
2008-12-23 10:15 ` Yue Wang [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=68bfdc900812230215n30f2f9e0me662fc38454c7fde@mail.gmail.com \
--to=yuleopen@gmail.com \
--cc=chofchof@ktug.or.kr \
--cc=jonathan_kew@sil.org \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
--cc=taco@elvenkind.com \
/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).