Skip Menu |

This queue is for tickets about the Lingua-Translit CPAN distribution.

Report information
The Basics
Id: 57725
Status: resolved
Priority: 0/
Queue: Lingua-Translit

People
Owner: ALINKE [...] cpan.org
Requestors: toapole [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Could you add something like "Streamlined System RUS"?
It should same as "Streamlined System BUL" but with to more chars: 'ы' -> 'y' 'ё' -> 'yo' 'Ы' -> 'Y' 'Ё' -> 'YO'
There actually is a Streamlined System for Russian with some additions and changes to the Bulgarian version. We would like to stick to the official proposals. Here are the differences: * the hard sign and the soft sign are not transliterated at all * 'ы' -> 'i' * 'ё' -> 'e' * 'э' -> 'e' We could add this transliteration in the next version which is about to be released within the next couple of weeks. Do you think the transliteration is appropriate or is there an official or commonly used transliteration scheme for Russian that results in plain ASCII you can name?
From: toapole [...] gmail.com
On Tue May 25 12:09:36 2010, ALINKE wrote: Show quoted text
> There actually is a Streamlined System for Russian with some additions > and changes to the Bulgarian version. We would like to stick to the > official proposals. > > Here are the differences: > > * the hard sign and the soft sign are not transliterated at all > * 'ы' -> 'i' > * 'ё' -> 'e' > * 'э' -> 'e' > > We could add this transliteration in the next version which is about
to Show quoted text
> be released within the next couple of weeks. > > Do you think the transliteration is appropriate or is there an
official Show quoted text
> or commonly used transliteration scheme for Russian that results in > plain ASCII you can name?
Hello http://en.wikipedia.org/wiki/Romanization_of_Russian Check out the last column (Passport 2003). It seems to be "ГОСТ 16876- 71, СТ СЭВ 1362-78" according http://ru.wikipedia.org/wiki/%D0%A2%D1%80%D0%B0%D0%BD%D1%81%D0%BB%D0%B8% D1%82%D0%B5%D1%80%D0%B0%D1%86%D0%B8%D1%8F_%D1%80%D1%83%D1%81%D1%81%D0%BA %D0%BE%D0%B3%D0%BE_%D0%B0%D0%BB%D1%84%D0%B0%D0%B2%D0%B8%D1%82%D0%B0_%D0% BB%D0%B0%D1%82%D0%B8%D0%BD%D0%B8%D1%86%D0%B5%D0%B9
We have been planing to add GOST (16876-71) before but haven't found the time to implement it, yet. So in order to provide a plain ASCII transliteration of Russian, I think it would be best to stick to GOST, because this transliteration scheme seems to be quiet common. Would that be a practical solution for your application of Lingua::Translit, too? Just curious, what kind of application are you using Lingua::Translit in?
From: toapole [...] gmail.com
GOST will be good. But "Passport 2003" seems to be more modern and usable. http://mvd.consultant.ru/doc.asp?ID=51135&PSC=1&PT=3&Page=5 In case of "Passport 2003", pronunciation is better also. I'm using your module to create readable URL part for blog/news posts in web-apps.
Ok, after doing some more research I think it's appropriate to add both transliterations to Lingua::Translit, because each may be particular useful in its own domain. As a result, both "Passport 2003" and "GOST (16876-71)" will be added to the next version of Lingua::Translit (v0.18). Thanks for the request and the hint on Passport 2003!
From: toapole [...] gmail.com
Thank you for the good module!
GOST 7.79 replaces GOST 16876-71 - but includes (basically) the same transliteration rules - at least for "table B". As a result, I just uploaded v0.18 which includes support for GOST 7.79:2000 (tables B) for Russian and Ukrainian. Passport 2003 may follow in a future release...