From: Yue Wang <yuleopen@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Jonathan Kew <jonathan_kew@sil.org>
Subject: Two issues related to xetex
Date: Tue, 12 May 2009 00:38:56 +0800 [thread overview]
Message-ID: <68bfdc900905110938u2d71d84eq3b18d167ceca3331@mail.gmail.com> (raw)
Hi, Hans and Mojca:
first, (to Mojca) the first-setup.sh script still deletes fontconfig
cache when updating on windows.
second, (to Hans) unicode-letters.tex is read when we dump plain TeX
or LaTeX format in TeXLive. This file is wrote by Jonathan Kew in
order to initialize XeTeX. It defines many important unicode
properties into XeTeX. However, ConTeXt do not load that file when
dumping the xetex format. The file is not even in ConTeXt
distribution. I suggest that the file should be loaded.
You can find the file in
http://scripts.sil.org/svn-public/xetex/TRUNK/texmf/tex/generic/xetex/unicode-letters.tex
XeTeX's plain TeX ini file can be find in
http://scripts.sil.org/svn-public/xetex/TRUNK/texmf/tex/xetex/config/xetex.ini
If the file is not loaded, thousands of lines should be copied to
third party modules (like the module I announce on the mailing list
today) in order to support some language correctly. This method is
quite messy, not to say inefficient for loading.
Yue Wang
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2009-05-11 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 16:38 Yue Wang [this message]
2009-05-11 17:08 ` Hans Hagen
2009-05-11 19:54 ` Mojca Miklavec
2009-05-11 21:13 ` Hans Hagen
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=68bfdc900905110938u2d71d84eq3b18d167ceca3331@mail.gmail.com \
--to=yuleopen@gmail.com \
--cc=jonathan_kew@sil.org \
--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).