ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Yue Wang" <yuleopen@gmail.com>
To: "Jin-Hwan Cho" <chofchof@ktug.or.kr>,
	"Taco Hoekwater" <taco@elvenkind.com>,
	"Hans Hagen" <pragma@wxs.nl>,
	 "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
	 "Kew Jonathan" <jon
Subject: different behavior between xetex and luatex
Date: Tue, 23 Dec 2008 04:26:18 +0000	[thread overview]
Message-ID: <68bfdc900812222026n4903d467qa3d6165d83d0eaa9@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Hi, all.

I expect different output in xetex and luatex using context. and I
think the problem is quite serious although I do not speak Turkish.
in turkish, fi can not be treat as ligatures and I can see luatex
handle that quite well. however, in xetex, fi are treated as
ligatures.
I attach the files and output here. I don't know it is a bug in xetex,
context or dvipdfmx:(

Yue Wang

[-- Attachment #2: a.pdf --]
[-- Type: application/pdf, Size: 2974 bytes --]

[-- Attachment #3: a.tex --]
[-- Type: application/x-tex, Size: 1075 bytes --]

[-- Attachment #4: b.pdf --]
[-- Type: application/pdf, Size: 2669 bytes --]

[-- Attachment #5: 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
___________________________________________________________________________________

             reply	other threads:[~2008-12-23  4:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23  4:26 Yue Wang [this message]
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

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=68bfdc900812222026n4903d467qa3d6165d83d0eaa9@mail.gmail.com \
    --to=yuleopen@gmail.com \
    --cc=chofchof@ktug.or.kr \
    --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).