# Touch Detective — Known Issues / Follow-ups

Parked June 14 2026. The browser entry works (TD1/TD2 games → per-scene
chapters, DS/Switch source filter, TD1 Switch bilingual). Open items:

## 1. TD2 Switch Japanese is sparse (~2%)
TD2's Switch scripts are Lua; JP only survives as comments above the active EN
call, and only ~2,015 of ~12,200 dialogue calls kept one. So TD2 Switch is
mostly EN-only and no parser can recover JP that isn't in the build.
(TD1 Switch is fine: 81% bilingual from the .aqc pools.)

## 2. TD2 Switch DB looks inflated
TD2 Switch = 79,659 rows in the DB (built from `td2_switch_attributed.txt`) but
the romFS 2 lua only has ~12,200 actual dialogue calls. The attributed dump
appears to carry heavy duplication / non-dialogue. Consider REBUILDING TD2
Switch directly from the lua (`romFS 2/Section_1/Script/**/*.lua`): cleaner
~12k dialogue rows, speakers from the `L_XXX` arg, scene = L###/chapterN, and
the JP comments paired inline.

## 3. Full Japanese catalogue = the JP DS ROMs (the real fix for JP)
`or1/` and `or2/` are the unpacked Japanese DS ROMs (Osawari Tantei). The JP
text is in `data/data/bin_subfiles/*` — LZ-compressed `data.bin` sub-files
encoded via the `td_ds_char_map.json` glyph table. Decoding (LZ10 + glyph map)
yields the complete JP for both games, which would pair with the DS English
dumps. Not done — it's a sizable extraction but is the authoritative JP source.

## Done / kept
- `games/touch_detective/build_db.py` (EN, DS+Switch, GAME→per-scene chapters).
- `games/touch_detective/add_japanese.py` (TD1 Switch 81% JP, TD2 Switch 2%).
