Skip to content
New issue

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

Allow any character in textbound annotation span #819

Open
spyysalo opened this issue Jul 3, 2012 · 3 comments
Open

Allow any character in textbound annotation span #819

spyysalo opened this issue Jul 3, 2012 · 3 comments

Comments

@spyysalo
Copy link
Member

spyysalo commented Jul 3, 2012

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.

@ghost
Copy link

ghost commented Jul 3, 2012

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.

@spyysalo
Copy link
Member Author

spyysalo commented Jul 3, 2012

Sanity checking absolutely does have a place in a standoff format used for import/export; it would be begging for trouble to take this out.

@ghost
Copy link

ghost commented Jul 5, 2012

@spyysalo: I agree with you on the import/export portion, I still hate the text component though since it is:

  • "Hard" to parse
  • Needs escaping to support text in the first place
  • If it is escaped it can't be treated as text if you use cut on it (meh!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant