Skip to content

Inconsistencies with specifications in parsing #2

@alion02

Description

@alion02

Right now, the library happily parses a5?!?!!?'''"""?!"?!?"!'? and TPS strings with Fs as top piece specifiers in them, which is technically incorrect.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions