You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current serverside and storage implementation does not allow textbound annotation spans to include newline or tab characters.
To avoid the restrictions this implies, the format and related functionality should be revised to support some form of escaping. Standard C-style escapes (\n for newline, \t for tab, \\ for backslash etc.) would be one obvious possibility.
The text was updated successfully, but these errors were encountered:
I reside in camp get-rid-of-the-bloody-text-component, sanity checking has no place in a storage format and the implications of the escaping means that you can't analyse the output as real text any more. I would suggest creating a set of tools for working with the format from a command line instead if you want fast and easy analysis.
The current serverside and storage implementation does not allow textbound annotation spans to include newline or tab characters.
To avoid the restrictions this implies, the format and related functionality should be revised to support some form of escaping. Standard C-style escapes (
\n
for newline,\t
for tab,\\
for backslash etc.) would be one obvious possibility.The text was updated successfully, but these errors were encountered: