Skip to content

parsing non-RTF content should throw exception #8

@stippi

Description

@stippi

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions