From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: does context support vietnamese?
Date: Thu, 18 Nov 2004 01:45:17 +0000 [thread overview]
Message-ID: <20041118014517.3394@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <20041118013604.GA695@monty>
The Thanh Han said this at Thu, 18 Nov 2004 08:36:05 +0700:
>Hi Adam,
>
>ET5 was the first proposed font encoding for vietnamese; then it was
>renamed to X5 with a few modifications. T5 is a minor update -- it's
>heavily based on X5 but I don't remember what has been changed.
Thanks. The questions now seem to be, is there a significant amount of
fonts/support files/work that relied on x5 that needs to be supported?
Because I just discovered that there were some serious bugs in the
ConTeXt interpretation of the x5 encoding, and that any regular user
would have demanded that something be changed!
Cheers,
adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-11-18 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041114132638.GD517@monty>
[not found] ` <41986F4A.4090903@wxs.nl>
[not found] ` <20041117014300.GC301@monty>
2004-11-17 10:05 ` Hans Hagen
2004-11-17 10:10 ` Adam Lindsay
2004-11-18 1:36 ` The Thanh Han
2004-11-18 1:45 ` Adam Lindsay [this message]
2004-11-19 6:09 ` The Thanh Han
2004-11-21 23:24 ` h h extern
2004-11-24 6:19 ` The Thanh Han
2004-11-17 21:50 ` Czech support (Was: Re: does context support vietnamese?)^[ David Antos
2004-11-17 22:23 ` h h extern
2004-11-18 0:54 ` Vit Zyka
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=20041118014517.3394@news.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).