public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "egor at kobylkin dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/12031] iconv -t ascii//translit with Greek characters
Date: Sat, 10 Aug 2019 09:25:00 -0000	[thread overview]
Message-ID: <bug-12031-716-4mmcLfRP2H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12031-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12031

--- Comment #16 from Egor Kobylkin <egor at kobylkin dot com> ---
AFAIK there are many versions of transcription tables for Greek to ASCII
transcription. Given that current iconf logic can only translit one to many but
not many to many symbols we take the "Standard" part of the following table

https://en.wikipedia.org/wiki/Romanization_of_Greek#Modern_Greek

and only keep the one letter Greek graphems. That "standard" seems to be close
to the ELOT 743 indeed but not the same. 

So we omit things like M and Μπ being transliterated as M and B accordingly.
Rather Μπ will be treated like two separate graphems and transliterated as Mp. 


Here is the list of some standards I have collected so far. There doesn't seem
a way to harmonize them all into one. But if anyone want to propose a solution
- please do.

+ ΕΛΟΤ 743 https://www.teicrete.gr/users/kutrulis/Ergalia/ELOT743.htm
Passports.
+ ISO 843 https://en.wikipedia.org/wiki/ISO_843
+ ALA-LC https://www.loc.gov/catdir/cpso/romanization/greek.pdf Book titles.
+ BGN/PCGN http://libraries.ucsd.edu/bib/fed/USBGN_romanization.pdf 
http://geonames.nga.mil/gns/html/Romanization/Romanization_Greek.pdf
Geographical names.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2019-08-10  9:25 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
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 [this message]
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 ` cvs-commit at gcc dot gnu.org
2019-11-26 11:43 ` fweimer at redhat dot com

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=bug-12031-716-4mmcLfRP2H@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@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).