I am using collabora/code:23.05.5.3.1 in a container environment.
Two questions here:
1- How to add a UI language and make it default? I can’t find it in the docs.
2- My instance has the necessary dictionary files out of the box for my desired language, but spellchecking doesn’t list that language on the UI. How to make it available an already installed language? And how to update those language files later? Is only downloading newer .aff and .dic files and overwriting enough?
<allowed_languages desc="List of supported languages of Writing Aids (spell checker, grammar checker, thesaurus, hyphenation) on this instance. Allowing too many has negative effect on startup performance." default="de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru">de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru</allowed_languages>
Thank you @Tex, I enabled the desired language for spellchecking with the environment variable as you pointed out.
But I don’t understand how changing URL parameters will work through Collabora Online docker image? I am using Nextcloud for cloud storage and set it to use CODE server to edit files online which doesn’t involve direct URLs of Collabora. How to apply it?
Secondly, would overriding dictionary files with new versions be enough for updating them?
I know that they automatically handle the UI language based on user. So:
A German user would automatically get the German UI.
An English user would automatically get the English UI.
I did a search through their code for the word “language”, and I think this might be the files (url.js + index.js) where they work their URL-substitution magic:
Thank you for you time. About the UI language, I think I will need to ask it in Nextcloud forums.
About spell-checking: how to set a default language system wide? Everytime I open a document, English (USA) is the default one. Because my Nextcloud UI is already a different language but Collabora is still displayed in English.
No, only for updating I asked. Because the dictionary versions shipped with Collabora is a bit old.
We could probably get that change submitted over to Github and merged for the upcoming versions.
Side Note: On another forum + another open-source software I use, a Spanish user just appeared and informed them the Spanish dictionary was way out of date. Turns out, the same maintainer split off and created:
Yes quite right. I suggested this because as you noticed, comparison stats are better and it is already a fork and updated version.
To be honest, I haven’t tested thoroughly, I am just keen on updated versions Because you know, languages are alive and continue evolving. And the one which LibreOffice uses right now actually seems abandoned.