From: "Martin Kolařík" <martin@mii.cz>
Subject: UTF and texutil files...
Date: Mon, 23 Aug 2004 15:00:17 +0200 [thread overview]
Message-ID: <NCBBIFBEODPJOENMOHHBCEHJHGAA.martin@mii.cz> (raw)
Hi all,
if I use UTF8 for chapter or section title the UTF characters are expanded
to \char XXX and this form is written into tui/tuo file.
But if such character is originally placed at the end of the word after
expansion and tui processing the space after end of word is read out (being
a part of syntax rule \char XXX <space>).
Example:
"Srovnání t-skupin"
in chapter in UTF text results to:
"Srovn\char 225 n\char 237 t-skupin"
and this processed back (e.g. into content) results to:
"Srovnánít-skupin"
Probably this cannot be corrected any way except patching ConTeXt itself --
but if it is possible I do not know how now :-),
thanks,
Martin
--------
Martin Kolarik
Moravske Pristroje, a.s., Masarykova 1148, Zlin 76302
tel. +420 603 498 498, fax +420 577 107 171
web: http://www.mii.cz
--------
e-mail: kolarik@mii.cz
e-mail: kolarik@click.cz
tel. +420 603 535 593
reply other threads:[~2004-08-23 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=NCBBIFBEODPJOENMOHHBCEHJHGAA.martin@mii.cz \
--to=martin@mii.cz \
--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).