-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document language in new documents does not respect language settings #496
Comments
I'm having the same exact issue. Except all new documents are in German instead of Danish. I can change the language to Danish after making it. But new documents are always in German. And with spreadsheets also the table names start out in German so that I have to manually change them. I found an old thread talking about replacing template documents in Client detailsOS: Arch Linux Server detailsOperating system: Web server: Database: PHP version: Nextcloud: richdocuments app: Collabora Online: LOOLWSD: 4.0.4 (git hash: 305832f) |
This is because of the locale of the templates shipped with the installation. You can specify your own templates in the settings as a workaround. Eventually this should be fixed in a way that at least empty files can be generated based on user language/locale. It will likely require modifications both in Collabora Online and in richdocuments. |
@thebearon I did not see the option to change the templates in the settings. Is it shipped in an update? I also opened a topic in the Nextcloud Community Support forum. https://help.nextcloud.com/t/how-do-i-change-the-default-language-in-collabora/53667 |
this still seems to be an issue. The per-server and per-user templates option would be the best way to solve this. |
It is currently not possible to change the empty templates, but I guess that would be the best option to avoid issues with the shipped ones. @thebearon The shipped templates don't have any language/locale set, how is the language determined then in collabora? |
@zeigerpuppy It is somewhat possible to change the default templates, see here. Onlyoffice has language default to the personal language of each user. |
Doesn't seem to work. I created template files of each type and copied them into the empty_templates folder in ncdata but every file opened still defaults to German. |
Same on my side... So no way to force a default language in the templates provided other than those already setup? Alternatively, since it's possible to upload your owns, is there a way to remove the "empty" ones as provided during installation (I guess)? |
@thebearon I was thinking if we could somehow change the language that is used in the empty template files on the fly? Do you have any hint where the language is set in those templates? |
You can create language agnostic template files, and the language will be set to the UI language. See e.g. https://cgit.freedesktop.org/libreoffice/online/commit/?id=a66083de9b35034c79fae29b4a1c08a0fc2682de |
This should be fine after fb68779. |
@thebearon cannot confirm, seeing this still with richdocuments 3.7.11 |
Make sure to run |
Just tried the occ command and got:
|
That is actually a mail issue: nextcloud/mail#4102 |
thank you, that did the trick! |
Describe the bug
When a new document is created, the document language is always set to English (USA), although language and locale are set to German (informal) and Germany.
The document language can be set to German in the menu and is correctly preserved when the document is closed and reopened.
Choosing the "Reset to default language" option in the menu seems to have no effect, neither when English is the current document language, nor when German is. The command seems to be ignored.
Expected behavior
Collabora should respect the language settings when new documents are created.
Screenshots
Client details:
Server details
Operating system:
Shared Webhosting
Web server:
Apache
Database:
MySQL 5.7.25
PHP version:
7.2.13
Nextcloud version:
15.0.5
Version of the richdocuments app
3.3.2
Version of Collabora Online
CODE 4.0.1-1
The text was updated successfully, but these errors were encountered: