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

OBOFormat parser does not unescape strings #50

Closed
GoogleCodeExporter opened this issue Mar 12, 2015 · 1 comment
Closed

OBOFormat parser does not unescape strings #50

GoogleCodeExporter opened this issue Mar 12, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

One symptom are errors parsing definitions, after a second write of an 
ontology. 

The reason is that escaped characters such as \{, \}, \", or \n are not 
transferred back to their original during the read. 

Later during the write, they are symbols are escaped again.

Added a test: OboEscapeCharsTest

Remark: There was already an obo file (escape_chars_test.obo), but no test made 
use of it.

Original issue reported on code.google.com by HDie...@lbl.gov on 2 Sep 2011 at 9:54

@GoogleCodeExporter
Copy link
Author

fix committed in rev 283.

Original comment by HDie...@lbl.gov on 2 Sep 2011 at 10:22

  • Changed state: Fixed

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