-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<u> for code point 128 (C1 control) causes exception #401
Comments
@julian.reschke@gmx.de changed component from |
@duerst@it.aoyama.ac.jp commented An error may be better than an exception. But one or the other is appropriate, because � is just an undefined control codepoint, and shouldn't turn up in an RFC at all. |
@julian.reschke@gmx.de commented AFAICT, it's not an undefined control point in Unicode - otherwise why does it show up in the Unicode database? But yes, if we want to exclude C1 controls, we need to clarify that in the documentation. |
@duerst@it.aoyama.ac.jp commented With "undefined control codepoint", I meant that it's a control, but it's not defined what kind of control. Some other controls have explanations (e.g. 009D = OPERATING SYSTEM COMMAND), see https://www.unicode.org/charts/PDF/U0080.pdf. U+0080 doesn't. On top of that, even for those controls that have explanations, this is just the ISO/IEC 6429:1992 interpretation, and Unicode doesn't force that. As for documentation, I hope there is already something about how to use non-ASCII characters carefully. Not using U+0080 can easily be seen as including that, there's no need for explicitly mentioning it. |
@julian.reschke@gmx.de commented Martin, the code fails in the same way for U+0092. |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed resolution from `` to |
@henrik@levkowetz.com commented Fixed in 30d209e: Added a default rendering (code point number) for code points without unicode code point names. Fixes issues #401 and #402. |
owner:henrik@levkowetz.com
resolution_fixed
type_defect
| by julian.reschke@gmx.deInput:
Output:
Issue migrated from trac:401 at 2022-02-05 12:48:15 +0000
The text was updated successfully, but these errors were encountered: