<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Default Installer Language" href="https://bugs.documentfoundation.org/show_bug.cgi?id=63827#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Default Installer Language" href="https://bugs.documentfoundation.org/show_bug.cgi?id=63827">bug 63827</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>The UI language of the installer is defined by ProductLanguage property [1]. It automatically selects the built-in language transform. The command line to run LO MSI installer in any supported language is > msiexec /i LibreOffice_X.Y.Z_Win_x64.msi ProductLanguage=1033 where 1033 is for en-US; the value is decimal LCID number [2]. Note that the [MS-LCID] document lists the IDs in hexadecimal, e.g. 0x0409 for en-US. It should be noted that msiexec sets this value itself if it's 0, and it's msiexec which reads HKEY_CURRENT_USER\Control Panel\International values, however that could be counter-intuitive. It's interesting if we can change this value dynamically in the installer to change UI language dynamically - which, if possible, would allow to add the "Choose installer language" page in the beginning. [1] <a href="https://docs.microsoft.com/en-us/windows/desktop/Msi/productlanguage">https://docs.microsoft.com/en-us/windows/desktop/Msi/productlanguage</a> [2] <a href="https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c">https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>