Hello all,
assuming that our Sanskrit locale is unmaintained (just look at the list of contributors in
https://translations.documentfoundation.org/sa_IN/), I just granted Babita all the permissions
necessary for work (in fact, I granted all the permissions that the current locale maintainer had
and the permission to overwrite existing translations on import).
In fact, a lot of Indic languages (incl. Sanskrit, Kashmiri and Dogri) had the same maintainer
until now, who appears to only actually maintain Santali (at least that's the only language where
he is the last contributor: https://translations.documentfoundation.org/sat/). I don't think it
will hurt even if we don't wait for his input when giving permissions on unmaintained languages.
By the way, does anyone know why we are using 'sa_IN' and not just 'sa' as a locale code for
Sanskrit?
Regards,
Rimas
On 2014.07.01 14:53, babita shinde wrote:
Hello,
I have created following user name on pootle server
username:- babitashinde123
Kindly give me an access for localization contribution of Libre office for
Sanskrit language.
Regards,
Babita Shinde
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.