Time for 1.1 is gone for localizations. I think we should do that before 1.2. There are some strings that are used in different places: hotspotSettings in Settings is used both in a button and on a title. We should duplicate strings, since we need that for fitting properly for Spanish (and other locales, for sure) Thoughts?

With "fitting" do you refer to space constraints or to the localization in general (adapt the translation to the role)? In general I agree: reusing strings in different contexts is bad (e.g. as a general rule we use verbs for buttons and nouns for titles). I'm wondering if the Settings App represents an exception though: for me an option is not really a button, more a link to the next section which carries the same title.

(In reply to Francesco Lodolo [:flod] from comment #1) > With "fitting" do you refer to space constraints or to the localization in > general (adapt the translation to the role)? Space constraints. Sorry. > > In general I agree: reusing strings in different contexts is bad (e.g. as a > general rule we use verbs for buttons and nouns for titles). > > I'm wondering if the Settings App represents an exception though: for me an > option is not really a button, more a link to the next section which carries > the same title. The thing is that we needed to shorten the translation: "Ajustes del punto de acceso" -> "Ajustes p. acc." just because it does not fit on the title, but now the translation is both on the button (which has lot more room), and seems really poor l10n. Making the button saying: "Ajustes del punto de acceso" and the title "Punto acceso", sounds much much better for us.

Is there so much difference? I remember opening bug 826221 about that, but the difference seemed smaller. Anyhow I tend to agree: a bit more work on the translation side but also better flexibility.