Jump to content
Rotwood Early Access is Available Now!

Unintended char-corruption in string_template.pot (public testing U45-543530-V)

jls17

By jls17

    • Branch: Preview Branch Version: Windows Fixed

Hello Klei,

In some sections of the file "string_templates.pot", existing UTF-8 characters did get replaced with a "replacement-character" and re-encoded afterwards. This is just a minor issue .. but hopefully no-one will copy those changes over to their localized texts.

If found the corruption in the following IDs:

  • STRINGS.CODEX.C01_EVIL.BODY.CONTAINER1
  • STRINGS.CODEX.C01_EVIL.BODY.CONTAINER2
  • STRINGS.CODEX.CRITTERDELIVERY.BODY.CONTAINER1
  • STRINGS.CODEX.JOURNALISTREQUEST.BODY.CONTAINER2
  • STRINGS.CODEX.JOURNALISTREQUEST.BODY.CONTAINER4
  • STRINGS.CODEX.MISSINGNOTES.BODY.CONTAINER2
  • STRINGS.CODEX.MYSTERYAWARD.BODY.CONTAINER2

The attached screenshot shows a sample-diff of some changes. At the top is the previous version of the file (HotShots-Update) .. at the bottom is the state for the current public-testing-branch. The second screenshot shows the result in-game.

Different UTF-8 characters have been replaced. But I don't think it was intended. The characters in the new version have the hex-byte sequence "EF BF BD" which is the UTF-8 encoded version of the replacement-character. I hope you can revert those changes.

Thank you

BR
jls

Example_IncorrectEncodedChars.png

Example_IncorrectEncodedChars_InGame.png

Steps to Reproduce
  • open game-installation folder
  • cd to OxygenNotIncluded_Data\StreamingAssets\strings
  • open "strings_template.pot" in some text-editor
  • search for ID string, like "STRINGS.CODEX.CRITTERDELIVERY.BODY.CONTAINER1"
  • inspect the text in the msgid-line .. just after the text "lemme just" there is a invalid character
  • like explained above, multiple sections are affected
  • Like 1
  • Thanks 1
Go to bugs

User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
jls17

@EricKlei: Thanks. In one entry, there are still 4 of them left: STRINGS.CODEX.MYSTERYAWARD.BODY.CONTAINER2

Example_IncorrectEncodedCharsLeft.png

Share this comment

Link to comment
Share on other sites
EricKlei

Thanks, those will be corrected in a future update, not necessarily the next one. We've updated our process to avoid this happening in the future too.

  • Like 1
  • Thanks 1
  • Ninja 1
  • Big Ups 1

Share this comment

Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...