Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index 

Technically, I wonder though - in case the all-in-one build would be

deemed too bulky, couldn't we download extra languages dynamically,
and then hold it - per user - in the configuration subdirectory?



But that is essentially the first approach I tried, where a language pack
would be installed in a directory of the user (like ~/Library/Application
Support/LibreOffice/4/langpacks). The problem with that was that the
changes necessary to teach LibreOffice to look for everything that a
language pack contains in that directory, too, are large and
controversial, to code that already is rather inscrutable. I didn't have
the patience and clout to continue. (Feel free to continue.) To just stop
distributing language packs is IMHO a much simpler and more pragmatic
approach.

--tml

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.