Closed Bug 883735 Opened 7 years ago Closed 7 years ago

[Translation][Spanish][Portugues] Some tokens are not translated

Categories

(Firefox OS Graveyard :: Gaia, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:leo+, b2g18 fixed)

RESOLVED FIXED
1.1 QE3 (26jun)
blocking-b2g leo+
Tracking Status
b2g18 --- fixed

People

(Reporter: leo.bugzilla.gaia, Unassigned)

Details

(Whiteboard: [TD-44891])

Attachments

(4 files)

Attached file screenshot
Description:
1. Settings - SIM Security : 3 tries left
2. Settings - Geolocation : Geolocation
3. Settings : Enable USB storage and Turn on Message
4. Settings - Cellular & Data : Message settings
5. Settings - Cellular & Data - Network operator - Automatic selection : automatic
6. Settings - Cellular & Data - Message settings : all tokens
7. Settings - Cellular & Data - Message settings - Auto retrieve : all tokens
8. Call log - select number : all tokens
9. FTU - Cellular Data - Next : Scanning for network
10. Message - New Messsage : To, Message
11. [SIM lock] Notification bar : Locked SIM card

Version Info
Mozilla build ID: 20130526070207
Gaia Revision : 4d10e1297b859cacc174c0a54af61a7678d7c32d
Gecko Revision : 52341e43539a0e8b9aa77a9128cc3871439b8aa6
blocking-b2g: --- → leo+
This needs to be split up into separate bugs. We can't block on a giant meta bug that encompasses multiple distinct issues that might already be tracked.
AFAIK these strings are already internationalized — e.g. they work fine in French.

The problem is “only” that our community has not translated those items in Spanish and/or Brazilian Portuguese for v1-train. I think the Spanish-speaking community is focusing on v1.0.1 and I guess the Brazilian one does the same.

Pike, can you confirm? Do we have any plans to address the v1-train branch in the short term?
Flags: needinfo?(l10n)
I've reached out to the l10n community, again this weekend, and I know that the Spanish community is working, but they didn't land on hg yet. Waiting for feedback for pt-BR still.
Flags: needinfo?(l10n)
When does es and pt-BR land on hg?
Flags: needinfo?(l10n)
Priority: -- → P2
Target Milestone: --- → 1.1 QE3 (24jun)
I don't know at this point.
Flags: needinfo?(l10n)
(In reply to Axel Hecht [:Pike] from comment #5)
> I don't know at this point.

The target milestone of Leo is 24th Jun.
Please discuss with l10n community about due date.
Is it possible that es and pt-BR land on hg until this weekend? It's best.
But if it's impossible, could you land on hg until next weekday?
(In reply to hyuna.cho from comment #6)
> (In reply to Axel Hecht [:Pike] from comment #5)
> > I don't know at this point.
> 
> The target milestone of Leo is 24th Jun.
> Please discuss with l10n community about due date.
> Is it possible that es and pt-BR land on hg until this weekend? It's best.
> But if it's impossible, could you land on hg until next weekday?

Forwarding that to willyaranda and Fernando.

Whatever we have by the 24th can only be considered an intermediate status, as en-US is likely not done with the scoped work until late this month.
Flags: needinfo?(willyaranda)
Flags: needinfo?(fernandopsilveira)
I am not 100% sure that we will be able to land translations this weekend, because we have a FirefoxOS camp in Madrid.

I will try to talk with Inma to see if it is possible to met on Sunday to finish what is on en-US right now.
Flags: needinfo?(willyaranda)
pt-BR will be ready next weekend (until June 29) for sure
Flags: needinfo?(fernandopsilveira)
Leo,
I am unblocking(leo-) this as of now as we are still not Localization complete .Feel free to renom if this happens once we are localization complete based on comment# 9.
blocking-b2g: leo+ → -
blocking-b2g: - → leo+
On a pvtbuild from today, it seems that a lot of those are fixed.
Delphine - can you or QA take a look to see if this is now completely resolved?
Keywords: qawanted
QA Contact: lebedel.delphine
most of the issue have been fixed, some polishing is still needed - see screenshots

Leo
Build  20130701070213
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/15923aca6e6d
Gaia   c7472acec84f0d4527cdd6fd555d289e1d3e1d1d
Keywords: qawanted
Sorry, but it's best to file issues on individual strings on the individual localization, and one per issue. The pt-BR localizer won't care about spanish results, and vice versa.

Resolving this as fixed, as for the issues reported at the time, it is.
Keywords: qawanted
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
* Spanish missing strings compared with en-US:
Settings 
- all string related to "# Device :: SIM toolkit - NAI (Next Action Indicator)"

System 
- icc-alertMessage-defaultmessage
- icc-confirmMessage-defaultmessage

Please check.
These strings have been added by recent STK-related patches, less than a week ago (e.g. bug 883735). They should be fixed soon, but feel free to open another bug and cc Pike if you need to monitor the l10n progress for these strings.
PS: thanks for retrieving the l10n IDs (icc-alertMessage-defaultmessage and so on), it makes it much easier for us to know whether it’s an i18n or l10n issue.
(In reply to Axel Hecht [:Pike] from comment #16)
> Sorry, but it's best to file issues on individual strings on the individual
> localization, and one per issue. The pt-BR localizer won't care about
> spanish results, and vice versa.
> 
> Resolving this as fixed, as for the issues reported at the time, it is.

new bugs for the issues mentioned above:
https://bugzilla.mozilla.org/show_bug.cgi?id=889169
https://bugzilla.mozilla.org/show_bug.cgi?id=889436
https://bugzilla.mozilla.org/show_bug.cgi?id=889441
You need to log in before you can comment on or make changes to this bug.