• What is the charset kludge of this message ???

    From Gunter Sandner@2:310/31.2 to Alle on Mon Aug 24 15:58:00 2020
    Hello together!

    Is the charset kludge of this message as intedend like this:
    CHRS: CP437 2
    ???


    Ciao
    Gunter

    --
    Some umlauts „”Ž™š

    --- OpenXP 5.0.45
    * Origin: Test-Origin (2:310/31.2)
  • From Michiel van der Vlist@2:280/5555 to Gunter Sandner on Mon Aug 24 16:23:12 2020
    Hello Gunter,

    On Monday August 24 2020 15:58, you wrote to Alle:

    @MSGID: 2:310/31.2@fidonet e7bcf7b0
    @PID: OpenXP/5.0.45 (Win32)
    @CHRS: CP437 2
    @TZUTC: 0200
    Hello together!

    Is the charset kludge of this message as intedend like this:
    CHRS: CP437 2
    ???

    Check.

    But why CP437? CP850, Latin-1 or UTF-8 are mostly used in Western Europe.

    Some umlauts äöüÄÖÜ

    Looks good.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: ZC1 certified techno-dick (2:280/5555)
  • From August Abolins@2:221/360 to Michiel van der Vlist on Tue Aug 25 21:17:18 2020
    On 24/08/2020 10:23 a.m., Michiel van der Vlist : Gunter Sandner wrote:


    Is the charset kludge of this message as intedend like this:
    CHRS: CP437 2
    ???

    Check.

    But why CP437? CP850, Latin-1 or UTF-8 are mostly used in Western Europe.

    Some umlauts ������

    Looks good.


    Cheers, Michiel

    Gunter's message arrived with CHRS: CP437 2, and the umlauts rendered perfectly here. But you quoted-reply with CHRS: CP1252 2, and that made the umlauts unreadable. :( Wouldn't it be best to reply with the same CHRS setting - especially if quoting the original 8-bit characters?

    --- TB(Stealth)/Win7
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Stas Mishchenkov@2:460/5858 to August Abolins on Tue Aug 25 21:58:32 2020
    Hi, August!

    25  ¢£ 20 21:17, August Abolins -> Michiel van der Vlist:

    @CHRS: UTF-8 4

    ------------^^^^^^^

    @TZUTC: 0300
    On 24/08/2020 10:23 a.m., Michiel van der Vlist : Gunter Sandner wrote:


    Is the charset kludge of this message as intedend like this:
    CHRS: CP437 2
    ???

    Check.

    But why CP437? CP850, Latin-1 or UTF-8 are mostly used in Western Europe.

    Some umlauts ������

    Looks good.

    Not at all. Michiel should have decoded correctly in 1252 if it answered by 1252.

    Have nice nights.
    Stas Mishchenkov.

    --- •®à®è¨© ᮡ¥á¥¤­¨ª ­¥ ⮫쪮 ¢­¨¬ â¥«ì­® á«ãè ¥â, ­® ¨ ¢®¢à¥¬ï ­ «¨¢ ¥â.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Michiel van der Vlist@2:280/5555 to August Abolins on Tue Aug 25 21:48:28 2020
    Hello August,

    On Tuesday August 25 2020 21:17, you wrote to me:

    But why CP437? CP850, Latin-1 or UTF-8 are mostly used in Western
    Europe.

    Some umlauts #ÿý#ÿý#ÿý#ÿý#ÿý#ÿý

    And now it does not look so good any more...

    Looks good.


    Cheers, Michiel

    Gunter's message arrived with CHRS: CP437 2, and the umlauts rendered perfectly here. But you quoted-reply with CHRS: CP1252 2, and that
    made the umlauts unreadable. :(

    Not here. TTMBOK they were correctly translated to CP1252 by my Golded.

    Wouldn't it be best to reply with the same CHRS setting - especially
    if quoting the original 8-bit characters?

    Why? Keep in mind that this is the test area. :-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: ZC1 certified techno-dick (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Stas Mishchenkov on Tue Aug 25 22:01:06 2020
    Hello Stas,

    On Tuesday August 25 2020 21:58, you wrote to August Abolins:

    Looks good.

    Not at all. Michiel should have decoded correctly in 1252 if it
    answered by 1252.

    What makes you say it was not correctly encoded?

    If you can not handle CP1252, try to treat it as Latin-1. CP1252 and Latin-1 are the same except for 0x80 - 0x9F.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: ZC1 certified techno-dick (2:280/5555)