(2021-04-24, 14:00)Stefan Frenz Wrote: Yes, LDInspector tests the set number and reports non-numbers as "contains non-numeric chars, which is very unlikely". Additional "-1" are hinted by "hint: optional qualifier is 1 (use only if it is greater than 1)". The second part after the set number is tested for numbers, too, resulting also in "contains non-numeric chars" if not a number.
I can add the "-" and/or "/" character for the set id which automatically would allow "700-1-1" and "700/1-1" - maybe another warning "which is very unlikely"? But, hum, I'm still not sure if adding this flexibility for some edge cases (or aren't they edges?) introduces problems for most other sets in checking file names. As I appreciate all feedback: maybe some other opinions from Johann or Philippe which helped me on my struggling way through the docs?
They are definitely edge cases—I can't even think of another example where this would come up, at least for OMR purposes. Frankly, it's a stretch whether even these models fit within the spirit of the OMR. So I'd agree that it may not be worth allowing this flexibility, if it might cause other legitimate errors to be missed.
Here's an idea: what if we allow "." for the set id, but not "-" or "/" (because they cause other potential conflicts)? Then it could be understood that "." is the preferred substitute for "/" in set numbers, because there are a lot of early sets that use this character, even if they don't represent specific models. This matches the convention used by some of the inventory sites.
And then if the "." is found, it could trigger a hint or warning but not an error.