From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Context & Vietnamese UTF-8
Date: Tue, 16 Nov 2004 12:36:24 +0000 [thread overview]
Message-ID: <20041116123624.13774@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <e5d3f26504111514422c1a93f3@mail.gmail.com>
VnPenguin said this at Mon, 15 Nov 2004 23:42:29 +0100:
>Hi all,
>I'm newbie of ConTeXt. I use VnTeX (vietnamese package for LaTeX of
>Han The Thanh) with UTF-8 without any problem on teTeX 2.x (with
>pdflatex).
>
>Now I would like to try ConTeXt and if it works I'll convert all my
>LaTeX src into ConTeXt later.
>
>Anyone could give me some links to read for this please.
Hi there.
I've worked on a bit of Unicode (output) for ConTeXt recently, and I
noticed that Vietnamese needs a little bit more work. There's already
viscii input and x5 encoding output (apparently) working in ConTeXt.
As I understand it, UTF-8 support will then require an update to
ConTeXt's unic-* files (giving named glyphs for input) and then a slight
update to the enco-x5 file. I guess what's really needed are canonical
internal names (like 'ygrave' or 'ohornhook') for ConTeXt's use.
Don't be afraid: it's not difficult, just a bit tedious. So I should ask,
Mr Penguin, how are you with sed, Perl, or Ruby?
Also, do you have any good references for character tables for the
encoding(s?) that VnTeX uses? I don't have it installed on my machine (yet).
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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-16 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 22:42 VnPenguin
2004-11-16 12:36 ` Adam Lindsay [this message]
2004-11-16 14:20 ` VnPenguin
2004-11-16 14:39 ` Adam Lindsay
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=20041116123624.13774@news.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).