~~~~ ~~~~~~~~

~~I'm looking to fix this, however,~~ description states: > **Additional context** Industries are not affected, despite having a very similar text input window string. However - Indeed industries are not...

I see, tho I really wanted to do something about this, sadly I am no more looking to fix this, as I am still running into problems with compiling OpenLoco...

**cs-CZ is done** as cs-CZ doesn't translate given park names by intention, as outlined in OpenRCT2/Localisation#3260 (in English) and [Translator guidelines: cs_CZ - Vlastní jména](https://github.com/OpenRCT2/Localisation/wiki/Translator-guidelines:-cs_CZ#vlastn%C3%AD-jm%C3%A9na) (in Czech)

@andOlga > The `ru-RU` localisation uses English scenario names as-is, and there's no description to translate here -- though I'm not sure why, and whether that's intentional. Assuming it is,...

@tupaschoal checking for you **pt-BR done** by https://github.com/OpenRCT2/Localisation/commit/15e4eb3e6903084d5bc1095057321ed5f0fa75fb , merged into OpenRCT2/objects by OpenRCT2/objects#398 . It was merged in silence with cs-CZ update, as visible by [blaming](https://github.com/OpenRCT2/objects/blame/master/objects/official/scenario_meta/rct1tw.scenario_meta.taiwan_park/object.json#L18)

For this Issue ca-ES, de-DE, fr-FR, nl-NL, tr-TR are pre-checked, since they dropped the trailing full stop (period at the end) by ~~itselves~~ themselves ([search for STR_5862 in this repo](https://github.com/search?q=repo%3AOpenRCT2%2FLocalisation%20STR_5862&type=code))...

Thanks for noticing, should be correct now