757759 - [fr] Incorrect or inconsistent translations in PDF Viewer

Status: RESOLVED FIXED

(Mozilla Localizations :: fr / French, defect)

Description

[Scoobidiver (away)]

I don't know if it's the right place to report as the PDF Viewer feature and add-on localizations are independent.

Here is a list of incorrect or inconsistent translations I've seen based on PDF Viewer 0.3.273:
* Previous Page and Next Page: "Précédente" and "Suivante". It should be "Page précédente" and "Page suivante" (consistent with Adobe Reader and SumatraPDF labels)
* Zoom Out and Zoom In: "Zoom arrière" and "Zoom avant" are consistent with the Adobe Reader and SumatraPDF labels but inconsistent with the Firefox View menu item labels. Maybe the Firefox View menu item labels should be changed.
* PDF.JS Build: "Version de PDF.JS" is not the version: 139200e is different from 0.3.273. I propose "Identifiant de compilation de PDF.JS".
* Page Width: "Pleine largeur" is better than "Largeur de la page". It's the term used by SumatraPDF and Adobe Reader.
* Page Fit: "Page entière" is better than "Ajuster à la page". It's the term used by SumatraPDF and Adobe Reader.
* Show Thumbnails: "Afficher les vignettes" instead of "Afficher/masquer les vignettes"
* Show Document Outline: "Afficher les signets" instead of "Afficher/masquer la structure". It's the term used by Adobe Reader.
* No Outline Available: "Pas de signets disponibles" instead of "Pas de structure disponible"
* Document Outline: "Signets" instead of "Structure du document"
* PDF is protected by a password: "Ce PDF est protégé par un mot de passe :" instead of "Ce PDF est protégé par un mot de passe :" (full space instead of half space before colon - see https://fr.wikipedia.org/wiki/Ponctuation#Les_espaces_autour_des_signes_de_ponctuation_.28r.C3.A8gles_actuelles.29)

Comment 1

[Benoit]

I think Goofy took care of this, so assigning to him until pdf.js lands on Mercurial.

Comment 2

[Yury Delendik (:yury)]

There is no translation of the pdf.js in the mozilla-central.

Comment 3

[Jean-Bernard Marcon]

Merci de ces corrections et propositions dont tu peux voir qu'elles ont été prises en compte dans la traduction pour le navigateur lui-même,

https://hg.mozilla.org/l10n-central/fr/file/4f375be2c081/browser/pdfviewer/viewer.properties

puisque désormais ce qui était une extension est intégré. Benoit et moi avons une seule réticence, pour la traduction de "outlines" par "signets", il ne nous semble pas que ce soit des marque-pages (au sens où ce seraient des liens choisis par un utilisateur pour les mémoriser) mais plutôt la structure du document (par exemple titres de niveaux successifs ou ancres sur le document) un peu comme on peut avoir le "squelette" d'un site page bien structuré en demandant un "plan du site". Comme tu vois, pour l'instant, c'est "signets" que Benoit adopté, mais il est possible qu'on revienne sur ce point.



 reply to Scoobidiver from comment #0)
> I don't know if it's the right place to report as the PDF Viewer feature and
> add-on localizations are independent.
> 
> Here is a list of incorrect or inconsistent translations I've seen based on
> PDF Viewer 0.3.273:
> * Previous Page and Next Page: "Précédente" and "Suivante". It should be
> "Page précédente" and "Page suivante" (consistent with Adobe Reader and
> SumatraPDF labels)
> * Zoom Out and Zoom In: "Zoom arrière" and "Zoom avant" are consistent with
> the Adobe Reader and SumatraPDF labels but inconsistent with the Firefox
> View menu item labels. Maybe the Firefox View menu item labels should be
> changed.
> * PDF.JS Build: "Version de PDF.JS" is not the version: 139200e is different
> from 0.3.273. I propose "Identifiant de compilation de PDF.JS".
> * Page Width: "Pleine largeur" is better than "Largeur de la page". It's the
> term used by SumatraPDF and Adobe Reader.
> * Page Fit: "Page entière" is better than "Ajuster à la page". It's the term
> used by SumatraPDF and Adobe Reader.
> * Show Thumbnails: "Afficher les vignettes" instead of "Afficher/masquer les
> vignettes"
> * Show Document Outline: "Afficher les signets" instead of "Afficher/masquer
> la structure". It's the term used by Adobe Reader.
> * No Outline Available: "Pas de signets disponibles" instead of "Pas de
> structure disponible"
> * Document Outline: "Signets" instead of "Structure du document"
> * PDF is protected by a password: "Ce PDF est protégé par un mot de passe :"
> instead of "Ce PDF est protégé par un mot de passe :" (full space instead of
> half space before colon - see
> https://fr.wikipedia.org/wiki/
> Ponctuation#Les_espaces_autour_des_signes_de_ponctuation_.28r.C3.
> A8gles_actuelles.29)

Comment 4

[Scoobidiver (away)]

(In reply to Scoobidiver from comment #0)
> * PDF.JS Build: "Version de PDF.JS" is not the version: 139200e is different
> from 0.3.273. I propose "Identifiant de compilation de PDF.JS".
It's not taken into account (similar to the one in http://mxr.mozilla.org/l10n-mozilla-release/source/fr/mail/chrome/messenger/aboutSupportMail.dtd).

> Maybe the Firefox View menu item labels should be changed.
Should I file a bug for that?

(In reply to Jean-Bernard Marcon from comment #3)
> Comme tu vois, pour l'instant, c'est "signets" que Benoit adopté, mais il est
> possible qu'on revienne sur ce point.
If you choose "Structure" or "Plan", you expect to see it in a document with chapters. But not all documents have those anchors. See http://www.dicosmo.org/HoldUp/HoldUpPlanetaire.pdf for instance.
"Signet" is also the term used in SumatraPDF.

Comment 5

[Benoit]

(In reply to Scoobidiver from comment #4)
> (In reply to Scoobidiver from comment #0)
> > * PDF.JS Build: "Version de PDF.JS" is not the version: 139200e is different
> > from 0.3.273. I propose "Identifiant de compilation de PDF.JS".
> It's not taken into account (similar to the one in
> http://mxr.mozilla.org/l10n-mozilla-release/source/fr/mail/chrome/messenger/
> aboutSupportMail.dtd).

That a suggestion has not been followed doesn't mean it hasn't been taken into account. It may just not have been considered an improvement. 

> > Maybe the Firefox View menu item labels should be changed.
> Should I file a bug for that?

Probably. The current labels seem to come from a time when the zoom was text-only.

> (In reply to Jean-Bernard Marcon from comment #3)
> > Comme tu vois, pour l'instant, c'est "signets" que Benoit adopté, mais il est
> > possible qu'on revienne sur ce point.
> If you choose "Structure" or "Plan", you expect to see it in a document with
> chapters. But not all documents have those anchors. See
> http://www.dicosmo.org/HoldUp/HoldUpPlanetaire.pdf for instance.

I'm not sure that's a valid argument. A PDF could also be a scanned document with no selectable text at all. We can not always match expectations.

> "Signet" is also the term used in SumatraPDF.

That one is. Consistency with other apps is important. But sometimes they happen to be wrong. Consider for example "Sélectionner tout" Vs. "Tout sélectionner".

Comment 6

[Scoobidiver (away)]

It would be fine to update extension strings accordingly.