FS#73184 - [kicad] 6.0.0-1 is missing translations

Attached to Project: Community Packages
Opened by Christian Roth (chr_) - Wednesday, 29 December 2021, 09:30 GMT
Last edited by George Rawlinson (rawlinsong) - Sunday, 02 January 2022, 21:02 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To George Rawlinson (rawlinsong)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
After upgrading the kicad package to version 6.0.0-1 changing the display-language through the interface under Preferences->Set Language->... to any language yields an Error message "Unable to switch language to ... ; The KiCad language file for this language is not installed."

Since commit e9fa9f68b293225f63bdb3aa495bb471c85aaac1 translations are built using the main cmake config file.
Commit 5418e3454cb701c18ace649635f9b2d5efcc491a switched the cmake option to default off.
Therefore translations are not built anymore in the new package.

My request is to change the cmake option "KICAD_BUILD_I18N" to ON, so that translations are built.
This is my first bug report in any open source project and english is not my first language, so please be gentle.

Additional info:
* package version: 6.0.0-1
* link to relevant commits:
e9fa9f68b293225f63bdb3aa495bb471c85aaac1 https://gitlab.com/kicad/code/kicad/-/commit/e9fa9f68b293225f63bdb3aa495bb471c85aaac1
5418e3454cb701c18ace649635f9b2d5efcc491a https://gitlab.com/kicad/code/kicad/-/commit/5418e3454cb701c18ace649635f9b2d5efcc491a

Steps to reproduce:
Try setting the language via Preferences->Set Language->...
Receive error message.
This task depends upon

Closed by  George Rawlinson (rawlinsong)
Sunday, 02 January 2022, 21:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  6.0.0-3
Comment by George Rawlinson (rawlinsong) - Sunday, 02 January 2022, 01:31 GMT
Package now in testing repository. Please have a look once it's been distributed to mirrors.
Comment by Christian Roth (chr_) - Sunday, 02 January 2022, 07:41 GMT
Problem resolved in version 6.0.0-3 from community-testing. Thank you very much!

Loading...