From: Hans Hagen <pragma@wxs.nl>
Subject: Re: DocBookInContext & multi-languages (newbie) / utf
Date: Mon, 02 Dec 2002 15:43:37 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021202153537.03d21258@server-1> (raw)
In-Reply-To: <20021202135950.GA18129@mail.inet.hr>
At 02:59 PM 12/2/2002 +0100, Gour wrote:
>Hans Hagen (pragma@wxs.nl) wrote:
>
> > sure, but for that i need input on how those vector look like; xtag-utf is
> > a starting point, but i also need the second 'bank', so whoi can
>
>Where can I get some more info how this xtag-utf vector should look like?
in xtag-utf.tex in .../tex/context/base (at least in my version and the beta)
> > (1) provide me with proper test files (can be simple text with utf 8 text)
>
>UTF-8_and_Unicode_FAQ has some test files and I'm sure this step is not a
>problem.
So, where can i find that doc?
> > (2) provide the mapping list in terms of <nr><nr> => \namedglyph
>
>I need some explanation: e.g. amacron (small latin letter "a" with
>macron") has
>Unicode code U+0101. When I look within Vim (g8 function) it shows me that it
>has "c4 81" hex value in UTF-8 encoding.
>
>In this way it's possible to get Unicode code & hex value in UTF-8 encoding.
>
>So, I'm interested, what would be the correct entry for the above
>mentioned list
>in the case for amacron:
>
>a) c4 81 -> amacron
>b) 0101 -> amacron
>
>or something else?
so, c4 is the trigger, and 81 the character; this means that the function
attached to c4 has to map the 81 onto \amacron
can you make me a file with a list like:
amacron : 01/01 : c4/c8 : <utfcode>
^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^
normal ascii real utf
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-12-02 14:43 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 [this message]
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 ` DocBookInContext ... [CSX+, UTF-8 Roman, and Nagari Codings] Richard Mahoney
2002-12-04 14:16 ` 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=5.1.0.14.1.20021202153537.03d21258@server-1 \
--to=pragma@wxs.nl \
--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).