You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
967ece7: Started refactoring of reading text from document files (drafts, charters, etc.) in order to normalise on one way of doing this, and making that return unicode rather than undecoded bytes. This is the first step of two, in order to gauge the possible issues and report on discrepancies.
660c81c: Tweaked the file content read refactoring in 967ece7 to try latin-1 conversion if unicode doesn't work.
1f976da: Third part of document read refactoring, after 967ece7 and 660c81c. This replaces all usage of the non-unicode-aware get_document_content() function with unicode-aware Document.text() or Document.text_or_error() methods. This was triggered by yet another report of unicode content not being shown properly, and should fix all instances of document (drafts, agendas, minutes, etc.) display in the datatracker not handling unicode characters properly.
resolution_fixed
type_defect
| by hlflanagan@gmail.comSee section 3.2.3 of https://datatracker.ietf.org/doc/rfc8187/?include_text=1 as compared to https://www.rfc-editor.org/rfc/rfc8187.txt
Issue migrated from trac:2370 at 2022-03-04 05:57:35 +0000
The text was updated successfully, but these errors were encountered: