mirror of
https://github.com/HIllya51/LunaTranslator.git
synced 2025-11-28 17:10:22 +08:00
46 lines
No EOL
3 KiB
Markdown
46 lines
No EOL
3 KiB
Markdown
# Functions of Various Translation Optimizations
|
|
|
|
1. ## Proper Noun Translation {#anchor-noundict}
|
|
|
|
This method directly replaces the original text with the translated text before translation. It supports using `Regex` and `Escape` for more complex replacements.
|
|
|
|
When loading metadata from VNDB, the game queries character name information to set as a preset dictionary. For English users, the extracted English names are populated as translations corresponding to the original text. Otherwise, the translation is filled with the same content as the original to avoid affecting translations when users make no modifications.
|
|
|
|
::: details Example
|
|
|
|
:::
|
|
|
|
1. ## Proper Noun Translation {#anchor-noundict}
|
|
|
|
If using the `sakura large model` and setting the prompt format to support the gpt dictionary prompt, it will be converted into the gpt dictionary format. Otherwise, it will refer to the VNR approach, replacing the original text with the placeholder `ZX?Z` (ps: I don't know what this means), and after the source translation, the placeholder is generally not destroyed. Then, after the translation, the placeholder will be replaced with the translation.
|
|
|
|
For game-specific entries, it is recommended not to add them in `Text Processing` -> `Translation Optimization`. In the past, the game's md5 value was used to distinguish entries for multiple games, but this implementation was not very good and has been deprecated. Now, it is recommended to add game-specific entries in the `Game Settings` -> `Translation Optimization` settings for this method.
|
|
|
|
The last column `Comment` is only used for the `Sakura Large Model`; other translations will ignore this column.
|
|
|
|
When loading metadata from VNDB, the game queries character name information to set as a preset dictionary. For English users, the extracted English text is populated as the translation corresponding to the original text. Otherwise, the translation is left empty to avoid affecting translations when users make no modifications.
|
|
|
|
::: details Setting Game-specific Entries
|
|
It is recommended to use:
|
|
|
|
Instead of:
|
|
|
|
:::
|
|
|
|
1. ## Translation Result Correction {#anchor-transerrorfix}
|
|
|
|
This method allows for certain corrections to the translation result after translation and can use the entire expression for complex corrections.
|
|
|
|
1. ## Custom Optimization {#anchor-myprocess}
|
|
|
|
Write a Python script to perform more complex processing
|
|
|
|
1. ## Skip sentences that contain only punctuation. {#anchor-skiponlypunctuations}
|
|
|
|
N/A
|
|
|
|
## Game-specific Translation Optimization
|
|
|
|
In `Game Settings` -> `Translation Optimization`, if `Follow Default` is deactivated, game-specific translation optimization settings will be used.
|
|
|
|
If `Inherit Default` is activated, the game-specific translation optimization dictionary will also use the default global dictionary. |