unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Drew Adams <drew.adams@oracle.com>
Cc: John Mastro <john.b.mastro@gmail.com>,
	Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Is there a way to "asciify" a string?
Date: Thu, 07 Jun 2018 19:15:32 +0200	[thread overview]
Message-ID: <87k1rav7pn.fsf@mbork.pl> (raw)
In-Reply-To: <68db4874-d7c2-4f4c-837e-1f0db59de7fc@default>


On 2018-06-03, at 00:33, Drew Adams <drew.adams@oracle.com> wrote:

>> My use case is much, much simpler than much of the stuff mentioned in
>> this thread.  99.5% (or more) of the cases are Polish names, where we
>> have only 9 "offending" letters, all easily asciified.  I thought there
>> is a simple, general solution (and I learned there isn't and probably
>> there can't be).
> ...
>> KISS
>
> If you want a really rudimentary, KISS solution along those
> lines, just apply a set of mappings of the chars you're
> interested in.
>
> I used that approach in the last millenium, in `unaccent.el'
> (and I still use it occasionally).
>
> I was interested only in translating letters with trema/umlaut,
> circumflex, grave & acute accents, cedilla, tilde, S-zed,
> guillemets, ae ligature, slashed O, angstrom, and upside-down
> question mark & exclamation point - so my translation alist
> contained only those mappings.  But you could using any
> mapping, just by redefining variable `reverse-iso-chars-alist'
> (not a good name, considering its generality, but that's what
> I was using it for).
>
> https://www.emacswiki.org/emacs/download/unaccent.el

Thanks, that's a good idea, although I was too lazy to perform all these
mappings myself and used the function mentioned earlier in the thread to
shave off all the accents.

Best,

-- 
Marcin Borkowski
http://mbork.pl



  reply	other threads:[~2018-06-07 17:15 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-27  6:22 Is there a way to "asciify" a string? Marcin Borkowski
2018-05-27  7:36 ` tomas
2018-05-27 12:36   ` Marcin Borkowski
2018-05-27 12:52     ` Teemu Likonen
2018-05-27 16:07       ` Eli Zaretskii
2018-05-27 16:59         ` Teemu Likonen
2018-05-28  5:24           ` Tak Kunihiro
2018-05-30 10:12           ` Marcin Borkowski
2018-05-30 17:05             ` Eli Zaretskii
2018-05-30 19:38               ` Marcin Borkowski
2018-05-27 20:00         ` tomas
2018-05-28 18:27           ` Eli Zaretskii
2018-05-29  6:37             ` tomas
2018-05-27 13:04     ` Yuri Khan
2018-05-30 10:14       ` Marcin Borkowski
2018-05-30 11:51         ` Yuri Khan
2018-05-30 15:04           ` Marcin Borkowski
2018-05-31  2:03       ` John Mastro
2018-06-02 18:07         ` Marcin Borkowski
2018-06-02 18:48           ` tomas
2018-06-07 17:16             ` Marcin Borkowski
2018-06-02 22:33           ` Drew Adams
2018-06-07 17:15             ` Marcin Borkowski [this message]
2018-06-02 18:12         ` Marcin Borkowski
2018-05-27 19:53     ` tomas
2018-05-28  8:15     ` Philipp Stephani
2018-05-28 10:28       ` Marcin Borkowski
2018-05-28 10:39         ` tomas
2018-05-28 15:30           ` Yuri Khan
2018-05-28 16:02             ` tomas
2018-05-30 10:12           ` Marcin Borkowski
2018-05-31 14:23     ` Stefan Monnier
2018-05-31 15:08       ` S. Champailler
2018-05-31 22:52         ` Richard Wordingham
2018-05-31 15:42       ` Marcin Borkowski
2018-05-31 15:53         ` Eli Zaretskii
2018-05-31 16:20           ` Yuri Khan
2018-05-31 19:03           ` Stefan Monnier
     [not found]       ` <mailman.871.1527781438.1292.help-gnu-emacs@gnu.org>
2018-05-31 23:23         ` James K. Lowden
2018-06-01  2:04           ` Stefan Monnier
2018-06-01  7:02           ` Eli Zaretskii
2018-05-27 14:55 ` Eric Abrahamsen
2018-05-27 16:00 ` Eli Zaretskii

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=87k1rav7pn.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=john.b.mastro@gmail.com \
    /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).