Skip to content

HTML Symbols not correctly parsed in 1.16? TexMath / HTML issue!? #2734

Closed
Tinkerer- opened this Issue · 5 comments

3 participants

@Tinkerer-

Since I've upgraded to pandoc 1.16 I have an issue with HTML characters. For example, &euml should become ë but instead pandoc decides to interpret it, and make it ë (&$euml;).

Example:

C:\Users\test>cat test.txt
This is a ë test
C:\Users\test>pandoc test.txt
<p>This is a &amp;euml; test</p>

From previous pandoc versions I would have expected the output to have been:

<p>This is a &euml; test</p>

I'm using pandoc 1.16.0.2, built by cabal.

Edit: when I'm using the Windows installed pandoc (also 1.16.0.2), pandoc behaves as expected!

Edit2: The difference between my Windows intalled pandoc ("good") and the cabal version ("bad"), as indicated by a diff of the version output is that the Windows installed version uses texmath 0.8.4.1, where the version compiled by Cabal uses texmath 0.8.4.2

@Tinkerer- Tinkerer- changed the title from HTML Symbols not correctly parsed in 1.16? to HTML Symbols not correctly parsed in 1.16? TexMath / HTML issue!
@Tinkerer- Tinkerer- changed the title from HTML Symbols not correctly parsed in 1.16? TexMath / HTML issue! to HTML Symbols not correctly parsed in 1.16? TexMath / HTML issue!?
@Jmuccigr

On a Mac here, pandoc 1.16.0.2. I get an ë for this:

This is a &euml; test.

EDIT: this was on the command line.

@jgm
Owner
@jgm jgm added a commit that closed this issue
@jgm Raise tagsoup lower bound to 0.13.7.
This fixes entity-related problems.

Closes #2734.
0180807
@jgm jgm closed this in 0180807
@jgm
Owner
@jgm
Owner
@Tinkerer-

Great, that fixed it! Thanks for the quick reply and for all the work on Pandoc in general!

@c-forster c-forster pushed a commit to c-forster/pandoc that referenced this issue
@jgm Raise tagsoup lower bound to 0.13.7.
This fixes entity-related problems.

Closes #2734.
49e0b2a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.