Good idea, thank you for raising this. I've changed how Objo Studio stores localisation string tables, and the fix will be in the next release: https://feedback.objo.dev/feature/1514
Studio now writes the values in Resources/Strings/<locale>.json as literal UTF-8 text, so a Russian table reads "Добро пожаловать" instead of "\u0414\u043e\u0431...". This applies everywhere those files are written: .objosln solution folders, .objo archives, and the resources deployed when you run or publish your app.
The files are also safe to hand to a translator and add back afterwards. When loading, Studio accepts literal Unicode text, \uXXXX escapes (so existing projects keep working unchanged), files saved with a UTF-8 BOM, and Windows-style CRLF line endings. One small note: characters outside the Basic Multilingual Plane, such as emoji, are stored as \uD83C\uDF89-style surrogate-pair escapes — they still load back unchanged.
The first time you save an existing project after the update, any escaped text is rewritten as literal characters, so expect a one-time change to those files.
