tomd outputs Unicode characters as HTML numeric entities (e.g. ’ for right single quote, • for bullet, – for en-dash) instead of direct Unicode. Found in 35 of 38 papers, 3,895 total occurrences.
This makes the markdown harder to read in plain text and breaks substring matching for tools that search the output.
Fix: apply html.unescape() (Python stdlib) to the output before writing, or emit Unicode directly during conversion.
Full evaluation report: https://github.com/cppalliance/paperlint-eval/blob/main/tomd-eval/report.md (see Check 1c).
tomd outputs Unicode characters as HTML numeric entities (e.g.
’for right single quote,•for bullet,–for en-dash) instead of direct Unicode. Found in 35 of 38 papers, 3,895 total occurrences.This makes the markdown harder to read in plain text and breaks substring matching for tools that search the output.
Fix: apply
html.unescape()(Python stdlib) to the output before writing, or emit Unicode directly during conversion.Full evaluation report: https://github.com/cppalliance/paperlint-eval/blob/main/tomd-eval/report.md (see Check 1c).