From: Oliver Buerschaper <oliver.buerschaper@mpq.mpg.de>
To: mailing ConTeXt users list for <ntg-context@ntg.nl>
Subject: Re: Plea for unicode help
Date: Thu, 5 May 2011 17:12:56 +0200 [thread overview]
Message-ID: <32AF2103-90A3-4956-81DD-F74396731A39@mpq.mpg.de> (raw)
In-Reply-To: <4DC2B270.7080106@elvenkind.com>
>> Awesome hint… hits the nail on the head! The "faulty" version (i.e. the one not appearing in the PDF with Minion Pro) is<dotlessi><acuteaccent> (where<acuteaccent> appears to translate to CC81 in hex, correct?).
>
> Yes. Useful site for find out stuff like that without having to do utf-8 calculations yourself:
>
> http://www.decodeunicode.org/en/u+0301/properties
>
> At the top right, it has numerical values for the current character in various encodings.
This page looks great. Jotted down for later reading ;-)
>> I guess I need to find and replace the accent combination by the direct slot?
>
> That would be wise for now, but I think context should be able to trap this automatically (at least in the mode=node case).
Sounds reasonable. By the way, is the direct encoding generally preferred over the combination method (say, by good Unicode practice ;-)? If yes, I certainly wouldn't mind a little warning message if I happen to use the other variant…
>> Can something similar happen for other "foreign" characters (like ß, umlauts, ae, etc.) or is this sort of error only possible with accents?
>
> IIRC, in principle it can happen with some other characters as well, but I do not think that happens often. It is mostly combining accents.
I see. So umlauts are good candidates to check, too.
Thanks again,
Oliver
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-05-05 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 11:32 Oliver Buerschaper
2011-05-05 11:38 ` Taco Hoekwater
2011-05-05 13:52 ` Oliver Buerschaper
2011-05-05 14:21 ` Taco Hoekwater
2011-05-05 15:12 ` Oliver Buerschaper [this message]
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=32AF2103-90A3-4956-81DD-F74396731A39@mpq.mpg.de \
--to=oliver.buerschaper@mpq.mpg.de \
--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).