search

UltraStar-Deluxe / format

UltraStar Format Specification
https://usdx.eu/format
MIT License
9 stars 2 forks source link

[Spec] Case insensitive header fields #36

Closed achimmihca closed 8 months ago

achimmihca commented 8 months ago

Suggestion

Why are header fields in all uppercase? Is this a convention or enforced by the format?

By defining header field names as case insensitive, one could make the format more robust and readable.

The following would then be equivalent

#VIDEOGAP: 1.2
#videogap: 1.2
#videoGap: 1.2
#VideoGap: 1.2

Use case

Use camelCase or PascalCase for header field names, e.g., #MedleyStartBeat

Extra info/examples/attachments

No response

Baklap4 commented 8 months ago

This has always been the case. Not quite sure what the actual reasoning is.

But by defining it to be case-senstive its up to the txt producers and then we might get a mix of, camelCase, PascalCase and UPPERCASE.

I agree with the readabilty and would vouch for PascalCase, but i wouldn't like to see a mix of the beforementioned ones. Stick with one format as this makes it easy to anticipate for :)

basisbit commented 8 months ago

I'd consider the different options to all be approximately similar good for the task. Thus it might be better to just keep it the way it has been the past 15 years or so, unless I am missing an important reason.

achimmihca commented 8 months ago

Ok. It is surprisingly consistent at the moment and it's not causing trouble. I guess better not change a good running system.

So, this issue can be closed as "won't implement"