fix: let taiwan and asia-ntsc answer each other

kronos tags the ST-V BIOS epr-19854.ic8 taiwan, mednafen_stv tags it
asia-ntsc, the SMPC area Mednafen names for Taiwan (ss.cpp:1119,
2363-2364). As siblings under asia they never matched, so a request in
one spelling dropped the file tagged in the other, and --region
taiwan,us dropped the Saturn sega_101.bin. AREA_TERRITORIES relates
each area to the territory it serves, china for asia-pal included, in
region.py and its installer copy.
This commit is contained in:
Abdessamad Derraz committed 2026-10-21 05:20:08 +02:00
1 parent e318bb4503
commit 7bcd41e0c4
7 files changed
+56 -8

No files matched your search

+4 -1
View File
@@ -186,7 +186,10 @@ What does not, and why each trap is easy to fall into:
`env.Loader.ReqSpec == "PAL"`, a video specification, and the Atari 2600 has
no region lock. There is no signal field: drop `region:` rather than map it.
The exception is hardware that fuses both axes in one register, such as the
Saturn SMPC area codes behind `asia-ntsc` and `asia-pal`.
Saturn SMPC area codes behind `asia-ntsc` and `asia-pal`. Mednafen names
them for Taiwan and China, so a `--region taiwan` request reaches an
`asia-ntsc` file and a `--region china` request an `asia-pal` one, and the
other way round (`AREA_TERRITORIES` in `scripts/region.py`).
- **A single-region system.** When every file of a system shares one region,
the pack filter keeps them all anyway, so annotating adds nothing.
- **A language without a territory.** Arabic MSX variants, CJK fonts. The