 | | Just testing character codes —Søren Bak
|
| | | æ<br> ø<br> ® (25 years ago, 28-Sep-99, to lugnet.off-topic.test)
|
| | | |
| | | | | Re: Just testing character codes —David Eaton
|
| | | | (...) but you'll notice using the numeric entity codes will change it when it gets displayed in html, not the named entity stuff! I.E: & # 1 6 3 ; when written without the spaces turns into: £ which is the symbol! (if you're reading this in the (...) (25 years ago, 28-Sep-99, to lugnet.off-topic.test)
|
| | | | |
| | | | | | Re: Just testing character codes —Todd Lehman
|
| | | | (...) Nope, there aren't any HTML entities (numeric or non-numeric) that are handled. By design, if you type '&', it's *always* converted to '&' by the web display interface, meaning that if you type 'æ' in your article, then the HTML (...) (25 years ago, 28-Sep-99, to lugnet.off-topic.test, lugnet.publish)
|
| | | | |
| | | | | | Re: Just testing character codes —David Eaton
|
| | | | (...) Hmm.... maybe it's something to do with how you're parsing web-input? I'm using the web interface to enter messages, and I'm typing: & # 1 6 3 ; (but without the spaces) and it comes out as a single character (the pound sign: "£") when I view (...) (25 years ago, 28-Sep-99, to lugnet.off-topic.test, lugnet.publish)
|
| | | | |
| | | | | | Re: Just testing character codes —Todd Lehman
|
| | | | (...) Thanks for reporting this. When I said earlier that it "didn't" convert stuff like that to raw form, I meant that I believed that didn't, because it shouldn't (it wasn't supposed have been). Alas, I did something dumb in a regex: In an (...) (25 years ago, 2-Oct-99, to lugnet.off-topic.test, lugnet.publish, lugnet.admin.general)
|
| | | | |
