Haroohie Site/content/blog/: 13.2024-08-03-chokuretsu-chinese-chartable — Chinese (Simplified) @ Weblate: Here, we can roughly see that `cmp r2, #0`, `cmp …

Translation

English

Here, we can roughly see that `cmp r2, #0`, `cmp r2, #0x60`, `cmp r2, #0xa` and `cmp r2, #0x23` are comparing `r2` with certain numbers. `U+000A` is a line break, and there is a statement `mov r0, #0x0e` in the corresponding branch. `0x0e` is 14 in decimal, and the line height of text in games is exactly 14 as I mentioned earlier. Then I modified it to `0x10` (16 in decimal), and went back to the game and... perfect! We lucked out here and solved this one almost immediately.

Chinese (Simplified)

Needs editing

Insufficient privileges for saving translations.

Skip

	English	Chinese (Simplified)	Actions
	The first `0x14` bytes are obviously the file header, where `0x04-0x07` is the size of the file[^1] (these bytes will need to be modified after expanding the character table). From `0x14` to the end is all the characters contained in the font image, in order. At first, I thought these two-byte characters might be UTF-16-LE encoded, but parsing with that encoding gave a garbled result. So I tried Shift-JIS encoding and found that it was consistent with the extracted image. I opened it with VS Code directly and change the encoding to Shift-JIS, and I got characters included in the file:	前 `0x14` 个字节显然是文件头，其中 `0x04-0x07` 是文件的大小[^1]（后续扩充码表需要修改此处）。从 `0x14` 到最后是字体图片包含的所有字符，按顺序排列。这种双字节的字符首先考虑 UTF-16-LE 编码，但是发现是乱码，于是尝试了一下 Shift-JIS 编码，发现和提取出来的图片是一致的。直接拿 VS Code 打开，改一下编码，就能得到包含的字符：
	``` plaintext ＠、。．・：？！＿々ー―～…‘’“”（）《》「」『』【】＋－×＝°％＆☆■♪０１２３４５６７８９ＡＢＣＤＥＦＧＨＩＪＫＬＭＮＯＰＱＲＳＴＵＶＷＸＹＺａｂｃｄｅｆｇｈｉｊｋｌｍｎｏｐｑｒｓｔｕｖｗｘｙｚぁあぃい... ```	``` plaintext ＠、。．・：？！＿々ー―～…‘’“”（）《》「」『』【】＋－×＝°％＆☆■♪０１２３４５６７８９ＡＢＣＤＥＦＧＨＩＪＫＬＭＮＯＰＱＲＳＴＵＶＷＸＹＺａｂｃｄｅｆｇｈｉｊｋｌｍｎｏｐｑｒｓｔｕｖｗｘｙｚぁあぃい... ```
	Since the modified text is in Simplified Chinese, I need to find a way to map Simplified Chinese characters to Shift-JIS codes. I wanted to directly use the [GB18030 encoding](https://en.wikipedia.org/wiki/GB_18030) at first, but I found that GB18030 contained far more characters than Shift-JIS, so I gave up on that. The solution I settled on was to count the number of Simplified Chinese characters in the translated text, sort them according to frequency of use, and then check whether they are in the original character table. If they are present, the original Shift-JIS code is directly used; if not, we replace a Japanese character that does not appear in the translated text. This ensures that as many characters as possible can be displayed correctly. Finally, the replacement table was saved as a `.json` file for use when importing text.	因为导入的文本是简体中文，所以需要想办法把简体中文汉字对应到 Shift-JIS 编码中。我本来想直接拿 GB18030 编码直接扔进去，但是发现 GB18030 包含的中文汉字远多于 Shift-JIS 包含的日文汉字，因此作罢。最后的解决方案是，统计翻译后的文本中出现的简体中文汉字次数，按照使用次数从多到少排序，然后依次检查是否在原有的码表中。如果在，就直接用原有的 Shift-JIS 编码；如果不在，就用未在翻译后的文本中出现的日文汉字替换掉。这样就能保证尽可能多的字符能够正确显示。最后将替换的对应表保存成 `.json` 文件，供导入文本时使用。
	The essential idea of how we process the character replacement is similar to that of the English project, but a Chinese localization needs to use far more characters than an English one. I extracted all the text and machine translated it to get an idea of which characters would be needed. The required Chinese characters number about 3,000, while the original character table only contains about 2,200 characters. The solution is either to simplify the use of words, or to expand the capacity of the character table. (By the way, the whole text of the game is about 800,000 words in Japanese, including many branches. So, if someone just wants to clear the game, it is very simple because there are only 5 chapters. But if one wants to play all the branches, it will take a long time. Of course, it is also hell to translate, and it even took me three days to finish just the machine translation.)	码表的处理思路与英文化项目类似，不过中文化需要用到的汉字远远多于英文化。我提取出了全部文本并且用机翻测试了一下，需要用到的汉字大概有 3000 字，而原有的码表只包含了约 2200 字。解决方法要么是精简用字，要么对码表扩容。（顺带一提，这个游戏全部文本大概 80 万字，其中包含了很多分支，所以如果只是想通关的话很简单，五章就结束了，但是要看完全部分支的话就需要很长时间了。当然，对于翻译来说也是个地狱，就连机翻我都用了 3 天才处理完。）
	### Font Image With a character table and replacement table, generating images becomes much simpler. The font size is 14px, which is exactly suitable for Chinese pixel fonts (you can refer to the article ["小点阵字体速览"](https://zhuanlan.zhihu.com/p/142419693) (Small Pixel Font Overview) written by 星夜之幻 (Xingyezhihuan)). I used SimSun, which is bundled with Microsoft Windows, to generate 13x14px characters. As for creating an automatically building workflow, the file `C:/Windows/Fonts/simsun.ttc` can be used.	### 字体图片有了码表和对应表，生成图片就简单了很多。字体大小是 14px，这个大小正好适合中文像素字体（可以参考星夜之幻前辈写的文章[“小点阵字体速览”](https://zhuanlan.zhihu.com/p/142419693)）。我用的是 Windows 自带的宋体，实际生成是 13x14px 的字符。自动构建的时候也可以读取 `C:/Windows/Fonts/simsun.ttc`。
	However, there is a small issue here. As the line height of the text in the game is exactly 14px, using a 14px font will cause the text on the top and bottom lines to stick together. This problem needs to be solved by modifying the executable file of the game.	不过这里有一个小小的问题，由于游戏中文字的行高正好就是 14px，如果用 14px 的字体就会出现上下两行的文字有粘连。这个问题就需要通过修改游戏的可执行文件来解决了。
	Additionally, due to the insufficient number of characters in the original character table that I mentioned earlier, the generated font image also needs to be larger than the original image. The original image size was 16x35328. If the image is imported directly using ChokuretsuTranslationCLI, only the top part of the image will be imported. The solution, without modifying the code, is to manually generate an empty binary file, import that empty binary file first, and then import the image. Then, ChokuretsuTranslationCLI will properly process the image with the new size.[^2]	另外，同样是基于前文所说的码表包含字符不够多的原因，生成的字体图片也需要比原来的图片更大。原来的图片尺寸是 16x35328 的，如果直接用 ChokuretsuTranslationCLI 导入，将会只导入图片的前面一部分。在不修改代码的前提下，解决办法是先手动生成一个空的二进制文件导入进去，然后再导入图片，此时 ChokuretsuTranslationCLI 就会以新的尺寸处理图片。[^2]
	## Images Modifying images is very easy, just simply exporting, editing, and importing them. However, there are some differences in the sorting of exported tiles compared to the actual displayed image, which require manual processing. The steps are relatively simple, so I won't go into further detail.	## 图片图片的修改没什么好说的，就是简单地导出、修改、导入。只不过有些图片导出后的图块排序和实际显示的图块排序有些差异，需要手动处理一下，也比较简单，不再赘述了。
	## Executable File Before delving deeper, I had limited knowledge about the executable files of NDS games. However, as I looked more into this game and [the Chinese localization revision project for the Pokémon Gen IV](https://xzonn.top/PokemonChineseTranslationRevise/), at least it was able to solve the problems I encountered in a straightforward manner.	## 可执行文件在我深入研究之前，我对 NDS 游戏的可执行文件的了解不多。不过随着我深入研究了这个游戏以及[《宝可梦》第四世代的汉化修正项目](https://xzonn.top/PokemonChineseTranslationRevise/)，至少也算是歪打正着地解决了我遇到的问题。
	Firstly, I'll briefly explain the executable files of the NDS game. They are divided into two parts: arm9 and arm7, which are further divided into the main program (`arm9.bin/arm7.bin`) and overlay programs (`overlay9_xxxx.bin/overlay7_xxxx.bin`). Taking arm9 as an example, the general part of the program is saved in `arm9.bin`, which will be loaded into the main memory at game startup (starting from `0x0200000000`); And `overlay9_xxxx. bin` files are dynamically loaded into memory as needed. All binary files are ARM machine code, so if I want to modify the logic of the game, it is necessary to modify the machine code. This requires the use of disassembly tools.	首先大致说明一下 NDS 游戏的可执行文件。其分为 arm9 和 arm7 两部分，而这两部分又分为主程序（`arm9.bin/arm7.bin`）和补丁程序（`overlay9_xxxx.bin/overlay7_xxxx.bin`）。以 arm9 为例，`arm9.bin` 中保存了程序的通用部分，会在游戏启动时加载到主内存（起始点为 `0x0200000000`）；而 `overlay9_xxxx. bin` 则根据需要动态加载到内存中。所有的二进制文件都是 ARM 的机器码，所以要想修改游戏的逻辑，就需要对机器码进行修改。这里就需要用到反汇编工具了。
	Referring to the article written by Haroohie Translation Club – ["Chokuretsu ROM Hacking Challenges Part 2 – Archive Archaeology"](https://haroohie.club/blog/2022-11-02-chokuretsu-archives), IDA can be used with [a plugin](https://github.com/kynex7510/nds_ida) to disassemble NDS ROM files. (By the way, the original author only implemented the disassembly function of `arm9.bin` and did not implement the function of `overay9_xxxx.bin`. I added the disassembly function of `overay9_xxxx.bin` based on the original author's work, see [here](https://github.com/Xzonn/NdsIda). The disassembly function of arm7 was not done since there is currently no need for it. If there is a need, I will conduct further research.)	参考了 Haroohie Translation Club 写的文章[“Chokuretsu ROM Hacking Challenges Part 2 – Archive Archaeology”](https://haroohie.club/blog/2022-11-02-chokuretsu-archives)，可以使用 IDA 搭配[插件](https://github.com/kynex7510/nds_ida)对 NDS 的 ROM 文件进行反汇编。（顺带一提，原作者仅实现了反汇编 `arm9.bin` 的功能，没有实现 `overay9_xxxx.bin` 的功能，我在原作者的基础上添加了 `overay9_xxxx.bin` 的反汇编功能，参见[此处](https://github.com/Xzonn/NdsIda)。arm7 的反汇编没有做，目前也没什么需求，如果有需求再说。）
	### Font Line Height In the Haroohie Translation Club's [build repository](https://github.com/haroohie-club/ChokuretsuTranslationBuild), I found that the [`src/symbols.x`](https://github.com/haroohie-club/ChokuretsuTranslationBuild/blob/main/src/symbols.x)[^3] file contains some functions that the team had already named:	### 字体行高在 Haroohie Translation Club 的构建项目[“ChokuretsuTranslationBuild”](https://github.com/haroohie-club/ChokuretsuTranslationBuild)中我发现 [`src/symbols.x`](https://github.com/haroohie-club/ChokuretsuTranslationBuild/blob/main/src/symbols.x)[^3] 文件有一些该团队已经命名的函数：
	``` javascript MI_DmaCopy32 = 0x02006ED0; MIi_CpuClearFast = 0x0200738C; GX_SetBankForBG = 0x0200277C; GX_SetGraphicsMode = 0x020025B8; arc_loadFileAndResolvePointers = 0x02033FC4; scene_renderDialogue = 0x0202D41C; ```	``` javascript MI_DmaCopy32 = 0x02006ED0; MIi_CpuClearFast = 0x0200738C; GX_SetBankForBG = 0x0200277C; GX_SetGraphicsMode = 0x020025B8; arc_loadFileAndResolvePointers = 0x02033FC4; scene_renderDialogue = 0x0202D41C; ```
	The function `scene_renderDialogue` looked very useful, so I took a look with IDA:	其中 `scene_renderDialogue` 这个函数看着很有用，拿 IDA 看一眼：
	![The result of disassembly using IDA, where the content related to line height were highlighted in green](/images/blog/0013/01_disassembly.png)	![使用 IDA 反汇编结果，其中与行高相关的内容已经高亮为了绿色](/images/blog/0013/01_disassembly.png)
	Here, we can roughly see that `cmp r2, #0`, `cmp r2, #0x60`, `cmp r2, #0xa` and `cmp r2, #0x23` are comparing `r2` with certain numbers. `U+000A` is a line break, and there is a statement `mov r0, #0x0e` in the corresponding branch. `0x0e` is 14 in decimal, and the line height of text in games is exactly 14 as I mentioned earlier. Then I modified it to `0x10` (16 in decimal), and went back to the game and... perfect! We lucked out here and solved this one almost immediately.	这里大概能看出来 `cmp r2, #0`、`cmp r2, #0x60`、`cmp r2, #0xa`、`cmp r2, #0x23` 是在比较，正好 `U+000A` 是换行符，而对应的分支里面有个 `mov r0, #0x0e`。`0x0e` 刚好又是十进制的 14，前面说过游戏中文字的行高是 14，这不是正好对上了吗？修改一下，改成 `0x10`（十进制的 16），回到游戏里一看，没错！就这样歪打正着地解决了。
	![The result of modifying line height to 16px](/images/blog/0013/02_increased_line_height.png)	![修改行高为 16px 的结果](/images/blog/0013/02_increased_line_height.png)
	### Expanding the Character Table This problem bothered me for quite a long time. Just changing the size of the character table is pointless on its own, as I have to modify the image size at the same time to make it display properly in the game. However, once the image contains approximately 2,500 Chinese characters (with only 300 characters expanded), importing it into the game will result in an error, which is manifested as a white screen after the manufacturers' logos are displayed. Obviously, this is due to the image being too large and causing insufficient memory, but I couldn't think of a better solution at first. Although I had made breakpoints in various places such as loading font image and displaying texts, I still hadn't figured out how to make the changes.	### 字库扩容这个问题困扰了我挺久，单纯修改码表大小没用，必须得同时修改图片大小才能让游戏中正常显示。但是，如果让图片包含大约 2500 个汉字（仅扩容 300 字），导入到游戏里就会出错，具体表现为游戏在厂商图标显示完毕后白屏。这显然应该是图片太大导致内存不够用了，但我一开始没有想到较好的解决办法。尽管我在字库图片读取、文本显示等多个地方都打了断点，但是还是没琢磨清楚该怎么改。
	At that moment, I happened to look at the build repo of Haroohie Translation Club again and found [a commit](https://github.com/haroohie-club/ChokuretsuTranslationBuild/commit/f8884a8057f38a9f6b0f384acf7bf3f95541a096):	这个时候我碰巧又看了 Haroohie Translation Club 的构建项目，发现了[一个提交](https://github.com/haroohie-club/ChokuretsuTranslationBuild/commit/f8884a8057f38a9f6b0f384acf7bf3f95541a096)：
	```plaintext commit f8884a8057f38a9f6b0f384acf7bf3f95541a096 Author: jonko0493 <email> Date: Tue Oct 10 03:51:20 2023 -0700	```plaintext commit f8884a8057f38a9f6b0f384acf7bf3f95541a096 Author: jonko0493 <email> Date: Tue Oct 10 03:51:20 2023 -0700
	Print debug logs to no$ console ```	Print debug logs to no$ console ```
	I pulled it down, built it locally, merged the modifications related to the executable file, and then opened the ROM file with DeSmuME:	拉下来在本地构建一下，把可执行文件相关的修改导入进去，然后拿 DeSmuME 打开 ROM 文件：
	![The console of DeSmuME, displaying debugging information](/images/blog/0013/03_emu_debug.png)	![DeSmuME 的控制台，展示了调试信息](/images/blog/0013/03_emu_debug.png)
	Wow, it really output the logs to the console of the emulator. Now it's easy to handle! I generated a very large image, and imported it into the game. Then I found that there was an error message showing the memory was not enough:	好家伙，真的把日志输出到模拟器的控制台里了。这下就好办了，生成一个超级大的图片，导入到游戏里，发现报错内存不够了：
	```plaintext memory is not enough[32256Byte] --memory report start-- --use list: 0 addr:021A2230 size: 16 list: 1 addr:021A2240 size: 32 list: 2 addr:021A2260 size: 224 ... list: 23 addr:02217CB0 size: 32256 --free list: 24 addr:0221FAB0 size: 11152 use memory size : 514176 503KB free memory size : 11152 11KB --memory report end-- ```	```plaintext memory is not enough[32256Byte] --memory report start-- --use list: 0 addr:021A2230 size: 16 list: 1 addr:021A2240 size: 32 list: 2 addr:021A2260 size: 224 ... list: 23 addr:02217CB0 size: 32256 --free list: 24 addr:0221FAB0 size: 11152 use memory size : 514176 503KB free memory size : 11152 11KB --memory report end-- ```
	After my calculation, the final address for memory allocation is `0x0221FAB0 + 0x2B90 = 0x02222640` (`11152` in decimal is `0x2B90`). I used the memory tool of DeSmuME to set a write breakpoint, and the last line of texts in the console during the write operation is as follows:	计算了一下，内存分配的最终地址是 `0x0221FAB0 + 0x2B90 = 0x02222640` （十进制的 `11152` 即为 `0x2B90`），拿 DeSmuME 的内存工具设一下写入断点，发现写入的时候控制台的最后一行文本是这样的：
	```plaintext gwork : s: 20e2660 e: 2242664: sz: 140000 ```	```plaintext gwork : s: 20e2660 e: 2242664: sz: 140000 ```
	I used IDA to locate this string, then jumped to the calling location, and I found the following assembly code:	拿 IDA 找这个字符串，然后跳转到调用的位置，发现了如下汇编代码：
	```arm loc_202A980: LDR R1, =dword_20A9AC8 MOV R0, #0x140000 LDR R2, [R1,#8] ORR R2, R2, #1 STR R2, [R1,#8] BL sub_2024750 MOV R1, R0 LDR R4, =dword_20A9AAC LDR LR, =dword_20A9AB4 LDR R12, =dword_20A9AB0 LDR R0, =aGworkSXEXSzX ; "gwork : s: %x e: %x: sz: %x\n" ADD R2, R1, #0x140000 MOV R3, #0x140000 STR R1, [R4] STR R1, [LR] STR R1, [R12] BL dbg_print20228DC ```	```arm loc_202A980: LDR R1, =dword_20A9AC8 MOV R0, #0x140000 LDR R2, [R1,#8] ORR R2, R2, #1 STR R2, [R1,#8] BL sub_2024750 MOV R1, R0 LDR R4, =dword_20A9AAC LDR LR, =dword_20A9AB4 LDR R12, =dword_20A9AB0 LDR R0, =aGworkSXEXSzX ; "gwork : s: %x e: %x: sz: %x\n" ADD R2, R1, #0x140000 MOV R3, #0x140000 STR R1, [R4] STR R1, [LR] STR R1, [R12] BL dbg_print20228DC ```
	The first `#0x140000` is likely related to memory allocation, while the latter two `#0x140000` are associated with debug information output. Since I want to expand the character table capacity to around 3,000 characters, I calculated and changed these numbers to `#0x160000` to meet the requirements.	第一个 `#0x140000` 应该是和内存分配有关的，后面两个 `#0x140000` 是和调试信息输出有关的。因为想要把字库容量扩容到 3000 字左右，计算了一下，将这几个数字改为 `#0x160000` 即可满足需求。
	In addition, I found this `#0x140000` in another location as well:	此外，在另一个地方也发现了这个 `#0x140000`：

	English	Chinese (Simplified)	Actions
	--- title: &title "Chokuretsu ROM Hacking Challenges from China – Character Conundrums!" description: &desc "Xzonn explores how he went about modifying the character table and line height for the Chinese translation of Chokuretsu" locale: 'en' navigation: author: 'Xzonn' year: 2024 month: 08 day: 04 tags: ['chokuretsu', 'romhacking', 'chinese'] image: '0013/00_thumbnail.png' head: meta: - property: 'og:title' content: title - property: 'og:description' content: desc - property: 'og:image' content: &img https://haroohie.club/images/blog/0013/00_thumbnail.png - property: 'og:image:alt' content: '' - property: 'og:url' content: 'https://haroohie.club/blog/2024-08-03-chokuretsu-chinese-chartable' - property: 'og:type' content: 'article' - name: 'twitter:title' value: title - name: 'twitter:description' value: desc - name: 'twitter:image' value: *img - name: 'twitter:site' value: '@haroohie' - name: 'twitter:card' value: 'summary_large_image' ---	--- title: &title "来自中国的《串联》ROM 破解挑战：字库难题" description: &desc "Xzonn 探讨了他如何修改《串联》汉化的码表和行高。" locale: 'zh-hans' navigation: author: 'Xzonn' year: 2024 month: 08 day: 04 tags: ['chokuretsu', 'romhacking', 'chinese'] image: '0013/00_thumbnail.png' head: meta: - property: 'og:title' content: title - property: 'og:description' content: desc - property: 'og:image' content: &img https://haroohie.club/images/blog/0013/00_thumbnail.png - property: 'og:image:alt' content: '' - property: 'og:url' content: 'https://haroohie.club/blog/2024-08-03-chokuretsu-chinese-chartable' - property: 'og:type' content: 'article' - name: 'twitter:title' value: title - name: 'twitter:description' value: desc - name: 'twitter:image' value: *img - name: 'twitter:site' value: '@haroohie' - name: 'twitter:card' value: 'summary_large_image' ---
	## Font First, let me briefly introduce the file structure of the game ROM:	## 字库先简单介绍一下这个游戏 ROM 的文件结构：
	### Character Table I extracted the character table file using the command-line tool "ChokuretsuTranslationCLI" in the ChokuretsuTranslationUtility, and opened it with the hex editor HxD:	### 码表用 ChokuretsuTranslationUtility 中的命令行工具“ChokuretsuTranslationCLI”提取码表文件，用 HxD 打开：
	## Executable File Before delving deeper, I had limited knowledge about the executable files of NDS games. However, as I looked more into this game and [the Chinese localization revision project for the Pokémon Gen IV](https://xzonn.top/PokemonChineseTranslationRevise/), at least it was able to solve the problems I encountered in a straightforward manner.	## 可执行文件在我深入研究之前，我对 NDS 游戏的可执行文件的了解不多。不过随着我深入研究了这个游戏以及[《宝可梦》第四世代的汉化修正项目](https://xzonn.top/PokemonChineseTranslationRevise/)，至少也算是歪打正着地解决了我遇到的问题。
	``` javascript MI_DmaCopy32 = 0x02006ED0; MIi_CpuClearFast = 0x0200738C; GX_SetBankForBG = 0x0200277C; GX_SetGraphicsMode = 0x020025B8; arc_loadFileAndResolvePointers = 0x02033FC4; scene_renderDialogue = 0x0202D41C; ```	``` javascript MI_DmaCopy32 = 0x02006ED0; MIi_CpuClearFast = 0x0200738C; GX_SetBankForBG = 0x0200277C; GX_SetGraphicsMode = 0x020025B8; arc_loadFileAndResolvePointers = 0x02033FC4; scene_renderDialogue = 0x0202D41C; ```
	The function `scene_renderDialogue` looked very useful, so I took a look with IDA:	其中 `scene_renderDialogue` 这个函数看着很有用，拿 IDA 看一眼：
	![The result of disassembly using IDA, where the content related to line height were highlighted in green](/images/blog/0013/01_disassembly.png)	![使用 IDA 反汇编结果，其中与行高相关的内容已经高亮为了绿色](/images/blog/0013/01_disassembly.png)
	![The result of modifying line height to 16px](/images/blog/0013/02_increased_line_height.png)	![修改行高为 16px 的结果](/images/blog/0013/02_increased_line_height.png)
	Print debug logs to no$ console ```	Print debug logs to no$ console ```
	At that moment, I happened to look at the build repo of Haroohie Translation Club again and found [a commit](https://github.com/haroohie-club/ChokuretsuTranslationBuild/commit/f8884a8057f38a9f6b0f384acf7bf3f95541a096):	这个时候我碰巧又看了 Haroohie Translation Club 的构建项目，发现了[一个提交](https://github.com/haroohie-club/ChokuretsuTranslationBuild/commit/f8884a8057f38a9f6b0f384acf7bf3f95541a096)：
	![The console of DeSmuME, displaying debugging information](/images/blog/0013/03_emu_debug.png)	![DeSmuME 的控制台，展示了调试信息](/images/blog/0013/03_emu_debug.png)
	I pulled it down, built it locally, merged the modifications related to the executable file, and then opened the ROM file with DeSmuME:	拉下来在本地构建一下，把可执行文件相关的修改导入进去，然后拿 DeSmuME 打开 ROM 文件：
	After my calculation, the final address for memory allocation is `0x0221FAB0 + 0x2B90 = 0x02222640` (`11152` in decimal is `0x2B90`). I used the memory tool of DeSmuME to set a write breakpoint, and the last line of texts in the console during the write operation is as follows:	计算了一下，内存分配的最终地址是 `0x0221FAB0 + 0x2B90 = 0x02222640` （十进制的 `11152` 即为 `0x2B90`），拿 DeSmuME 的内存工具设一下写入断点，发现写入的时候控制台的最后一行文本是这样的：
	## Conclusion Overall, my research results are largely based on the work of those who came before me. The solutions to several issues were somewhat accidental, but there were still some gains for me. The subsequent work will mainly involve translation. However, researching how to localize the game into Chinese is much more interesting than simply translating texts.	## 结语总体来说，我的研究成果基本上都是基于前辈们已有的结果，几个问题的解决方式也算是歪打正着，不过也算是有所收获。后续的工作主要就是翻译了，不过，研究如何汉化可比翻译文本有意思多了。
	00000000 01 00 00 00 38 11 00 00 14 00 00 00 14 00 00 00 ....8........... 00000010 01 00 00 00 81 97 81 41 81 42 81 44 81 45 81 46 .....—.A.B.D.E.F 00000020 81 48 81 49 81 51 81 58 81 5B 81 5C 81 60 81 63 .H.I.Q.X.[.\.`.c 00000030 81 65 81 66 81 67 81 68 81 69 81 6A 81 73 81 74 .e.f.g.h.i.j.s.t 00000040 81 75 81 76 81 77 81 78 81 79 81 7A 81 7B 81 7C .u.v.w.x.y.z.{.\| ```	00000000 01 00 00 00 38 11 00 00 14 00 00 00 14 00 00 00 ....8........... 00000010 01 00 00 00 81 97 81 41 81 42 81 44 81 45 81 46 .....—.A.B.D.E.F 00000020 81 48 81 49 81 51 81 58 81 5B 81 5C 81 60 81 63 .H.I.Q.X.[.\.`.c 00000030 81 65 81 66 81 67 81 68 81 69 81 6A 81 73 81 74 .e.f.g.h.i.j.s.t 00000040 81 75 81 76 81 77 81 78 81 79 81 7A 81 7B 81 7C .u.v.w.x.y.z.{.\| ```
	```plaintext memory is not enough[32256Byte] --memory report start-- --use list: 0 addr:021A2230 size: 16 list: 1 addr:021A2240 size: 32 list: 2 addr:021A2260 size: 224 ... list: 23 addr:02217CB0 size: 32256 --free list: 24 addr:0221FAB0 size: 11152 use memory size : 514176 503KB free memory size : 11152 11KB --memory report end-- ```	```plaintext memory is not enough[32256Byte] --memory report start-- --use list: 0 addr:021A2230 size: 16 list: 1 addr:021A2240 size: 32 list: 2 addr:021A2260 size: 224 ... list: 23 addr:02217CB0 size: 32256 --free list: 24 addr:0221FAB0 size: 11152 use memory size : 514176 503KB free memory size : 11152 11KB --memory report end-- ```
	``` plaintext ├── dat.bin ├── evt.bin ├── grp.bin ├── scn.bin ├── snd.bin ├── bgm │ ├── BGM001.bin │ ├── BGM002.bin │ ├── ... │ └── BGM034.bin ├── movie │ ├── MOVIE00.mods │ └── MOVIE01.mods └── vce ├── ANZ_ANOTHER00.bin ├── ANZ_ANOTHER01.bin ├── ... └── TRY_WRITE00.bin ```	``` plaintext ├── dat.bin ├── evt.bin ├── grp.bin ├── scn.bin ├── snd.bin ├── bgm │ ├── BGM001.bin │ ├── BGM002.bin │ ├── ... │ └── BGM034.bin ├── movie │ ├── MOVIE00.mods │ └── MOVIE01.mods └── vce ├── ANZ_ANOTHER00.bin ├── ANZ_ANOTHER01.bin ├── ... └── TRY_WRITE00.bin ```
	``` plaintext ＠、。．・：？！＿々ー―～…‘’“”（）《》「」『』【】＋－×＝°％＆☆■♪０１２３４５６７８９ＡＢＣＤＥＦＧＨＩＪＫＬＭＮＯＰＱＲＳＴＵＶＷＸＹＺａｂｃｄｅｆｇｈｉｊｋｌｍｎｏｐｑｒｓｔｕｖｗｘｙｚぁあぃい... ```	``` plaintext ＠、。．・：？！＿々ー―～…‘’“”（）《》「」『』【】＋－×＝°％＆☆■♪０１２３４５６７８９ＡＢＣＤＥＦＧＨＩＪＫＬＭＮＯＰＱＲＳＴＵＶＷＸＹＺａｂｃｄｅｆｇｈｉｊｋｌｍｎｏｐｑｒｓｔｕｖｗｘｙｚぁあぃい... ```
	Referring to the article written by Haroohie Translation Club – ["Chokuretsu ROM Hacking Challenges Part 2 – Archive Archaeology"](https://haroohie.club/blog/2022-11-02-chokuretsu-archives), IDA can be used with [a plugin](https://github.com/kynex7510/nds_ida) to disassemble NDS ROM files. (By the way, the original author only implemented the disassembly function of `arm9.bin` and did not implement the function of `overay9_xxxx.bin`. I added the disassembly function of `overay9_xxxx.bin` based on the original author's work, see [here](https://github.com/Xzonn/NdsIda). The disassembly function of arm7 was not done since there is currently no need for it. If there is a need, I will conduct further research.)	参考了 Haroohie Translation Club 写的文章[“Chokuretsu ROM Hacking Challenges Part 2 – Archive Archaeology”](https://haroohie.club/blog/2022-11-02-chokuretsu-archives)，可以使用 IDA 搭配[插件](https://github.com/kynex7510/nds_ida)对 NDS 的 ROM 文件进行反汇编。（顺带一提，原作者仅实现了反汇编 `arm9.bin` 的功能，没有实现 `overay9_xxxx.bin` 的功能，我在原作者的基础上添加了 `overay9_xxxx.bin` 的反汇编功能，参见[此处](https://github.com/Xzonn/NdsIda)。arm7 的反汇编没有做，目前也没什么需求，如果有需求再说。）
	Wow, it really output the logs to the console of the emulator. Now it's easy to handle! I generated a very large image, and imported it into the game. Then I found that there was an error message showing the memory was not enough:	好家伙，真的把日志输出到模拟器的控制台里了。这下就好办了，生成一个超级大的图片，导入到游戏里，发现报错内存不够了：
	```plaintext gwork : s: 20e2660 e: 2242664: sz: 140000 ```	```plaintext gwork : s: 20e2660 e: 2242664: sz: 140000 ```
	```arm loc_202A980: LDR R1, =dword_20A9AC8 MOV R0, #0x140000 LDR R2, [R1,#8] ORR R2, R2, #1 STR R2, [R1,#8] BL sub_2024750 MOV R1, R0 LDR R4, =dword_20A9AAC LDR LR, =dword_20A9AB4 LDR R12, =dword_20A9AB0 LDR R0, =aGworkSXEXSzX ; "gwork : s: %x e: %x: sz: %x\n" ADD R2, R1, #0x140000 MOV R3, #0x140000 STR R1, [R4] STR R1, [LR] STR R1, [R12] BL dbg_print20228DC ```	```arm loc_202A980: LDR R1, =dword_20A9AC8 MOV R0, #0x140000 LDR R2, [R1,#8] ORR R2, R2, #1 STR R2, [R1,#8] BL sub_2024750 MOV R1, R0 LDR R4, =dword_20A9AAC LDR LR, =dword_20A9AB4 LDR R12, =dword_20A9AB0 LDR R0, =aGworkSXEXSzX ; "gwork : s: %x e: %x: sz: %x\n" ADD R2, R1, #0x140000 MOV R3, #0x140000 STR R1, [R4] STR R1, [LR] STR R1, [R12] BL dbg_print20228DC ```
	In addition, I found this `#0x140000` in another location as well:	此外，在另一个地方也发现了这个 `#0x140000`：
	## A Foreword from Jonko Hi everyone! Today's blog post is from Xzonn who is working on translating Suzumiya Haruhi no Chokuretsu into Chinese. I became aware of Xzonn a month or two after he forked some of our repos on GitHub (as he describes in this very post!) and as soon as I found out he was doing this work I knew I had to reach out to him. What you're reading today is a reproduction (in English courtesy the man himself, with prose edits by me) of a blog post [on Xzonn's site](https://xzonn.top/posts/Suzumiya-Haruhi-no-Chokuretsu-Chinese-Localization.html). The hope is that by translating his work into English, we can reach an even larger audience for his work (and vice-versa, since he's been translating our posts into Chinese as well 🥰). Please enjoy!	## Jonko 的前言大家好！今天的博客来自 Xzonn，他正在将《凉宫春日的串联》翻译成中文。Xzonn 在 GitHub 上 fork 了我们的一些仓库（就像他在这篇文章中所说的那样！）一两个月后，我注意到了他。当我发现他在做这项工作时，我就知道我应该联系他。你今天读的是[在 Xzonn 的网站上](https://xzonn.top/posts/Suzumiya-Haruhi-no-Chokuretsu-Chinese-Localization.html)的一篇文章的副本（由他本人提供，并由我进行了英语编辑）。希望通过将他的作品翻译成英文，可以为他的作品吸引更多的观众（反之亦然，因为他也一直在将我们的帖子翻译成中文🥰）。敬请阅读！
	From the file names, it can be roughly inferred that `dat.bin` stores data files, `evt.bin` stores game storyline related scripts, and `grp.bin` stores image files. These three files are actually archive files, which store a large number of small files. The other files are all audio or video files. To modify the font used in this game, I need to edit the character table and the image of the font itself. The character table is file #`0x71` in `dat.bin`, and the font image is file #`0xE50` in `grp.bin`.	从文件名可以大概看出，`dat.bin` 存放数据文件，`evt.bin` 存放游戏剧情相关的脚本，`grp.bin` 存放图片文件，这三个文件实际上都是一个文件包，其中储存了较多的小文件。其他文件和音频或视频相关。要修改的字库包括了码表和图片，码表是 `dat.bin` 中的第 `0x71` 个文件，图片是 `grp.bin` 中的第 `0xE50` 个文件。
	The first `0x14` bytes are obviously the file header, where `0x04-0x07` is the size of the file[^1] (these bytes will need to be modified after expanding the character table). From `0x14` to the end is all the characters contained in the font image, in order. At first, I thought these two-byte characters might be UTF-16-LE encoded, but parsing with that encoding gave a garbled result. So I tried Shift-JIS encoding and found that it was consistent with the extracted image. I opened it with VS Code directly and change the encoding to Shift-JIS, and I got characters included in the file:	前 `0x14` 个字节显然是文件头，其中 `0x04-0x07` 是文件的大小[^1]（后续扩充码表需要修改此处）。从 `0x14` 到最后是字体图片包含的所有字符，按顺序排列。这种双字节的字符首先考虑 UTF-16-LE 编码，但是发现是乱码，于是尝试了一下 Shift-JIS 编码，发现和提取出来的图片是一致的。直接拿 VS Code 打开，改一下编码，就能得到包含的字符：
	Since the modified text is in Simplified Chinese, I need to find a way to map Simplified Chinese characters to Shift-JIS codes. I wanted to directly use the [GB18030 encoding](https://en.wikipedia.org/wiki/GB_18030) at first, but I found that GB18030 contained far more characters than Shift-JIS, so I gave up on that. The solution I settled on was to count the number of Simplified Chinese characters in the translated text, sort them according to frequency of use, and then check whether they are in the original character table. If they are present, the original Shift-JIS code is directly used; if not, we replace a Japanese character that does not appear in the translated text. This ensures that as many characters as possible can be displayed correctly. Finally, the replacement table was saved as a `.json` file for use when importing text.	因为导入的文本是简体中文，所以需要想办法把简体中文汉字对应到 Shift-JIS 编码中。我本来想直接拿 GB18030 编码直接扔进去，但是发现 GB18030 包含的中文汉字远多于 Shift-JIS 包含的日文汉字，因此作罢。最后的解决方案是，统计翻译后的文本中出现的简体中文汉字次数，按照使用次数从多到少排序，然后依次检查是否在原有的码表中。如果在，就直接用原有的 Shift-JIS 编码；如果不在，就用未在翻译后的文本中出现的日文汉字替换掉。这样就能保证尽可能多的字符能够正确显示。最后将替换的对应表保存成 `.json` 文件，供导入文本时使用。
	Here, we can roughly see that `cmp r2, #0`, `cmp r2, #0x60`, `cmp r2, #0xa` and `cmp r2, #0x23` are comparing `r2` with certain numbers. `U+000A` is a line break, and there is a statement `mov r0, #0x0e` in the corresponding branch. `0x0e` is 14 in decimal, and the line height of text in games is exactly 14 as I mentioned earlier. Then I modified it to `0x10` (16 in decimal), and went back to the game and... perfect! We lucked out here and solved this one almost immediately.	这里大概能看出来 `cmp r2, #0`、`cmp r2, #0x60`、`cmp r2, #0xa`、`cmp r2, #0x23` 是在比较，正好 `U+000A` 是换行符，而对应的分支里面有个 `mov r0, #0x0e`。`0x0e` 刚好又是十进制的 14，前面说过游戏中文字的行高是 14，这不是正好对上了吗？修改一下，改成 `0x10`（十进制的 16），回到游戏里一看，没错！就这样歪打正着地解决了。
	### Expanding the Character Table This problem bothered me for quite a long time. Just changing the size of the character table is pointless on its own, as I have to modify the image size at the same time to make it display properly in the game. However, once the image contains approximately 2,500 Chinese characters (with only 300 characters expanded), importing it into the game will result in an error, which is manifested as a white screen after the manufacturers' logos are displayed. Obviously, this is due to the image being too large and causing insufficient memory, but I couldn't think of a better solution at first. Although I had made breakpoints in various places such as loading font image and displaying texts, I still hadn't figured out how to make the changes.	### 字库扩容这个问题困扰了我挺久，单纯修改码表大小没用，必须得同时修改图片大小才能让游戏中正常显示。但是，如果让图片包含大约 2500 个汉字（仅扩容 300 字），导入到游戏里就会出错，具体表现为游戏在厂商图标显示完毕后白屏。这显然应该是图片太大导致内存不够用了，但我一开始没有想到较好的解决办法。尽管我在字库图片读取、文本显示等多个地方都打了断点，但是还是没琢磨清楚该怎么改。
	[^1]: This value is not actually the size of the file but rather a pointer to the "end pointers" section; because the character table has no end pointers, it ends up just being the end of the file. [^2]: Sorry for putting you through this, Xzonn! I've since added the ability to specify that an image has a "new size" on import! [^3]: This file now has a lot of functions in it, but at the time it really was just the function Xzonn shows (see [here](https://github.com/haroohie-club/ChokuretsuTranslationBuild/blob/80b63ce25528a31ed9d14139a34f8f52ae083945/src/symbols.x)). I actually added a bunch more functions in after I saw their blog post!	[^1]: 这个值实际上不是文件的“大小”，而是指向“结束指针”部分的指针；因为字符表没有结束指针，所以它最终只是文件的结尾。 [^2]: 很抱歉让你经历了这些，Xzonn！在这之后我添加了在导入时修改图像的“新尺寸”的功能！ [^3]: 这个文件现在有了很多的函数，但当时它确实只有 Xzonn 展示的这些函数（参见[这里](https://github.com/haroohie-club/ChokuretsuTranslationBuild/blob/80b63ce25528a31ed9d14139a34f8f52ae083945/src/symbols.x)）。实际上，在我看到他的文章后，我添加了更多的函数！

Loading…

Xzonn

Translation changed

English

Chinese (Simplified) 10 characters edited Current translation Translated

a month ago

admin

Translation changed

English

Chinese (Simplified) 386 characters edited Translated

~~Here, we can roughly see that~~ 这里大概能看出来`cmp r2, #0`, 、`cmp r2, #0x60`, 、`cmp r2, #0xa` ~~and~~ 、`cmp r2, #0x23` are comparing `r2` with certain numbers. `U+000A` is a line break, and there is a statement `mov r0, #0x0e` in the corresponding branch. `0x0e` is 14 in decimal, and the line height of text in games is exactly 14 as I mentioned earlier. Then I modified it to `0x10` (16 in decimal), and went back to the game and... perfect! We lucked out here and solved this one almost immediately.是在比较，正好`U+000A`是换行符，而对应的分支里面有个`mov r0, #0x0e`。`0x0e`刚好又是十进制的14，前面说过游戏中文字的行高是14，这不是正好对上了吗？修改一下，改成`0x10`（十进制的16），回到游戏里一看，没错！就这样歪打正着地解决了。

a month ago

None

String updated in the repository

English

Chinese (Simplified) 479 characters edited Needs editing

a month ago

Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: 0x0e

Reset

Glossary

English	Chinese (Simplified)
No related strings found in the glossary.

String information

Source string location

:129

String age

a month ago

Last updated

a month ago

Source string age

a month ago

Translation file

content/blog/13.2024-08-03-chokuretsu-chinese-chartable/zh-hans.md, string 26