|
Bugzilla – Full Text Bug Listing |
| Summary: | Thunderbird integrated Lightning calendar is not properly localized | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Michael Lashkevich <lashkevi> |
| Component: | Firefox | Assignee: | E-mail List <bnc-team-mozilla> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | astieger, bruno, chcao, duge, fkrueger, forgotten_c-AT0h9V-M, forgotten_HjfGXHkK4k, forgotten_lsStjVqOGJ, friedhelm.stappert, hans, ke, matthias, me, pcerny, sreeves, t.rother, terudej-suse, timo, tux, wolfgang, yunhe.guo |
| Version: | Leap 15.0 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| URL: | https://bugzilla.mozilla.org/show_bug.cgi?id=1484532 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Snapshot for a fresh profile. | ||
|
Description
Michael Lashkevich
2015-07-22 22:07:33 UTC
please reassign as appropriate. (known issue) The upstream buildsystem does not directly allow multi locale builds. For TB itself there is a certain procedure applied in the build to package languages. For Lightning this is again different. I need to look into this. Confirmation for this issue, its still present in the latest rpm update to 38.4.0.1.1 on OpenSuse 13.2 x64, de_DE. All UI items derived from lightning (Tasks. Calendar) are not localized after installation of MozillaThunderbird-translations-common (In reply to Thomas Rother from comment #3) > Confirmation for this issue, its still present in the latest rpm update to > 38.4.0.1.1 on OpenSuse 13.2 x64, de_DE. Moving to a maintained distribution. It is still the problem in current (Leap) version: after every Thunderbird update localization is not available in lightning. Workaround: 1. Remove Lightning add-on 2. Install Lightning from Mozilla page (or over integrated function in Thunderbird) Issue confirmed for leap 42.1 x86_64, TB 38.7.0-13.1 from official repo-update *** Bug 989286 has been marked as a duplicate of this bug. *** *** Bug 1000293 has been marked as a duplicate of this bug. *** carrying forward, not TB version specific Still present in Leap 42.2 after online update to Thunderbird 45.5. After the last update I rebuilt Thunderbird in my OBS home repo with the "ac_add_options --disable-calendar" switch. It restores the previous state where everybody who needed Lightning had to install it as an add-on, but got a fully localized version which survived the frequent online updates. Maybe a solution for the official package as well? (In reply to Hans Schwimmbeck from comment #11) > After the last update I rebuilt Thunderbird in my OBS home repo with the > "ac_add_options --disable-calendar" switch. It restores the previous state > where everybody who needed Lightning had to install it as an add-on, but got > a fully localized version which survived the frequent online updates. > Maybe a solution for the official package as well? It is not a solution, but a workaround, which may help an inexperienced user to understand that he could install the add-on by himself. @Wolfgang is there anything we can help to hack (about the build process) I don't know if it support the multilanguage in the manifest and jar Actually we have locale calendar en-US jar:chrome.jar!/calendar-en-US/locale/en-US/calendar/ locale lightning en-US jar:chrome.jar!/lightning-en-US/locale/en-US/lightning/ Seems easy (but certainly the trap) to add locale calendar fr jar:chrome.jar!/calendar-fr/locale/fr/calendar/ locale lightning fr jar:chrome.jar!/lightning-fr/locale/fr/lightning/ and so on Ideally this part of locales should goes to the language pack of thunderbird, so if a user activate the language he want, then all TB is correctly localized. I was hit by this a few day ago, when a user ask me why the calendar was always in english instead of french or german. If you pull the Thunderbird spec file you'll find the logic how the core language packs are created. If you find a way to use a similar process for Lightning that would help quite a lot. I'm pretty sure there is one somehow because I expect the addon to be built also somehow for the different locales. I just didn't have time to experiment much with it (and probably don't have in the near future). Probably the Thunderbird community on IRC also can give some hints how this could be implemented. At Mozilla there was a bug filed. There were several comments: Some mentioned, that it is a packaging problem. Some indicate, that there might be different multi-language packages and may be not all including the translations for Lightning. I don't know much myself about those things but there might be some information, that could help tracking down the issue. Here is the link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1266696 Good luck. *** Bug 1054623 has been marked as a duplicate of this bug. *** still the same in leap 42.3... can there be a quick and dirty "solution"? e.g. that the correct lightning plugin is reloaded automagically, e.g. via script if a new thunderbird-version is loaded from the update repository? Given today's update to Thunderbird 52.4 (in German) from the Mozilla repo with calendar UI and preferences switching again from German to English reminded me of the unsolved issue. In view of the upstream situation at https://bugzilla.mozilla.org/show_bug.cgi?id=1266696, is there any chance for a local solution? Thx. This is automated batch bugzilla cleanup. The openSUSE 42.2 changed to end-of-life (EOL [1]) status. As such it 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 openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime The bug still persistent in Leap 42.3. Every time an update of Thunderbird appears, I need to reinstall Lightning as an add-on to make Russian translations working. Same here for German localization. openSUSE 42.3 fully patched. Just recently had to re-install Lightning again, in order to be back on German Lightning. I just wonder: Why is it for an integrated part so difficult to utilize and use a localization file. Preferable a file for the main app and ALL integrated parts. Or a separate translation file. (So worst case just the latest few new words would show up in untranslated english.) But why just have fully translated add-ons. (Even integrated ones.) The issue appears independent of the openSUSE version. In fact, current Tumbleweed and Leap 15.0 Beta are also affected. asking again: is it possible to automatically reinstall the lightning plugin via script? that might be a reasonable solution much better that every user has to reinstall the plugin itself! thanks in advance! Christian @Christian Lorch:
Updates usually work via a repository. So updated files and dependencies get loaded/installed/updated.
I personally don't like the idea of any additional/special scripts running during update/upgrade.
New version of Thunderbird require new version of Lightning.
I don't know how they package those files in the repositories at (open)SUSE.
There is the basic Thunderbird package ("MozillaThunderbird", in English, I presume) and the corresponding translation files (common languages translations in "MozillaThunderbird-translations-common" as well as extra translations in "MozillaThunderbird-translations-other").
Since I didn't find any Lightning packages in the appropriate installation/update repositories, I assume that Lightning - as a TB core component - is now within the "MozillaThunderbird" package.
However, what I don't understand is WHY the translations for Lightning are not in the corresponding translation files as well.
Either in the above mentioned translation files of Thunderbird, or if that is not working, within separate Lightning translation files (something like "MozillaLightning-translation-commons" and "MozillaLightning-translation-other").
That is an annoying bug and known for several / many years now.
Thanks in advance for fixing.
(In reply to Rolf Gloor from comment #24) > Since I didn't find any Lightning packages in the appropriate > installation/update repositories, I assume that Lightning - as a TB core > component - is now within the "MozillaThunderbird" package. yes, all correct so far. > However, what I don't understand is WHY the translations for Lightning are > not in the corresponding translation files as well. Somehow same here. > Either in the above mentioned translation files of Thunderbird, or if that > is not working, within separate Lightning translation files (something like > "MozillaLightning-translation-commons" and > "MozillaLightning-translation-other"). We use a reverse engineered way to build locale packages from source along with the Thunderbird build (we do the same for FF fwiw). You can find it here starting from line 324: https://build.opensuse.org/package/view_file/mozilla:Factory/MozillaThunderbird/MozillaThunderbird.spec?expand=1 You also see a commented try to expand it to Lightning translations. I failed to find a working way back then. If someone want to give it a try feel free to finish/fix the work and report here. I'm not sure when exactly I will find time to look at it again. Reproducible with Leap 15 incl. current updates and german locale. I've disabled all language packs except german. *** Bug 1108574 has been marked as a duplicate of this bug. *** I'd like to chime in here. This is still an issue with Leap 15 - and more importantly, with the release of Thunderbird 60, it's not as easy to work around anymore, since Mozilla doesn't seam to publish the Lightning xpi estension file anymore (or at least not in an easy to find location). So, I had to download a release tarball of Thunderbird 60 and extract the localized extension package from there. This is certainly anything but user-friendly. What strikes me, though, is the fact that I can see the official Thunderbird packages do seem to contain localization files for the Lightning Calender in: /usr/lib64/thunderbird/extensions/langpack-de@thunderbird.mozilla.org (my locale is 'de') But how do I get Lightning to actually make use of these translations? (In reply to Timo Sigurdsson from comment #29) > I'd like to chime in here. This is still an issue with Leap 15 - and more > importantly, with the release of Thunderbird 60, it's not as easy to work > around anymore, since Mozilla doesn't seam to publish the Lightning xpi > estension file anymore (or at least not in an easy to find location). > > So, I had to download a release tarball of Thunderbird 60 and extract the > localized extension package from there. This is certainly anything but > user-friendly. > > What strikes me, though, is the fact that I can see the official Thunderbird > packages do seem to contain localization files for the Lightning Calender in: > /usr/lib64/thunderbird/extensions/langpack-de@thunderbird.mozilla.org > (my locale is 'de') > > But how do I get Lightning to actually make use of these translations? For the time being, as a workaround, you may use https://ftp.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1/linux-x86_64/ Unfortunately, the issue is not solved with the update to Thunderbird 60.2.1. By the way, I have just noticed with version 60.x that the date format of forwarded e-mails is set to English instead of German. Anyone else seeing this? FYI, I have reported the issue sometime ago upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1484532 FYI: I have updated Thunderbird to version 60.3.1, which also changed lightning from 6.2.3 -> 6.2.3.1 with the correct localization. A possible solution for lightning at Mozilla's side is still under discussion (https://bugzilla.mozilla.org/show_bug.cgi?id=1484532), so has something else changed? Nothing was done to Thunderbird except the 60.3.1 bump and a general localization update. So are you saying that the bug is solved with 60.3.1? For me it's not solved. Lightning still untranslated for me with 60.3.1 (In reply to Wolfgang Rosenauer from comment #36) > For me it's not solved. Lightning still untranslated for me with 60.3.1 I have to correct myself. In fact, I was so excited that the update seemed to solve the problem that I forgot to think twice before writing the comment (I installed lightning.xpi from https://bugzilla.mozilla.org/show_bug.cgi?id=1484532#c38 before). Sorry guys! FYI and as a workaround: Current version of Lightning (6.2.5) is available via https://addons.thunderbird.net/addon/lightning/ again. FYI: A fresh installation of Ubuntu 19.04 provides Thunderbird without built-in Lightning calendar. Is this also feasible for openSUSE? Thx. Should be fixed for Tumbleweed when version 68.1.1 is released. |