| Summary: | Missing language names in the LO Windows installer | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Petr Mladek <pmladek> |
| Component: | Libreoffice | Assignee: | Don't use this account, use tml@iki.fi <tlillqvist> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | andre.schnabel, gautier.sophie, jlc |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Screenshot whowing the problem. | ||
for tor I guess More specifically, the strings in question are: STR_NAME_MODULE_LANGPACK_BO STR_NAME_MODULE_LANGPACK_OC STR_NAME_MODULE_LANGPACK_OM STR_NAME_MODULE_LANGPACK_SI STR_NAME_MODULE_LANGPACK_UG The language codes mean: bo = Tibetan, oc = Occitan, om = Oromo, si = Sinhalese, ug = Uyghur. Would it be enough to add entries for these to scp2/source/ooo/module_langpack.ulf ? Probably. Did that. Note that this breaks the string freeze that I think is in force for the libreoffice-3-3 branch. Closing - Sophie |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 39376 [details] Screenshot whowing the problem. I tried to enable more localizations in the custom installation of LibO_3.3.0_beta2_Win_x86_install_multi.exe. I saw STR_NAME_MODULE_LANGPACK_XX instead of human readable language name in some cases. Steps to reproduce: 1. Start LibO_3.3.0_beta2_Win_x86_install_multi.exe 2. Select custom installation 3. Try to enable more optional localizations See a also the attached screenshot.