This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* someone originally decided to translate [プテラノドン](https://ja.wikipedia.org/wiki/%E3%83%97%E3%83%86%E3%83%A9%E3%83%8E%E3%83%89%E3%83%B3) as [Pterodactyl](https://en.wikipedia.org/wiki/Pterodactylus) for some reason unknown to me. I thought maybe the skeleton looks more like a pterodactyl instead, but it doesn't, it has that huge crest
@@ -667,9 +666,9 @@ If you want to do a actual, proper retranslation of this game yourself and are n
* removing `system.bin` from `pack/global/first.dat` in the pack editing script makes the text in `system.bin` appear correctly
* Changes are successfully made in `pc`, `foodarea` and `helplib` after modifying how `textinsert.py` chose to skip rows that were too short. Since `pc`, `foodarea` and `helplib` have less columns than all the other `text` files, they were previously skipped entirely.
3. Chapter titles: These are copied from the files in the 4.15 ISO, in this case from `PSP_GAME/USRDIR/visual/event`. While other translated graphics are included with flame's tools, for some reason the chapter start/end graphics aren't.
5. The Mishy issue was not entirely the fault of the tools. For some reason, Mishy's internal name ("Michy") was exposed in `chr_names.tsv` as well as his name that is displayed above his textboxes (originally "Michey"). For comparison, Mensa was called "Mrs. Mensa" in the original translation, and has an internal name of "Mensa", but only appeared once in `chr_names.tsv` (as "Mrs. Mensa"). I've also been able to break shopkeepers by changing the wrong names in `chr_names.tsv`, so just make sure you only change the right one? I recommend not changing any character names that appear to already use Latin characters when dumped from Japanese.
5. The Mishy issue was not entirely the fault of the tools. For some reason, Mishy's internal name ("Michy") was exposed in `chr_names.tsv` as well as his name that is displayed above his textboxes (originally "Michey"). For comparison, Mensa was called "Mrs. Mensa" in the original translation, and has an internal name of "Mensa", but only appeared once in `chr_names.tsv` (as "Mrs. Mensa"). I've also been able to break shopkeepers by changing the wrong names in `chr_names.tsv`, so just make sure you only change the right one? I recommend not changing any names in `chr_names.tsv` that appear to already use Latin characters when dumped from Japanese.
6. Extra Japanese text (underneath my English): I would usually be able to fix these by reformatting my English text to use an extra line in the text box. However, I encountered this again for two lines when reading the message at the end of Volans' sidequest, but wasn't able to fix it this way.
* this appears to be fixable by increasing the max length for `0x41` op codes, as defined in the `bin` method, from 10 to 11. Now all the Japanese text is replaced as long as there is enough rows of English text. Due to a related logical error that should also now be fixed, it was [truncated to 3 rows](https://i.imgur.com/FEP7Gk1.jpg) when I tried to add an additional row instead of 10
* this appears to be fixable by increasing the max length for `0x41` op codes, as defined in the `bin` method in `scriptinsert.py`, from 10 to 11. Now all the Japanese text is replaced as long as there is enough rows of English text. Due to a related logical error that should also now be fixed, it was [truncated to 3 rows](https://i.imgur.com/FEP7Gk1.jpg) when I tried to add an additional row instead of 10
* so in conclusion, while other text boxes can be freely resized, `0x41` opcodes require as least the same number of rows of English text as Japanese text
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[More comparison screenshots](https://imgur.com/a/yJB1fTj). These are mostly one-liners that were particularly non-sensical. There shouldn't be any major spoilers if you're interested in avoiding them.
[More comparison screenshots](https://imgur.com/a/yJB1fTj). These are mostly one-liners that were particularly non-sensical. There shouldn't be any major spoilers if you're interested in avoiding them, but they might reveal some smaller details.
---
##Introduction
I wasn't happy with the English in the [existing Nayuta no Kiseki fantranslation](https://heroesoflegend.org/forums/viewtopic.php?f=22&t=73), so I used their [publicly available tools](https://heroesoflegend.org/forums/viewtopic.php?f=22&t=340) to make my own edit.
Initially I only wanted to only fix various inconsistencies, nonsensical lines, and the awkward direct-from-Japanese punctuation and formatting. Since I can read zero Japanese, I started out by using Google Translate and Linguee for help on trying to gauge what the more confusing parts were even trying to say, and editing the rest of the English myself.
Initially I only wanted to only fix various inconsistencies, nonsensical lines, and the awkward direct-from-Japanese punctuation and sentence structure. Since I can read zero Japanese, I started out by using Google Translate and Linguee for help on trying to gauge what the more confusing parts were even trying to say, and editing the rest of the English myself.
But in addition to some parts simply not making any sense, I later noticed others had made some modicum of sense, but the online translators (especially after discovering DeepL, which lets you manually fiddle with alternative translations) gave results that make much *more* sense than the original. It seems that knowledge of the context is something that the original English writers were missing when writing much of the dialogue. Some of the more [drastic changes in meaning](https://i.imgur.com/YRqCdl3.png) have been things taken [almost literally from](https://i.imgur.com/tp5cbZ5.png) these online translators. I ended up also changing the rest of the text to whatever *I*, as a native US English speaker, subjectively think might sound better, taking into account the original translation, any new machine translation(s), and what I knew about the context.
But in addition to some parts simply not making any sense, I later noticed others had made some modicum of sense, but the online translators (especially after discovering DeepL, which lets you manually fiddle with alternative translations) made much *more* sense than the original. It seems that knowledge of the context is something that the original English writers were missing for much of the dialogue. Some of the more [drastic changes in meaning](https://i.imgur.com/YRqCdl3.png) have been things taken [almost literally from](https://i.imgur.com/M05LHD8.png) these online translators. I ended up also changing the rest of the text to whatever *I*, as a native US English speaker, subjectively think might sound better, taking into account the original translation, any new machine translation(s), and what I knew about the context.
But I'm not a big creative writer, so I think it still might be drier and closer to literal Japanese compared to most previous official localizations: lines with simple phrases or sounds in Japanese like *eh* or *naruhodo* are replaced with simple phrases or sounds in English, rather something potentially more expressive, meaningful, or entertaining. However, now I believe the English to be actually comprehensible. For instance, *yappari* is no longer almost always 'as expected,' even when one of the [many alternatives](https://en.wiktionary.org/wiki/やはり) or similar English phrases make more sense. But again, I don't even know Japanese, so maybe I just made everything worse, especially for anything more nuanced.
But I'm not a big creative writer, so I think it still might be drier and close*r* to literal Japanese compared to most previous official localizations: lines with simple phrases or sounds in Japanese like *eh* or *naruhodo* are replaced with simple phrases or sounds in English, rather something potentially more expressive, meaningful, or entertaining. However, now I believe the English to be actually comprehensible. For instance, *yappari* is no longer almost always 'as expected,' even when one of the [many alternatives](https://en.wiktionary.org/wiki/やはり) or similar English phrases make more sense. But again, I don't even know Japanese, so maybe I just made everything worse, especially for anything more nuanced.
I would appreciate reporting of any issues: technical bugs, glaring mistranslations, lore inconsistencies, or even just general English weirdness and typos. I did a playthrough or two with my changes and fixed a number of mistakes, but it is possible that I missed some. There are a few remaining [issues](#known-issues).
I would appreciate reporting of any issues: technical bugs, mistranslations, lore inconsistencies, or even just general English weirdness and typos. I've fixed a number of mistakes, but it is possible that I missed some. There are a few remaining [issues](#known-issues).
Go to the [release page](https://github.com/dackst/nayuta/releases) for a changelog. If you're interested in more detail on the changes made from the original project, you can look at the [script notes](./notes.md) file. If you're *really* interested, you can easily view almost all the text changes from the original at once [here](https://github.com/dackst/nayuta/compare/a6cecc6651f386ab3fabcab64cf440e021fa99bd...original).
@@ -35,9 +35,12 @@ Go to the [release page](https://github.com/dackst/nayuta/releases) for a change
1. Download xdelta patch from latest<sup>[1](#note1)</sup> [release](https://github.com/dackst/nayuta/releases).
2. Apply the xdelta patch to an unmodified Nayuta no Kiseki ISO<sup>[2](#note2)</sup>.
2. Apply the xdelta patch to an unmodified<sup>[2](#note2)</sup> Nayuta no Kiseki ISO.
The easiest and most widely applicable method of doing this would probably be to use a web-based patcher, like the one located [here](https://hack64.net/tools/patcher.php). On Windows, you can also use [xdeltaUI](https://www.romhacking.net/utilities/598/). I've had success with [this](https://www.romhacking.net/utilities/959/) on Android.
@@ -64,8 +74,8 @@ These are all issues that exist in the original fantranslation that I don't know
* long achievement names are cut off in the notification box when unlocking them, e.g. "armor of anhillat"
* the above two *could* be solved by shortening them, but I'm not willing to butcher them further
* characters that use idiosyncratic manners of speaking in Japanese probably still don't here
* E.g. Geo is supposed to [sound like an old man](https://legendofheroes.fandom.com/wiki/Lychnis_Gio) (characters even comment on it several times in-game), Eris is supposed to sound [domineering](https://legendofheroes.fandom.com/wiki/Song_Priestess_Elislette) or something. Algol and Nemeas are definitely supposed to sound unique too
* Noi has her own verbal tic with the way she ends sentences in Japanese that is lost
* E.g. Geo is supposed to [sound like an old man](https://kiseki.fandom.com/wiki/Gio) (characters even comment on it several times in-game), Eris is supposed to sound [domineering](https://kiseki.fandom.com/wiki/Erislet) or something. Algol and Nemeas are definitely supposed to sound unique too
* Noi has her own verbal tic that is lost
* things like slang or shifts in politeness or tone are probably still not accurately conveyed
* text speed isn't as synced to voices as it is in Japanese (text speed should still be modified to be faster than the voices, if anything)
@@ -76,15 +86,15 @@ These are all issues that exist in the original fantranslation that I don't know
This repository contains modifications of [flame's 2017 tools](https://heroesoflegend.org/forums/viewtopic.php?f=22&t=340) for modifying the text and images in Nayuta no Kiseki, as well as modifications of the English text and images dumped from version 4.15 of original project from 2016.
The original tools require a Windows installation of Python 3 to ["work"](./notes.md#why-not-just-use-flames-tools-directly). With the changes made in this repo, all of the non-working parts of these tools should be fixed. Also, the Python scripts for the dumping and inserting of binary files no longer require a Windows-based version of Python, but the beginning extraction/setup scripts and the final rebuilding scripts still do.
The original tools require a Windows installation of Python 3 to ["work"](./notes.md#why-not-just-use-flames-tools-directly). With the changes made in this repo, all of the non-working parts of these tools should be fixed. Also, the Python scripts for the dumping and inserting of binary files no longer require a Windows-based version of Python, but the beginning ISO extraction/workspace setup scripts and the final ISO rebuilding scripts still do.
You should still have access to an unmodified Nayuta no Kiseki ISO<sup>[2](#note2)</sup>.
You should still have access to an unmodified<sup>[2](#note2)</sup> Nayuta no Kiseki ISO.
1. Download and extract [the original tools](https://heroesoflegend.org/forums/viewtopic.php?f=22&t=340) and paste the [contents of this repository](https://github.com/dackst/nayuta/archive/master.zip) into the extracted folder. Overwrite files if necessary.
1. Download and extract [the original tools](https://heroesoflegend.org/forums/viewtopic.php?f=22&t=340), and paste the [contents of this repository](https://github.com/dackst/nayuta/archive/master.zip) into the extracted folder. Overwrite files if necessary.
2. Drag your unmodified ISO over `_extract_new.bat` to set up a new environment (Run `_extract_new.bat path/to/original.iso`)
3. Modify files to your liking. See flame's `readme.txt` for more on this.
4. Run `build_all.bat` (or `build_all.sh`) to build the a new ISO out of the `ISO` folder with the changes, named `output.iso`.
* If you changed files that weren't modified before, you will have to have to add them to `copy_all.py` or copy them to the correct location yourself. You also *might* have to run the pack editing function in `copy_all.py` on some relevant file for your changes to appear.
* If you changed files that weren't modified before, you will have to have to add them to `copy_all.py` or copy them to the correct location yourself. You also *might* have to run the pack editing function in `copy_all.py` on some relevant file for your changes to appear.
