[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] Add hy-RU to the Pootle translation server


I hope this message is in plain text format (I didn't know the reason for the added tags; thanks for telling it; this problem is new for me). But if the messiness continues in this message also, please, disregard it. Thanks.

> I don't know if and what difference there is between the current 'hy'
> translation and the most common ortography (is it the "Modern"/USSR1940
> Armenian orthography, or something else?) and the proposed hy-RU, but
> please resolve this dispute in a sensible manner.

No difference. And yes, the most common Armenian orthography is the "modern"/USSR1940 one.

I have already sent an extensive explanation to Samvel and am not going to discuss the issue of Armenian locales any more. I sent that message without including  l10n@global.libreoffice.org address to save you from reading my long messy messages.

Best,
Seda


12.07.2019, 20:15, "Eike Rathke" <erack@redhat.com>:
> Hi Stamboltsyan,
>
> On Friday, 2019-07-12 15:13:25 +0400, Stamboltsyan Seda wrote:
>
>>  <div>Samvel,</div><div> </div><div>Your explanation is a mess. What you have explained about hy_AM is the following:</div><div> </div><div>"<span style="font:small monospace">For hy_AM/hye_AM the Institute of Language and Ministry of Education of RA have not yet made the official decision. There is an ongoing work on unified orthography, after completion of which, it will also be implemented under this code. For now we will use either IR or RU variant for this (subject to discussion with the min-edu)."</span></div><div><br />There is NO "ongoing work on unified orthography", as you say. And hy_AM has been used for all these years for the Eastern Armenian (that is, the main language of ARMENIA) with the main orthography used in Armenia. You write: "For now we will use either IR or RU variant for this". Really? Who has decided that? Have you asked the opinion of all the other Armenians of Armenia who are going to use LibreOffice or any other application localized for Armenia?</div><div> </div><div>Once again: the locale name hy_RU for Armenian of ARMENIA is not correct, whether it is used by your organization or some others also. A full stop. Don't attach the name of Russia to the Armenian of Armenia. And there is NO separate Armenian for the Armenians of Russia, which means there just can't be any separate locale for Armenian used in Russia.</div><div> </div><div>Please, don't insist on the wrong decision of minority (like you) against the already established and correct hy_AM.</div><div> </div><div>S.</div>
>
> (Btw, could you *please* teach your mail client to send proper plain
> text as the text/plain message body? Thanks.)
>
> To explain why such crux workaround is necessary from the technical side:
>
> There are 5 variants to write Armenian, as per
> https://bugs.documentfoundation.org/show_bug.cgi?id=116058#c2
> but only 4 distinct language tags. Omitting A.2) 'axm' there leaves us
> with 4 variants and 3 distinct language tags. To resolve that from
> a *technical* point it was addressed with commit
> https://cgit.freedesktop.org/libreoffice/core/commit/?id=01d9d5b491d03004b3690c2a1ff4d99997e02a5a
> which as possible tags added hy-RU and hy-IR.
>
> This has nothing to do with attaching Armenians to Russia or whatsoever.
> This is a technical workaround solution, not a political one.
>
> If the IANA language tag registry knew distinct variant subtags for the
> different ortographies then all this wouldn't be a problem. To properly
> solve this best would be to request such variant subtags, see
> http://langtag.net/register-new-subtag.html
>
> I don't know if and what difference there is between the current 'hy'
> translation and the most common ortography (is it the "Modern"/USSR1940
> Armenian orthography, or something else?) and the proposed hy-RU, but
> please resolve this dispute in a sensible manner.
>
> The 'hy' tag default locale is of course hy-AM and whatever the most
> common ortography used with Eastern Armenian as used in Armenia is
> should be translated under the 'hy' tag.
>
>   Eike
>
> --
> GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
>
> --
> To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
> Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/l10n/
> Privacy Policy: https://www.documentfoundation.org/privacy
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

References:
[libreoffice-l10n] Add hy-RU to the Pootle translation serverԻԴ | Սամվել Հարությունյան <samvel.harutyunyan@realschool.am>
Re: [libreoffice-l10n] Add hy-RU to the Pootle translation serversophi <sophi@libreoffice.org>
Re: [libreoffice-l10n] Add hy-RU to the Pootle translation serverStamboltsyan Seda <sedastam@yandex.com>
Re: [libreoffice-l10n] Add hy-RU to the Pootle translation serverStamboltsyan Seda <sedastam@yandex.com>
Re: [libreoffice-l10n] Add hy-RU to the Pootle translation serverԻԴ | Սամվել Հարությունյան <samvel.harutyunyan@realschool.am>
Re: [libreoffice-l10n] Add hy-RU to the Pootle translation serverStamboltsyan Seda <sedastam@yandex.com>
Re: [libreoffice-l10n] Add hy-RU to the Pootle translation serverEike Rathke <erack@redhat.com>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.