From: Keld Simonsen <keld@keldix.com>
To: pere at hungry dot com <sourceware-bugzilla@sourceware.org>
Cc: libc-locales@sourceware.org
Subject: Re: [Bug localedata/12031] iconv -t ascii//translit with Greek characters
Date: Mon, 04 May 2015 21:10:00 -0000 [thread overview]
Message-ID: <20150504211045.GB5988@rap.rap.dk> (raw)
In-Reply-To: <bug-12031-716-92V4IFXnD5@http.sourceware.org/bugzilla/>
On Mon, May 04, 2015 at 09:00:36PM +0000, pere at hungry dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=12031
>
> --- Comment #9 from Petter Reinholdtsen <pere at hungry dot com> ---
> (In reply to Mike FABIAN from comment #8)
>
> > I am a bit puzzled about à ->
> > AE, shouldn???t this be transliterated to Ae, even in English locales?
> > (Same with Ã, transliterating to just O or maybe Oe in
> > translit_neutral for all locales which do not have special rules
> > seems better.
>
> For me it make more sense to transliterate a capital letter to all capital
> letters, to ensure words with only capital letters look sane. For example
> SÃRING would end up like SOERING, not SOeRING. Sure, if the capital letter is
> the first one in the sentence, it would make more sense to use Ãvelse ->
> Oevelse,
> but I suspect special norwegian characters at the start of the sentence
> is less common than capital special norwegian letters in an all capital word.
> Most Norwegian words do not start with æ, ø or å. :)
The same goes for Danish which due to some common hertiage use the same letters
and to some extent the same transliteration rules.
I would also recommend transliterating Ã, Ã, Ã
to AE, OE, AA
Best regards
Keld
next prev parent reply other threads:[~2015-05-04 21:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12031-716@http.sourceware.org/bugzilla/>
2011-05-15 7:32 ` drepper.fsp at gmail dot com
2011-09-24 7:14 ` mistresssilvara at hotmail dot com
2012-02-03 19:48 ` alexander.karlstad at gmail dot com
2012-02-04 11:59 ` pere at hungry dot com
2012-04-29 0:56 ` nick.andrik at gmail dot com
2014-02-16 21:31 ` jackie.rosen at hushmail dot com
2014-05-28 19:54 ` schwab at sourceware dot org
2014-06-26 5:16 ` pravin.d.s at gmail dot com
2014-06-30 9:14 ` fweimer at redhat dot com
2015-05-04 20:40 ` maiku.fabian at gmail dot com
2015-05-04 21:07 ` pere at hungry dot com
2015-05-04 21:10 ` Keld Simonsen [this message]
2015-05-04 21:13 ` keld at keldix dot com
2015-05-27 7:06 ` myllynen at redhat dot com
2015-09-18 9:29 ` ekobylkin at paypal dot com
2015-09-18 16:39 ` ekobylkin at paypal dot com
2019-08-07 7:44 ` egor at kobylkin dot com
2019-08-07 7:49 ` egor at kobylkin dot com
2019-08-07 14:34 ` myllynen at redhat dot com
2019-08-10 9:25 ` egor at kobylkin dot com
2019-08-12 7:17 ` myllynen at redhat dot com
2019-09-02 15:28 ` egor at kobylkin dot com
2019-09-04 7:01 ` egor at kobylkin dot com
2019-09-04 7:07 ` egor at kobylkin dot com
2019-09-07 14:45 ` egor at kobylkin dot com
2019-11-26 11:43 ` fweimer at redhat dot com
2019-11-26 11:43 ` cvs-commit at gcc dot gnu.org
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150504211045.GB5988@rap.rap.dk \
--to=keld@keldix.com \
--cc=libc-locales@sourceware.org \
--cc=sourceware-bugzilla@sourceware.org \
/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).