#3739 Potential unicode issue in markdown processing
Opened a year ago by tibbs. Modified 6 months ago

This pull request: https://pagure.io/packaging-committee/pull-request/799 introduced an odd apostrophe character at https://pagure.io/packaging-committee/pull-request/799#_1,37

It looks OK in the diff view, but when rendered as the project's overview page, it rendered (on my browser, at least) as a combination of mojibake and tofu. That should be visible at https://pagure.io/packaging-committee/blob/f7a3b1049db60d2d429422b8f5241f11e0c1a658/f/README.md

Firefox won't even let me choose any text encoding besides Unicode so I honestly have no idea how it was encoded, but it does seem as if the encoding was changed somehow between the diff view of the PR and the the rendered overview page.


I also noticed the same tofu sequence on https://docs.pagure.org/pagure/usage/markdown.html

I guess either there's a more general oddity with single quotes, or the source of that docs page also uses the same odd single quote character as the above PR.

Edit: Also note how the ellipses are rendered on that docs page (search for "others").

I have a case where long dash is rendered incorrectly. This README (under Related tools) shows â instead of .

I have a case where long dash is rendered incorrectly. This README (under Related tools) shows â instead of –.

Yes as you reported in https://pagure.io/pagure/issue/2428.

I am guessing the web frontend is just corrupting unicode to ascii...

Login to comment on this ticket.

Metadata