For those of you who have chosen to do the website translation:

If you update the website translation, please post here and I can make your translation live.

Thank you for your help!

7 August 2025:
I've updated the website translations for the new unlock code system. You will see the new translation lines mainly at the bottom of the page. Further up the page you may notice there are texts that are no longer used (e.g. with GAMEpassword) but I don't yet know how to remove them.

Hi.

I updated the Brazilian Portuguese website text.

Thanks! I've put it in place and it seems to be working.

While I might update a few lines after it's more clear what "Application's secret" is, Lithuanian website text has been updated and the new lines seem to be showing up fine.

Ukrainian updated

Czech updated

Thank you for these updates. I've put Czech, Ukrainian and Lithuanian live.

Quote from Sobis :

While I might update a few lines after it's more clear what "Application's secret" is, Lithuanian website text has been updated and the new lines seem to be showing up fine.

I don't know exactly but I think it is a secret key held by an external application that uses an API. I guess the program and LFS both know the secret key, to initiate an encrypted communication.

Finnish updated, which includes In-Game Text, In-Game Help and LFS.net-text. One thing that got me wondering about is the "Client ID" and "Client Secret" in the API management.

As I'm not aware of how LFS API Management works, does anyone know, if the "CLIENT ID" and "CLIENT SECRET" need to be labeled literally as that in the code of the external application that uses an API? Or can they be labeled something different in the application's code, if it's even necessary at all?

If LFS API requires external application that uses API to have fields literally labeled "CLIENT ID" and "CLIENT SECRET" in its code, I will keep them as those in the translation and don't start to translate them.