8000 Consume blanks after =encoding in pod reader by silby · Pull Request #10544 · jgm/pandoc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Consume blanks after =encoding in pod reader #10544

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

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Conversation

silby
Copy link
Contributor
@silby silby commented Jan 15, 2025

I neglected to properly consume empty lines after =encoding commands, which produced various incorrect parses depending on the content between there and the next command. If I had actually looked closely at the golden test I originally generated I might have noticed the problem!

Fixes #10537

I neglected to properly consume empty lines after =encoding commands,
which produced various incorrect parses depending on the content between
there and the next command. If I had actually looked closely at the
golden test I originally generated I might have noticed the problem!

Fixes jgm#10537
@jgm jgm merged commit 806dcb0 into jgm:main Jan 15, 2025
10 of 13 checks passed
@jgm
Copy link
Owner
jgm commented Jan 15, 2025

thanks!

massifrg pushed a commit to massifrg/pandoc that referenced this pull request May 7, 2025
The reader did not properly consume empty lines after =encoding commands,
which produced various incorrect parses depending on the content between
there and the next command.

Fixes jgm#10537
christopherkenny pushed a commit to christopherkenny/pandoc that referenced this pull request May 23, 2025
The reader did not properly consume empty lines after =encoding commands,
which produced various incorrect parses depending on the content between
there and the next command.

Fixes jgm#10537
christopherkenny pushed a commit to christopherkenny/pandoc that referenced this pull request May 23, 2025
The reader did not properly consume empty lines after =encoding commands,
which produced various incorrect parses depending on the content between
there and the next command.

Fixes jgm#10537
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

Successfully merging this pull request may close these issues.

POD reader: A directive immediately following an =encoding directive is treated as text
2 participants
0