Printing values for Roms that don't use extra memory is nonsensical. e.g.

extra_memory: false
extra_memory_type: 0x20
extra_memory_start: 0x20202020
extra_memory_end: 0x20202020

Which currently prints the 0x20 values (which is an ASCII SPACE) which is the correct way to set values when they should be left blank in the header

Need to:

• Decide what to display as the values (e.g. None or "N/A") or hide them completely
• Implement solution

No Debian package is produced in OBS

https://build.opensuse.org/package/show/home:billyrayvalentine/megadrive-cart-info

Need to:
Create a Debian build and test for Debian and Ubuntu

https://en.opensuse.org/openSUSE:Build_Service_Debian_builds

Passing an invalid filename, path that is a directory etc, throws exceptions which are uncaught and results in a panic. Fix this so that an error is caught and presented more gracefully e.g. "invalid filename $filename" etc.

Values are duplicated in both the RPM spec and the Cargo.toml.
Cargo.toml should be the single source of truth for values such as Version, Description, License etc

Need to:
Create a build.rs so that values from the Cargo.toml are set in the RPM spec - thus avoiding duplication.

As the version should always be set in the Cargo.toml, consider removing the set version service in OBS which sets the Version from the last tag it finds from git.

Some roms use the new style region identifier which is not currently recognised

https://www.plutiedev.com/rom-header#region

Needs to:
implementation so that new style region identifier is recognised

e.g. Phantasy Star IV currently prints:
region: 4

Where as this is actually Americas (U)

Need to add guidance on how to install RPM from obs

To help identify gaps in the shift-jis coverage and to aid development of other missing features, it would be useful to capture the raw bytes (pre UTF8, numeric) conversion and have them be able to be printed as a debug feature:

e.g. ./megadrive-cart-info --some-flag

........
game name domestic: バーチャレーシング
game_name_domestic_raw: 0x83, 0x6f, 0x81, 0x5b, 0x83, 0x60, 0x83, 0x83, 0x83, 0x8c, 0x81, 0x5b, 0x83, 0x56,
0x83, 0x93, 0x83, 0x4f

Need: Explore this solution more and implement

Bytes with values of 0x81 - 0x9F are the first of a double byte value. If the second byte is missing, the program will panic with an index error.

Need to:

• Decide how to handle a missing second byte - either silently drop it or convert the first byte to a unicode replacement char (u+FFFD)
• Implement unit test
• Implement solution