A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Validator.nu GNU Output
Jump to navigation
Jump to search
Support for the GNU error message format has been requested.
Issues
The GNU spec isn’t quite specific. The following issues need to be addressed:
- What should be put in as the file name when there is none?
- Currently, the empty string is put in the file name field in this case.
- How does one stuff a URI in the file name field considering that the colon is a field separator?
- The URI is put there as is, because consumers are expected to run a smarter regexp.
- What should be done if line breaks occur in the message?
- U+21A9 is written instead.
- Do the anticipated consuming apps support UTF-8?
- The output is UTF-8-only.
- Should this format only include errors? How does one distinguish informative messages?
- Each message is prepended
type subtype:. (The colon is followed by a space and subtype with its preceding space is optional.) - The type and subtype have the same semantics as in the JSON format.
- Each message is prepended
- Validator.nu counts columns by UTF-16 code units with a tab simply counting as one column. The GNU format counts “ASCII” columns with 8-stop tab expansion.
- Columns are reported by UTF-16 code unit without tab expansion.