Results 1 to 3 of 3

Thread: /death™

  1. #1
    Community Member GlassCannon's Avatar
    Join Date
    Jul 2006
    Posts
    448

    Default /death™

    I like playing with chat Alt codes. Right now the only ones that work are ™ ® © ? and maybe some special alphabetics with stuff over the top. (that 4th one is a check mark)

    I'm not sure why the fun ones have been castrated of compatibility with friendly, playful chat.

    I'm talking about symbols like the heart, music signs and other fun things you find in various Unicode Charts

    Then again I haven't had my ? today so my ? is a bit low. I ? ? so much...

    I don't think I have time to log in and ? or ? or ? (questing takes time), sadly.

    I ?? you all the best.


    Edit: Wow, the window showed them but the forums changed all of them to ?'s like an angry, disgruntled boss who hates smiling and sunshine and anything happy.
    Last edited by GlassCannon; 06-14-2016 at 04:33 PM. Reason: Oh my... the website even hates special characters...

  2. #2
    Community Member Greantun's Avatar
    Join Date
    Apr 2013
    Posts
    718

    Default

    Quote Originally Posted by GlassCannon View Post
    I like playing with chat Alt codes. Right now the only ones that work are ™ ® © ? and maybe some special alphabetics with stuff over the top. (that 4th one is a check mark)

    I'm not sure why the fun ones have been castrated of compatibility with friendly, playful chat.

    I'm talking about symbols like the heart, music signs and other fun things you find in various Unicode Charts

    Then again I haven't had my ? today so my ? is a bit low. I ? ? so much...

    I don't think I have time to log in and ? or ? or ? (questing takes time), sadly.

    I ?? you all the best.


    Edit: Wow, the window showed them but the forums changed all of them to ?'s like an angry, disgruntled boss who hates smiling and sunshine and anything happy.
    More than likely the forum doesn't support storing Unicode, only extended ASCII. I know that if you use Unicode and store it in ascii, it will come out with ? characters for the Unicode ones.

  3. #3
    Community Member DYWYPI's Avatar
    Join Date
    Feb 2016
    Posts
    0

    Default

    Hmm, for the forum's symbol output quandary; it looks like the DDO forums perhaps has different parameters; such as the database encoding, maybe it's the 'editor textarea' config. when it "saves", or a 'mismatch' with encoding. Because what it's doing upon [Preview]; is outputting the 'Replacement character' and 'Asterisk' for some characters thus suggesting a encoding mismatch. Alas my mind has faded on such subjects...

    Albeit let's test a widely accepted UTF-8 miscellaneous Symbol; (U+2660). Thus to try answer that question; for these DDO forums to wrongly output: "??*" (U+2660). Using the decimal Numeric Character References (NCR) "♠" for the 'black spade suit' glyph (was required to be typed for Preview to work).

    Getting back to that question, NCR is the preferable choice over the entities, entities are limited to a subset of Unicode characters, NCR can specify any character and theoretically Hexadecimal has less ambiguity - the forum doesn't seem to accept Hex, which is mostly a nuisance. The forum wasn't configured by me so I don't know what setting and Language packs they've used in the [DDO] vBulletin templates. It appears to be parsing some NCRs but not appearing to parse Character Entity References (Preview only!).

    Update: Furthermore the flipping "Preview" also differs to the actual Saved output! Argh! The preview converts some but not the others; the 'save' converts them all so it looketh like in these particular forums - suggesting more than just the text editor but actual storage is lacking some support also. :-/
    Last edited by DYWYPI; 06-15-2016 at 08:34 AM. Reason: Unpredicted forum parsing behaviour. Gnome With the Wand of Death.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload