1006893 - [B2G][1.4][l10n] Nepali: a lot of variables in the localization has been translated while it shouldn't

Status: RESOLVED WONTFIX

(Mozilla Localizations :: ne-NP / Nepali (Nepal), defect)

Description

[demerick]

Attachment: 2014-05-06-17-26-00.png

Description:
The string "%e %B %Y, {{shortTimeFormat}}" appears with brackets on the message report screen

Repro Steps:
1) Update a Buri to BuildID: 20140505000201
2) Have another device send a message to the DUT
3) Tap the 'messaging' app from the home screen
4) Long press on the received message
5) Tap on 'View message report'

Actual:
The string "%e %B %Y, {{shortTimeFormat}}" appears with brackets

Expected:
The string "%e %B %Y, {{shortTimeFormat}}" shows with no brackets

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140505000201
Gaia: fccb15d6940db51615545574877a62d69406b1c2
Gecko: bf937fbec8c1
Version: 30.0
Firmware Version: v1.2-device.cfg

Repro frequency: 100%
See attached: screenshot

Comment 1

[demerick]

1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140430024002
Gaia: a8f5ca74ce896569c601c6849d534ff9fa7ce8cb
Gecko: d79b289ab63f
Version: 28.0
Firmware Version: v1.2-device.cfg

Nepali is not an available language on the Buri 1.3 MOZ RIL.

Comment 2

[Théo Chevalier]

Please, look at this list and fix all those variables accordingly. http://transvision-beta.mozfr.org/variables/?locale=ne-NP&repo=gaia_1_4
 You must not translate the English text between {{ and }}, those a variable the OS will replace dynamically.

I you have any trouble fixing that, we (the L10n team) will be happy to help you review your fix.

Basically, what you need to do is:

Go through the link posted above, and for each variable, replace it with the English text, and make sure the sentence is still correct in your language.

For instance:

Less than {{value}} {{unit}} remaining.

is currently: {{मान}} {{एकाइ}} भन्दा कम बाकि।
But should be:
{{value}} {{unit}} भन्दा कम बाकि।

OR

{{unit}} {{value}} भन्दा कम बाकि।

(You can move the variables into the sentence, but cannot modify their name.)

Comment 3

[Jason Smith [:jsmith]]

Why is this specifically nomed for 2.0? Isn't this a a locale-specific bug?

Comment 4

[Théo Chevalier]

(In reply to Jason Smith [:jsmith] from comment #3)
> Why is this specifically nomed for 2.0? Isn't this a a locale-specific bug?

It is locale-specific. But if Nepali is requested at some point for 2.0, we can't ship it broken like this. What's the right flag for this kind of blocker?

Comment 5

[Jason Smith [:jsmith]]

(In reply to Théo Chevalier [:tchevalier] from comment #4)
> (In reply to Jason Smith [:jsmith] from comment #3)
> > Why is this specifically nomed for 2.0? Isn't this a a locale-specific bug?
> 
> It is locale-specific. But if Nepali is requested at some point for 2.0, we
> can't ship it broken like this. What's the right flag for this kind of
> blocker?

I don't think we have a flag for this actually. Historically, we only block b2g on a locale-specific bug if it's an IOT blocker caught during certification. Anytime before that, we don't typically track the locale-specific issues on the blocking b2g flag.

We might want to introduce a way to track this for locale-specific issues though. Let's talk with Delphine about this tomorrow.

Comment 6

[Théo Chevalier]

(In reply to Jason Smith [:jsmith] from comment #5)
> (In reply to Théo Chevalier [:tchevalier] from comment #4)
> > (In reply to Jason Smith [:jsmith] from comment #3)
> > > Why is this specifically nomed for 2.0? Isn't this a a locale-specific bug?
> > 
> > It is locale-specific. But if Nepali is requested at some point for 2.0, we
> > can't ship it broken like this. What's the right flag for this kind of
> > blocker?
> 
> I don't think we have a flag for this actually. Historically, we only block
> b2g on a locale-specific bug if it's an IOT blocker caught during
> certification. Anytime before that, we don't typically track the
> locale-specific issues on the blocking b2g flag.
> 
> We might want to introduce a way to track this for locale-specific issues
> though. Let's talk with Delphine about this tomorrow.

Ok, thanks :)

Comment 7

[Avash Mulmi]

Thank you Theo for the instruction. 
Will start correcting the errors.

Thanks!

Comment 8

[Avash Mulmi]

I have corrected and updated the errors mentioned in the given site.

Thanks!

Comment 9

[Delphine Lebédel]

Marking as resolved fixed as per comment 8

Comment 10

[bmorgan]

This issue has been fixed on the Buri 1.4 MOZ RIL

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140519000201
Gaia: defd0650fb9d30c6515d50a89e72d8fb74ce7e62
Gecko: d95594048b36
Version: 30.0
Firmware Version: v1.2-device.cfg

Comment 11

[Théo Chevalier]

Hi, 

Just noticed that there are still variables that needs to be fixed on 1.4: http://transvision.mozfr.org/variables/?locale=ne-NP&repo=gaia_1_4

Also, all the fixes must be uplifted to 2.0 (master), otherwise you'll never get rid of those issues.
See the full list of variables that needs to be fixed for 2.0: http://transvision.mozfr.org/variables/?locale=ne-NP&repo=gaia

Note that if you fix that on master(http://mozilla.locamotion.org/ne/firefoxos/ ) before July 19th, you won't have to uplift your fixes to 2.0 and 2.1.

Feel free to ask if you have any question (here, by email or on IRC on #l10n), we'll be glad to help
Thanks

Comment 12

[Avash Mulmi]

Yes, we were unable to find alternate word for some of them so have left them as it is. Some of them did not have words with less characters so not sure what to do.
Will work on the new strings that have been added.

Comment 13

[Théo Chevalier]

This should be a no-brainer, you must not translate what's inside {{ and }}, this is breaking a lot of features.
Note that we won't be able to Sign-off ne-NP translations for Firefox OS if this bug is not fixed.

Comment 14

[Avash Mulmi]

Updated the two strings with {{ }} problem, that were either missed during last correction or were added after that.
I have notified the current localizers about it too, so I hope it won't be an issue from now on.

Comment 15

[Théo Chevalier]

(In reply to Avash Mulmi from comment #14)
> Updated the two strings with {{ }} problem, that were either missed during
> last correction or were added after that.
> I have notified the current localizers about it too, so I hope it won't be
> an issue from now on.

You still need to fix all of those on master (currently 2.0) too http://transvision.mozfr.org/variables/?locale=ne-NP&repo=gaia it's a worthless effort if you don't fix master

Comment 16

[Bansaj Pradhan]

(In reply to Théo Chevalier [:tchevalier] from comment #15)
> (In reply to Avash Mulmi from comment #14)
> > Updated the two strings with {{ }} problem, that were either missed during
> > last correction or were added after that.
> > I have notified the current localizers about it too, so I hope it won't be
> > an issue from now on.
> 
> You still need to fix all of those on master (currently 2.0) too
> http://transvision.mozfr.org/variables/?locale=ne-NP&repo=gaia it's a
> worthless effort if you don't fix master
Fixed all the reported bugs on master((http://mozilla.locamotion.org/ne/firefoxos/)

Comment 17

[BMO Automation]

We've stopped shipping Firefox OS for phones. Thus resolving this as WONTFIX.