/ LaTeXML Public
Two more wrongly encoded cases in LaTeXML.pm #949
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge.
While investigating #948 I spotted a broken bold 0 encoding when printing to stdout from latexmlc.
Turns out there were two cases that needed new patches
toString) to return differently encoded values -- since exactly one of our
toStringcalls isn't returning bytes. So I added an explicit check there.
Keeps feeling awkward... I still don't care enough to raise a larger stink about refactoring :> If I hit this once again I might.