You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RB3Enhanced contains a few localised strings that would be best to translate to each language supported by the game:
Generic:
RB3Enhanced $RB3E_BUILDTAG$ is active. Thank you for playing!
RB3Enhanced $RB3E_BUILDTAG$ (with $MOD_VERSION$) is active. Thank you for playing!
Modifiers:
Black Background
Force HOPOs - HOPOs being hammer-on-pull-offs in guitar
Mirror Mode - Mirror to mean reversed, like looking into a reflection / mirror
Gem Color Shuffle - Shuffle to mean the order is mixed around
Note Shuffle - See above
Double Bass Pedal - To mean two bass pedals
Liveless:
Manage Liveless
Enter the user code of the user you would like to join. (Case insensitive) - Where "user code" is like a 5 letter code, or key, that someone needs to give you to enter.
Your user code is $USER_CODE$. Anyone with this code and on your server can join you. Server: $SERVER_NAME$
Connected to the Liveless server! Select 'Join User Code' to join another player, or 'Show My User Code' to show your own user code. (Be careful when streaming - anyone with this code can join you!) - Where "streaming" means livestreaming e.g. on Twitch, YouTube.
What file should these be committed to? I'm happy to open a PR for French 🙂
Otherwise I can reply straight in this Issue if you prefer with a translation for each line.
Note: In french you're supposed to have a space before ! and ?, unlike english, so that space you see before ! and ? is intentional 🙂
For all purposes I've replaced "User" (Utilisateur) with "Player" (Joueur) as it is much shorter in french, and in the context of a game, conveys the same meaning.
I supposed this is meant to be a Welcome message. In that case, "Thanks for playing" is not translatable (it really only exists in the past tense, "Merci d'avoir joué"). This is why I replaced it with "have a good game" (Bon jeu). You can also have "thanks for the support" (Merci pour votre soutien!) if you think it's closer to what you meant.
If however this is meant to be a "goodbye" message, then "Merci d'avoir joué !" is the closest to "Thanks for playing!".
RB3Enhanced $RB3E_BUILDTAG$ est actif. Bon jeu !
RB3Enhanced $RB3E_BUILDTAG$ (avec $MOD_VERSION$) est actif. Bon jeu !
Modifiers:
Fond sombre
Forcer les hammer-on & pull-offs
Mode miroir
Couleurs des notes au hasard
Notes au hasard
Deux pédales de basse
Liveless:
I'm assuming "liveless" here is a proper noun, and so I'm keeping it as-is.
User Code simply translated to "Code" here for space reason. Other possible translations are "Code Utilisateur" (User Code, gendered male), "Code Ami(e)" (Friend Code, both genders), "Code Joueur" (Player Code, gendered male), "Code Unique" (Unique Code).... Pick your poison. In french "Code" is neutral, short, ungendered in that context, and has an implicit connotation of "secret" that english does not have, so I deem it sufficient/clear enough on its own in that context.
Gérer Liveless
Entrez le Code de la personne à rejoindre (majuscules sans importance)
Votre Code est: $USER_CODE$. Toute autre personne du même serveur ($SERVER_NAME$) peut utiliser ce Code pour vous rejoindre.
Connexion au serveur Liveless réussie ! Sélectionnez "Rejoindre via Code" pour rejoindre quelqu'un en particulier, ou "Voir mon Code" pour afficher votre propre Code de joueur. (Attention si vous filmez - avec ce Code, n'importe qui peut vous rejoindre !)
This sentence is written in traditional french where the reader is assumed to be male. If you can fit a few more characters, you can replace Code de joueur with any of the following for a modern & gender-indifferent version ✨
Code de joueur·euse (modern, gender-inclusive). Beware that the separator is · not .
Code de joueur(euse) (traditional, gender-inclusive)
Code de joueur ou de joueuse (traditional/administrative, gender-inclusive)
Code identifiant ("ID Code", gender-neutral but less clear in context)
RB3Enhanced $RB3E_BUILDTAG$ esta activo. ¡Gracias por jugar!
RB3Enhanced $RB3E_BUILDTAG$ (con $MOD_VERSION$) esta activo. ¡Gracias por jugar!
Modifiers:
Fondo Negro
Forzar Ligados
Modo Espejo
Notas Aleatorias
Doble Pedal
Liveless:
Configuración Liveless
Ingresa el código del usuario con cual te quieras unir. (No sensible a mayúsculas)
Tu código es $USER_CODE$. Cualquier persona que use este código se puede unir. Servidor: $SERVER_NAME$
¡Conectado al servidor de Liveless! Elige 'Unirse con código' para unirte con otro jugador, o 'Mostrar mi código' para ver tu propio código. (Ten cuidado si estas en directo - ¡cualquier persona puede unirse con este código!)
Unirse con código
Mostrar mi código
Cerrar
Translation made in collaboration with Lynxeption, Slothdemon1991, and Aloquendiar.
I have a few nitpicks about the French translations.
Note: In french you're supposed to have a space before ! and ?, unlike english, so that space you see before ! and ? is intentional 🙂
Even better would be to use an "espace fine", or thin space (U+2009), on the left side of the exclamation or interrogation point. It's technically more correct, as it leaves a little less space between the word and the mark.
See this resource for more information about the different spacing used in French, especially for digital editing.
I supposed this is meant to be a Welcome message. In that case, "Thanks for playing" is not translatable (it really only exists in the past tense, "Merci d'avoir joué"). This is why I replaced it with "have a good game" (Bon jeu). You can also have "thanks for the support" (Merci pour votre soutien!) if you think it's closer to what you meant.
If however this is meant to be a "goodbye" message, then "Merci d'avoir joué !" is the closest to "Thanks for playing!".
Yes, this is indeed the case. "Amusez-vous !" could also be an alternative (maybe have it be randomly chosen? though, it may complicate things).
* `Entrez le Code de la personne à rejoindre (majuscules sans importance)`
I feel like "joueur" instead of "personne" would be more clear in this context, but it's true that it's less inclusive (expect if you use "joueur·euse" or similar). Also, "(majuscules sans importance)" should be "(insensible à la casse)", it's more clear. See one of the meanings of casse.
* `Connexion au serveur Liveless réussie ! Selectionnez "Rejoindre via Code" pour rejoindre quelqu'un en particulier, ou "Voir mon Code" pour afficher votre propre Code de joueur. (Attention si vous filmez - avec ce Code, n'importe qui peut vous rejoindre !)`
"Selectionnez" should have an accent: "Sélectionnez"
Finally, in your translations I wouldn't capitalize the word "code" as we are just talking about a general code, and I have never seen such capitalisation in a user interface.
Thanks for the nitpicking 🙂 I've added the missing accent
I know a more technically accurate translation of "casing" would be "casse", but I translated it that way on purpose ("caps do not matter") because the word "casse" in is less well known and therefore less clear for any given player than just, yeah, caps do not matter. But if this had been a software or an administrative website instead of a video game, I would have used "insensible à la casse".
Regarding the capitalisation of the word "Code", any is good, i tend to either capitalize or highlight a word in an interface when it's used to designate something specific (here, the User code), but it will also be perfectly understandable if the uppercase is removed, so I don't have a strong opinion about this one.
For "casing", fair enough: the same thing was done in the Spanish translation. Though, one could argue that "casse" will never be known and understood if it is seldom used 🙂
Personally, I find that video games (or really any other media, after all) are a good medium for learning new words and expanding one's vocabulary, so I would argue in favour of "casse".
Activity
louvenarde commentedon Mar 13, 2025
What file should these be committed to? I'm happy to open a PR for French 🙂
Otherwise I can reply straight in this Issue if you prefer with a translation for each line.
InvoxiPlayGames commentedon Mar 13, 2025
Reply in this issue - currently don't have any of the code in place for handling translated RB3E strings unfortunately.
louvenarde commentedon Mar 13, 2025
French
Note: In french you're supposed to have a space before ! and ?, unlike english, so that space you see before ! and ? is intentional 🙂
For all purposes I've replaced "User" (Utilisateur) with "Player" (Joueur) as it is much shorter in french, and in the context of a game, conveys the same meaning.
RB3Enhanced $RB3E_BUILDTAG$ est actif. Bon jeu !RB3Enhanced $RB3E_BUILDTAG$ (avec $MOD_VERSION$) est actif. Bon jeu !Modifiers:
Fond sombreForcer les hammer-on & pull-offsMode miroirCouleurs des notes au hasardNotes au hasardDeux pédales de basseLiveless:
Gérer LivelessEntrez le Code de la personne à rejoindre (majuscules sans importance)Votre Code est: $USER_CODE$. Toute autre personne du même serveur ($SERVER_NAME$) peut utiliser ce Code pour vous rejoindre.Connexion au serveur Liveless réussie ! Sélectionnez "Rejoindre via Code" pour rejoindre quelqu'un en particulier, ou "Voir mon Code" pour afficher votre propre Code de joueur. (Attention si vous filmez - avec ce Code, n'importe qui peut vous rejoindre !)Code de joueurwith any of the following for a modern & gender-indifferent version ✨Code de joueur·euse(modern, gender-inclusive). Beware that the separator is·not.Code de joueur(euse)(traditional, gender-inclusive)Code de joueur ou de joueuse(traditional/administrative, gender-inclusive)Code identifiant("ID Code", gender-neutral but less clear in context)Rejoindre via CodeVoir mon CodeFermerInvoxiPlayGames commentedon Mar 13, 2025
Thank you so much! I'll add it once the translation code is in place.
carlmylo commentedon Mar 13, 2025
Spanish
Generic:
Modifiers:
Liveless:
Translation made in collaboration with Lynxeption, Slothdemon1991, and Aloquendiar.
ConfuSomu commentedon Mar 15, 2025
Hello,
I have a few nitpicks about the French translations.
Even better would be to use an "espace fine", or thin space (U+2009), on the left side of the exclamation or interrogation point. It's technically more correct, as it leaves a little less space between the word and the mark.
See this resource for more information about the different spacing used in French, especially for digital editing.
Yes, this is indeed the case. "Amusez-vous !" could also be an alternative (maybe have it be randomly chosen? though, it may complicate things).
I feel like "joueur" instead of "personne" would be more clear in this context, but it's true that it's less inclusive (expect if you use "joueur·euse" or similar). Also, "(majuscules sans importance)" should be "(insensible à la casse)", it's more clear. See one of the meanings of casse.
"Selectionnez" should have an accent: "Sélectionnez"
Finally, in your translations I wouldn't capitalize the word "code" as we are just talking about a general code, and I have never seen such capitalisation in a user interface.
That's it!
Thank you!
louvenarde commentedon Mar 15, 2025
Thanks for the nitpicking 🙂 I've added the missing accent
ConfuSomu commentedon Mar 16, 2025
For "casing", fair enough: the same thing was done in the Spanish translation. Though, one could argue that "casse" will never be known and understood if it is seldom used 🙂
Personally, I find that video games (or really any other media, after all) are a good medium for learning new words and expanding one's vocabulary, so I would argue in favour of "casse".
Best regards