NEW Guide for SV i18n Converter Tools + SV i18n Translation Merger. (CP to i18n) This guide will walk you through the process of updating translations for mods that have transitioned to the i18n format, even if your existing translation is not in i18n.
Spoiler:
Show
1) Gather the Files:
Download the older version of the translation you want to update.
Download the older version of the mod that uses the non-i18n translation.
Download the newer version of the mod that has been converted to the i18n format.
2) Prepare Your Workspace:
Create a folder for this process.
Extract the contents of all downloaded archives (mods and translation) into this folder.
Place the following executables in the same folder:
transtar.exe
SV i18n Translation Merger.exe
SV i18n Converter Tools.exe
3) Extract Content with Transtar:
Launch Transtar.exe.
Select the folder containing the older version of the mod (the one with content.json).
Click "Extract". This will generate a CP.json file.
Repeat the same process for the older version of the translation.
3.5) Troubleshooting Transtar Errors:
Sometimes, due to JSON formatting errors, Transtar might not be able to process the files completely.
If you encounter errors:
Note the "Line" number where the error occurred.
Click "Open File".
Locate the specified line and identify the problem (e.g., incorrect spacing, extra comma).
You can use a website like https://jsonlint.com/ to validate the entire file for errors, but you'll need to remove all comments (//) from the file first.
Once you've fixed the errors, save the file.
Repeat step 3. The errors should be resolved (at least for that line and file).
4) Compare the Extracted CP.json Files:
Open the CP.json files you extracted from both the older mod and the older translation.
Compare the num values and the corresponding key values.
Ideal Scenario: If the num values and key values match perfectly, the translation is likely well-structured. Proceed to step 5.
Mismatch Scenario: If there are mismatches, it indicates potential errors in the translation. Proceed to step 4.5.
4.5) Use JSON Merger and Sorter:
Launch SV i18n Converter Tools.exe.
Click on the "Launch JSON Merger and Sorter" button.
Select both CP.json files (from the older mod and translation).
Click "Process Files".
This will generate new CP.json files with perfectly matching num and key values. (JSON Merger and Sorter will overwrite the original CP.json files.)
5) Prepare the Old Translation for i18n:
Move the updated CP.json file (from the older translation) to your workspace folder.
In SV i18n Converter Tools.exe, click "Combine Source Files". This will create an i18n file for your older translation.
Delete the unnecessary files and rename the generated default.json file to something descriptive (e.g., old_translation_default.json).
Repeat the same process for the CP.json file of the older mod, creating a default.json for the original English text.
Finally, copy the i18n file (likely default.json) from the new version of the mod into your workspace folder.
6) Transfer Translations with SV i18n Translation Merger:
Launch SV i18n Translation Merger.exe.
Select the following files:
NEW MOD: The i18n file (default.json) from the new version of the mod.
OLD MOD: The default.json file you created from the older version of the mod.
OLD TRANSLATION: The default.json file you created from the older version of the translation.
Check the box for "Compare by text only" (as the i18n keys in the old and new mods might not match).
Click "Translate!".
Once the process reaches 100%, save the output file as YourLanguage.json (e.g., ru.json for Russian).
7) Verify the Translation:
Open the default.json file (from the new mod) and your newly created YourLanguage.json file.
Compare the files to see how many strings have been successfully translated.
You have now successfully updated your old translation to work with the new i18n version of the mod!
2. Download the Updated Mod Version: Next, download the latest version of the mod that you want to translate.
3. Acquire the Outdated Mod Version: This step can be tricky, as not all mod authors keep older versions readily available. Here are three methods to find them: 3.1. Check for "Old Files": Some authors conveniently provide older versions in an "Old Files" section on the mod page.
3.2. Utilize Search Engines: Try searching for the mod's name followed by its version number enclosed in quotation marks (e.g., "Main RRRR Download V1.6.4").
3.3. Explore the Archive (if available): If the mod's archive is accessible, locate the desired older version. Right-click on it and select "Inspect" or "Inspect Element". This will open your browser's developer tools.
Find the data-id attribute associated with the old mod version (it will usually highlight the mod in yellow when you hover over it).
Then, open the download link for the new version and replace its file_id in the URL with the data-id you found.
4. Organize and Extract Files: Once you have downloaded all the necessary files, place them in a single folder and extract their contents.
5. Select the Correct i18n Files: The program requires three input files: NEW MOD: The i18n file from the new mod version (.json). OLD MOD: The i18n file from the old mod version (in the same language as the new version) (.json). OLD TRANSLATION: The translation file of the old mod version (in the language you want to transfer) (.json). Refer to the image provided for a visual guide on selecting the correct files.
6. Initiate the Translation Process: Click the "Translate" button and choose a location to save the updated translation file.
Provide a suitable name for the file (e.g., pt.json).
7. Verify the Results: Once the process is complete, open the updated translation file (e.g., pt.json) using a comparison tool like WinMerge.
You'll see that the file structure matches the new mod's translation file, and all relevant strings from the old translation have been seamlessly integrated.
I've revamped my SV i18n Converter Tools! Now you can convert old mods and their translations (that don't have i18n) into the i18n format, run JSON Merger and Sorter on them (it will fix any issues in the i18n), and then use SV i18n Translation Merger to transfer the translation to the new version of the mod!
Привет, спасибо за замечательную программу. Как я понял, она заменяет все, что находится после двоеточия. Возможно ли заменить на то, чтобы программа заменяла после второго знака " , либо после комбинации символов ": ? Есть моды, которые используют два знака двоеточия в ключе, и из-за этой программы перевод просто ломает все эти ключи, стирая все, что написано после первого двоеточия.
Спасибо за ответ, но это не то, что я имел ввиду. В файле вместо стандартных, например, "CP_key": "текст", есть такие: "CP_key:Maru": "текст" Вот здесь прога и удаляет всё в ключе, оставляя "CP_key: "текст"
Если возможно, дополните, когда будет свободное время, скрипт данным случаем. Мне не к спеху, для будущих обновлений. Буду благодарен. Так же учтите возможность тройного двоеточия. "CP_key:spring:Maru": "текст"
Yesterday, while testing the translation transfer from the old SVE 1.15 to 1.15.2, I fixed 3 bugs:
Deletion of \n (during the insertion of translated strings containing \n).
Replacement of the i18n key with the translated value if it matches the value character for character (example: "Farm": "Farm").
Replacement of the part of the i18n key after the dot with the translated value if it matches the value character for character (example: "Alex.Farm": "Farm").
After this, I was able to perfectly transfer all 10k lines. If you still encounter a bug while transferring your translation, please let me know. I might not have caught all the cases, especially considering that different modders use different key formats and might use Chinese characters or other special symbols.
While the new mod version and the old translation are easily accessible, the old mod version can sometimes be difficult to find (it's best to find the same version as the translation). Authors often hide old mod versions, but you can cleverly retrieve them using the FILE ARCHIVE. You can check the page's source code to find their IDs and then substitute those IDs when attempting to download the new mod version.
18 comments
Guide for SV i18n Converter Tools + SV i18n Translation Merger. (CP to i18n)
This guide will walk you through the process of updating translations for mods that have transitioned to the i18n format, even if your existing translation is not in i18n.
1) Gather the Files:
2) Prepare Your Workspace:
transtar.exeSV i18n Translation Merger.exeSV i18n Converter Tools.exe3) Extract Content with Transtar:
3.5) Troubleshooting Transtar Errors:
4) Compare the Extracted CP.json Files:
4.5) Use JSON Merger and Sorter:
5) Prepare the Old Translation for i18n:
6) Transfer Translations with SV i18n Translation Merger:
7) Verify the Translation:
- Open the default.json file (from the new mod) and your newly created YourLanguage.json file.
- Compare the files to see how many strings have been successfully translated.
You have now successfully updated your old translation to work with the new i18n version of the mod!Guide for SV i18n Translation Merger. (i18n)
SV i18n Translation Merger: A Step-by-Step Guide
This guide demonstrates how to effortlessly update your Stardew Valley mod translations using the SV i18n Translation Merger.
We'll be using the Romanceable Rasmodius Redux Revamped mod and its outdated PT-BR translation as a practical example.
1. Download the Outdated Translation:
Begin by downloading the outdated translation file that you wish to update.
2. Download the Updated Mod Version:
Next, download the latest version of the mod that you want to translate.
3. Acquire the Outdated Mod Version:
This step can be tricky, as not all mod authors keep older versions readily available. Here are three methods to find them:
3.1. Check for "Old Files":
Some authors conveniently provide older versions in an "Old Files" section on the mod page.
3.2. Utilize Search Engines:
Try searching for the mod's name followed by its version number enclosed in quotation marks (e.g., "Main RRRR Download V1.6.4").
3.3. Explore the Archive (if available):
If the mod's archive is accessible, locate the desired older version. Right-click on it and select "Inspect" or "Inspect Element". This will open your browser's developer tools.
Find the data-id attribute associated with the old mod version (it will usually highlight the mod in yellow when you hover over it).
Then, open the download link for the new version and replace its file_id in the URL with the data-id you found.
4. Organize and Extract Files:
Once you have downloaded all the necessary files, place them in a single folder and extract their contents.
5. Select the Correct i18n Files:
The program requires three input files:
NEW MOD: The i18n file from the new mod version (.json).
OLD MOD: The i18n file from the old mod version (in the same language as the new version) (.json).
OLD TRANSLATION: The translation file of the old mod version (in the language you want to transfer) (.json).
Refer to the image provided for a visual guide on selecting the correct files.
6. Initiate the Translation Process:
Click the "Translate" button and choose a location to save the updated translation file.
Provide a suitable name for the file (e.g., pt.json).
7. Verify the Results:
Once the process is complete, open the updated translation file (e.g., pt.json) using a comparison tool like WinMerge.
You'll see that the file structure matches the new mod's translation file, and all relevant strings from the old translation have been seamlessly integrated.
Вот здесь прога и удаляет всё в ключе, оставляя "CP_key: "текст"
"CP_key:spring:Maru": "текст"
.
- Deletion of \n (during the insertion of translated strings containing \n).
- Replacement of the i18n key with the translated value if it matches the value character for character (example: "Farm": "Farm").
- Replacement of the part of the i18n key after the dot with the translated value if it matches the value character for character (example: "Alex.Farm": "Farm").
After this, I was able to perfectly transfer all 10k lines.If you still encounter a bug while transferring your translation, please let me know. I might not have caught all the cases, especially considering that different modders use different key formats and might use Chinese characters or other special symbols.
昨晚另一个工具都已经解禁了.
这个工具有没有其它下载渠道?
- The new version of the mod (original language)
- The old version of the mod (original language)
- The old version of the mod (your language)
While the new mod version and the old translation are easily accessible, the old mod version can sometimes be difficult to find (it's best to find the same version as the translation). Authors often hide old mod versions, but you can cleverly retrieve them using the FILE ARCHIVE. You can check the page's source code to find their IDs and then substitute those IDs when attempting to download the new mod version.