Currently there is only one set of default template for Calc/Writer/....
This default template is good for English contents, but for other languages this template may not be appropriate.
For example, for Simplified Chinese users, different Headings and Body Text styles (font size, line height, paragraph spacing, paper size etc) should be applied in order to fit the Chinese document convention. For other UI languages, they may require much different default styles.
So, we should:
1. Implement different default template per locale, for each LibreOffice component (Calc, Writer, Draw, etc);
2. The template should be put in the "translations" submodule, so that it only takes effect when a certain UI translation is built and installed.
3. When templates for a certain locale does not exist, then it should fallback to the default English template.
Sounds good to me. :D
Over to the UX-advise pile...
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
I don't think that we can provide localized templates for various if not all languages. That's the purpose of the extensions site https://extensions.libreoffice.org/templates
(In reply to Heiko Tietze from comment #4)
> I don't think that we can provide localized templates for various if not all
> languages. That's the purpose of the extensions site
If the localized teams want to provide localized templates that we can bundle, that is a good thing to have, but we need to ask devs how feasible it is to achieve before shooting it down.
We currently have locale specific page sizes, so having locale templates isnt that much of stretch forward.
OpenOffice.org (and AOO) has localized templates as long as I remember. Templates are organized in language-specific folders under share/template. So the question is more, why LibreOffice has not continued that, and whether the reason is still valid.
I would also like to see localized templates in LibO. Most of my customers are not that good in english, so the english templates are not very usefull to them.
Gabor, didn't you implement this request?
(In reply to Heiko Tietze from comment #8)
> Gabor, didn't you implement this request?
No, that was bug #89676 which turned out to just request localized names and in that sense, a duplicate of bug #114088 which is indeed fixed for 6.0.
Localized template content is a completely different beast, I can't tackle it yet.
IIRC, Andras once said these were removed because they raised the installer size considerably.
Installer-Size came to my mind short after I posted my report...
What about adding the localized templates to the offline-Help-Installer? It would become an "localized content installer" then.
That way not all people would benefit from it (because I think most people don't install the offline helpfile) but it wouldn't bloat the installer and it would be better then pointing users to some extension sites...
Maybe the templates can be put into an extension that is automatically downloaded (user install) with the current GUI-Language from an trusted Libo-Server?
Please add keyword 'needsUXEval' and CC 'firstname.lastname@example.org' if input from UX is needed.