How do I change the default language in Collabora?

When installing Nextcloud with Collabora you have the option to choose dictionaries that can be used in Collabora. The problem is that when you create a new Collabora document, the default language of the document is always ‘German’, independent of what languages you chose.

For a long time the solution to this issue has been changing the template files in the core/templates/filetemplates folder as is explained in this topic:

But this solution is not working anymore, as you can see in that topic. So I open a new topic to raise this issue again, in search for a new solution. Does anyone have ideas?

All the best,

P.S I installed Collabora & Nextcloud using this playbook: . Those all update to the latest versions (NC16.0.1).

The issue is also raised in the Nextcloud repo:

Yesterday I installed Collabora and indeed noticed the default language in new documents to be German. Searching for a solution led me here. Since the file path mentioned in various conversations did not work I did a search for such templates in the nextcloud tree om my server.
It seems that now the Collabora app installs its own templates in the apps/richdocuments/assets/ subdirectory. I made English templates with LibreOffice on my desktop and copied these to that subdirectory on my cloud server and that solved the issue, at least for me.
Hope this info is useful for someone.


@haro Thanks. Your solution was the right one for me.

But I wonder why this is managed this way.
How do we do when you need several languages, depending on the person who’s using Lool.

Why not detect the preferred browser languages or the nextcloud webui language of the user and use it first.

And if not set then use a default template.

@quenenni You are right and I do not know why the current setup was chosen.
Providing templates for all possible languages in the app itself is not doable. Ideally a language neutral template should be provided which could complete itself once the user chooses the preferred language when opened on LibreOnline. That way the user can select the language preferable for that document and only be limited by the lanuages installed in LibreOnline.
Another option might be that the installer has a section where the admin is informed that such templates need to be provided in the various languages desired and where to store them.
Either way, as I am not involved the development of these tools, I do not know where it will go.