New working software list additions
-----------------------------------
Addams Family Values (prototype) [snescentral, VGHF]
Armored Police Metal Jack (USA, early prototype) [snescentral, VGHF]
Congo's Caper (prototype) [snescentral, VGHF]
Might and Magic II - Gates to Another World (USA, prototype) [snescentral, VGHF]
Might and Magic II - Gates to Another World (USA, earlier prototype) [snescentral, VGHF]
Operation Thunderbolt (prototype) [snescentral, VGHF]
Rock n' Roll Racing (USA, prototype) [snescentral, VGHF]
Street Racer (prototype) [snescentral, VGHF]
Tom & Jerry (USA, prototype, alt) [snescentral, VGHF]
World Cup USA 94 (USA, prototype) [snescentral, VGHF]
Mortal Kombat 3 (USA, final prototype) [togemet2]
New NOT_WORKING software list additions
---------------------------------------
Mortal Kombat II (USA, final prototype) [togemet2]
- snes.xml: mk2u is identical to mk2ua when it should be a revision, not simply a split ROM. Replace with correct dump.
- snes.xml: mk3p1 is identical to mk3up, and there's no evidence of two prototypes from the same day on different hardware. Keep documented board, remove duplicate.
The free-for-all on labels in software lists is not working. There's no
consistency, labels are getting excessively long, people are starting to
use non-ASCII characters in labels making it harder for others to type
them when manipulating files on the command line, and there's too much
markup being put in labels.
The length limit is 127 characters, same as for labels in MAME itself.
This should be long enough to be descriptive. Remember that the Win32
path limit is 260 characters, and many applications and frameworks have
issues with longer paths, including Windows Explorer and the .NET
framework. Labels are used as filenames, so concessions need to be
made for this.
I have not abbreviated excessively long labels myself - they're
currently causing 135 validity errors. Someone else can fix them.
Printable ASCII characters are allowed, with a few exceptions. The
exceptions are limited to characters most likely to cause issues for
interactive shells and scripts:
* ! - csh event substitution (very difficult to escape properly)
* $ - sh varibale expansion
* % - csh job control, cmd variable expansion
* / - UNIX directory separator
* : - sh path separator, Windows drive qualifier
* \ - sh escape, Windows directory separator
Most of the labels that had to be edited were using ! for markup, or
using ! and % for titles in labels. Strangely, titles in labels are
often forced to lower case, despite this never being enforced for
software lists. There are also various other edits to titles used for
labels, such as moving articles to the end (with or without a comma),
or replacing spaces with underscores. As I already said, there's no
consistency at all.
There is far too much markup in labels. They're even being used for
notes in some cases (e.g. at least one case where a dumper's name is in
the label). The XML schema supports metadata - use it. For example,
you can use part_id for an unrestricted display name for a software
part. You can also use XML comments for notes.
And while on the topic of metadata, vgmplay.xml is putting the same
thing in the part_id as well as the label. The part_id should have
the actual title, not the title mangled to make it more suitable for
use as a filename. Addressing this would be a lot of work, given how
large the file is.
For now, empty data areas in software lists cause a verbose message
rather than a validation warning. There are thousands of software
lists using empty data areas to indicate the size/width of cartridge
RAM/EEPROM/etc.
Get rid of a couple of copies of the CC0 text. Add header comment to
CC0 files to remind people editing them what the terms are. Also add
some missing XML headers. The header comments in layouts won't bloat
the binary - they get stripped out before compressing, same as any other
comments.
This effectively reverts b380514764 and
c24473ddff, restoring the state at
598cd52272.
Before pushing, please check that what you're about to push is sane.
Check your local commit log and ensure there isn't anything out-of-place
before pushing to mainline. When things like this happen, it wastes
everyone's time. I really don't need this in a week when real work™ is
busting my balls and I'm behind where I want to be with preparing for
MAME release.
