Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

[l10n] Localizability issues with introduction steps #2567

Closed
flodolo opened this issue Apr 5, 2017 · 12 comments
Closed

[l10n] Localizability issues with introduction steps #2567

flodolo opened this issue Apr 5, 2017 · 12 comments
Assignees
Milestone

Comments

@flodolo
Copy link
Collaborator

flodolo commented Apr 5, 2017

Not sure how done this is, but better filing for nothing than forgetting.

schermata 2017-04-05 alle 18 36 31
Using text-transform: uppercase is a bad idea in general.

schermata 2017-04-05 alle 18 36 56
Again, text-transform, and unlocalized string. Also, fixed width is really risky, see how crowded Italian is, and it's not even the wordiest language.

schermata 2017-04-05 alle 18 37 07
Hard-coded skip and done, but more important, that "DONE" solution is going to work for maybe 5 or 6 locales, you need something that stretches to fit way longer text.

@flodolo flodolo changed the title [l10n] Localizability issues with introduction [l10n] Localizability issues with introduction steps Apr 5, 2017
@ghost ghost assigned johngruen Apr 5, 2017
@ghost
Copy link

ghost commented Apr 5, 2017

@johngruen assigning this to you in our triage. If that's not right, let us know.

@ghost ghost added this to the Sprint 54.4 milestone Apr 5, 2017
@johngruen
Copy link
Contributor

@flodolo thanks for this review... I think my PR fixes some of this stuff, and others we can work around. @pdehaan any brilliant way to grep for string length so we can figure out locales with the longest strings?

@pdehaan
Copy link
Collaborator

pdehaan commented Apr 5, 2017

@johngruen We could maybe do some grep for string length (or character count), but not sure how reliable it'd be (since five "i"s will be much smaller than 4 "w"s, for example).
We could maybe just render each of those strings into a DOM element and then measure it's rendered width... meh.

ianb added a commit that referenced this issue Apr 6, 2017
Change SKIP to be capitalized in the source text and not as a text-transform, so that localizers can apply their own judgement. Helps #2567
@ianb
Copy link
Contributor

ianb commented Apr 6, 2017

In 2dc1dd4 I changed SKIP to be the text SKIP and removed the text-transform, so that localizers can apply their own judgement. That commit also replaces DONE entirely, replacing it with a checkmark icon.

@johngruen changed "Firefox Screenshots BETA" to be a fixed string that does not get translated at all.

I think there's still the possibility of explanatory or header text overflowing the containers, as almost happens in your second screenshot.

@johngruen
Copy link
Contributor

Hey @flodolo mind taking a look, we've made some changes that i think address most of your issues

@flodolo
Copy link
Collaborator Author

flodolo commented Apr 8, 2017

Is there an easy way to trigger this without creating a new profile?

Remaining issue: text-transform on "Skip".

I'm still seeing the text, not a checkmark

schermata 2017-04-08 alle 06 38 48

Note that the layout is still risky. Italian fits, I'm not sure all languages will

schermata 2017-04-08 alle 06 40 39

@SoftVision-CosminMuntean

Is there an easy way to trigger this without creating a new profile?

@flodolo If you remove the add-on from "about:addons" page, then if you reinstall it, should work.

@flodolo
Copy link
Collaborator Author

flodolo commented Apr 10, 2017

@flodolo If you remove the add-on from "about:addons" page, then if you reinstall it, should work.

Thanks, it works. I was expecting this to be stored behind a pref, but it isn't.

For completeness, I'm on 6.0.9943 and still seeing DONE instead of a checkmark.

@jaredhirsch
Copy link
Member

Remaining issue: text-transform on "Skip".

It looks like the string is actually uppercased in the properties file. Maybe we should add a note for localizers?

For completeness, I'm on 6.0.9943 and still seeing DONE instead of a checkmark.

Seems fixed on current master to me:

screen shot 2017-04-12 at 3 07 10 pm

@flodolo
Copy link
Collaborator Author

flodolo commented Apr 13, 2017

It looks like the string is actually uppercased in the properties file. Maybe we should add a note for localizers?

Sorry, I was looking at "Done" and didn't think to check SKIP. If it's uppercase in the file, that's OK, locales can decide to keep it or use lowercase.

Seems fixed on current master to me:

Definitely not on https://pageshot.dev.mozaws.net/homepage/install-test-local.html (also don't have images), which brings to the next question: how often is that add-on updated?

@ghost ghost modified the milestones: Sprint 54.4, Sprint 54.5 Apr 17, 2017
@ghost ghost modified the milestones: Sprint 54.5, Sprint 54.6 May 1, 2017
@ghost
Copy link

ghost commented May 1, 2017

@ianb is going to update the -dev add-on. right now it's a manual process

@ianb
Copy link
Contributor

ianb commented May 1, 2017

We're planning on automating the dev deployment before we go live on server localization. I believe all other issues have been fixed – no text-transform, and we use an icon for "done".

@ianb ianb closed this as completed May 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants