public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "nick.andrik at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/12031] iconv -t ascii//translit with Greek characters
Date: Sun, 29 Apr 2012 00:56:00 -0000	[thread overview]
Message-ID: <bug-12031-716-wKNWIDxKtq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12031-716@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Nick Andrik <nick.andrik at gmail dot com> 2012-04-28 19:40:48 UTC ---
Created attachment 6380
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6380
Greeklish trasliteration

I have created a first version of a file to use for greeklish (greek to ascii)
transliteration.

The conversion scheme is:

alpha -> a
beta -> b
gamma -> g
delta -> d
epsilon -> e
zeta -> z
eta -> h
theta -> 8
iota -> i
kappa -> k
lamda -> l
mu -> m
nu -> n
xi -> ks
omikron -> o
pi -> p
ro -> r
sigma -> s
tau -> t
ypsilon -> y
phi -> f
chi  -> x
psi -> ps
omega -> w

From my experiments I realized that there isn't "chained" transliteration.
By this, I mean that I had to specify the greeklish transliterations for all
accented versions of letters, even I had specified for the simply one.

Example:
ETA with PERISPOMENI -> ETA (this is already in translit_combining)
ETA -> H (this is my addition)
If I try to convert "ETA with PERISPOMENI" to ascii then I get ?, I had to edit
it to this:
ETA with PERISPOMENI -> ETA;H

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-04-29  0:56 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 [this message]
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
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-wKNWIDxKtq@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sources.redhat.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).