macOS provides localisations for these languages by default:
Arabic, Catalan, Croatian, Simplified Chinese, Traditional Chinese, Traditional Chinese (Hong Kong), Czech, Danish, Dutch, English (Australia), English (UK), English (U.S.), Finnish, French, French (Canada), German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Malay, Norwegian, Polish, Brazilian Portuguese, Portuguese, Romanian, Russian, Slovak, Spanish, Spanish (Latin America), Swedish, Thai, Turkish, Ukrainian, Vietnamese
LibreOffice on macOS should provide localisations for these languages by default. This will eliminate most of the bad UX and bugs LibreOffice users on macOS experience due to less-than-optimal language pack installing steps (which also causes bugs with the new macOS security measures.
Of course, this list is not limited to these languages, we can extend the list with other languages that are long-time localised. The reason we would be including these are, ensuring that if the user uses macOS with a certain localisation, we would %100 be sure that the users gets the localisation same as the system.
See bug #129177 for the proposed enhancement for the additional language packs.
Steps to Reproduce:
User Profile Reset: No
I like this idea. Don't know whether it is either achievable or realistic though.
Any idea whether this will be implemented or not? So far there is no reasonable solution for #129177 I believe?
A stupid comment say that this new version of libreoffice 7.1.5 is not valid when trying to install the french language
This stupid error was also when installing french language whith 7.1.4
All of this is on macos 10.16.6
Sorry it was 10.13.6 for macos version
This feature request has been discussed by ESC in 2023-02:
However the objections are partly very unspecific, e.g. "+ integrating the langpacks into the installer is problematic", problematic how? This was done successfully in NeoOffice as reported by Patrick and many other apps on macOS.
Additional discussion about this happened in bug https://bugs.documentfoundation.org/show_bug.cgi?id=144053#c27
So while I agree that bundling help is maybe out of scope / would increase size too much, I don't see that as counterargument to provide UI translations on macOS by default in the installer.
The entire language pack situation degrades UX a lot. I am not aware of another app doing this on macOS. So for macOS users this is unfamiliar, unexpected and feels cumbersome.
If the bandwidth problem is unsolvable, then the alternative should be presenting a language selection pop up at first start and then download the translations, like GCompris does for its data files.