unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: How to translate LaTeX into UTF-8 in Elisp?
Date: Tue, 04 Jul 2017 13:18:43 +0200	[thread overview]
Message-ID: <87mv8kfo18.fsf@fastmail.fm> (raw)
In-Reply-To: <87bmp2rud7.fsf@jane>


On Mon, Jul 03 2017, Marcin Borkowski wrote:
> On 2016-12-08, at 18:04, Marcin Borkowski <mbork@mbork.pl> 
> wrote:
>
>> Hi all,
>>
>> I have a string with embedded sequences like "\'e" or "\H{o}". 
>> The
>> Emacs TeX input method knows how to convert them into "é" or 
>> "ő" (when
>> typing, of course).  Is there a way to use that to perform 
>> similar
>> conversions in a string?
>
> Hi all,
>
> I'm revisiting this old thread now.  Since I got no satisfying 
> answers
> back then, here is my plan for solution.  I'm going first to map 
> \', \`
> etc. onto /names/ (this is a rather short list!), construct a 
> Unicode
> name of the character I want and then use =ucs-names=.
>
> For instance, \' maps to "ACUTE", then \'a will map to "LATIN 
> SMALL
> LETTER A ACUTE" and this can be fed into =char-from-name=.
>
> It is a horrible hack, but it should work.  Any better ideas?

Have you tried looking into the input method mechanism that 
translates "\'e" into "é"? The info on how do such translations is 
stored somewhere somehow, so it should in principle be possible to 
use it to do the translations you want. I don't know very much 
about quail (I define a few custom input methods in my init files, 
but that's about it), but it looks like the info is stored as an 
alist somewhere of the form ("\\'e" ?é).

Perhaps you've already explored this idea and found it too 
unwieldy, but you didn't mention it anywhere. 



-- 
Joost Kremers
Life has its moments



      parent reply	other threads:[~2017-07-04 11:18 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
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 [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

  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=87mv8kfo18.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@mbork.pl \
    /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).