Closed
Bug 1095673
Opened 10 years ago
Closed 6 years ago
[Camera][Video] import late.en-US.properties in the locales.ini file
Categories
(Firefox OS Graveyard :: Gaia::Video, defect)
Firefox OS Graveyard
Gaia::Video
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: djf, Unassigned)
Details
Attachments
(1 file)
For bug 1079519 and bug 1079543 we needed to introduce new strings into the 2.1 tree well past the late-l10n deadline. The decisio from product/UX was that even if these error strings remained untranslated, it would be a better user experience to have them than to not have them at all. The hope, however, is that there will be some way to get translations from at least a few locales into the 2.1 build somehow. Stas has proposed that we add an @import of a non-existant "late.en-US.properties" file to locales.ini. That way, any localizations of these strings can be placed directly into the gaia apps in late.{locale}.properties files, and no changes will ever need to be made to the localization repos. This bug is simply for making that change to the locales.ini file for the camera and video apps.
Reporter | ||
Comment 1•10 years ago
|
||
Stas, I think this is the change you had in mind. Please review once you've finished your discussions with Flod and Pike. Note that this patch is for v2.1 only. We don't need to do anything on master for this bug, do we?
Attachment #8519104 -
Flags: review?(stas)
Comment 2•10 years ago
|
||
Comment on attachment 8519104 [details] [review] link to v2.1 patch on github Hi David, thank you for creating the patch for this. Talking to flod, it seems like a better and indeed simpler approach would be to simply uplift the two bugs in question to v2.1 with the English strings in {video,camera}.en-US.properties and then break the l10n string freeze on 2.1. It's not ideal, but there has already been a precedent and flod believes that we should pursue the simplest solution possible which doesn't require any additional work (like writing a special script to cherry-pick translations from master in bug 1095686) and which doesn't involve any new processes. I'm canceling the review request for now. The late.en-US.properties idea was intended as a work around to the current string freeze, but it looks like that in the current circumstances it might be better to break the string freeze and not introduce a new l10n process.
Attachment #8519104 -
Flags: review?(stas)
Comment 3•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•