From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.help Subject: Re: How to translate LaTeX into UTF-8 in Elisp? Date: Tue, 04 Jul 2017 07:55:19 +0200 Message-ID: <87podg21bs.fsf@jane> References: <87shpyfj2q.fsf@mbork.pl> <87bmp2rud7.fsf@jane> <87y3s6vzwg.fsf@debian.uxu> <87van9dgo3.fsf@jane> <20170703093138.GA20828@tuxteam.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1499147773 31708 195.159.176.226 (4 Jul 2017 05:56:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 4 Jul 2017 05:56:13 +0000 (UTC) User-Agent: mu4e 0.9.19; emacs 26.0.50 Cc: help-gnu-emacs@gnu.org, Emanuel Berg To: tomas@tuxteam.de Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jul 04 07:56:07 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dSGoZ-0007bI-7j for geh-help-gnu-emacs@m.gmane.org; Tue, 04 Jul 2017 07:55:59 +0200 Original-Received: from localhost ([::1]:38739 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSGoe-0001ur-NE for geh-help-gnu-emacs@m.gmane.org; Tue, 04 Jul 2017 01:56:04 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33372) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSGoB-0001uh-CB for help-gnu-emacs@gnu.org; Tue, 04 Jul 2017 01:55:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dSGo7-0002vb-4U for help-gnu-emacs@gnu.org; Tue, 04 Jul 2017 01:55:35 -0400 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:39896) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSGo6-0002vT-UB for help-gnu-emacs@gnu.org; Tue, 04 Jul 2017 01:55:31 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 66CCEE6669; Tue, 4 Jul 2017 07:55:29 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwU7wMfbYNSk; Tue, 4 Jul 2017 07:55:24 +0200 (CEST) Original-Received: from localhost (static-dwadziewiec-jedenpiec7.echostar.pl [109.232.29.157]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 759C8E62DE; Tue, 4 Jul 2017 07:55:24 +0200 (CEST) In-reply-to: <20170703093138.GA20828@tuxteam.de> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.110.48.8 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:113683 Archived-At: 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 wrote: >> >> > Marcin Borkowski 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