Bug 1626827

I confirm this problem with thunderbird-60.0-1.fc28.x86_64 using french:

- Thunderbird is in french
- Calendar (Lightning) stay in english

Confirmed with DE; also (per https://bodhi.fedoraproject.org/updates/FEDORA-2018-be22632a02) with RU.

Apparantly, the build process is not fully adjusted to the fact that lightning is shipped with TB now.

it works as described in German, however moving from one date to another needs 1 minute or even more the first time in a session.

I confirm the problem. It's a packaging problem. Please see : 

https://bugzilla.mozilla.org/show_bug.cgi?id=1469678

The langpacks for lightning have to be generated separately and added to the rpm.

Regards,

Je viens de mettre à jour Thunderbird avec la version thunderbird-60.2.1-2.fc29.x86_64 et comme avec les versions précédentes thunderbird est en français mais la partie lightning est elle toujours en anglais.

IF YOU ARE NOT BILINGUAL FRENCH-ENGLISH: 

I just upgraded to thunderbird-60.2.1-2.fc29.x86_64 and as with previous versions thunberbird is in french but the lightning part is still in english.

I just upgraded to thunderbird-60.3.0-1.fc29.x86_64 available on koji.

For french language, this new version fixes the problem of translation in calendar (lightning).

*** Bug 1643521 has been marked as a duplicate of this bug. ***

Same player shoot again with thunderbird-60.5.1-1.fc29.x86_64 and Fedora in french: lightning is still in english.

As Didier G is reporting, this bug is back with TB version 60.5.1-1.fc29, i.e. lightning interface is in English. 

I presume that langpacks were not generated/integrated in the rpm...

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Same on F28 using TB 60.6

Same on F30 using TB 60.6.1.

Good surprise, I just upgraded to thunderbird-60.7.0-1.fc30.x86_64 and lightning is in system language, in my case in french.

Moving Thunderbird bugs to Jan to manage them meanigfuly.

Similar issue seems to be fixed for SeaMonkey just now. The idea is to "add manually" the needed things into the result .xpi file at the install stage. Certainly, the appropriate locales data should be present somewhere in the build tree after the compile stage is finished :)

Consider install section of https://src.fedoraproject.org/rpms/seamonkey/blob/master/f/seamonkey.spec , (scroll to if with langpacks, if with calendar etc.). Probably something similar can be performed for Thunderbird as well.

Note, that the fix itself does not changes lightning version numbers. IOW if the extension is copied into the user local profile, it might not be overwritten by the updated one.

For SeaMonkey case, user has compelled to perform some steps to take the changes effect:
- go to about:addons and remove calendar extension completely;
- restart SeaMonkey;
- go to about:config, type something like "installedDistro" in a search, find "extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103}" and reset it (by right click menu);
- restart SeaMonkey again.

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Bug is now fixed

Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.