Wedge
Public area => Bug reports => The Pub => Test board => Topic started by: Arantor on April 25th, 2012, 07:33 PM
-
80 € U+20AC € Euro reserved control
82 ‚ U+201A ‚ Low-"9" opening quotation mark Break Permitted Here
83 ƒ U+0192 ƒ1 or ƒ Florin/script f/folder No Break Here
84 „ U+201E „ Low-"99" opening quotation mark Index
85 … U+2026 … Ellipsis Next Line
86 † U+2020 † Single dagger Start of Selected Area
87 ‡ U+2021 ‡ Double dagger End of Selected Area
88 ˆ U+02C6 ˆ Circumflex ^ accent (combining?) Character Tabulation Set
89 ‰ U+2030 ‰ o/oo per mille Character Tabulation with Justification
8A Š U+0160 Š1 or Š S + caron accent Line Tabulation Set
8B ‹ U+2039 ‹ Single left angle quote < (guillemet) Partial Line Down
8C Œ U+0152 Œ OE ligature Partial Line Up
8E Ž U+017D Ž2 or Ž Z + caron accent Single Shift Two
91 ‘ U+2018 ‘ "6" opening quotation mark Private Use One
92 ’ U+2019 ’ "9" closing quotation mark/apostrophe Private Use Two
93 “ U+201C “ "66" opening quotation mark Set Transmit State
94 ” U+201D ” "99" closing quotation mark Cancel Character
95 • U+2022 • Solid bullet Message Waiting
96 – U+2013 – En-dash Start of Guarded Area
97 — U+2014 — Em-dash End of Guarded Area
98 ˜ U+02DC ˜ Tilde ~ accent (combining?) Start of String
99 ™ U+2122 ™ Trademark TM reserved control
9A š U+0161 š1 or š s + caron accent Single Character Introducer
9B › U+203A › Single right angle quote > (guillemet) Control Sequence Introducer
9C œ U+0153 œ oe ligature String Terminator
9E ž U+017E ž2 or & #382; z + caron accent Privacy Message
9F Ÿ U+0178 Ÿ Y + diaeresis/umlaute accent Application Program Command
-
Works for me...?
-
Apparently it's an SMF bug.
Also of note is that the fourth column (the second instance of characters) were all entities before I posted, so entities are not treated as literals but converted to entities. This has all sorts of interesting consequences.
-
I think it's always been the case - and I occasionally used it to enter entities that I didn't know the Alt code for.. :P
-
Question, then, should the entity be left as a literal, or be treated as though the entity should be converted to its character equivalent?
This may have other concerns, e.g. nobbc or even the controversial 39 entity.
-
I'd tend not to change anything, because it's not *too* broken... And the 39 can always be changed later on (with a simple DB query...), so I'm not too worried about that one for now...