1060682 - [tiles] new tab page legal text translations fr-FR

Status: RESOLVED INVALID

(Mozilla Localizations :: fr / French, defect)

Description

[Bryan Clark (DevTools PM) [:clarkbw]]

Attachment: newTab_fr.properties

Hello, bug 1058971 was filed to provide translations for a few text properties on the New Tab page of the Firefox Desktop which could be considered 'legal text'.  I'm attaching the translations they provided for your team to review.  The translation service used would appreciate testing and is happy to take your feedback if you feel this text does not convey the correct Mozilla voice.  Ultimately this is your module and your translations but we requested these translations to assist your efforts.

Comment 1

[Bryan Clark (DevTools PM) [:clarkbw]]

Attachment: newTab_fr.dtd

Comment 2

[Théo Chevalier]

Thanks, but you could have saved time for everyone, we already translated those files:

http://hg.mozilla.org/l10n-central/fr/file/36fbce2a7c8d/browser/chrome/browser/newTab.dtd
http://hg.mozilla.org/l10n-central/fr/file/36fbce2a7c8d/browser/chrome/browser/newTab.properties

Comment 3

[Ed Lee :Mardak]

(In reply to Théo Chevalier [:tchevalier] from comment #2)
> we already translated those files
Thanks. Just double checking that certain strings are legally equivalent (that's why the legal bug 1058971 was filed):

newtab.sponsored.button=SPONSORISÉES vs PARRAINÉE

newtab.sponsored.explain and newtab.enhanced.explain

newtab.intro.paragraph1/2/3

Comment 4

[Théo Chevalier]

People who did the translation obviously didn't know the context and didn't reach the level of quality we are requiring.

The noun SPONSORISÉ/E is not French. That's an Anglicism [1] so we can't use it, and the appropriated translation for Sponsored is Parrainé. Moreover, in this context, that's wrong to use a plural (SPONSORISÉES is a plural), because it concerns only one tile, as we can see in your own screenshot [2].

You better ask other Mozilla localizers to check if the third-party localization is correct, because in French it wasn't.


[1] http://books.google.fr/books?id=wPP_K4_n6rQC&pg=PA143&lpg=PA143&dq=sponsoriser+anglicisme&source=bl&ots=waZxgc7YHr&sig=pE5RC77488JR3KcBYXHrBrRjKTI&hl=fr&sa=X&ei=CUQDVLKgHsrhar3wgfAD&ved=0CFEQ6AEwBg#v=onepage&q=sponsoriser%20anglicisme&f=false

[2] https://people.mozilla.org/~elee/tmp.png

Comment 5

[Ed Lee :Mardak]

(In reply to Théo Chevalier [:tchevalier] from comment #4)
> You better ask other Mozilla localizers to check if the third-party
> localization is correct, because in French it wasn't.
Thanks. That's what we're doing.

> [2] https://people.mozilla.org/~elee/tmp.png
Curious, where did you find this? That's not quite the design we have implemented in nightly.

Comment 6

[Théo Chevalier]

(In reply to Ed Lee :Mardak from comment #5)

> > [2] https://people.mozilla.org/~elee/tmp.png
> Curious, where did you find this? That's not quite the design we have
> implemented in nightly.

You posted it on IRC. But don't worry, we are testing l10n in Nightly.

Comment 7

[Ed Lee :Mardak]

Attachment: comment 2 screenshot

Thanks for translating the strings so fast! Just making sure I'm uplifting them to aurora correctly.

Comment 8

[Théo Chevalier]

(In reply to Ed Lee :Mardak from comment #7)
> Created attachment 8482167 [details]
> comment 2 screenshot
> 
> Thanks for translating the strings so fast! Just making sure I'm uplifting
> them to aurora correctly.

From what I can see on the screenshot, it looks good to me. But I can't say for sure about the non-breaking spaces we are using in a lot of strings.

But as a side note, I think we're really doing it wrong here. What if localizers want to fix strings in Beta in two weeks? Given the tight schedule, you have to expect that. I'm not saying it will happen for French, but you should consider it.

Comment 9

[Ed Lee :Mardak]

(In reply to Théo Chevalier [:tchevalier] from comment #8)
> From what I can see on the screenshot, it looks good to me. But I can't say
> for sure about the non-breaking spaces we are using in a lot of strings.
What non-breaking spaces are you referring to? Are you referring to the spaces around the inline images?

For de-DE, they used <span style='display:inline-block;'>auf %1$S,</span> to make sure the "auf" and comma stays with the image instead of splitting to separate lines.