-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TranslationZed 0.10 BUGs #171
Comments
Still can't delete the dropped string by this tool? |
And the "TAB" before strings will be replaced with 4 spaces. |
The SurvivalGuide_EN.txt text format is incompatible. It will be deleted all lines without a key. |
The sorting function doesn't work after the searchbar is used (The empty selection is changed to "value" or "key") |
I started to make a latvian translation. Created a folder "LV" where needed. TranslationZed created the language file named language.txtLV.txt Inside the file I had to change the syntax manually. It was: languageLV= { key = "Value"; So the game recognised the file only after I named it correctly and got rid of the curly brackets and quotes. |
And Translate Zed doesn't seem to understand that I have changed something. Everytime I open the program all files are shown green. |
Following my discussion with @Mishasama in #416 and @Fantazmagore at Discord, it turned out that TranslationZed actually is open sourced since May last year, with the code available at @timbaker's (EasyPickings) GitHub repo along with other tools at https://github.com/timbaker/translatoid, thanks! It seems that it have been updated to 0.20 since then. I have figure out how to compile it yet, but precompiled binaries are available under https://github.com/timbaker/translatoid/releases. Currently it seems TranslationZed uses the 4-space indents (and converts all whitespaces including tabs) and removes all comments (lines beginning with It also indeed seems not to understand and don't parse/ignore and remove everything after
I'm not sure if you can remove strings and I'm not sure how the program handles removed strings, but it still feature a tool for old format of Items and Recipes (I personally didn't use them). It also seems that while EN UK appears there when loaded (regular EN does not), it doesn't save it properly, first similar issue @Fantazmagore experienced – language file is malformed, it also lacks support for all of the newly added .txt files as well ( The tool is not ideal and in fact very crude, especially compared to online solution we have (Weblate, Crowdin, Transifex…), but it's what there currently and serves its purpose. Probably I won't have time to dig deeper into it today, but I will when I'll have some time to look into the issues and maybe fork it with appropriate PRs sent. :) |
I think you need to right click each string and choose "Mark As Resolved" option for it to save it when exiting. |
Yup, I'm doing that. I change the line, click "Mark As Resolved", the entry becomes white. After I'm done for the day I click File->Save Translations and it creates the .txt file with the Resolved entries. And I close TranslationZED. When I open TranslationZED and load the "Translate" folder next time, everything in LV (in my case), is green again. I figured that I could just continue translating from where I left off. Found the line alphabetically and continued, Marked the Resolved ones and saved afterwards. That was a big mistake. The program overwrote my previous progress and just created a new .txt from scratch. Ragequited because of this last weekend. :D For now it looks like I'll better continue to do it manually, using Eclipse or Notepad. Thanks, Faalagorn :) |
That sounds aweful indeed… I spend too much time doing thing too and losing them can be heartbreaking, glad you're not giving up! I'll let you know if anything changes, but It's probably best to do it manually for you, as I think TranslationZed doesn't cope with new languages well at this point… |
|
Please check the below problems.
The text was updated successfully, but these errors were encountered: