From: Marcin Borkowski <mbork@mbork.pl>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org, Emanuel Berg <moasen@zoho.com>
Subject: Re: How to translate LaTeX into UTF-8 in Elisp?
Date: Tue, 04 Jul 2017 07:55:19 +0200 [thread overview]
Message-ID: <87podg21bs.fsf@jane> (raw)
In-Reply-To: <20170703093138.GA20828@tuxteam.de>
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
next prev parent reply other threads:[~2017-07-04 5:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 17:04 How to translate LaTeX into UTF-8 in Elisp? Marcin Borkowski
2016-12-08 18:21 ` Carlos Konstanski
2016-12-08 19:13 ` Marcin Borkowski
2016-12-08 22:12 ` Stefan Monnier
2017-01-27 11:48 ` Marcin Borkowski
2017-01-28 8:15 ` Kendall Shaw
2017-07-03 4:56 ` Marcin Borkowski
2017-07-03 5:43 ` Emanuel Berg
2017-07-03 9:16 ` Marcin Borkowski
2017-07-03 9:31 ` tomas
2017-07-04 5:55 ` Marcin Borkowski [this message]
2017-07-03 10:24 ` Emanuel Berg
2017-07-03 17:36 ` Marcin Borkowski
2017-07-03 20:01 ` Emanuel Berg
2017-07-04 10:23 ` Héctor Lahoz
2017-07-03 8:37 ` Teemu Likonen
2017-07-04 5:57 ` Marcin Borkowski
2017-07-04 7:13 ` Udyant Wig
2017-07-04 9:27 ` Thien-Thi Nguyen
2017-07-04 20:37 ` Emanuel Berg
2017-07-05 7:05 ` Udyant Wig
2017-07-05 16:06 ` Emanuel Berg
2017-07-13 17:45 ` Thien-Thi Nguyen
2017-07-14 1:48 ` Udyant Wig
2017-07-04 11:18 ` Joost Kremers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87podg21bs.fsf@jane \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=moasen@zoho.com \
--cc=tomas@tuxteam.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).