View Issue Details

IDProjectCategoryView StatusLast Update
0000970CATS.cacert.orgTranslation: User Interfacepublic2019-01-02 20:06
ReporterTed Assigned ToTed  
Status closedResolutionfixed 
Summary0000970: User Interface Translation to French
DescriptionSee language file
TagsCATS, Translation


related to 0001107 new CACert CATS Manual has only one page, which is mostly empty 



2011-08-22 22:01

administrator   ~0002316

Current status:
Translation done by ???

Two reviews needed


2011-08-31 04:31

updater   ~0002377

english version can be found here


2011-09-04 22:10


french.php (13,147 bytes)


2011-09-04 22:13

reporter   ~0002402

I have reviewed the french translation and checked with the browser that the translation makes sense. I have not managed to check the admin part.


2012-10-17 21:36

reporter   ~0003260

le fichier en pièce jointe est plus juste :

Pièces jointes french.php [^] (13,147 octets) 2011-09-05 00:10

que le fichier :

Description See language file [^]

sinon la traduction est correcte


2012-10-17 22:25

administrator   ~0003261

Two reviews completed, ready to deploy.


2012-11-19 22:21

administrator   ~0003344

Activated the language in the production environment.


2012-12-31 16:28

reporter   ~0003585

Last edited: 2012-12-31 17:17

Twice apears in [3] the word «mèl» as translation of «e-mail». This is not correct.

(1) Orthography is «mél.» with accut (not with gravis) and with a point at the end. This is an abreciation as «tél.» for telephone and can only be used before an e-mail adress, f.ex. «Mél.» as «Tél. 012 345 67 89». (source: french government [1])

(2) as equivalent of e-mail in french is the word «courriel» as published in the 'Journal officiel' from 20/06/2003 in France and in the 'Grand Dictionnaire terminologique' published by the Office québécois de la langue française. [2] [4]

«mèl» should be replaced by «courriel» in both case.

Also should be replaced (2x) «email» by «courriel» (email without hiphen is in french a material made by fusing powdered glass). Fused powdered glass is not electronic mail.

By fixing this, could be replaced (2x) the english «mail» by the french «courriel» as it is confusing, when using different words for the same terme.
resp. «adresse courriel» or «adresse électronique» if it is «e-mail-adress»

[4] also the dictionaries of Robert, Larousse, Hachette gives preference to courriel instead of the 'Anglic[isme] déconseillé'.


2013-01-01 12:24

reporter   ~0003586

correction apporté au french.php, fichier envoyer au rapporteur assigné Ted pour ajout au bug tracker


2013-01-07 21:13

administrator   ~0003595

L10N, please send me your proposal of the file education list or personal mail, or attach it to this bug, so I can add it to SVN.

All in all the proposals sound sensible to me, but my french is not good enough to count this as a review. So before installing on the production server I'd need two french speaking people who confirm your proposals.


2013-01-07 22:02


french2.php (13,119 bytes)


2013-01-07 22:06

reporter   ~0003596

see file french2.php
I chanched as written december 31, 2012 (2x adresse mèl --> adresse courriel; 1x email --> courriel; 1x mail --> courrier [after cross checking with EN and DE; 'mail' means there 'snail mail']; 1x Help --> Aide [this was not mentioned before]).


2013-01-19 20:45

administrator   ~0003710

Last edited: 2013-01-19 20:48

I checked in french2.php to SVN (and to the new github repository

Any french speaking person may review the changes and give a statement here, we need two positive statements before the changes can be moved to the release version.


2013-04-07 22:23

reporter   ~0003866

I don't perfectly agree with L10N : according to his previous message (2012-12-31) about french gov directives, "adresse courriel" line 7 should be simply : "Mel". Ok for the other changes.


2013-04-08 01:01

reporter   ~0003868


Sorry a lot of mistakes remaining in this translation, I just pushed a change.
Do you really think google translates good french ? :(

I may not have corrected everything, but main things seems good for understanding (french native speaker and working with PKI in France - lots of things are not precise)

I let the words courriel and mèl, but "e-mail" is mainly used in France. I'm not sure if Canadian french uses the same word.

Another thing which must be ruled by french speakers, how to translate assurer ?
As the word assureur means insurer, professional of the insurance market. It is not correct here, and has been a problem for years. Is there a clear statement on this point from CAcert ?


2013-07-05 13:21

reporter   ~0004096

I do not understand the comment of bergerc from 2013-04-08.

- As mentioned above, "courriel" is the official term in both, Canada an France.
- The terms "assurer"/"assurance" does not appear in this texts (french.php, resp. french2.php); if they would, they were translated with "accréditeur"/"accréditation", following the french CAcert-Terminology that can be found at "CAcert Translations".
- When I look to french2.php, I see common words as name, next quesstion, yes, no, zip code, street, ... and no PKI special vocabulary.

Maybe bergerc's comment is not about this translation, but about some other text?

@Ted: Howmany reviews are still needed?


2013-07-05 13:41

reporter   ~0004097

@L10N : I did not update french.php or french2.php attached to this ticket, but rather I pushed a change to the github repository, please see the pull request located here :


2013-07-05 17:04


french3.php (26,450 bytes)   

define("accept_Login_01","Vous n'�tes pas enregistr�. <br /> Veuillez v�rifier votre certificat et confirmer l'enregistrement.");

define("accept_Login_02","Informations du certificat");

define("accept_Login_03","D�livr� �:");

define("accept_Login_04","Nom commun (CN)");

define("accept_Login_05","Num�ro de s�rie");

define("accept_Login_06","Adresse �lectronique");

define("accept_Login_07","D�livr� par:");


define("accept_Login_09","Unit� d'organisation");

define("accept_Login_10","D�livr� le");

define("accept_Login_11","Expire le");

define("accept_Login_12","Inscription avec ce certificat?<br /><br />".

                         "Seulement le num�ro de s�rie du certificat sera stock�. Vous devrez fournir le nom commun du certificat (\"Common Name\") si vous souhaitez obtenir un certificat imprim� apr�s passage du test<br />".

                         "Aucun certificat imprim� ne peut �tre d�livr� pour les certificats anonymes (dont le nom commun est \"CAcert WoT User\").");


define("Button_01","Cr�er une nouvelle mati�re");

define("Button_02","Retour � la table des mati�res");

define("Button_03","Retour � la liste des questions");

define("Button_04","Nouvelle question");

define("Button_05","Afficher sous forme de liste");

define("Button_06","Affichage graphiques (ligne)");

define("Button_07","Affichage graphiques (barres)");

define("Button_08","Meilleure r�ponse");

define("Button_09","Plus mauvaise r�ponse");

define("Button_10","Connexion r�ussie");


define("Button_12","enregistrer les modifications");

define("Button_13","�diter les r�ponses");

define("Button_14","Ajouter la r�ponse");

define("Button_15","Supprimer la r�ponse");

define("Button_16","�valuer le test");

define("Button_17","Informations statistiques");

define("Button_18","Informations de l'utilisateur");

define("Button_19","Statistiques du test");

define("Check_Cert_01","Votre nom doit �tre inclus dans le certificat si vous souhaitez obtenir un document par courrier postal ou par courrier �lectronique.<br />Vous pouvez continuer l'enregistrement, mais vous ne pouvez pas choisir les options <i>par courrier postal </i> ou <i>par courrier �lectronique.</i>.<br /> Vous pouvez �galement annuler cette inscription et vous enregistrer avec un autre certificat, dans lequel votre nom est inclus pour obtenir des documents par ces moyens.");

define("certificateDocu_01","Si vous le souhaitez, nous pouvons vous fournir un document attestant que vous avez a pass� le test d'accr�diteur. Le document sera �mis � votre nom comme indiqu� dans votre certifcat num�rique.");
define("certificateDocu_02","Non, je ne souhaite pas ce document.");

+define("certificateDocu_03","Oui, envoyez-moi s'il vous plait le document en pi�ce-jointe au format pdf par courriel. Nous utiliserons l'adresse �lectronique fourni dans le certificat.");
+define("certificateDocu_03","Oui, envoyez-moi s'il vous plait le document en pi�ce-jointe au format pdf par courriel. Nous utiliserons l'adresse �lectronique fourni dans le certificat.");



define("certificateDocu_08","code postal");




define("certificateDocu_12","tous les champs doivent �tre rempli, si vous souhaitez le recevoir par courrier postal.");

define("Class_Answer_01","d�tails des r�ponses");



define("Class_Answer_04","Au moins 2 r�ponses � donner.");

define("Class_Answer_05","r�ponses au moins une r�ponse doit �tre marqu� comme 'correct' et au moins 2 doivent �tre fournies.");

define("Class_Answer_06","Au moins une r�ponse doit �tre marqu� comme 'correct'.");

define("Class_Answer_07","Dans un texte � trous, les r�ponses correctes et incorrectes doivent �tre diff�rents.");

define("Class_Answer_08","Il a au moins une bonne et une mauvaise r�ponse.");



define("Class_Progress_01","nombre de questions");

define("Class_Progress_02","Trop de donn�es stock�e dans la base de donn�es. "); // geh?rt zu Lernfortschritte_angezeigt

define("Class_Progress_03","voir le dernier test");

define("Class_Progress_04","progr�s de l'apprentissage");

define("Class_Progress_05","Plus aucune donn�e disponible"); /*Bsp: Keine weiteren Infos zu : 5 Fragen */

define("Class_Progress_06","Aucune information disponible pour:");


define("Class_Progress_08","questions r�ponses incorrecte");

define("Class_Question_01","Cliquez ici pour voir plus d'informations sur ce sujet");

define("Class_Question_02","d�sactiver la question");

define("Class_Question_03","activer la question");

define("Class_Question_04","supprimer la question");

define("Class_Question_05","questions non disponibles dans la base de donn�es");

define("Class_Question_06","d�tails sur la question");

define("Class_Quiz_01","il y a pas assez de questions � ce sujet. Veuillez choisir un autre sujet.");


define("Class_Quiz_03","test d'�valuation");

define("Class_Quiz_04","Votre score total est:");

define("Class_Quiz_05","Le minimum obligatoire pour valider le test est:");

define("Class_Quiz_06","Vous avez atteint: "); /*Bsp: vous avez atteint 0 %  .... */

define("Class_Quiz_07","et par cons�quent vous");/* vous avez atteint 0 %  et donc vous n'avez pas r�ussit le test   */

define("Class_Quiz_08","avez r�ussi le test.");

define("Class_Quiz_09","n'avez pas r�ussit le test.");/*Bsp:You have reached 0 %  and so you did not pass  */

define("Class_Quiz_10_AnonymousCert", "Vous avez fait le test � l'aide d'un certificat anonyme, vous ne pouvez donc pas demander une version imprim�e ou en PDF de l'attestation de r�ussite du test.<br />");
define("Class_Quiz_11_RequestCert", "Demander une attestation de r��ussite");
define("Class_Quiz_12_ExplainCert", "En raison de probl�mes de confidentialit�, nous ne recueillons pas vos donn�es personnelles ici.<br /><br />".                                  

                                    "Pour demander une attestation papier ou PDF, envoyez un courriel � <a class=\"http\" href=\" pour AssurerChallenge\"></a> en pr�cisant si vous souhaitez une version papier ou une version PDF. Si vous d�sirez une attestation imprim�e, veuillez inclure votre adresse postale.<br />".
                                    "Le courriel peut �tre <a class=\"http\" href=\"education.txt\">chiffr�</a> et <b>doit �tre sign� par le certificat que vous avez utilis� pour effectuer le test</b> ainsi, nous pouvons v�rifier la r�ussite du test en v�rifiant son num�ro de s�rie. ".
+                                    "Jetez un oeil � la zone situ�e dans le coin sup�rieur droit ( \"connect� en tant que:\") pour v�rifier les informations sur le certificat que vous utilisez.<br />".
+                                    "<br /><em>Pour un certificat imprim�, nous vous demandons pour un don de 5 euros pour l'envoi en Europe et de 10 euros pour un envoi dans le reste du monde, afin de couvrir les frais d'exp�dition.<br />".
+                                    "Cliquez sur le bouton ci-dessous pour faire un don � CAcert via Paypal, la page suivante vous pr�sente les m�thodes disponibles pour faire un don <a class=\"http\" href=\"\"></a>.</em><br />".

                                    "<br />Nous sommes d�sol�s pour le d�sagr�ment..<br />");

define("Class_Quiz_13_Donate5", "5 euros pour les frais d'exp�dition en Europe");

define("Class_Quiz_14_Donate10", "10 euros pour les frais hors Europe");


define("Class_Topic_02","no. des questions");

define("Class_Topic_03","questions par test");


define("Class_Topic_05","�diter la rubrique");

define("Class_Topic_06","Activer la rubrique");

define("Class_Topic_07","D�sactiver la rubrique: toutes les questions de cette rubrique vont �tre d�sactiv�es �galement.");

define("Class_Topic_08","Supprimer la rubrique avec affect�e toutes les questions et r�ponses");

define("Class_Topic_09","Le pourcentage minimum qui doit �tre un nombre et ne doit pas �tre plus grand que 100.");

define("Class_Topic_10","rubrique existe d�j�.");

define("Class_Topic_11","Nombre de questions doit �tre un entier non n�gatif.");


define("Collect_Question_01","Cette question existe d�j�. ");

define("Collect_Question_02","Au moins un �cart doit �tre d�fini. Les espaces sont cr��s par [ ]. La bonne r�ponse est � l'int�rieur des crochets. Tous les supports doivent �tre ferm�s.");

define("Collect_Question_03","saisir la question");


define("Function_getContent_02_Intro",'<div class="centered">Pour une courte introduction, veuillez jetez un oeil � <a href="" rel="external">le WiKi</a></div><br />');

define("Function_getTopic_01","Afficher la progression");

define("Function_getTopic_02","Afficher les statistiques");

define("Function_getTopic_03","d�marrer le test");


define("Function_reallyDel_02","�tes-vous certain de vouloir supprimer cette rubrique?");

define("Function_reallyDel_03","Si vous confirmez la suppression, toutes les questions et r�ponses seront supprim�s �galement.");

define("Function_reallyDel_04","�tes-vous certain de vouloir supprimer cette question?");

define("Get_Content_01","Inscription annul�e.");

define("Global_01","vous devez �tre connect� pour utiliser cette fonction");






define("Global_07",'<h4 class="centered">Aucune donn�e disponible</h4>');





define("Global_12","type de question");



define("Global_15","r�pondu correctement dans %");

define("Global_16","Vous n'�tes pas connect� actuellement");

define("Global_17","La connexion a �chou�. Un certificat CAcert client valide est requis.");

define("Global_18","Question ID");

define("Global_19","Echec de connexion");


define("Index_01","Connect� en tant que:");

define("Login_01","Votre certificat n'a pas pu �tre valid�.");

define("Login_02","Votre certificat a �t� r�voqu�.");

define("Login_03_No_Org_Certs","Les certificats d'organisation ne sont pas accept�s pour le CATS car ils ne sont pas directement li�s � un compte utilisateur.");








define("Menue_08","switch to EN");

define("Menue_09","zu DE wechseln");

define("Menue_10","changer vers FR"); /* ?? a rajout� certainement has certainly added */

define("Statistic_01","meilleur r�sultat pour sujet: ");

define("Statistic_02","pires r�sultats pour sujet: ");

define("Statistic_03","questions dans cette rubrique:");



define("Statistic_06","Infos utilisateur");


define("Statistic_08","utilisateurs enregistr�s");


define("Statistic_10","certificats racine");

define("Statistic_11","certificat de classe I utilisateur");

define("Statistic_12","certificat de classe III utilisateur");

define("Statistic_13","param�tres de langue");



define("Statistic_16","option de livraison ");

define("Statistic_17","courrier postal");



define("Statistic_20","infos de test");


define("Statistic_22","tests termin�s");

define("Statistic_23","tests r�ussis");

define("Statistic_24","fran�ais"); /* ligne rajout� num�rotation d�caler a corrig� lors de l'int�gration Line numbering added offset corrected during the integration */

define("Title_01","CATS rubriques");

define("Title_02","CATS collecte les questions");

define("Title_03","CATS statistiques");

define("Title_04","d�marrer le test CATS");

define("Title_05","CATS D�couvrez les progr�s");

define("Title_06","CATS informations certificat");

define("Topic_01","Remarque: Vous ne pouvez pas d�clarer des r�ponses comme correcte ici, alors qu'elles ont �t� d�clar�es incorrectes ci-dessous.");

define("Topic_02","Pr�sentation des rubriques");

define("Topic_03","questions sur cette rubrique:");

french3.php (26,450 bytes)   


2013-07-05 17:29

reporter   ~0004098

Oups… you corrected french.php in github, although here in the bugtracker already existed a newer version french2.php. I have merged the two versions (github with your corrections and french2.php) as a document named french3.php

As sometimes before :/?/! was a space and sometimes not, I checked the rules. In fr_FR, there is a (small) space before :;!?» and after «, while there is no (small) space in fr_CH (as in de or it) and neither in fr_BE (as in nl). Canada is as Switzerland and Belgium for ?!;, but as France for :«». As two countries applied the same rules (Switzerland and Belgium), I applied as they do.

Sorry for not changing in github, but I can only read there.


2013-07-05 21:02

reporter   ~0004099

I integrated these modifications on my fork/branch of the github, but I have doubts : Some texts did originally start with a lower case letter, so I let them, but you used capitals/upper case everywhere, did you check on the CATS live system if it's legitimate ? (I did not)

I also corrected some typos that were still there.


2013-07-09 09:23

reporter   ~0004104

A new pull request has been sent with the last updates


2013-12-23 10:49

reporter   ~0004484

@Ted: It seams, that there is no more discussion about this topic. Can we go further to the two reviews?

I proovreaded the latest version from bergerc at and for me it looks now very well: language, accents, typography, upper/lower case. If you want, you can count this as first review. (Or is this not possible, as I was involved in some steps?)


2014-02-11 22:53

administrator   ~0004580

Merged the changes into testserver branch, installed them on the testserver.

Please review versus the english texts

Use at the moment for a live test.

L10N, I'd apprecate if you'd have at least a short look at the github file to verify that I did not mess up the pull request. And you count as reviewer since it's not code but language to be reviewed. And we're not subject to Security Policy anyway. :-)

speedy67 and/or nvasseur, if you could give us the second/third review it would be great!


2014-11-22 17:43

administrator   ~0005118

Sent a direct request to speedy67, nvasseur and Lordguy asking for a second review.


2014-11-23 02:49

reporter   ~0005119

second review ok


2014-11-25 00:14

reporter   ~0005126

Last edited: 2014-11-25 00:14

Minor changes needded :
line 1 : changed "please check your certificate" ("votre certificat") to "please check your certificate information" ("les informations de votre certificat")
line 7 : change "Adresse électronique" into "Mel" according to L10N
line 13 : Added a space before "?"
line 14 : changed "un attestation" into "une attestation" (female gender in french), change "passage" into "réussite" (in french, "passage" means "taking", not "passing")
line 16 : first character turned to capital
line 17 : changed "matière" (matter subject) into "sujet" (topic)
line 18 : changed "table des matières" (table of contents) into "Retour à la gestion des sujets"
line 19 : changed "liste" (list) into "gestion" (management)
line 29 : changed "Editer" (publish/release) to "Modifier" (modify)
ligne 37 : changed "passé" into "réussi" (same reason as line 14)
line 39 : Added brackets as in original text
line 40 : added a space before column character
line 45 : changed "lieu" (place) into "ville" (city)
line 53 : put "réponse" to the right place (certainly accidentally moved to the beginning of the sentence)
line 55 : replaced "différents" with "différentes" (to respect french grammar rules)
line 55 : replaced "Il a" (It has) with "Il doit y avoir" (It has to be")
line 64 : added "plus" ("no more" and not "any") and a space before the column caracter
line 66 : changed "questions réponses incorrects" (means nothing) into "questions avec réponses incorrectes"
line 73 : added a space character before column character
line 77 : replaced "obligatoire" (mandatory) with "requis" (required), added a space character before column character
line 78 : added a space character before column character
line 79 : added a space character at the end of the line for a correct transition with the next text line
line 84 : replaced "En raison de problèmes de confidentialité" with "Par soucis du respect de la vie privée" (more compliant with legal terms regarding privacy)
line 88 : first "pour" removed (useless)
line 113 : moved "actuellement" to right place
line 138 : added a space character before column character
line 141 : "car ils ne sont pas directement liés à" changed to "car ils peuvent être difficilement liés à" to be closer to original text
line 148 : changed "Thèmes" (theme) into "Sujets" (topic)
line 152 : added "le" and space character before column character
line 153 : replaced "pires" with "plus mauvais"
line 154 : added a space character before column character
line 176 : replaced "rubrique" (section) with "sujet" (topic)
line 180 : replaced "CATS Découvrez les progrès" with "Progrès d'apprentissage CATS"
line 182 : added "s" to "correcte"
line 183 : replaced "Présentation des rubriques" with "Vue d'ensemble des sujets"
line 184 : replaced "rubrique" (section) with "sujet" (topic)

I don't reach to upload the file, how may I do ?


2014-11-26 14:05

reporter   ~0005129

Last edited: 2014-11-26 14:06

I do not agree with all the minor changes from Speedy67

line 7: I did not propose to write "Mel". In I wrote, that "Mel" should be replaced. In some circumstances, it can be "Mél." (with accent and point).

line 13: spaces before punctuation marks is a hot iron. As descrived in it is different following fr_FR, fr_BE, fr_CA, fr_CH. At least, we should follow the same rules in the same document. It was fr_CH/fr_BE/fr_CA for !? and fr_CH/fr_BE for ". If the fr_FR space is added here, we have to add all other fr_FR spaces.

line 40: see line 13
line 45: changed "lieu" (place) into "ville" (city) --> Lieu is a neutrum term. ville is different in BE/CA/CH/FR. That was the reason to replace ville before into lieu. Ville has at least 2000 inhabitans (FR), 10 000 inhabitants (CH), 20 000 (Algérie), in special cases or some municipalities (CA, BE, CGO). "Lieu" as 'inhabitated place' is independent of any country and used in postal circumstances.

line 78: see line 13
line 138: see line 13
line 154: see line 13

For the other minor changes, I agree. As with exeption from the Line-7-case, we have to descide, how it should be (as in France, as in the majority of the countries concerned, as neutral as possible), I did not change anything. For further details, please read the linked former notes.


2014-11-26 18:19

reporter   ~0005130

You're right, ok for Mél.

Line 45 : In France, the neutrum term for this use is "Commune" which doesn't refer to the population of the area. Otherwise, 70% of the population in industrial contries is living in towns so who will make the difference ? Perhaps me because I do actually live in a place with less than 2 000 inhabitants. But I suppose that this word isn't more suitable in other french versions. It's impossible to reach a perfect translation with a such scientific precision. The only solution, is to write a separate file for each kind of french.
It's so on for the ponctuation problem... Note that in fr_FR, nobody take care of the difference between the half and full space. For me (I learned dactylography in my past and still practice it everyday), some lakes of space are very shoking.

Note that changed nothing at the moment because I don't know how to upload my file.


2014-12-15 08:57

reporter   ~0005176

Last edited: 2014-12-15 12:58

"Commune" (municipality) is a term of the administrative division. We record the place name as in postal adress. Often, there are several named places in one municipality. "Lieu" means otherwise 'named place' and is used by postal service. Maybe it is less common in France. An alternative would be "Localité".

For the typographie, I would prefer a compromise. In the version as (finaly not) reviewed, it was as in fr_CH and fr_BE (done by me), because there are more assurer in the WoT register for this countries as for France or Canada. "Majority" could also be calculated on the base of inhabitants (most in France) or by surface (biggest: Canada). I think is important: It has to be always the same typography. And we have to justify our choice. Only some rare experts (Speedy67, me), will see, that it is for some countries a little bit unusual.

I hope we finish this year, as CATS can be done in french as soon as possible.


2015-01-25 00:43

reporter   ~0005262

@bergerc, @Lordguy, @speedy67

The French translation is finished, but did not pass the review, as typography is fr_BE/fr_CH and one reviewer asked for fr_FR.

Please read and give your advice.

There are some possibilities to get further, but we have to take a decision.


2015-01-25 16:41

reporter   ~0005264

Last edited: 2015-01-25 16:42

I wrote to the cacert-translation list the following e-mail*:

> Let's finish the French CATS
> The French translation of CATS is finished, but did not pass the review, as
> typography is fr_BE/fr_CH and one reviewer asked for fr_FR.
> I made a proposition, how the issue could be solved. Please read
> [^] and give your advice.
> There are some possibilities to get further (see link below), but we have to
> take a decision to get French finally into CATS (after more than 5 years).

One the same list, two answers where given:

**** First answer by Hervé ***
"Le mot "Commune" est celui qui est utilisé dans les formulations administratives
(France), toutefois, "localité" peut sans problème être utilisé lorsqu'on parle
d'adresse postale.

Peut-on envisager plusieurs fichier xx_FR ?"

In English: In France, "commune" is used for administrative purposes, but the term "localité" fit well for postal adresses.

*** Second answer by Grégoire ***
"Localité" for fr_FR is certainly the best fit. I do not know for other countries.

In french3.php there are some typos.
May I suggest adding an ending "s" (plural as questions and réponses) "incorrectes" in the following phrase: "Class_Progress_08","questions réponses incorrecte" ?
May I also suggest removing the ending "t" at "réussit" in the following phrase: "Class_Quiz_09","n'avez pas réussit le test.")
Same as first suggestion "correcte" shall have an ending "s" as "réponses" is plural. "Topic_01","Remarque: Vous ne pouvez pas déclarer des réponses comme correcte ici, alors qu'elles ont été déclarées incorrectes ci-dessous.")


2015-01-25 18:21

reporter   ~0005270

Couldn't we find something acceptable in all locales ?
It's hard enough to get a translation done in frech, I think we will never get the thing done in all locales (this thread started in 2011!)


2015-01-25 21:47

reporter   ~0005278

I agree completly with Bergerc.

It seems that "localité" is OK for France and Switzerland as well. In Belgium and Canada it is used by the government. What about Luxembourg?

To avoid 5 European locals (and later about 20 African ones), we need a compromise about half/small spaces before some punctuation marks (see for details).

As proposed, it follows the CH/BE rules, because in CH and BE are more assurers as in FR and CA and it fits also for 50% in CA. If someone does not agree, he can propose another way (for example as in FR due to the bigest population or as in CA due to the bigest surface).

If a compromise can be found in January, I can ad the latest changes in february as I have some days holidays and after review in March we could roll out the French CATS in a Easter egg.... after 40 months.


2016-02-17 13:30

reporter   ~0005496

@Ted: It seams, that there is no more discussion about this topic. Can we go further to the two reviews?

Most of the suggestions made here are now merged in this file:

Please merge it to SVN.

Best regards

The compromises are:
- Typographie remains as in fr_CH, fr_BE and partially in fr_CN (no half spaces before :/?/!)
- inhabited place is "localité" as neutrum for ville/commune/lieu/etc.
- "code postal" as in FR, CN, BE, LU, Tunisie, Maroc (and not as in CH "numéro postal")


2016-02-17 13:42

reporter   ~0005497

In my opinion this version (5496) is OK.


2016-02-17 21:28

reporter   ~0005498


For me this version is also good, it's a good compromise between all languages.

OK to commit it to the CATS


2016-02-17 23:25

reporter   ~0005499


For me this version is also good, it's a good compromise between all languages.



2016-02-18 16:33

reporter   ~0005500


I regret that the fr_FR half spaces was not held.

There is just a mistake at line 39 where the circumflexe accent is missing to "plaît" (see

I agree with the other compromises.


2016-02-18 20:15

reporter   ~0005501

@speedy67: Of course, you are right. As Ted did not pass here until now, I corrected it in Github. Thank you. Eights eyes see more than six ;-)


2018-09-03 07:37

administrator   ~0005607

Hmm... the modifications seem to be ready to deploy... I'll have to look into that!


2018-09-03 20:12

administrator   ~0005608

The changes are now merged into the production server.

Note that I currently have troubles accessing https from the testserver, so the installation on the testserver is not up to date!

A few notes:
* Currently CATS uses ISO-8859-1, so the language files also have to use this encoding
* An alternative would be to use HTML entities, which would probably ease the migration to UTF-8...
* I'm not using the SVN server anymore, my master for CATS is If you want to keep SVN up to date, you're welcome... :-)
* If more changes are wanted for french, please create a new case for it and add this case as related. I guess this will keep things more clearly arranged.


2019-01-02 20:06

reporter   ~0005723

Ted merged the changes into the production server and it's operational for several weeks now.

Issue History

Date Modified Username Field Change
2011-08-22 21:15 Ted New Issue
2011-08-22 21:15 Ted Issue generated from: 0000969
2011-08-22 21:16 Ted Issue cloned: 0000971
2011-08-22 22:01 Ted Note Added: 0002316
2011-08-22 22:01 Ted Assigned To => Ted
2011-08-22 22:01 Ted Status new => needs work
2011-08-22 22:07 Ted Status needs work => needs review & testing
2011-08-31 04:31 INOPIAE Note Added: 0002377
2011-09-04 22:10 nvasseur File Added: french.php
2011-09-04 22:13 nvasseur Note Added: 0002402
2012-10-17 21:36 Lordguy Note Added: 0003260
2012-10-17 22:25 Ted Note Added: 0003261
2012-10-17 22:25 Ted Status needs review & testing => ready to deploy
2012-11-19 22:21 Ted Note Added: 0003344
2012-11-19 22:21 Ted Status ready to deploy => solved?
2012-11-19 22:21 Ted Resolution open => fixed
2012-12-27 17:12 Werner Dworak Relationship added related to 0001107
2012-12-31 16:28 L10N Note Added: 0003585
2012-12-31 16:28 L10N Status solved? => needs feedback
2012-12-31 16:28 L10N Resolution fixed => reopened
2012-12-31 16:48 L10N Note Edited: 0003585
2012-12-31 17:17 L10N Note Edited: 0003585
2013-01-01 12:24 Lordguy Note Added: 0003586
2013-01-07 21:13 Ted Note Added: 0003595
2013-01-07 21:13 Ted Status needs feedback => needs work
2013-01-07 22:02 L10N File Added: french2.php
2013-01-07 22:06 L10N Note Added: 0003596
2013-01-19 20:45 Ted Note Added: 0003710
2013-01-19 20:47 Ted Note Edited: 0003710
2013-01-19 20:48 Ted Note Edited: 0003710
2013-04-07 13:13 Ted Status needs work => needs review & testing
2013-04-07 22:23 speedy67 Note Added: 0003866
2013-04-08 01:01 bergerc Note Added: 0003868
2013-07-05 13:21 L10N Note Added: 0004096
2013-07-05 13:41 bergerc Note Added: 0004097
2013-07-05 17:04 L10N File Added: french3.php
2013-07-05 17:29 L10N Note Added: 0004098
2013-07-05 21:02 bergerc Note Added: 0004099
2013-07-09 09:23 bergerc Note Added: 0004104
2013-12-23 10:49 L10N Note Added: 0004484
2014-02-11 22:53 Ted Note Added: 0004580
2014-02-11 22:54 Ted Status needs review & testing => needs review
2014-11-22 17:43 Ted Note Added: 0005118
2014-11-23 02:49 Lordguy Note Added: 0005119
2014-11-25 00:14 speedy67 Note Added: 0005126
2014-11-25 00:14 speedy67 Note Edited: 0005126
2014-11-26 14:05 L10N Note Added: 0005129
2014-11-26 14:06 L10N Note Edited: 0005129
2014-11-26 14:06 L10N Note Edited: 0005129
2014-11-26 18:19 speedy67 Note Added: 0005130
2014-12-15 08:57 L10N Note Added: 0005176
2014-12-15 12:55 L10N Note Edited: 0005176
2014-12-15 12:58 L10N Note Edited: 0005176
2014-12-15 13:43 L10N Tag Attached: CATS
2014-12-15 13:43 L10N Tag Attached: Translation
2015-01-25 00:43 L10N Note Added: 0005262
2015-01-25 16:41 L10N Note Added: 0005264
2015-01-25 16:42 L10N Note Edited: 0005264
2015-01-25 18:21 bergerc Note Added: 0005270
2015-01-25 21:47 L10N Note Added: 0005278
2016-02-17 13:30 L10N Note Added: 0005496
2016-02-17 13:42 L10N Note Added: 0005497
2016-02-17 21:28 bergerc Note Added: 0005498
2016-02-17 23:25 Lordguy Note Added: 0005499
2016-02-18 16:33 speedy67 Note Added: 0005500
2016-02-18 20:15 L10N Note Added: 0005501
2018-09-03 07:37 Ted Status needs review => ready to deploy
2018-09-03 07:37 Ted Note Added: 0005607
2018-09-03 20:12 Ted Status ready to deploy => solved?
2018-09-03 20:12 Ted Resolution reopened => fixed
2018-09-03 20:12 Ted Note Added: 0005608
2019-01-02 20:06 L10N Status solved? => closed
2019-01-02 20:06 L10N Note Added: 0005723