![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Hi Cloph,
I'd like to ask you to add LibreOffice Online project to Pootle.
How to make pots:
git clone ssh://logerrit/online
cd online/loleaflet
make pot
pot files are created in po/ directory: loleaflet-ui.pot and
loleaflet-help.pot.
Thanks!
Andras
Hi Andras
This is a great idea!!!
Valter
Hello guys, watssup.
I was wondering if there is a way to create Language Support, other than English.
Is there???
I am not programmer, i have no idea how to build such magic feature like that.
I am able to become language-content contributor, but not developing debuging, and tracking any program. :))))
And maybe LibreOffice can initiate to create spelling and grammar check, for every single language. So it will save many lifes, for not depending their activity on paid office software (If they paid, haha) :))))))
Spelling and grammar check in every language, makes life easier. :))))
Million Thanks.
Andy.
Hi Andyan,
Sgrìobh Andyan G. Raharja na leanas 28/02/2016 aig 02:45:
Hello guys, watssup.
I was wondering if there is a way to create Language Support, other than English.
Is there???
Not sure what you mean, the Help files or live support i.e. where people ask question?
I am not programmer, i have no idea how to build such magic feature like that.
I am able to become language-content contributor, but not developing debuging, and tracking any program. :))))
Well, you might be able to help with translation
And maybe LibreOffice can initiate to create spelling and grammar check, for every single language. So it will save many lifes, for not depending their activity on paid office software (If they paid, haha) :))))))
It's kind of up to each locale in question to handle that, mostly spelling and grammar checks for LO are developed outside LO but offered in LO i.e. the spellcheckers for example are Hunspell extensions.
Spelling and grammar check in every language, makes life easier. :))))
True but with 6000 languages on the planet, LO can't be the one which has to do them all.
Did you have any particular language in mind?
Michael
That 6.000 count only includes natural, living languages. Dead and
extinct languages would probably double that number. Conlangs would
triple, if not quadruple that number.
As is, LibO is perilously close to the maximum number of languages that
can be supported, without undergoing a major UI redesign.
jonathon
That is quite worrying - in what sense do you mean that?
Michael
Sgrìobh toki na leanas 29/02/2016 aig 09:18:
As is, LibO is perilously close to the maximum number of languages
that can be supported, without undergoing a major UI redesign.
That is quite worrying - in what sense do you mean that?
* Ease in selecting the correct language.
Currently, there is a bewildering array of languages and locales, that
most people will never utilize. For those who do, finding the
appropriate one can be challenging.
By way of example, most people don't realize that "Greek, Ancient" is
not "Koine Greek", and that LibO doesn't formally support "Koine Greek".
Whilst using "Greek, Ancient" usually works, both the spell checker and
grammar checker will do a number on one, when one is not paying close
attention.
* Ability to utilize neighbouring, almost supported languages.
By way of example, the minority languages of France. Configure LibO for
one of them, and almost all of the other minority languages are
automatically excluded. (I'll grant that Ethnologue is at least
partially to be blamed for that situation.)
On a slightly more practical/political level, not all of the
semi-official languages of South Africa, can be configured in a single
LibO setup. The same thing applies to India, and its semi-official
languages. (Those two countries rank as having the second largest and
largest number of official languages, and semi-official languages,
respectively, in the world.)
I don't have a good solution to either issue. 
Whilst «country, language, writing system, aeon, modifier» is ostensibly
the simplest approach, spinning that many choices will be overwhelming
for non-power users. (^2)
How many people write Turkish in the Arabic writing system. On the
flipside, enabling that will allow users of Braille, Moon and other A11Y
writing systems to do both spell checking and grammar checking. On the
gripping hand, it will enable one to easily include Xhosa, Pedi, Griqua,
and the rest of the semi-official Khosian languages of South Africa,
without grammar/spelling clashes.
Something that makes language selection slightly more complicated, but
is extremely helpful to those who use unsupported languages, or
neighbouring semi-supported languages, would be three or four "user
language #" in each of the Western, Asian, & CTL language groups.
(There are/were technical & legal reasons why that is no longer provided.)
^2: I think that this modification will also require some changes in the
ODF specifications.
jonathon
Sorry,
What i mean is, i want to know how to create Spelling and Grammar Check, in other language, not just English.
let's say it is like Proofreader and autocorrect featurein Ms Office.
:))))))))))
Sgrìobh toki na leanas 29/02/2016 aig 10:36:
As is, LibO is perilously close to the maximum number of languages
that can be supported, without undergoing a major UI redesign.
Ah ok I get it, you don't mean locales LO is technically able to provide but in terms of practical handling by the end user.
Broadly agree with all your points. I think the whole locale handling of LO needs hauled over from start to finish. I haven't even gotten as far on my list of annoyances as smart locale selection (which is what you seem to be driving at) - just the pure selection of a locale during installation is nuts (even got a bug on it but apart from attracting a troll, not much action https://bugs.documentfoundation.org/show_bug.cgi?id=82184&redirected_from=fdo)
I think if we moved to a langpack approach, we could do a lot more smart stuff i.e. the installer pings the OS for the country and based on that, presents a likely list of locales but with a visible prompt to suggest there is a full list available. But not in the infuriating automated way it does this currently.
By way of example, most people don't realize that "Greek, Ancient" is
not "Koine Greek", and that LibO doesn't formally support "Koine Greek".
Whilst using "Greek, Ancient" usually works, both the spell checker and
grammar checker will do a number on one, when one is not paying close
attention.
Couldn't that be fixed by a better name?
* Ability to utilize neighbouring, almost supported languages.
By way of example, the minority languages of France. Configure LibO for
one of them, and almost all of the other minority languages are
automatically excluded. (I'll grant that Ethnologue is at least
partially to be blamed for that situation.)On a slightly more practical/political level, not all of the
semi-official languages of South Africa, can be configured in a single
LibO setup. The same thing applies to India, and its semi-official
languages. (Those two countries rank as having the second largest and
largest number of official languages, and semi-official languages,
respectively, in the world.)
This is one I've not run into - what do you mean they can't be configured in a single LO setup? As in, I can't pick French, Breton and Basque in one run of the installer or at all?
Plus, since were on the topic, I'll mention the other infuriating habit of LO (and other word processors) which is to actively pull the text locale from the users keyboard. It's driving me and anyone else using keyboard A for language B nuts.
Michael
Ok, starting with spellchecking (if there is none for your language) you'd have to look into building a Hunspell extension https://hunspell.github.io/
At the most primitive level, it's just a wordlist of correctly spelled words at its heart but good spellcheckers get a bit more complex than that.
What language are you missing proofing tools for?
Michael
Sgrìobh Andyan G. Raharja na leanas 29/02/2016 aig 10:54:
Small addendum, I thought I'd filed one - I did but the guy trolling the other bug closed it as resolved even though it isn't so I re-opened it
https://bugs.documentfoundation.org/show_bug.cgi?id=86752
M
Sgrìobh Michael Bauer na leanas 29/02/2016 aig 10:59:
Ah ok I get it, you don't mean locales LO is technically able to provide
but in terms of practical handling by the end user.
For the immediate future, practical handling is critical.
However, there are a couple of technical issues that might be
problematic, were LibO to have support more than a couple of thousand
language/locale combinations.
Broadly agree with all your points. I think the whole locale handling of LO needs hauled over from start to finish.
I haven't even gotten as far on my list of annoyances as smart locale
selection (which is what you seem to be driving at)
I'm not a fan of smart locale selection, mainly because I'm more
familiar with it failing, than operating correctly. (XFCE consistently
generates an error message "unknown locale" because it recognizes
neither the self-selected "smart locale selection", nor my attempts to
fix that selection.)
I think if we moved to a langpack approach, we could do a lot more smart stuff i.e.
That works if the initial selection is for the primary language/locale
that is used.
Whilst using "Greek, Ancient" usually works, both the spell checker and
grammar checker will do a number on one, when one is not paying close
attention.Couldn't that be fixed by a better name?
Naming conventions are based upon ISO/SIL recommendations.
There are 4 ISO 396-3 Codes:
* Cappadocian;
* Modern;
* Mycenaean;
* Ancient;
None of those are Koine Greek.
Whilst the differences between them are subtle, they are enough that
both spell checking and grammar checking fail, if one uses them instead
of Koine Greek. "Fail", as in a significant percentage of false
positives are generated."
This is one I've not run into - what do you mean they can't be
configured in a single LO setup? As in, I can't pick French, Breton and
Basque in one run of the installer or at all?
This depends upon which languages one is wanting to use.
Say one uses both Bastia and Bonifacio. How do you configure LibO so
that the recipient of the document will be able to spell check/grammar
check content in both languages? ISO 639-2 code for both is cos. I
_think_ it is ISO 369-6 that enables office suites, etc. to correctly
differentiate between the two languages.
Thanks! Why loleaflet-ui-XX.po is missing for most of the languages?
Regards,
Andras
Bug in pootle's update_stores that I have yet to pin down.
Languages with "_" in langauge-identifier do get it, all others don't
for some reason and if your langauge-code contains "-" you get
nothing....
i.e. pt_BR has both, fr only help and ca-valencia doesn't appear at
all. Only difference in the on-disk files is "Langauge: lang\n" string
in the po files...
ciao
Christian
Hi Andras, *,
>
> I'd like to ask you to add LibreOffice Online project to Pootle.Sorry it took so long, but it's finally available in Pootle
https://translations.documentfoundation.org/projects/libo_online/Thanks! Why loleaflet-ui-XX.po is missing for most of the languages?
Bug in pootle's update_stores that I have yet to pin down.
Found the cause - the problem that triggers it is that the
basefilename is "loleaflet-ui-<lang>" - the regular expression that
pootle uses starts matching there and then gets confused.
help works since that has enough letters to not be in the match.
Languages with "_" in langauge-identifier do get it,
Since the regular expression also covers an optional region part...
all others don't
for some reason and if your langauge-code contains "-" you get
nothing....
that would also match ca-valencia and kmr-Latn, if only the second
part would be max. three characters..
Solved it by adding a simple substring match instead.
Upstream probably needs to refactor the filename-filter-function to
also pass in the name of the pot, then a universal matching would be
possible.
NOTE: libo_ui and libo_help are not affected, since those use a
one-directory-per-language setup (non-gnu in pootle), and for those
there is no filter, all files in the language directory are read-in
without running a filter on the filename)
android and website project do fall into the bug, but it is not
triggered as the basename of those doesn't contain "-" or "_" (and
there are no ca-valencia and kmr-Latn translations)
ciao
Christian
Hi *,
[…]
Thanks! Why loleaflet-ui-XX.po is missing for most of the languages?
Bug in pootle's update_stores that I have yet to pin down.
FYI: filed https://github.com/translate/pootle/issues/4729 and my
workaround - pootle devs seem to touch this area anyway, so updated
versions will be fixed for everybody 
ciao
Christian
Thanks a lot for your work and the fix Christian
Cheers
Sophie