H-uru
/
moul-assets
mirror of https://github.com/H-uru/moul-assets.git
17
4
Fork 3
Code Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
281 Commits
1 Branch
0 Tags
38 GiB
Tree: 08f03f3fe1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '08f03f3fe1'
${ noResults }
moul-assets/compiled/dat/KIFrench.loc

1111 lines
39 KiB
Raw Normal View History Unescape

Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<?xml version="1.0" encoding="utf-8"?>
<localizations>
<age name="KI">
<set name="CCR">
<element name="Away">
<translation language="French">PAC momentanément absent</translation>
</element>
<element name="Cancel">
<translation language="French">Annuler</translation>
</element>
<element name="Comment">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Commentaire :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="ConversationEnded">
<translation language="French">(fin de conversation)</translation>
</element>
<element name="ConversationStarted">
<translation language="French">(début de conversation)</translation>
</element>
<element name="NoCCR">
<translation language="French">(Aucun CCR en contact, message non envoyé)</translation>
</element>
<element name="PetitionSent">
<translation language="French">(%1s envoyé) %2s</translation>
</element>
<element name="PetitionTitle">
<translation language="French">Pétition en ligne</translation>
</element>
<element name="PetitionType">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Type de pétition :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="PopupBug">
<translation language="French">Rapport de bug</translation>
</element>
<element name="PopupExploit">
<translation language="French">Exploits et problèmes de cheats</translation>
</element>
<element name="PopupFeedback">
<translation language="French">Remarques et suggestions</translation>
</element>
<element name="PopupGeneral">
<translation language="French">Aide générale</translation>
</element>
<element name="PopupHarass">
<translation language="French">Harcèlement et code de conduite</translation>
</element>
<element name="PopupStuck">
<translation language="French">Coincé</translation>
</element>
<element name="PopupTechnical">
<translation language="French">Problèmes techniques</translation>
</element>
<element name="Subject">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Objet :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="Submit">
<translation language="French">Valider</translation>
</element>
</set>
<set name="Chat">
<element name="AFK">
<translation language="French"> (Je suis à la surface. Je serai de retour dans une minute)</translation>
</element>
<element name="BroadcastMsgRecvd">
<translation language="French"> </translation>
</element>
<element name="BroadcastSendTo">
<translation language="French"> </translation>
</element>
<element name="CCRFromPlayer">
<translation language="French">De %1s à PAC :</translation>
</element>
<element name="CCRMsgRecvd">
<translation language="French">De PAC :</translation>
</element>
<element name="CCRSendTo">
<translation language="French">À PAC :</translation>
</element>
<element name="CannotFindBuddy">
</element>
<element name="ErrorMsgRecvd">
<translation language="French">Erreur :</translation>
</element>
<element name="InterAgeMsgRecvd">
<translation language="French">De </translation>
</element>
<element name="InterAgeNotAvailable">
<translation language="French">(Commutateur Inter-Âge non disponible)</translation>
</element>
<element name="InterAgePlayerRecvd">
<translation language="French">%1s dans %2s</translation>
</element>
<element name="InterAgeSendTo">
<translation language="French">À </translation>
</element>
<element name="LeftTheAge">
<translation language="French">(%1s a quitté l'Âge)</translation>
</element>
<element name="LeftTheGame">
<translation language="French">(%1s a quitté le jeu)</translation>
</element>
<element name="LogStarted">
<translation language="French">Début de Chat.log...</translation>
</element>
<element name="LogStopped">
<translation language="French">...Fin de Chat.log.</translation>
</element>
<element name="MarkerAllTeams">
<translation language="French">Toutes les équipes</translation>
</element>
<element name="MarkerGreenTeam">
<translation language="French">Équipe verte</translation>
</element>
<element name="MarkerRedTeam">
<translation language="French">Équipe rouge</translation>
</element>
<element name="MarkerTOAllTeams">
<translation language="French">À : Toutes les équipes &gt;</translation>
</element>
<element name="MarkerTOGreenTeam">
<translation language="French">À : Équipe verte &gt;</translation>
</element>
<element name="MarkerTORedTeam">
<translation language="French">À : Équipe rouge &gt;</translation>
</element>
<element name="NoOneListening">
<translation language="French">(Vous êtes trop loin. Vous devriez peut-être crier ?)</translation>
</element>
<element name="NoOneToReply">
<translation language="French">(Il n'y a personne à qui répondre.)</translation>
</element>
<element name="PrivateMsgRecvd">
<translation language="French">De </translation>
</element>
<element name="PrivateSendTo">
<translation language="French">À </translation>
</element>
<element name="TOPrompt">
<translation language="French">À :</translation>
</element>
<element name="WentOffline">
<translation language="French">(%1s est hors ligne. Conversation impossible.)</translation>
</element>
</set>
<set name="Commands">
<element name="Accept">
<translation language="French">accepter</translation>
</element>
<element name="AddBuddy">
</element>
<element name="Afk">
<translation language="French">absent</translation>
</element>
<element name="Amazed">
</element>
<element name="AskQuestion">
</element>
<element name="AutoShout">
</element>
<element name="BeckonBig">
</element>
<element name="BeckonSmall">
</element>
<element name="BlowKiss">
</element>
<element name="Bow">
</element>
<element name="CCR">
<translation language="French">/pac</translation>
</element>
<element name="CallMe">
</element>
<element name="ChangePassword">
</element>
<element name="ChatAllAge">
<translation language="French">/crier</translation>
</element>
Support for /age (and localizations) to switch KI folder context without clicking
3 years ago
<element name="ChatAge">
<translation language="French">/âge</translation>
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="ChatBuddies">
<translation language="French">/amis</translation>
</element>
<element name="ChatClearAll">
<translation language="French">/effacerconversation</translation>
</element>
<element name="ChatNeighbors">
<translation language="French">/voisins</translation>
</element>
<element name="ChatPrivate">
<translation language="French">/p</translation>
</element>
<element name="ChatReply">
<translation language="French">/répondre</translation>
</element>
<element name="ChatStartLog">
<translation language="French">/démarrerlog</translation>
</element>
<element name="ChatStopLog">
<translation language="French">/arrêterlog</translation>
</element>
<element name="Cheer">
<translation language="French">salut</translation>
</element>
<element name="Clap">
<translation language="French">applaudir</translation>
</element>
<element name="Cower">
</element>
<element name="Crazy">
</element>
<element name="Cries">
<translation language="French">pleurnicher</translation>
</element>
<element name="Cringe">
</element>
<element name="CrossArms">
</element>
<element name="Cry">
<translation language="French">pleurer</translation>
</element>
<element name="Dance">
<translation language="French">danser</translation>
</element>
<element name="Doh">
</element>
<element name="DontKnow">
<translation language="French">jenesaispas</translation>
</element>
<element name="DumpLog">
</element>
<element name="DumpLogs">
</element>
<element name="Dunno">
<translation language="French">chaispas</translation>
</element>
<element name="Flinch">
</element>
<element name="Groan">
</element>
<element name="Ignore">
</element>
<element name="Invite">
<translation language="French">inviter</translation>
</element>
<element name="Kneel">
</element>
<element name="LOL">
<translation language="French">mdr</translation>
</element>
<element name="Laugh">
<translation language="French">rire</translation>
</element>
<element name="LeanLeft">
</element>
<element name="LeanRight">
</element>
<element name="LookAround">
</element>
<element name="Me">
</element>
<element name="No">
<translation language="French">non</translation>
</element>
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<element name="Ok">
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="Okay">
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<translation language="French">daccord</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="OverHere">
</element>
<element name="Peer">
</element>
<element name="Petition">
<translation language="French">/pétition</translation>
</element>
<element name="PetitionBug">
<translation language="French">/bug</translation>
</element>
<element name="PetitionExploit">
<translation language="French">/exploit</translation>
</element>
<element name="PetitionFeedback">
<translation language="French">/opinion</translation>
</element>
<element name="PetitionGeneral">
<translation language="French">/aide</translation>
</element>
<element name="PetitionHarass">
<translation language="French">/harcèlement</translation>
</element>
<element name="PetitionStuck">
<translation language="French">/coincé</translation>
</element>
<element name="PetitionTechnical">
<translation language="French">/supporttechnique</translation>
</element>
<element name="Point">
<translation language="French">pointer</translation>
</element>
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<element name="ROFL">
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="ROTFL">
<translation language="French">mdrept</translation>
</element>
<element name="RemoveBuddy">
</element>
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<element name="Sad">
<translation language="French">triste</translation>
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="Salute">
</element>
<element name="ScratchHead">
</element>
<element name="SendFriendInvite">
</element>
<element name="ShakeFist">
</element>
<element name="Shoo">
</element>
<element name="ShowInvites">
<translation language="French">montrerinvit</translation>
</element>
<element name="Shrug">
<translation language="French">épaules</translation>
</element>
<element name="Sit">
<translation language="French">assis</translation>
</element>
<element name="SlouchSad">
</element>
<element name="Sneeze">
<translation language="French">éternuer</translation>
</element>
<element name="Stop">
</element>
<element name="TalkHand">
</element>
<element name="TapFoot">
</element>
<element name="Taunt">
</element>
<element name="Thanks">
<translation language="French">merci</translation>
</element>
<element name="ThumbsDown">
</element>
<element name="ThumbsDown2">
</element>
<element name="ThumbsUp">
</element>
<element name="ThumbsUp2">
</element>
<element name="Thx">
<translation language="French">mrc</translation>
</element>
<element name="Unignore">
</element>
<element name="Uninvite">
<translation language="French">supinvit</translation>
</element>
<element name="Wave">
<translation language="French">signemain</translation>
</element>
<element name="WaveBye">
</element>
<element name="WaveLow">
</element>
<element name="Winded">
</element>
<element name="Yawn">
<translation language="French">bâiller</translation>
</element>
<element name="Yes">
<translation language="French">oui</translation>
</element>
</set>
<set name="Config">
<element name="ChatFadeTime">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Temps de fondu des discussions :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="Description">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Description :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="FontSize">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Taille de police :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="OnlyBuddies">
<translation language="French">Uniquement accepter les messages privés et les e-mails des Amis</translation>
</element>
<element name="OwnerCoOwners">
<translation language="French">%1s propriétaires</translation>
</element>
<element name="OwnerConfig">
<translation language="French">Paramètres de %1s</translation>
</element>
<element name="OwnerVisitors">
<translation language="French">%1s visiteurs</translation>
</element>
<element name="Settings">
<translation language="French">Paramètres du KI</translation>
</element>
<element name="Volume">
<translation language="French">Volume</translation>
</element>
</set>
<set name="EmoteStrings">
<element name="Amazed">
</element>
<element name="AskQuestion">
</element>
<element name="BeckonBig">
</element>
<element name="BeckonSmall">
</element>
<element name="BlowKiss">
</element>
<element name="Bow">
</element>
<element name="CallMe">
</element>
<element name="Cheer">
<translation language="French">%1s salue</translation>
</element>
<element name="Clap">
<translation language="French">%1s applaudit</translation>
</element>
<element name="Cower">
</element>
<element name="Crazy">
</element>
<element name="Cries">
<translation language="French">%1s pleurniche</translation>
</element>
<element name="Cringe">
</element>
<element name="CrossArms">
</element>
<element name="Cry">
<translation language="French"><![CDATA[<snif> %1s est triste]]></translation>
</element>
<element name="Dance">
<translation language="French">%1s danse</translation>
</element>
<element name="Doh">
</element>
<element name="DontKnow">
<translation language="French">%1s hausse les épaules</translation>
</element>
<element name="Dunno">
<translation language="French">%1s hausse les épaules</translation>
</element>
<element name="Flinch">
</element>
<element name="Groan">
</element>
<element name="Her">
</element>
<element name="His">
</element>
<element name="Kneel">
</element>
<element name="LOL">
<translation language="French">%1s est mort de rire</translation>
</element>
<element name="Laugh">
<translation language="French">%1s rit</translation>
</element>
<element name="LeanLeft">
</element>
<element name="LeanRight">
</element>
<element name="LookAround">
</element>
<element name="No">
<translation language="French">%1s refuse de la tête</translation>
</element>
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<element name="Ok">
<translation language="French">%1s dit ok</translation>
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="Okay">
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<translation language="French">%1s dit d'accord</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="OverHere">
</element>
<element name="Peer">
</element>
<element name="Point">
<translation language="French">%1s pointe du doigt</translation>
</element>
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<element name="ROFL">
<translation language="French">%1s est mort de rire écroulé par terre</translation>
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="ROTFL">
<translation language="French">%1s est mort de rire écroulé par terre</translation>
</element>
Add KI commands and emote text for /ok, /rofl, /sad, and some minor capitalization and foreign language goodies
3 years ago
<element name="Sad">
<translation language="French"><![CDATA[<snif> %1s est triste]]></translation>
</element>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
<element name="Salute">
</element>
<element name="ScratchHead">
</element>
<element name="ShakeFist">
</element>
<element name="Shoo">
</element>
<element name="Shrug">
<translation language="French">%1s hausse les épaules</translation>
</element>
<element name="SlouchSad">
</element>
<element name="Sneeze">
<translation language="French">%1s éternue</translation>
</element>
<element name="Stop">
</element>
<element name="TalkHand">
</element>
<element name="TapFoot">
</element>
<element name="Taunt">
</element>
<element name="Thanks">
<translation language="French">%1s vous remercie bien !</translation>
</element>
<element name="ThumbsDown">
</element>
<element name="ThumbsDown2">
</element>
<element name="ThumbsUp">
</element>
<element name="ThumbsUp2">
</element>
<element name="Thx">
<translation language="French">%1s vous remercie</translation>
</element>
<element name="Wave">
<translation language="French">%1s fait un signe de la main</translation>
</element>
<element name="WaveBye">
</element>
<element name="WaveLow">
</element>
<element name="Winded">
</element>
<element name="Yawn">
<translation language="French">%1s bâille</translation>
</element>
<element name="Yes">
<translation language="French">%1s acquiesce de la tête</translation>
</element>
</set>
<set name="Errors">
<element name="AuthFailed">
<translation language="French">Un problème est survenu pendant la connexion. Veuillez vérifier votre compte et votre mot de passe et réessayer.
#14</translation>
</element>
<element name="AuthFailed2">
<translation language="French">Un problème est survenu pendant la connexion. Veuillez vérifier votre compte et votre mot de passe et réessayer.
#23</translation>
</element>
<element name="AuthTimeout">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#15</translation>
</element>
<element name="AuthenticationTimedOut">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#19</translation>
</element>
<element name="BadJournalElement">
<translation language="French">Élément de journal incorrect</translation>
</element>
<element name="BadPassword">
</element>
<element name="CCRInternal">
Replace non-Latin-1 characters in .loc files Uru's fonts are limited to Latin-1 characters. If any characters outside that range are used in in-game texts, the characters are either not displayed at all or are replaced with a question mark symbol. This change replaces all non-Latin-1 characters in all .loc files with ASCII equivalents, so that they are displayed properly in-game. Specifically, the following replacements are performed: * Unicode dashes to ASCII hyphen-minus ([–—] to -) * "Curly" quotes to "straight" quotes ([‘’‚] to ', [“”„] to ") * Unicode ellipsis to ASCII dots (… to ...) * œ to oe (sorry France)
3 years ago
<translation language="French">Vous avez été refusé(e) car les PAC doivent disposer d'un code client interne.
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
#08</translation>
</element>
<element name="CCRLobby">
Replace non-Latin-1 characters in .loc files Uru's fonts are limited to Latin-1 characters. If any characters outside that range are used in in-game texts, the characters are either not displayed at all or are replaced with a question mark symbol. This change replaces all non-Latin-1 characters in all .loc files with ASCII equivalents, so that they are displayed properly in-game. Specifically, the following replacements are performed: * Unicode dashes to ASCII hyphen-minus ([–—] to -) * "Curly" quotes to "straight" quotes ([‘’‚] to ', [“”„] to ") * Unicode ellipsis to ASCII dots (… to ...) * œ to oe (sorry France)
3 years ago
<translation language="French">Vous avez été refusé(e) car les PAC doivent se connecter par le biais d'une salle protégée.
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
#07</translation>
</element>
<element name="CantFindAge">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#13</translation>
</element>
<element name="CantSend">
<translation language="French">Envoi impossible</translation>
</element>
<element name="CommandError">
Consistently use guillemets in French translation The French translation was inconsistent about its quote style. Some parts used guillemets, but others used double quotes. As far as I know, guillemets are the standard quote form in French. Note that in French, there are spaces on the inside of the guillemets as well, not just on the outside as in most other languages. These inside spaces should be non-breaking spaces, so that the guillemets are line-wrapped together with the text being quoted.
3 years ago
<translation language="French">Impossible de « %1s »</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="EmailAddressTooLong">
</element>
<element name="EmptyError">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#01</translation>
</element>
<element name="FailedToCreatePlayer">
<translation language="French">Un problème est survenu pendant la création de votre joueur. Veuillez quitter le programme et réessayer.
#24</translation>
</element>
<element name="FailedToSendMsg">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#18</translation>
</element>
<element name="InvalidErrorCode">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#25</translation>
</element>
<element name="InvitesDisabled">
</element>
<element name="KickedOff">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#05</translation>
</element>
<element name="LinkingBanned">
<translation language="French">Votre capacité de liaison a été désactivée
#26</translation>
</element>
<element name="LinkingRestored">
<translation language="French">Votre capacité de liaison a été rétablie
#27</translation>
</element>
<element name="LoggedInElsewhere">
Replace non-Latin-1 characters in .loc files Uru's fonts are limited to Latin-1 characters. If any characters outside that range are used in in-game texts, the characters are either not displayed at all or are replaced with a question mark symbol. This change replaces all non-Latin-1 characters in all .loc files with ASCII equivalents, so that they are displayed properly in-game. Specifically, the following replacements are performed: * Unicode dashes to ASCII hyphen-minus ([–—] to -) * "Curly" quotes to "straight" quotes ([‘’‚] to ', [“”„] to ") * Unicode ellipsis to ASCII dots (… to ...) * œ to oe (sorry France)
3 years ago
<translation language="French">Vous avez été déconnecté(e) car quelqu'un d'autre utilise déjà votre compte.
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
#02</translation>
</element>
<element name="MalformedLogDumpCmd">
</element>
<element name="MissingEmailAddress">
</element>
<element name="NotAuthenticated">
<translation language="French">Un problème est survenu pendant la connexion. Veuillez vérifier votre compte et votre mot de passe et réessayer.
#04</translation>
</element>
<element name="OldVersion">
Replace non-Latin-1 characters in .loc files Uru's fonts are limited to Latin-1 characters. If any characters outside that range are used in in-game texts, the characters are either not displayed at all or are replaced with a question mark symbol. This change replaces all non-Latin-1 characters in all .loc files with ASCII equivalents, so that they are displayed properly in-game. Specifically, the following replacements are performed: * Unicode dashes to ASCII hyphen-minus ([–—] to -) * "Curly" quotes to "straight" quotes ([‘’‚] to ', [“”„] to ") * Unicode ellipsis to ASCII dots (… to ...) * œ to oe (sorry France)
3 years ago
<translation language="French">Cette version d'Uru est trop ancienne. Veuillez quitter le programme et mettre le jeu à jour.
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
#11</translation>
</element>
<element name="PasswordTooLong">
</element>
<element name="PeerTimedOut">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#20</translation>
</element>
<element name="PlayerDisabled">
Replace non-Latin-1 characters in .loc files Uru's fonts are limited to Latin-1 characters. If any characters outside that range are used in in-game texts, the characters are either not displayed at all or are replaced with a question mark symbol. This change replaces all non-Latin-1 characters in all .loc files with ASCII equivalents, so that they are displayed properly in-game. Specifically, the following replacements are performed: * Unicode dashes to ASCII hyphen-minus ([–—] to -) * "Curly" quotes to "straight" quotes ([‘’‚] to ', [“”„] to ") * Unicode ellipsis to ASCII dots (… to ...) * œ to oe (sorry France)
3 years ago
<translation language="French">Le joueur que vous avez sélectionné n'est pas autorisé à Uru. Veuillez contacter le support clientèle pour plus d'informations.
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
#12</translation>
</element>
<element name="PlayerNotFound">
<translation language="French">Joueur introuvable</translation>
</element>
<element name="ProtocolVersionMismatch">
Replace non-Latin-1 characters in .loc files Uru's fonts are limited to Latin-1 characters. If any characters outside that range are used in in-game texts, the characters are either not displayed at all or are replaced with a question mark symbol. This change replaces all non-Latin-1 characters in all .loc files with ASCII equivalents, so that they are displayed properly in-game. Specifically, the following replacements are performed: * Unicode dashes to ASCII hyphen-minus ([–—] to -) * "Curly" quotes to "straight" quotes ([‘’‚] to ', [“”„] to ") * Unicode ellipsis to ASCII dots (… to ...) * œ to oe (sorry France)
3 years ago
<translation language="French">Cette version d'Uru est trop ancienne. Veuillez quitter le programme et mettre le jeu à jour.
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
#22</translation>
</element>
<element name="SDLDescProblem">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#16</translation>
</element>
<element name="ServerSilence">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#10</translation>
</element>
<element name="ServerSilence2">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#21</translation>
</element>
<element name="Silenced">
<translation language="French">Votre aptitude à la discussion a été désactivée
#28</translation>
</element>
<element name="TextOnly">
<translation language="French">Doit être en texte uniquement</translation>
</element>
<element name="TimeBroke">
<translation language="French"><![CDATA[<liaison temporelle rompue>]]></translation>
</element>
<element name="TimedOut">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#03</translation>
</element>
<element name="UnknownPlayerType">
<translation language="French">Type de joueur inconnu</translation>
</element>
<element name="UnknownReason">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#06</translation>
</element>
<element name="UnknownReason2">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#09</translation>
</element>
<element name="Unsilenced">
<translation language="French">Votre aptitude à la discussion a été rétablie
#29</translation>
</element>
<element name="UnspecifiedError">
<translation language="French">Il semble y avoir un problème avec la connexion. Veuillez quitter le programme et réessayer.
#17</translation>
</element>
</set>
<set name="Folders">
<element name="Devices">
<translation language="French">Appareils</translation>
</element>
<element name="OwnLists">
<translation language="French">Listes de propriétaires de l'Âge :</translation>
</element>
<element name="VisLists">
<translation language="French">Listes de visiteurs :</translation>
</element>
</set>
<set name="Image">
<element name="InitialTitle">
<translation language="French"><![CDATA[<écrire une légende>]]></translation>
</element>
</set>
<set name="Invitation">
<element name="AcceptUsage">
<translation language="French"><![CDATA[Utilisation : /accepter <Nom de l'ami> <Mot de passe>]]></translation>
</element>
<element name="CouldNotCast">
<translation language="French">Impossible de diffuser l'élément de liste vers la note</translation>
</element>
<element name="DeletedInvitation">
<translation language="French">Invitation supprimée : </translation>
</element>
<element name="InviteAccepted">
<translation language="French">Invitation en cours d'acceptation avec l'Ami : %1s et la Touche : %2s</translation>
</element>
<element name="InviteKeyAdded">
<translation language="French">Touche d'invitation ajoutée : %1s</translation>
</element>
<element name="InviteNotFound">
<translation language="French">Invitation introuvable</translation>
</element>
<element name="InviteUsage">
<translation language="French"><![CDATA[Utilisation : /inviter <Mot de passe>]]></translation>
</element>
<element name="Keys">
<translation language="French">Touches : </translation>
</element>
<element name="MaxInvites">
<translation language="French">Nombre max d'invitations atteint</translation>
</element>
<element name="MissingInviteFolder">
<translation language="French">Dossier d'invitation manquant</translation>
</element>
<element name="RemoveNodeFailed">
<translation language="French">Échec de la suppression du Noeud</translation>
</element>
<element name="RevokeBody">
<translation language="French"><![CDATA[Votre droit de visite à l'Âge %1s n'est plus valide.
<Pardon>
Signé,
%2s (Propriétaire)]]></translation>
</element>
<element name="RevokeTitle">
<translation language="French">Visite à %1s supprimée</translation>
</element>
<element name="UninviteUsage">
<translation language="French"><![CDATA[Utilisation : /supinvit <Mot de passe>]]></translation>
</element>
<element name="VisitBody">
<translation language="French">Venez visiter l'Âge %1s en vous rendant au MT Nexus et en utilisant votre Lien privée
Signé(e),
%2s (Propriétaire)
</translation>
</element>
<element name="VisitTitle">
<translation language="French">Invitation à %1s</translation>
</element>
</set>
<set name="Journal">
<element name="InitialMessage">
<translation language="French"><![CDATA[<écrire un message>]]></translation>
</element>
<element name="InitialTitle">
<translation language="French"><![CDATA[<écrire un titre>]]></translation>
</element>
</set>
<set name="MarkerGame">
<element name="AddMarkerButton">
<translation language="French">Ajouter un marqueur</translation>
</element>
<element name="CaptureGame">
<translation language="French">Partie Capture</translation>
</element>
<element name="Captured">
<translation language="French">capturé(s)</translation>
</element>
<element name="Captures">
Consistently use guillemets in French translation The French translation was inconsistent about its quote style. Some parts used guillemets, but others used double quotes. As far as I know, guillemets are the standard quote form in French. Note that in French, there are spaces on the inside of the guillemets as well, not just on the outside as in most other languages. These inside spaces should be non-breaking spaces, so that the guillemets are line-wrapped together with the text being quoted.
3 years ago
<translation language="French">%1s a capturé « %2s ». %3s</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="DoneEditButton">
<translation language="French">Modification terminée</translation>
</element>
<element name="EditButton">
<translation language="French">Modifier la partie</translation>
</element>
<element name="EndGameButton">
<translation language="French">Terminer la partie</translation>
</element>
<element name="FinishedGame">
</element>
<element name="FoundMarker">
Consistently use guillemets in French translation The French translation was inconsistent about its quote style. Some parts used guillemets, but others used double quotes. As far as I know, guillemets are the standard quote form in French. Note that in French, there are spaces on the inside of the guillemets as well, not just on the outside as in most other languages. These inside spaces should be non-breaking spaces, so that the guillemets are line-wrapped together with the text being quoted.
3 years ago
<translation language="French">Marqueur « %1s » trouvé.</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="GameBegins">
<translation language="French">Que la partie commence !</translation>
</element>
<element name="GameEnded">
<translation language="French">Fin de la partie... %1s</translation>
</element>
<element name="GameResults">
<translation language="French">Résultats de la partie :</translation>
</element>
<element name="GoBackButton">
<translation language="French">Précédent</translation>
</element>
<element name="GreenTeamScore">
<translation language="French">Équipeverte(%1s)</translation>
</element>
<element name="GreenTeamWins">
<translation language="French">L'équipe verte a gagné ! %1s à %2s</translation>
</element>
<element name="HoldGame">
<translation language="French">Partie Défense</translation>
</element>
<element name="InstructCapNMarkers">
<translation language="French">L'équipe qui capture le plus grand nombre de marqueurs parmi les %1s marqueurs en moins de %2s minute%3s... gagne !</translation>
</element>
<element name="InstructCapNoMarker">
<translation language="French">Cependant, puisqu'il n'y a aucun marqueur dans cette partie... tout le monde gagne et tout le monde perd !</translation>
</element>
<element name="InstructCapOneMarker">
<translation language="French">L'équipe qui capture l'unique marqueur en moins de %1s minute%2s... gagne !</translation>
</element>
<element name="InstructHoldNMarkers">
<translation language="French">L'équipe qui capture et défend le plus grand nombre de marqueurs parmi les %1s marqueurs en moins de %2s minute%3s... gagne !</translation>
</element>
<element name="InstructHoldNoMarker">
<translation language="French">Cependant, puisqu'il n'y a aucun marqueur dans cette partie... tout le monde gagne et tout le monde perd !</translation>
</element>
<element name="InstructQuest">
<translation language="French">Impossible d'inviter des joueurs... c'est un partie en solo.</translation>
</element>
<element name="InvitePlayerButton">
<translation language="French">Inviter un joueur</translation>
</element>
<element name="InviteRecvd">
<translation language="French">Invitation à un Jeu de marqueurs reçue. Vérifiez vos messages.</translation>
</element>
<element name="LastMarker">
<translation language="French">C'était le dernier marqueur.</translation>
</element>
<element name="MarkerListButton">
<translation language="French">Liste des marqueurs</translation>
</element>
<element name="MarkersRemaining">
<translation language="French">Marqueurs restants : %1s</translation>
</element>
<element name="MarkersUnclaimed">
<translation language="French">Marqueurs non demandés : %1s</translation>
</element>
<element name="NMarkers">
<translation language="French">%1s marqueurs</translation>
</element>
<element name="NameCapture">
<translation language="French">capture</translation>
</element>
<element name="NameHold">
<translation language="French">défense</translation>
</element>
<element name="NameQuest">
<translation language="French">quête</translation>
</element>
<element name="NameUnknown">
<translation language="French">style inconnu</translation>
</element>
<element name="NoMarker">
<translation language="French">aucun marqueur</translation>
</element>
<element name="OneMarker">
<translation language="French">un marqueur</translation>
</element>
<element name="OneMoreLeft">
<translation language="French">Il ne reste plus qu'un marqueur !</translation>
</element>
<element name="OwnerTitle">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">PROPRIÉTAIRE :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="PlayButton">
<translation language="French">Jouer</translation>
</element>
<element name="Popup10min">
<translation language="French">10 min</translation>
</element>
<element name="Popup1Min">
<translation language="French">1 min</translation>
</element>
<element name="Popup2min">
<translation language="French">2 min</translation>
</element>
<element name="Popup5min">
<translation language="French">5 min</translation>
</element>
<element name="PrematureEnding">
<translation language="French">Le Maître de jeu a interrompu la partie !</translation>
</element>
<element name="QMessage">
<translation language="French"> %1s souhaiterait vous inviter pour une partie de %2s.
%3s
souhaitez-vous jouer ?</translation>
</element>
<element name="QTitle">
<translation language="French">Rejoindre le Jeu de marqueurs de %1s</translation>
</element>
<element name="QuestGame">
<translation language="French">Partie Quête</translation>
</element>
<element name="RedTeamScore">
<translation language="French">Équiperouge(%1s)</translation>
</element>
<element name="RedTeamWins">
<translation language="French">L'équipe rouge a gagné ! %1s à %2s</translation>
</element>
<element name="RemoveMarkerButton">
<translation language="French">Supprimer un marqueur</translation>
</element>
<element name="ResetGameButton">
<translation language="French">Réinitialiser la partie</translation>
</element>
<element name="StartGameButton">
<translation language="French">Commencer la partie</translation>
</element>
<element name="StatusAllFound">
<translation language="French">Tous les marqueurs de la quête ont été trouvés.</translation>
</element>
<element name="StatusIn">
<translation language="French"> dans %1s</translation>
</element>
<element name="StatusNMarkers">
<translation language="French">Il y a %1s marqueurs</translation>
</element>
<element name="StatusNoMarkers">
<translation language="French">Il n'y a aucun marqueur</translation>
</element>
<element name="StatusNotAllFound">
<translation language="French">Tous les marqueurs de la quête n'ont pas été trouvés.</translation>
</element>
<element name="StatusOneMarker">
<translation language="French">Il y a un marqueur</translation>
</element>
<element name="StopPlayingButton">
<translation language="French">Arrêter de jouer</translation>
</element>
<element name="TieGame">
<translation language="French">Égalité. %1s à %2s</translation>
</element>
<element name="Time">
Use non-breaking spaces around French punctuation where appropriate In French, some punctuation characters (question mark, exclamation mark, colon, semicolon) also have a space before the symbol, not just after the symbol as in most other languages. This preceding space should be a non-breaking space, so that the punctuation is not wrapped onto a new line separate from the preceding word.
3 years ago
<translation language="French">Temps de jeu :</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="TimeRemaining">
<translation language="French">Temps restant : %1s:%1s</translation>
</element>
<element name="WaitingForStart">
<translation language="French">En attente du démarrage</translation>
</element>
<element name="createErrorExistingGame">
</element>
<element name="pendingActionEndingGame">
</element>
<element name="pendingActionLoading">
</element>
<element name="pendingActionPrepareGame">
</element>
<element name="pendingActionResetGame">
</element>
<element name="pendingActionSaving">
</element>
<element name="pendingActionUpgradeKI">
</element>
</set>
<set name="Messages">
<element name="AutoShoutDisabled">
</element>
<element name="AutoShoutEnabled">
</element>
<element name="DeleteJournal">
<translation language="French">Êtes-vous sûr(e) de vouloir supprimer "%1s" ?</translation>
</element>
<element name="DeletePicture">
<translation language="French">Êtes-vous sûr(e) de vouloir supprimer "%1s" ?</translation>
</element>
<element name="DeletePlayer">
Consistently use guillemets in French translation The French translation was inconsistent about its quote style. Some parts used guillemets, but others used double quotes. As far as I know, guillemets are the standard quote form in French. Note that in French, there are spaces on the inside of the guillemets as well, not just on the outside as in most other languages. These inside spaces should be non-breaking spaces, so that the guillemets are line-wrapped together with the text being quoted.
3 years ago
<translation language="French">Êtes-vous sûr(e) de vouloir retirer « %1s » de votre dossier « %2s » ?</translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="FullImages">
<translation language="French">Votre KI ne peut plus stocker les images dans votre journal. Il est plein.</translation>
</element>
<element name="FullMarkerGames">
</element>
<element name="FullMarkers">
<translation language="French">Votre KI ne peut plus stocker les marqueurs dans votre journal. Il est plein.</translation>
</element>
<element name="FullNotes">
<translation language="French">Votre KI ne peut plus stocker de texte dans votre journal. Il est plein.</translation>
</element>
<element name="InviteSuccess">
</element>
<element name="LeaveGame">
<translation language="French">Êtes-vous sûr(e) de vouloir quitter Uru ?</translation>
</element>
<element name="LogDumpFailed">
</element>
<element name="LogDumpSuccess">
</element>
<element name="NexusLinkAdded">
<translation language="French">Un lien a été ajouté a votre Nexus</translation>
</element>
<element name="OfferLinkTo">
Consistently use guillemets in French translation The French translation was inconsistent about its quote style. Some parts used guillemets, but others used double quotes. As far as I know, guillemets are the standard quote form in French. Note that in French, there are spaces on the inside of the guillemets as well, not just on the outside as in most other languages. These inside spaces should be non-breaking spaces, so that the guillemets are line-wrapped together with the text being quoted.
3 years ago
<translation language="French"><![CDATA[On vous propose une liaison vers « %1s » <cool !>. Souhaitez-vous y aller ?]]></translation>
Flip all Cyan LOC files through plLocalizationEditor. This round-trips the entire Cyan localization database through the plLocalizationEditor built from H-uru/Plasma#958. This means that: - the XML files are re-encoded from UTF-16 to UTF-8 and therefore should load faster due to less run-time re-encoding - journals should be written out as CDATA with the esHTML data visible in the clear
3 years ago
</element>
<element name="OpenHyperlink">
</element>
<element name="PasswordChangeFailure">
</element>
<element name="PasswordChangeSuccess">
</element>
</set>
<set name="Neighborhood">
<element name="AgeOwnedStatus">
<translation language="French">%1s propriétaire%2s et %3s visiteur%4s.</translation>
</element>
<element name="BottomLine">
<translation language="French">%1s sur %2s</translation>
</element>
<element name="MakePorP">
<translation language="French">Rendre %1s</translation>
</element>
<element name="NoName">
<translation language="French"><![CDATA[<aucun nom>]]></translation>
</element>
<element name="None">
<translation language="French">Aucune inscription dans aucun quartier</translation>
</element>
<element name="PorPAgeOwnedStatus">
<translation language="French">%1s propriétaire%2s et %3s visiteur%4s. Il s'agit d'un Âge %5s.</translation>
</element>
</set>
<set name="Player">
<element name="Added">
</element>
<element name="AlreadyAdded">
</element>
<element name="CreateBuddyTitle">
</element>
<element name="EnterID">
</element>
<element name="InAge">
<translation language="French">est en ligne et explore l'Âge %1s.</translation>
</element>
<element name="InCleft">
<translation language="French">est en ligne, perdu(e) dans la crevasse.</translation>
</element>
<element name="InCoset">
<translation language="French">est en ligne et change de vêtements.</translation>
</element>
<element name="NotFound">
</element>
<element name="NotYourself">
</element>
<element name="NumberOnly">
</element>
<element name="Offline">
<translation language="French">est hors ligne.</translation>
</element>
<element name="Removed">
</element>
</set>
<set name="YesNoDialog">
<element name="AcceptButton">
<translation language="French">Accepter</translation>
</element>
<element name="DeclineButton">
<translation language="French">Refuser</translation>
</element>
<element name="NoButton">
<translation language="French">Non</translation>
</element>
<element name="OKButton">
<translation language="French">Ok</translation>
</element>
<element name="QuitButton">
<translation language="French">Quitter</translation>
</element>
<element name="YESButton">
<translation language="French">Oui</translation>
</element>
</set>
</age>
</localizations>