Closed Bug 596381 Opened 14 years ago Closed 14 years ago

New localizations needed for username/secret changes

Categories

(Cloud Services Graveyard :: Firefox Home, defect)

Product:
Cloud Services Graveyard
Component:
Firefox Home
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: st3fan, Unassigned)

References

Details

We are just using new terminology for Username and Secret Phrase, so I think the only strings that we need to change are:

Username -> Account Name
Secret Phrase -> Sync Key
Incorrect Secret Phrase -> Incorrect Sync Key
User Name Not Found -> Account Name Not Found

I'm not sure about the terminology and the consonistency between 'username' and 'user name'.
(In reply to comment #0)
> We are just using new terminology for Username and Secret Phrase, so I think
> the only strings that we need to change are:
> 
> Username -> Account Name
> Secret Phrase -> Sync Key
> Incorrect Secret Phrase -> Incorrect Sync Key
> User Name Not Found -> Account Name Not Found
> 
> I'm not sure about the terminology and the consonistency between 'username' and
> 'user name'.

What are we using on the Firefox client? Can we be consistent with what we're using there?
cc:ing sethb.

Seth - this is the bug we'll be using to track the actual strings that require translation for Fx Home 1.0.3. Please let Stefan know what you need from him to give to the localizers.
Flagging for blocking FF Home 1.0.x.  please + the flag with the version it is blocking
Flags: blocking-fx-home1.0.x?
Seth - can we ask the l10n team for Firefox Home to give us the strings/copy for the following What's New item:

"bug fixes" (yes, two words)...

(this is also good to have on file for future releases What's New content)
(In reply to comment #4)
> Seth - can we ask the l10n team for Firefox Home to give us the strings/copy
> for the following What's New item:
> 
> "bug fixes" (yes, two words)...
> 
> (this is also good to have on file for future releases What's New content)

Sounds good, I'll put in the request to get it translated for the languages that the Apple Store supports.
Blocks: 583241
Open tasks for this project can always be found when looking at the dependency tree of the main Firefox Home Project tracker.

https://bugzilla.mozilla.org/showdependencytree.cgi?id=583241&hide_resolved=1

Just so you know, I'll always leave that bug open and will use it to manage tasks from there.
From many of our localizers, we are getting feedback like this:

"A note for developers: the translation of "Sync Key" can be awfully long (for example "chiave di sincronizzazione" in Italian, but fr and es-AR seem to have a similar translation) and they should keep that in mind (I know they'll hate us for this ;-)."
Caitlin, can you send me the list again of the subset of languages that Apple's App Store supports?  I need that shortlist if you get a chance.
Brazilian Portuguese
Dutch
French
German
Italian
Japanese
Korean
Russian
Chinese (Simplified)
Spanish
Australian English
Canadian English
Mexican Spanish
Portuguese
Swedish
US English
(In reply to comment #7)
> From many of our localizers, we are getting feedback like this:
> 
> "A note for developers: the translation of "Sync Key" can be awfully long (for
> example "chiave di sincronizzazione" in Italian, but fr and es-AR seem to have
> a similar translation) and they should keep that in mind (I know they'll hate
> us for this ;-)."

That's good feedback. Is that primarily because there's no easy way to compress synchronization to sync in those languages? This is what we're going to be calling it in the Firefox UI (desktop, mobile) as well, so we do want to be consistent. Not sure there are great options here, but we're open to suggestions.
(In reply to comment #10)
> (In reply to comment #7)
> > From many of our localizers, we are getting feedback like this:
> > 
> > "A note for developers: the translation of "Sync Key" can be awfully long (for
> > example "chiave di sincronizzazione" in Italian, but fr and es-AR seem to have
> > a similar translation) and they should keep that in mind (I know they'll hate
> > us for this ;-)."
> 
> That's good feedback. Is that primarily because there's no easy way to compress
> synchronization to sync in those languages? This is what we're going to be
> calling it in the Firefox UI (desktop, mobile) as well, so we do want to be
> consistent. Not sure there are great options here, but we're open to
> suggestions.

We could also interpret Sync as a brand or product name -- I certainly would --, much like Microsoft Windows. Not even the French translated that into "Fenêtres" ;). So Sync Key could simply become Chiave Sync in Italian. I'm not a localiser, just saying that this wouldn't be a new thing to do from a product perspective.
I added :flod from the Italian team.  He can represent the collective feedback the best.
(In reply to comment #11)
> We could also interpret Sync as a brand or product name

I suppose that's the right call. I didn't have much time to take an overall look at all Sync's files until now, but it looks like "Sync Key" is used as "Sync's key" (or "syncBrand.shortName.label Key" if you prefer)

For example: instead of "Your Firefox Sync Key" the fullName.label is used
http://hg.mozilla.org/mozilla-central/file/6a3efef10e69/browser/locales/en-US/chrome/browser/syncKey.dtd#l1

Maybe we could also ask the developers if the "syncBrand.shortName.label Key" was their starting thought and explain that to dev-l10n (like happened in the past with Personas), since there are at least other 4-5 languages that translate the "sync" part.
http://mxr.mozilla.org/l10n-central/search?string=error.login.reason.synckey&find=services
(In reply to comment #13)
> (In reply to comment #11)
> > We could also interpret Sync as a brand or product name
> 
> I suppose that's the right call. I didn't have much time to take an overall
> look at all Sync's files until now, but it looks like "Sync Key" is used as
> "Sync's key" (or "syncBrand.shortName.label Key" if you prefer)

I didn't specify it as "syncBrand.shortName.label Key" in the strings, mostly because I didn't think of this issue until now ;). That doesn't mean that we can't come up with a guideline on how to translate Sync Key, though.
Hey Caitlin, for our Dutch App Store, can you or someone try to ask Apple if we could do the following:

- change ‘Mozilla website’ to ‘Mozilla-website’ for nl
- change ‘Firefox Home Ondersteuning’ to ‘Firefox Home-ondersteuning’ (either
that, or ‘Ondersteuning voor Firefox Home’
Hi Seth,
I am able to manage the description of the app through our account. I can't change the app name "Firefox Home" but can change the copy elsewhere. Can you be more specific where you'd like these changes?
The first comment in Bug 584390 for the Dutch team spells out the necessary changes, but just to be safe, I included Tonnes on this bug so he can explain further.
(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #11)
> > > We could also interpret Sync as a brand or product name
> > 
> > I suppose that's the right call. I didn't have much time to take an overall
> > look at all Sync's files until now, but it looks like "Sync Key" is used as
> > "Sync's key" (or "syncBrand.shortName.label Key" if you prefer)
> 
> I didn't specify it as "syncBrand.shortName.label Key" in the strings, mostly
> because I didn't think of this issue until now ;). That doesn't mean that we
> can't come up with a guideline on how to translate Sync Key, though.

Any resolution to this?
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
The current french is Clé de synchronisation which is key of synchronization or sync's key.  Spanish is also translated as Sync's key.

Japanese still says passphrase.
I set this to resolved/fixed again because I think this was a build problem.
I should have clarified; Japanese still says Passphrase in Japanese.
秘密の言葉 directly translated "words of secret".
Reopening this bug because the japanese translations are missing.

There is also a request for Swedish, but since that is a completely new language for the app, I doubt we can get that in 1.0.4.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Japanese translation was not updated when we update strings for 1.0.3 since we could not take enough time to update Fx4, Sync and many documentations consistently at the same time.

Now ja locale udated including term "Sync Key" for 1.0.4.
Thank you very much dynamis. I will sync the app with Verbatim today and include the new strings.
Japanese translations are in. So closing this bug.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Based on Verbatim:
Brazilian Portuguese, Czech still states secret phrase
Korean states sync password

Danish, Sinhala, Swedish need translations
Flags: blocking-fx-home1.0.4?
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.