Request for the addition of Santali (Ol Chiki) langauge

l10n
#1

Hi,
Myself Prasanta Hembram from India. I want to help translate Libre
office in the Santali language with the Ol Chiki script. Weblate seems
to support Santali but someone has already contributed in a different
script (in Devanagari script). I request developers to kindly add
Santali (Ol Chiki) to the weblate.

#2

Hi Prasanta,

First of all, welcome to the localization team!

Hi,
Myself Prasanta Hembram from India. I want to help translate Libre
office in the Santali language with the Ol Chiki script. Weblate seems
to support Santali but someone has already contributed in a different
script (in Devanagari script). I request developers to kindly add
Santali (Ol Chiki) to the weblate.

Could you confirm that olck is the right language code and also that it's a left to right language?
Thanks in advance,
Cheers
Sophie

#3

Thanks for the reply Sophie, I confirm that Olck is the right script code
and may be written as sat@olck or sat_olck

Santali language has ISO 639 code "sat" and script code "Olck". Also this
language is written from left to right with Ol Chiki script.

Plural-Forms: nplurals=3; plural=n==1 ? 0 : n==2 ? 1 : 2

with best regards
Prasanta Hembram

#4

Hi Prasanta,

Thanks for the reply Sophie, I confirm that Olck is the right script code
and may be written as sat@olck or sat_olck

Santali language has ISO 639 code "sat" and script code "Olck". Also this
language is written from left to right with Ol Chiki script.

Plural-Forms: nplurals=3; plural=n==1 ? 0 : n==2 ? 1 : 2

Thanks, with all that, I can create the language in Weblate.
Do you have an account in Weblate already? if not please create one and let me know your username or mail address you used there, so I can create the corresponding language group and give you rights.
Cheers
Sophie

#5

Hi,

Thanks for the reply Sophie, I confirm that Olck is the right script code
and may be written as sat@olck or sat_olck

The correct BCP47 language tag is sat-Olck not sat@olck nor sat_olck.

  Eike

#6

Hi Eike,

Hi,

Thanks for the reply Sophie, I confirm that Olck is the right script code
and may be written as sat@olck or sat_olck

The correct BCP47 language tag is sat-Olck not sat@olck nor sat_olck.

Yes, thanks, this is how I wrote it in Weblate, Christian also pointed it to me :slight_smile:
Cheers
Sophie

#7

Hello, Eike
Apology and thanks for correcting my wrong suggestion, you are right Eike
according to CLDR (
https://unicode-org.github.io/cldr-staging/charts/37/supplemental/languages_and_scripts.html)
it is correct. I was little confused with the arbitrary use of @ and _
while translating various software like. Inkscape (
https://gitlab.com/inkscape/inkscape/-/tree/master/po) that uses "sat" and
sat@deva. and the same for sat_olck in other projects. In linux they use
something different like sat_IN for some reason. I'm still not able to
understand how code pairing is done, but they work :-/

As, Ol Chiki is now the official script for Santali language which means,
the code "sat" should mean same as "sat-Olck" but here in Weblate (Libre)
already "sat" code is occupied with Devanagari writings, means current
"sat" code assigned in Libre (
https://translations.documentfoundation.org/languages/sat/) should be
"sat-Deva" *my question* is will it not cause any confusion in future
related to default script for Santali language. As for Santali Wikipedia (
https://sat.wikipedia.org) and in many places "sat" is the default code
where the Ol-Chiki script is used. If anyone wishes to write in another
script then let them change to their lexeme language codes like sat-Deva,
sat-Latn, sat-Beng, sat-Orya etc. If it will cause little or no issue tyhem

#8

Sophi should i start the localisation in weblate for Santali-Olck.
https://translations.documentfoundation.org/languages/sat-Olck/libo_ui-master/
or wait a bit.

#9

Hi Prasanta,

Sophi should i start the localisation in weblate for Santali-Olck.
https://translations.documentfoundation.org/languages/sat-Olck/libo_ui-master/
or wait a bit.

You can go on, I've added you as admin of your language, meaning that you can translate and also review others suggestions.

There is a translation guide here:
https://wiki.documentfoundation.org/UI_and_Help_files_Content_Guide
please give a special attention to unique terms in UI.
Don't hesitate to come back to me if you have any questions.

Cheers
Sophie

#10

Hello Sophie,
Again, Thank you so much for your kind support. I have read the translation
guide and stick to it. Soon, I will start my translation for this beautiful
language. I will definitely share any issues I face during translation.

#11

Hi,

while translating various software like. Inkscape (
https://gitlab.com/inkscape/inkscape/-/tree/master/po) that uses "sat" and
sat@deva. and the same for sat_olck in other projects. In linux they use
something different like sat_IN for some reason. I'm still not able to
understand how code pairing is done, but they work :-/

As, Ol Chiki is now

Now? Since when?

the official script for Santali language which means,
the code "sat" should mean same as "sat-Olck" but here in Weblate (Libre)
already "sat" code is occupied with Devanagari writings, means current
"sat" code assigned in Libre (
https://translations.documentfoundation.org/languages/sat/) should be
"sat-Deva"

The 'sat' with the default sat-IN locale suppressing the Devanagari
script was added already in 2008, back then BCP47 wasn't used and proper
language tags mostly unknown and not supported (and not even today by
many software). It also seems that the Linux sat_IN locale actually
implies Devanagari. See https://lh.2xlibre.net/locale/sat_IN/ that in
Dates (LC_TIME) uses Devanagari letters.

*my question* is will it not cause any confusion in future
related to default script for Santali language.

Yes, that may be. The remedy would be to explicitly state the script and
not rely on omitted defaults, in fact the IANA language subtag registry
https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
does not list any Suppress-Script for 'sat'.

For document content written by LibreOffice that can easily be done
fiddling with the language code mapping tables, reading sat/sat-IN
should still default to sat-Deva-IN though to not break existing
documents and map the sat_IN locale properly.

For the UI translations we probably could change 'sat' to an explicit
sat-Deva, at least it's doable in code and hopefully also in Weblate,
but it needs to be coordinated and as long as we map sat/sat-IN to
sat-Deva/sat-Deva-IN it shouldn't really matter.

  Eike