• (nodebb)

    I wouldn't be surprised to find out that the sender of the email didn't declare the encoding correctly. In such a case, what exactly is Outlook (or any other mail reader) supposed to do?

  • doesn't matter (unregistered) in reply to Steve_The_Cynic

    It is an Outlook internal error message that it wasn't able to open a folder. Therefore MS isn't using the right encoding for their own error messages.

  • RLB (unregistered) in reply to Steve_The_Cynic

    I wouldn't be surprised to find out that the sender of the email didn't declare the encoding correctly. AFAICT, it's not an email which isn't being displayed, but an entire email folder. The error message is Outlook's, not part of a mail.

  • P. Wolff (unregistered)

    if (trim != null || trip == null) {trip.additionalComment.display();}

  • Foo AKA Fooo (unregistered)

    1700 is the 17th century, not the 18th!

    Sorry, couldn't miss this opportunity to nitpick the other way than usual. :)

  • Just a Dev (unregistered) in reply to Foo AKA Fooo

    haha, technically you are right. The 17th century comprises this period of time. January 1, 1601 – December 31, 1700

  • scriptninja (github)

    Am I mistaken in thinking that outlook display could also occur with the correct encoding but with the relevant system font not containing the appropriate glyph?

    I mean I am admittedly more inclined to think the display assumes CP1252 and the message is in something reasonable. I just thought the above could also produce the same symptom.

  • Sou Eu (unregistered)

    The Google Maps error actually kind of makes sense. The owner of the site is redirected to their Google control panel where they can verify a correct API key or authorize more calls to the API (stupid Google for raising their prices).

  • Peter of the Norse (unregistered) in reply to scriptninja

    That looks like Ariel. The version of Arial that ships with every version of Windows since XP is fully Unicode compliant. There’s no way it missed ü. ,

  • (nodebb) in reply to doesn't matter

    Well, maybe the text above the picture could have contained a better explanation.

  • (nodebb) in reply to scriptninja

    Am I mistaken in thinking that outlook display could also occur with the correct encoding but with the relevant system font not containing the appropriate glyph?

    That usually produces little boxes (on the hillside, little boxes made of ticky-tacky? Sorry).

  • Vilx- (unregistered)

    That Google Maps error is not really that noteworthy. A lot of websites have this, and the cause is simple - it used to be that you could just embed Google Maps wherever you wanted without much fanfare. However after a while Google decided that they don't like it after all and now you need an API key to do it. Perhaps even a subscription fee, although I'm not sure about that. Older websites that still haven't upgraded their code with the newer version of Google Maps and the API key now show this error. It's quite common.

  • anonymous (unregistered) in reply to Vilx-

    I've mostly seen it happen with newer but neglected/abandoned websites where the API key has presumably expired and/or payment wasn't received to renew it.

  • Lőrinczy, Zsigmond (github)

    Regarding Outlook: you get this subtitue-character when the encoding is stated to be UTF-8, but actually it is some single-byte encoding like win-1252 or iso-8859-1

  • (nodebb)

    Regarding Outlook: you get this subtitue-character when the encoding is stated to be UTF-8, but actually it is some single-byte encoding like win-1252 or iso-8859-1

    That would be convincing except that win-1252 and iso-8859-1 are both multi-byte (er, variable-width) encodings, just not the same as UTF-8.

  • Foo AKA Fooo (unregistered) in reply to Steve_The_Cynic

    Nope, they're 8-bit, i.e. single-byte encodings. (Whereas ASCII is 7-bit, which is also single-byte.)

    But as others have said, none of this matters since this is a message from Outlook itself, and it should know its own encoding.

  • Officer Johnny Holzkopf (unregistered) in reply to Steve_The_Cynic

    Umlauts and Eszett (as well as many other "non-US English symbols") are not part of the regulatr 7-bit ASCII, but are in 8-bit ASCII, which is a single byte encoding. In ISO-8859-1 (western europe): ä=E4h ö=F6h ü=FCh Ä=C4h, Ö=D6h, Ü=DCh, ß=DFh. On the other hand, UTF-8 requires 2 bytes for each symbol: ä=C3hA4h, ö=C3hB6h, ü=C3hBCh, Ä=C3h84h, Ö=C3h96h, Ü=C3h9Ch, ß=C3h9Fh.

  • (nodebb) in reply to Foo AKA Fooo
    1700 is the 17th century, not the 18th!

    Agree, and an xkcd reference: https://xkcd.com/2249/

  • Deal Emma (unregistered)

    As a speaker of the German language, I find the error message given by Outlook is actually more infuriating than it displaying one tofu character: "The folder cannot be displayed. The folder storage location [sic!] could not be accessed by Microsoft Outlook. The element could not be ?pened. Please try again."

    • They're basically saying variations of the same thing three times.
    • There is no button to "Try again".

Leave a comment on “Variable Trust”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article