Conversation
Needs to be treated as binary for xref to remain valid
|
BTW the PDFs added are fully functional PDFs that will work in products such as Adobe Acrobat Reader. Likely just need to rename with a |
|
Failure of linelint is against the 2 different sample functional PDF files in |
Added EOL to last line of PDF to pass linelint CI check used by Rouge. This is not required by real PDF files.
|
I'm sorry, @ronaldtse. I'm no longer a maintainer on this project. |
|
Apologies for unnecessarily tagging you @pyrmont , thank you for the quick response! |
Co-authored-by: Jeanine Adkisson <jeanine.adkisson@gmail.com>
Co-authored-by: Jeanine Adkisson <jeanine.adkisson@gmail.com>
Co-authored-by: Jeanine Adkisson <jeanine.adkisson@gmail.com>
Please accept this lexer for PDF syntax (a.k.a. "COS syntax").
PDF (Portable Document Format) is an object-based declarative page description language that, in reality, is a random access, binary (non-text) format. It is formally defined by ISO 32000-2:2020 and corrected by errata (please do not refer to outdated legacy Adobe documentation!). However, with care text-centric PDFs (full or portions) can be created such as might be used in documentation. This token-based, forward lexing lexer is not intended to be used with binary real-world PDFs as that is not how real PDFs need to be lexed (this will also likely generate Ruby UTF-8 errors anyway!).
We wish to leverage this Rouge PDF parser upstream in current and future PDF ISO standards and specifications based on AsciiDoc via Metanorma for use with the many code fragment examples in the documentation.