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

parsing non-RTF content should throw exception #8

Open
stippi opened this issue Nov 25, 2015 · 0 comments
Open

parsing non-RTF content should throw exception #8

stippi opened this issue Nov 25, 2015 · 0 comments

Comments

@stippi
Copy link

stippi commented Nov 25, 2015

When parsing content that is not RTF, and when the content by chance contains no '{' characters, the low level parser will keep adding all chars to its character sequence cache. In the end, no hook function of the listener will be called and it looks the same to the upper layers as if an empty but otherwise valid RTF document was parsed. Any suggestions on how to best fix this? I can see multiple ways to approach this.

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

No branches or pull requests

1 participant