Closed Bug 885927 Opened 11 years ago Closed 11 years ago

[b2g] [Calendar] Edit event: Button "Edit" appears in English

Categories

(Firefox OS Graveyard :: Gaia::Calendar, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:leo+, b2g18+ verified, b2g-v1.1hd fixed)

VERIFIED FIXED
1.1 QE4 (15jul)
blocking-b2g leo+
Tracking Status
b2g18 + verified
b2g-v1.1hd --- fixed

People

(Reporter: delphine, Unassigned)

References

Details

(Keywords: l12y, late-l10n, Whiteboard: l10n [LeoVB+])

Attachments

(2 files)

Attached image Screenshot
Leo, v1.1
Gaia   cca61224e6df8e9f7e450d77cb6a8cf91029be64
BuildID 20130621070212
Version 18.0

* Repro:
- Go into Calendar
- Create an event
- Click on that event

* Expected result: 
- Everything appears localized

* Actual result:
- the "Edit" button appears in English (see screenshot) instead of Polish
Whiteboard: l10n
It needs to be localizable first.
Assignee: marcoos+bmo → nobody
Component: pl / Polish → Gaia::Calendar
Product: Mozilla Localizations → Boot2Gecko
Keywords: l12y
blocking-b2g: --- → leo?
Keywords: late-l10n
(In reply to Stefan Plewako [:stef] from comment #1)
> It needs to be localizable first.

The edit string is localizable. But it is not added to any locale files. Please go ahead and add the new string id to each locale file. It look something like below in en-US locale file

back=Back
save=Save
hide=Hide
cancel=Cancel
confirm=Confirm
done=Done
events=Events
<Add the new string here to be localized for this language>
edit=Edit

The same needs to added for other locale files also. Please provide the localized string for all languages if you want me to do this.
Flags: needinfo?(splewako)
From l10n perspective it is not localizable.

First it needs to be added to:
https://github.com/mozilla-b2g/gaia/blob/v1-train/apps/calendar/locales/calendar.en-US.properties then it needs to be merged into
http://hg.mozilla.org/gaia-l10n/en-US/file/tip/apps/calendar/calendar.properties and then I can localize it.
Flags: needinfo?(splewako)
A string is added for "Edit" string to locale file to enable localization.
Attachment #766601 - Flags: review?(jlal)
Flags: needinfo?(jlal)
Priority: -- → P3
Target Milestone: --- → 1.1 QE4
in master https://github.com/mozilla-b2g/gaia/commit/18d39f8bbf25905da1bd1df6147d815bda1052db
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(jlal)
Resolution: --- → FIXED
Attachment #766601 - Flags: review?(jlal) → review+
tracking-b2g18: --- → +
Now this is landed, could you help in getting the string localized?
Flags: needinfo?(splewako)
No. It landed on master only and sadly we don't localize it.

It needs to be merged into v1-train and then into http://hg.mozilla.org/gaia-l10n/en-US (by Pike) - this is how it works, don't blame me.
Flags: needinfo?(splewako)
Is this a blocker for you all? This remains leo? as of right now.
Flags: needinfo?(leo.bugzilla.gaia)
I don't think landing this at this point has a lot of impact on what we're shipping in 1.1
(In reply to Axel Hecht [:Pike] from comment #9)
> I don't think landing this at this point has a lot of impact on what we're
> shipping in 1.1

I disagree. This impacts the read only view in the Calendar app, which is a 1.1 feature. If we don't take this patch, then the read only view feature will not be fully localized for 1.1.
Exposing the patch to localizers doesn't mean we get localized strings.

We're way past bedtime here.
(In reply to Axel Hecht [:Pike] from comment #11)
> Exposing the patch to localizers doesn't mean we get localized strings.
> 
> We're way past bedtime here.

Not exposing that patch means we don't have any opportunity to get localized strings for a target 1.1 feature. That seems like a net loss IMO.

The only argument here that we be on the table here for not accepting this patch would mean either:

1) accepting we have a target 1.1 feature that won't be localized and don't take the patch
2) accepting we take a risk that a target 1.1 feature might not have all localizations and take the patch
3) alter the 1.1 read only view code to see if it use an edit
4) Disable the read only feature for 1.1

[1] I think is not the right path to go because it is a net loss - no opportunity for localizations and this will likely fail in IOT.

[2] I think is not a bad solution, but does put us at risk for missing localizations.

[3] I think if available, is the best choice to go with. It avoids doing new localizations and ensures that a target 1.1 feature is localized.

[4] Needs an argument to product to turn the feature off

needinfo on product for a call here. I'll email release drivers as well about this.
Flags: needinfo?(ffos-product)
Alex is following up over email on this for what to do here.
Flags: needinfo?(ffos-product)
blocking-b2g: leo? → leo+
Uplifted 18d39f8bbf25905da1bd1df6147d815bda1052db to:
v1-train: 923ae8c993360c92b70e8bb6c3502ef5a4b2ae04
This is exposed to localizers, post sent to .l10n.
Flags: needinfo?(leo.bugzilla.gaia)
Whiteboard: l10n → l10n [LeoVB+]
v1.1.0hd: 923ae8c993360c92b70e8bb6c3502ef5a4b2ae04
When set to Polish language, the EDIT button is localized in Polish

Environmental Variables
Build ID: 20130729070226
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/8135299f3efd
Gaia: 7aaffc8ccb6cf7ddd1e97943c108f1cb9eae5de0
Platform Version: 18.1
Verified fixed on today's latest Leo build. Marking as so
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: