Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Need Help changing language in ACC Client

Avatar

Avatar
Boost 3
Level 1
mxfanatic
Level 1

Likes

3 likes

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
mxfanatic
Level 1

Likes

3 likes

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
mxfanatic
Level 1

13-07-2019

When trying to install the ACC Client 'setup-client-7.0.8981' I accidentally selected French. Now, even when I quit and restart the installer, it only shows french. How do I change this? I love the french, but I can't read much of it. Thanks for the help!

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Boost 10
Level 3
CedricRey
Level 3

Likes

24 likes

Total Posts

65 posts

Correct Reply

12 solutions
Top badges earned
Boost 10
Applaud 5
Boost 5
Affirm 5
Give Back
View profile

Avatar
Boost 10
Level 3
CedricRey
Level 3

Likes

24 likes

Total Posts

65 posts

Correct Reply

12 solutions
Top badges earned
Boost 10
Applaud 5
Boost 5
Affirm 5
Give Back
View profile
CedricRey
Level 3

18-05-2021

Hi,

First, this is not a very clever solution, but it's the easier and faster. Here what you can do if you're stuck in another language than english :

Go to the "bin" folder of your console installation (you'll find the "nlclient.exe" file, not the parent one with "setup.exe"). Just change the name of the "lang" folder (for example, rename it as "lang--").

Restart the console, and voila.

This won't change the default language of the console, but it won't find the necessary translation files  (and the exec program is in english by default) so it will run in english.

 

This won't solve the problem if you want another language (de, jpn or fr). In this case, the real and clean solution (and for advanced user) is to change a Windows registry entry. Launch "regedit" program (Windows+R shortcut), and the key is easy to find :

HKEY_CURRENT_USER\Software\Neolane\NL_5

Double clic on the "Language" entry on the right and change it to "eng" for english (I suppose), "fra" for french, "jpn" for japanese or "deu" for german.

 

But as we all know, it can be difficult to access to the registry (security policies, user rights etc.), so I do not know if it works, but at least, if the 2 solutions above are not ok for you, you can try to backup the file from the "%USER-FOLDER%\AppData\Roaming\Neolane\NL_5" folder, run the "setup.exe" program, remove the console, then re-install the console. I don't know if it clears the registry (maybe reboot the system bettween uninstall et install ??) but you can give it a try. To complete, if the \AppData\Roaming\Neolane\NL_5 folder have been clear (connexions and cache), replace it with the backup you made before.

 

Hope this could help in the future.

 

Cedric

CedricRey
Hmmm, I don't understand why, the second solution I gave (and the smart one) use to work for my 2-3 first tests, and now it seems that my console returns to the server language when I connect to it. Whenever I change to another lang (for example Japanese), the login interface starts in japanese, but when I login to my french instance, it return in french. I'm pretty sure to had the console logged in japanese, english then in german (to check the registry entry value), but It doesn't work anymore for me, and I don't know if it comes from the server language (because it changes only when I connect) or the default console installation language... Sorry if it doesn't work for you.
CedricRey
Hi, after another test, I confirm that the installation lang is linked with the instance locale (<userInfo instanceLocale="xx-YY"/>). It's defined into the config-instanceName.xml(serverconf > shared > datastore@lang value), so if you "force" the lang into the registry and that corresponds to the instance lang, it should be ok. Another thing : the registry entry also seems to follow the operator @locale attribute. So it should not be necessary to change the registry (if no access), but by "forcing" the locale for the operator (with "English (US)" for example), connecting / disconnecting / closing the console, it could resolve the foreign language.