Bug 168219 - [l10n] kabyle language build
Summary: [l10n] kabyle language build
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL: https://pkgs.org/download/libreoffice...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-01 06:58 UTC by Athmane MOKRAOUI
Modified: 2025-09-02 12:40 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Athmane MOKRAOUI 2025-09-01 06:58:25 UTC
Hi,

We noticed that some Linux distros have no `libreoffice-l10n-kab` package to install even if the translation is still active on Weblate.

The only distros that are shipping the kabyle package is OpenSuse and ArchLinux. May be they have internal process to build the packages themselves.

We also would like to know the situation about the MSI package where some discussions were blocked at which code to use : 2143 or 0x1000

Link : https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/

First let's start with Linux.
Regards,

---
Athmane MOKRAOUI
l10-kab team member.
Comment 1 Adolfo Jayme Barrientos 2025-09-01 08:32:26 UTC
Each distro is responsible for creating their own packages. Therefore, there is little point reporting a bug here in this upstream tracker. Rather, a report needs to be filed in each distro’s bug trackers.

MSIs are provided by this project, so it’s appropriate to file bugs here in relation to that.
Comment 2 Christian Lohmaier 2025-09-01 11:13:16 UTC
If it is about a specific distro not carrying those packages: then indeed out of scope for the TDF run bugzilla.

TDF provided builds do support Kabyle / have it enabled.

I'm not aware of any discussions about it being blocked in the MSI package either, in fact it is enabled in the TDF windows builds for Windows (all UI languages are part of the single installer)

Also there's no special switch required to enable the language, if using the --with-lang=ALL switch, then it is included in the built.
Linux distros might not have updated their package definitions to package those files, or have a manually crafted list of languages, but then again that needs to be brought up to the corresponding linux distro's packager/in their bugtracking system.

and re microsoft langauge IDs: They basically don't add anything anymore since it is considered deprecated, so for languages not covered already they all use private/pseudo-codes but that doesn't cause any problem when installing.

"0x1000 Locale without assigned LCID if the current user default locale. See section 2.2.1.", so the reference is useless for newer/smaller languages that have been included into that document without actually assigning proper IDs/all adding it under that catch-all.

TDF uses 1625 (0x659) in the msi / it is true that for document language purposes that had been changed sometime back in 2011 – but that doesn't really matter if the codes for the msi and the code for dictionaries/langauges-of-document/what's used by LibreOffice itsellf don't match up.
Comment 3 Athmane MOKRAOUI 2025-09-02 12:40:27 UTC
Thank you Adolfo and Christian,

I opened a bug on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111036

Thank you again.