| Hello, to take a step back: Here’s the way you can distribute localizations on macOS 1. Include all localizations in the standard download (used by all Apple software, MS Office etc.) 2. Offer precompiled .app bundles in the language of choice (used by Firefox) 3. Offer language packs as a separate download and installation (used by LO) What would the standard macOS way be to distribute language packs? 1 is the standard way and with file system compression it would not use significantly more disk space than today (I’ll have to google to find out how you actually turn it on) 2 is also an acceptable choice with one-step install 3 is a quirky solution requiring multiple steps, I can’t remember any other app having a similar install option on macOS? As such 1 or 2 would be the preferred option if we were to design the system today, agree? One of the nice thing about macOS historically is that you could easily change your system UI language and have your apps follow, while this was not easily done on e.g., Windows. I don’t see any real advantages of 3, only drawbacks from a user perspective Doing option 3 without installing to the .app bundle would be worse, in that the available localization will depend on the user - you would have to install it for every single user on the machine Eivind
|
_______________________________________________ LibreOffice mailing list LibreOffice@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/libreoffice
