Custom AI Translator has been launched, which can use any model that conforms to the OpenAI API specifications for translation. Please prepare your own API Key.
Hi there. I'm not sure if with this tool you also “support” .w3strings localization files from Patch 1.32, or is it only intended for the next-gen files (I couldn't find that information on the Description page), but would you mind taking a look at, let's say, the Polish text for ID 1083150 inside the content0's pl.w3strings file (here's a link to that file: https://mega.nz/file/rpQCmbiA#Q5CIZSrjiUzxqA5WYSESfGMw_7TO7qdyx6MWChAbsR0)? It is getting truncated when viewed inside the program, or getting exported to, let's say, a CSV file. The full text for that ID should be:
(...) Kawalkada jeźdźców przetoczyła się przez unurzany we krwi dziedziniec. Na nikogo nie patrzyli, o nic nie pytali - dokładnie wiedzieli, dokąd zmierzają i co jest ich celem. Mieli zabić starą królową i pojmać cintryjską księżniczkę. O tym, co miało się z nią stać potem, nikt głośno nie mówił.<br><br> Calanthe wraz z grupką najwierniejszych poddanych zabarykadowała się w zamku. Chroniły ich kamienne mury i brama obłożona zaklęciem - ale wszyscy zdawali sobie sprawę, że ani jedno, ani drugie długo nie wytrzyma zmasowanego natarcia nilfgaardziej armii i wspierających ją czarodziejów. Po czterech dniach żołnierze wdarli się do środka…
but only the first “paragraph” is getting shown:
(...) Kawalkada jeźdźców przetoczyła się przez unurzany we krwi dziedziniec. Na nikogo nie patrzyli, o nic nie pytali - dokładnie wiedzieli, dokąd zmierzają i co jest ich celem. Mieli zabić starą królową i pojmać cintryjską księżniczkę. O tym, co miało się z nią stać potem, nikt głośno nie mówił.<br><br>
(If exported/decoded with w3strings encoder v0.4.1 that second paragraphs doesn't get omitted):
(...) Kawalkada jeźdźców przetoczyła się przez unurzany we krwi dziedziniec. Na nikogo nie patrzyli, o nic nie pytali - dokładnie wiedzieli, dokąd zmierzają i co jest ich celem. Mieli zabić starą królową i pojmać cintryjską księżniczkę. O tym, co miało się z nią stać potem, nikt głośno nie mówił.<br><br> [[CSV_EXPORT_NL]]Calanthe wraz z grupką najwierniejszych poddanych zabarykadowała się w zamku. Chroniły ich kamienne mury i brama obłożona zaklęciem - ale wszyscy zdawali sobie sprawę, że ani jedno, ani drugie długo nie wytrzyma zmasowanego natarcia nilfgaardziej armii i wspierających ją czarodziejów. Po czterech dniach żołnierze wdarli się do środka…
Some other examples of IDs with cropped Polish text: 1085579, 1085582, 1135327, 1135344, 1135348... (not all of those are from the content0's pl.w3strings file)
This doesn't seem to be reproducible with the Next-gen Polish files – CDPR seem to have corrected those weird CRLF's/line breaks.
Let me explain why this is the case. This software uses the w3strings encoder as the backend for encoding and decoding w3strings. The software reads the CSV file output by the encoder. and read by line, the wrong line break will cause the data after the wrong line break to be treated as invalid data and discarded. I wouldn't try to support a file like this with the wrong line break if it doesn't avoid affecting the reading of other normal files.
After I finished the translation, I didn’t know where to save it, and there was no path option. Is it because the something was missing that it failed to save successfully?
Did you see the prompt for a successful save? If not, check the latest logs in appdata/roaming/witcher3stringeditor/logs.If you don't understand, you can send me the logs.
Does that mean I should edit it in Excel? Instead, I prefer to edit CSV in Notepad++. That way I can always undo my edits with Ctrl+Z.
In any case, this tool is very effective for beginners who are not familiar with editing w3strngs. For those who would like to translate my mod, I will introduce it on my mod page.
1.Please update to 1.3.61 immediately, there is a serious bug in the previous version, which may cause multiple different file data to be incorrectly merged into one file. 2.You can get the update on Google Drive first. 3.I'm stupid again.
Hello, what is the api of the batch translate ? is it use DEEPL or Google Translate or something else ? I'd like to congratulate you because your tool has encouraged me to start translating again. Your string editor is much more practical and intuitive than the old one. In fact, I'm going to provide a French localization thanks to the available string file! I send you the French localization by message nexus
I find it less accurate than Deepl for the French language but I think integrating an api (translation software) must be difficult so thank you for integrating one! It makes translation easier for me
Is there a way to add filtering to the lines (UI, subtitles or dialog choices lines)? I guess the hex key already carries the necessary information, but I cannot find any official info what categories those key values represent.
The only obvious thing that I found was that the 0 value means that the line corresponds to the dialog lines, quests names and descriptions, names of creatures in bestiary and descriptions, as well as character descriptions, and, additionally, gameplay tips. Any other hex values are generally UI/HUD, menu entries and item names, in-world character names, tips during loading and so on. I didn't go further to investigate, since it seems non-zero values do not correspond to some major general categories.
58 comments
Some other examples of IDs with cropped Polish text: 1085579, 1085582, 1135327, 1135344, 1135348... (not all of those are from the content0's pl.w3strings file)
This doesn't seem to be reproducible with the Next-gen Polish files – CDPR seem to have corrected those weird CRLF's/line breaks.
Instead, I prefer to edit CSV in Notepad++.
That way I can always undo my edits with Ctrl+Z.
In any case, this tool is very effective for beginners who are not familiar with editing w3strngs.
For those who would like to translate my mod, I will introduce it on my mod page.
Thanks for letting me know.
2.You can get the update on Google Drive first.
3.I'm stupid again.
I'd like to congratulate you because your tool has encouraged me to start translating again. Your string editor is much more practical and intuitive than the old one. In fact, I'm going to provide a French localization thanks to the available string file! I send you the French localization by message nexus