We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The below only applies to v3.0 and v4.0 (i.e., not v2.1):
For properties with value type TEXT (e.g., NOTE), backslashes are only permitted as part of an escape sequence.
TEXT
NOTE
Currently, other (stray) backslashes are kept verbatim, and validate() does not provide an error message.
validate()
I would expect that validate() yields an error message. Optionally, if the REPAIR flag is given, validate() might remove stray backslashes.
REPAIR
Example: NOTE:_\x_\:_\\_\;_\,_\n_\N_ is decoded to _\x_\:_\_;_,_<LF>_<LF>_ where <LF> is the LF (\n) character.
NOTE:_\x_\:_\\_\;_\,_\n_\N_
_\x_\:_\_;_,_<LF>_<LF>_
<LF>
\n
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The below only applies to v3.0 and v4.0 (i.e., not v2.1):
For properties with value type
TEXT
(e.g.,NOTE
), backslashes are only permitted as part of an escape sequence.Currently, other (stray) backslashes are kept verbatim, and
validate()
does not provide an error message.I would expect that
validate()
yields an error message.Optionally, if the
REPAIR
flag is given,validate()
might remove stray backslashes.Example:
NOTE:_\x_\:_\\_\;_\,_\n_\N_
is decoded to_\x_\:_\_;_,_<LF>_<LF>_
where<LF>
is the LF (\n
) character.The text was updated successfully, but these errors were encountered: