664330 - Not localized string

Status: RESOLVED INCOMPLETE

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Leszek Zyczkowski]

On the Dev Derby page is not localized string:
NOTE: Firefox 5 will introduce support for CSS3 Animations. You should use the Firefox Beta or Aurora channel for this Dev Derby. Your demo will not work in Firefox 4.
See: https://developer-stage9.mozilla.org/pl/demos/devderby#upcoming

Comment 1

[Leszek Zyczkowski]

This string should be corrected asap because is in the June challenge.

Comment 2

[Luke Crouch [:groovecoder]]

Leszek, can you group your other non-localized string bugs into this one and mark them duplicates? lorchard is going to re-extract all strings.

Comment 3

[Leszek Zyczkowski]

Attachment: Fonts for choose colors

Comment 4

[Leszek Zyczkowski]

(In reply to comment #2)
> Leszek, can you group your other non-localized string bugs into this one and
> mark them duplicates? lorchard is going to re-extract all strings.

OK. I add to this bug all bugs involve MDN localization.

On promote page are too large font for colors. See attached image.

Comment 6

[Leszek Zyczkowski]

On the bottom each page is not localized string "Privacy Policy:. This string is in the messages. po file but not displayed localized.

Comment 8

[Leszek Zyczkowski]

On the bottom each page is not localized string "Join MDN".

Comment 10

[Leszek Zyczkowski]

Go e.g. Web page and in the right pane is displayed e.g. 2 weeks ago ago. Should be only one time: 2 weeks ago.

Comment 13

[Leszek Zyczkowski]

Not localized string "Explore MDN". See: https://developer-stage9.mozilla.org/pl/learn

In meantime this string was changed to "Explore other parts of MDN" and is displayed as "Topics" tooltip. "Topics" is also not translated.

Comment 14

[Leszek Zyczkowski]

On the home page in the right pane is not localized string "Firefox 4 for developers". See: https://developer.mozilla.org/pl/

Comment 16

[Leszek Zyczkowski]

On the home page in the right pane is not localized string "Join the MDN forum and share your thoughts on the open web:". See: https://developer.mozilla.org/pl/

Comment 18

[Les Orchard [:lorchard]]

I can't find any of these strings left out of l10n markup, now. Thinking they're have either since been marked up with template redesigns, or have just been removed altogether.

For strings that remain un-localized, we should try to separate them into:

1) strings that are not marked up in the project and 
2) strings that just haven't been localized by volunteers

Bugs filed for #1 can be fixed by the dev team. Bugs filed for #2 can only be addressed by volunteer localizers

Comment 19

[Luke Crouch [:groovecoder]]

reopening because I'm working on something to help us spot #1

Comment 20

[Luke Crouch [:groovecoder]]

taking longer to wrap up than I though, so I won't try to push this into today's release.

Comment 21

[Luke Crouch [:groovecoder]]

I think these are on cron jobs, but not sure how often they run. In any case, on stage9 we need to:

cd locale/ && svn up
python manage.py update_product_details

Comment 22

[Luke Crouch [:groovecoder]]

also add:

settings.STAGE = True

to settings_local.py

Comment 23

[Luke Crouch [:groovecoder]]

we may also need to restart apache, to reload the locale/ directory?

Comment 24

[Luke Crouch [:groovecoder]]

sorry, that shouldn't be settings.STAGE = True, just:

STAGE = True

Comment 25

[Dumitru Gherman [:dumitru]]

Done.

Comment 26

[Luke Crouch [:groovecoder]]

did you restart (both) apache server(s)? I see the new messages.mo on the filesystem but it's not loading for x-testing:

https://developer-stage9.mozilla.org/x-testing/

Comment 27

[Dumitru Gherman [:dumitru]]

I did. You still don't see the change?

Comment 28

[Luke Crouch [:groovecoder]]

Nope. Apache/django is looking for x_testing, which is a symlink to xx_testing under locale/. I wonder if apache needs an explicit follow symlinks directive for that?

Comment 29

[Les Orchard [:lorchard]]

(In reply to comment #28)
> Nope. Apache/django is looking for x_testing, which is a symlink to
> xx_testing under locale/. I wonder if apache needs an explicit follow
> symlinks directive for that?

Not sure if this is the issue, but does our locale stuff use gettext at all?

In a PHP app, I couldn't get arbitrary locales to work (eg. x-testing) unless they were configured as system-wide locales in Linux.

Comment 30

[Luke Crouch [:groovecoder]]

It's gettext, but that's what I'm using locally too and I didn't have to add x-testing ...

Comment 31

[Les Orchard [:lorchard]]

(In reply to comment #30)
> It's gettext, but that's what I'm using locally too and I didn't have to add
> x-testing ...

Are you running OS X or Linux, locally? You don't need to configure the locales on OS X.

Comment 32

[Luke Crouch [:groovecoder]]

OS X. so yeah - maybe we need to add x-testing locale to the box itself?

Comment 33

[Les Orchard [:lorchard]]

(In reply to comment #32)
> OS X. so yeah - maybe we need to add x-testing locale to the box itself?

Yeah... unfortunately, it was a year or two ago when I did this, so I can't remember what all I had to do. :/

Comment 34

[Luke Crouch [:groovecoder]]

dumitru, can you go thru http://www.gnu.org/software/gettext/FAQ.html#integrating_noop with me so we can try to debug this?

Comment 35

[Luke Crouch [:groovecoder]]

Les, dumitru and I don't really know where to start. can you remember anything you searched for to do this?

Comment 36

[Les Orchard [:lorchard]]

(In reply to comment #35)
> Les, dumitru and I don't really know where to start. can you remember
> anything you searched for to do this?

I think just things like "linux install new locale"... Something like this looks vaguely familiar, but only for ubuntu:

http://marzoa.com/2009/04/29/install-new-locales-on-ubuntu/

Comment 37

[Luke Crouch [:groovecoder]]

dumitru: can we try this now that you're out of marionette school? ;)

Comment 38

[Dumitru Gherman [:dumitru]]

CC'ing Jake and Jeremy here to help...

Comment 39

[Jake Maul [:jakem]]

I don't have any good idea on this. My google-fu isn't revealing any procedures for creating a brand-new locale, only adding pre-existing locales to a box that just doesn't have that locale compiled yet.

The link in comment 36 doesn't work on RHEL... the file /usr/share/i18n/SUPPORTED doesn't exist, nor does 'locale-gen'. I suspect both might be under other names, but that it wouldn't willingly create locale data for a locale it doesn't already know about.

This kinda bothers me, and makes me think there must be a better way to go about solving this problem (spotting un-localized strings) than adding test locales. If test locales were the recommended solution, I would have expected to see more easy-to-find documentation on how to set them up.

Maybe we can build a list of 'msgid' lines in one locale, and compare to all others? That seems like a relatively straightforward shell script I could write. Let me know if that seems like it would get you the info you need.

Comment 40

[Luke Crouch [:groovecoder]]

to spot un-localized strings we're looking for strings in the code that are missing 'msgid' lines altogether, so there's no way to automatically compare between locales.

this is a known practice in localizability testing - http://msdn.microsoft.com/en-us/goglobal/bb688150

cc'ing Stas and gandalf:

how do we normally catch un-localized strings in code?

Comment 41

[Luke Crouch [:groovecoder]]

Attachment: Locale Definition File

Locale Defintion file for localedef - just copies en_US for testing

Comment 42

[Luke Crouch [:groovecoder]]

I ran into this again while looking at bug 690399. I tried adding a local definition on a centOS 5.6 box on rackspace. I got as far as trying the instructions from http://linux.die.net/man/1/localedef, using the attached sourcefile, and the following command options:

localedef -f UTF-8 -i xx_TESTING.UTF-8 xx_TESTING

No errors, but it didn't generate the xx_TESTING file, or else I couldn't find where it was outputting the file. I'm commenting here in case this gives us ideas for how to fix compeltely.

Comment 43

[Corey Shields [:cshields]]

What's the next action for this?  Should we talk about it when we meet about MDN tomorrow?

Comment 44

[Luke Crouch [:groovecoder]]

Let's talk about kuma wiki stuff first and if we have time we can talk about this. It's not a very high priority. Mostly a nice-to-have.

Comment 45

[Jake Maul [:jakem]]

Per today's meeting discussions, we're going to close this out for now. If it becomes a significant issue, we can re-evaluate. Thanks!