Just an example: "Firefox will".
1) Many languages don't use an ausiliary verb to create the future form.
2) If (like us) you're trying to translate the interface using
impersonal forms, you should also try to avoid the personification of
I don't like this dialog either. It looks weird in Czech.
What would look proper in Czech? Instead of simply complaining,
perhaps we could assume that the design was well-motivated and not
frivolous, and instead try and figure out how to come up with an
Please try to remember that we're all on the same team.
Mike, would you give it ui-r+ if it was just "Firefox:"? Because that's
what we're forced to do in sk. If not, we should come up with re-wording.
Looking at the mock-up, since the last mozilla-1.9.1 build doesn't have
that panel yet, I also see a problem of length: a long localized string
for "Firefox will:" is likely to create a wide space on the left, as
soon as I understand that dialog's structure, and a bad distributed layout.
Possible solutions? Replace that "Firefox will:" with something like
"Available history configurations" and place the combo box under the
string, not on the same line. But it's just an hypothesis since I didn't
see that dialog on a working build (and that's another big problem of
string freezes, a lot of new strings land all together without a working
Nastavení: Pamatovat historii
Použít vlastní nastavení historie
Settings: To remeber history
To not remeber history
To use custom settings for history
would be fine.
The problem with the current desing is:
Firefox si má: Pamatovat historii
Firefox si nemá: Pamatovat historii
Firefox má: Použít vlastní nastavení historie
Firefox: Si má pamatovat historii
Firefox: Si nemá pamatovat historii
Firefox: Má použít vlastní nastavení historie
This looks strange (in Czech).
IMHO that was the thing wladow is asking for Slovak.
But you know ... language is more than playing with words, capitals and
punctuation marks. This sentence fragmentation dosn't look like Czech at
all. More over, it looks funy.
The best practice is to use sentence fragments with infinitive in such
places. If you need to put it in complete sentence you have to do the
same way as it was in English "Firefox will" + "....". But here the
problem comes - I need to use different forms for "Firefox will".
AFAIK, French and all latin based languages will have the same issue. I
don't know what Cédric will choose as a workaround but personnally what
I would do is drop &brandShortName; in the translation and put it like
that in neutral form:
Ne pas conserver l'historique
Utiliser des paramètres personnalisés pour l'historique
(comportement = behaviour)
> But you know ... language is more than playing with words, capitals and
> punctuation marks. This sentence fragmentation dosn't look like Czech at
> all. More over, it looks funy.
Yes, I know. Obviously I can't understand the above texts; I was just
suggesting what came to my mind. :-)
Another possible way to solve this is to leave the "pre" string blank,
and put full sentences inside the drop-down menu. Does that sound
The dropdown already seems complete to me without the prefix. What is
the purpose of it? The prefix just sounds like "this is a
preference/option you can change", but so is everything else in this window.
The purpose of the label is to make the line flow a little better when
it happens to be in English. In terms of localization, we should have
added a note about the label (I'm still learning all of things one can
do wrong, unfortunately by doing them). This would carry the same
general meaning and work fine for the interface:
Privacy Level: [History will be remembered by Firefox / No History
will be remembered by Firefox / Custom Settings]
In general if a sentence structure doesn't work, I don't think there
is much of an issue with playing with the labels to communicate
basically the same overall message. Not having the label at all would
also work fine (depending on what the drop down box says).
>Why don't you try to involve l10n in an earlier stage for this kind of
Sorry about that, this interface is indeed coming in very late in the
process. Since we added another beta and Ehsan had time to work on
the changes, we decided to see if we could get the interface landed
for 3.5 instead of waiting until the next release. Overall this is
good since it helps build the theme of 3.5 being about privacy, but it
does mean we only have a short time to discuss strings and
By the way, I don't think it's only a matter of time: as far as I know,
there's no way for a localizer to know which parts of the interfaces
you're working on, we see those changes only when strings land and break
our locales (and that's too late). Moreover, I don't remember
interactions between localizers and ui designers in the last years.
I think it's time to find a system to make this interaction possible:
what about a specific e-mail address to follow in BugZilla? I don't know
how many localizers will be interested in this kind of discussion, but
it's worth trying.
Watching l1...@mozilla.com is what a few people do to get into the loop
on patches at the time that I do. That obviously gets you *a lot* of
bugmail, including registration bugs etc.
I guess we could create a fake bugmail address like
comm...@localization.bugs with something like "Localization Community
[:l10n]" as "real name" for easier CCing.
As for interactions between the UI folks and the community, there is a
growing amount of posting of mockups on planet. I know that planet is
again a lot of data, but that is a problem for all of us, to some
extent. Not sure if we have help on the horizon there.
FWIW, I watch l1...@mozilla.com to make sure I see all that is going on with Mozilla l10n in Bugzilla. Like Axel said, it will get you a very high number of new bugmail messages, but if you use Gmail to help filter your Bugmail, I've found archiving (and keyboard shortcuts to archive) is a way to do quick bug triage. Probably not most ideal, but you do see everything going on.
Many of you may already know this, but to watch a user in Bugzilla, do the following:
1) Sign into your Bugzilla Account.
2) Click on "Preferences" in the top strip
3) On the next screen, click the second tab named "Email Preferences"
4) Scroll to the bottom of the page and add the Bugmail addresses of users you would like to follow. (In this case, l1...@mozilla.com)
5) Click "submit changes"
> Watching l1...@mozilla.com is what a few people do to get into the loop
> on patches at the time that I do. That obviously gets you *a lot* of
> bugmail, including registration bugs etc.
> I guess we could create a fake bugmail address like
> comm...@localization.bugs with something like "Localization Community
> [:l10n]" as "real name" for easier CCing.
Also there's 'l12y' keyword which may be added to such bugs.
Then one can create (and even share) saved search for bugs marked l12y and/or
CCed to l1...@mozilla.com. RSS feeds for such queries are easy to follow and do
not involve so much email traffic.
I don't think that the l12y keyword is the right choice here.
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=484645 to get a
watch account created.