From: Richard Mahoney <rbm49@ext.canterbury.ac.nz>
Subject: Re: DocBookInContext ... [CSX+, UTF-8 Roman, and Nagari Codings]
Date: Wed, 4 Dec 2002 08:14:06 +1300 [thread overview]
Message-ID: <20021203191406.GC44925@ext.canterbury.ac.nz> (raw)
In-Reply-To: <20021202174029.GA24554@mail.inet.hr>
On Mon, Dec 02, 2002 at 06:40:30PM +0100, Gour wrote:
> So here I see something like:
>
> \defineUTFcharacter amacron 1 1
>
> which corresponds to the Unicode code of amacron: U+0101 and it's according to
> the output of Vim's function: "ga" which shows:
>
> <ā> 257, Hex 0101, Octal 401.
>
> Now, it just a question of little work to slowly populate this vector with the
> values for different Unicode characters.
To save yourself time you could look at two C programmes that indicate
CSXp, UTF-8 Roman, and UTF-8 Devanagari codings:
`csxp2ur' -- converts CSXp --> UTF-8 Roman
`ur2ud.c' -- converts UTF-8 Roman --> UTF-8 Devanagari
Both are from:
ftp://bombay.oriental.cam.ac.uk/pub/john/software/programs/
Regards,
Richard
--
Richard Mahoney | E-mail: rbm49@ext.canterbury.ac.nz
78 Jeffreys Road | r.mahoney@comnet.net.nz
Fendalton | Telephone: 0064-3-351-5831
CHRISTCHURCH 8005 | Cellular: 0064-25-829-986
NEW ZEALAND | http://homepages.comnet.co.nz/~r-mahoney
next prev parent reply other threads:[~2002-12-03 19:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 7:20 DocBookInContext & multi-languages (newbie) Gour
2002-11-29 19:18 ` Simon Pepping
2002-11-30 20:15 ` Gour
2002-11-30 20:55 ` Bruce D'Arcus
2002-12-01 6:40 ` Gour
2002-12-02 19:46 ` Simon Pepping
2002-12-02 20:30 ` Tobias Burnus
2002-12-02 21:54 ` Hans Hagen
[not found] ` <Pine.LNX.4.44.0212022106550.2205-100000@tom.physik.fu-berl in.de>
2002-12-02 21:59 ` Hans Hagen
2002-12-03 12:48 ` Tobias Burnus
2002-12-03 13:59 ` Willi Egger
[not found] ` <Pine.LNX.4.44.0212031306170.23965-100000@warp9.physik.fu-b erlin.de>
2002-12-03 13:45 ` Hans Hagen
2002-12-02 12:28 ` DocBookInContext & multi-languages (newbie) / utf Hans Hagen
2002-12-02 13:59 ` Gour
2002-12-02 14:43 ` Hans Hagen
2002-12-02 16:36 ` Taco Hoekwater
2002-12-02 17:40 ` Gour
2002-12-02 20:16 ` Simon Pepping
2002-12-02 21:57 ` Hans Hagen
2002-12-03 20:03 ` Simon Pepping
2002-12-03 23:31 ` Hans Hagen
2002-12-04 14:10 ` Gour
2002-12-04 16:31 ` Hans Hagen
2002-12-04 20:08 ` Gour
2002-12-05 0:10 ` multi-languages [UTF-8 Roman and UTF-8 Nagari test files] Richard Mahoney
2002-12-05 11:58 ` DocBookInContext & multi-languages (newbie) / utf Hans Hagen
2002-12-05 12:22 ` Taco Hoekwater
2002-12-05 13:25 ` Hans Hagen
2002-12-05 14:03 ` Tobias Burnus
2002-12-05 19:09 ` Create Type 1 fonts with Indological diacritics and UTF-8 TTF Richard Mahoney
2002-12-06 14:10 ` Hans Hagen
2002-12-06 15:22 ` Docu set Michael Hallgren
2002-12-07 14:12 ` Patrick Gundlach
2002-12-07 17:37 ` Michael Hallgren
2002-12-06 15:36 ` Re: Create Type 1 fonts with Indological diacritics and UTF-8 TTF Gour
2002-12-06 16:47 ` Hans Hagen
2002-12-03 19:14 ` Richard Mahoney [this message]
2002-12-04 14:16 ` Re: DocBookInContext ... [CSX+, UTF-8 Roman, and Nagari Codings] Gour
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=20021203191406.GC44925@ext.canterbury.ac.nz \
--to=rbm49@ext.canterbury.ac.nz \
--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).