help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to translate LaTeX into UTF-8 in Elisp?


From: Marcin Borkowski
Subject: Re: How to translate LaTeX into UTF-8 in Elisp?
Date: Tue, 04 Jul 2017 07:55:19 +0200
User-agent: mu4e 0.9.19; emacs 26.0.50

On 2017-07-03, at 11:31, tomas@tuxteam.de wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, Jul 03, 2017 at 11:16:12AM +0200, Marcin Borkowski wrote:
>> 
>> On 2017-07-03, at 07:43, Emanuel Berg <moasen@zoho.com> wrote:
>> 
>> > Marcin Borkowski <mbork@mbork.pl> writes:
>> >
>> >> I'm revisiting this old thread now. Since I got no
>> >> satisfying answers back then, here is my plan for
>> >> solution [...]
>
>> > If you setup the names consistently it is even
>> > a good-looking solution.
>
> [...]
>  
>> I'm not sure whether I follow you here.  Why should *I* setup the names?
>> They are in ucs-names (as I said), and they are official Unicode names.
>> 
>> It is still a hack, since it relies on the Unicode names being correct.
>> Have you seen this?
>> 
>> https://codepoints.net/U+FE18?lang=en
>> 
>> Notice the typo in the name.  It's in the standard (somehow it slipped
>> through;-)), so the typo is there forever (or rather, for as long as
>> Unicode is going to be around).
>
> Yes: they even listed a "correction". Unicode (and Emacs) seem to have
> a mechanism in place for a code point to have more than one name (I
> don't know whether there can be more than two, though). So perhaps the
> only thing to cope with is that the mapping name -> code point isn't
> injective (whatever that means for your approach)?

Interesting.  The "other" name doesn't appear in (ucs-names), though, so
it's not useful for me here.  In any case, I am aware of no such typos
in accented letters anyway;-).

Best,

-- 
Marcin Borkowski



reply via email to

[Prev in Thread] Current Thread [Next in Thread]