From: "S. Champailler" <schampaillerspam@skynet.be>
To: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Is there a way to "asciify" a string?
Date: Thu, 31 May 2018 17:08:47 +0200 (CEST) [thread overview]
Message-ID: <1408913120.160961.1527779327833@webmail.appsuite.proximus.be> (raw)
In-Reply-To: <jwvpo1b29d0.fsf-monnier+gmane.emacs.help@gnu.org>
I second that, removing accents and other "nationalities" is much trickier than one might expect (you can look at Java example, the Java unicode support is quite complete), especially for lanugages far away from english such as russian. By "tricky" I mean there are *hundreds* of edge cases. Nevertheless, there are ways do sort of do what you want by playing with thigsn such as "non spacing combining characters", "normalized strings", etc. If you have the opportunity, just try to do it, the great lesson you'lll get of that is that human languages are super complexe (and thus super interesting).
Today, everyone should use Unicode, it's much simpler. Many file systems support unicode.
stF
> Le 31 mai 2018 à 16:23, Stefan Monnier <monnier@iro.umontreal.ca> a écrit :
>
>
> > Still, I need something *simple*. I have a person's name (possibly with
> > some national characters), and I want to derive a filename from it.
>
> I really strongly recommend you try to solve this problem by doing
> nothing: keep the name in its full glory. Nowadays users *should*
> expect this to work.
>
>
> Stefan
>
>
next prev parent reply other threads:[~2018-05-31 15:08 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
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 [this message]
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=1408913120.160961.1527779327833@webmail.appsuite.proximus.be \
--to=schampaillerspam@skynet.be \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).