1. Forum
  2. Fidonet
  3. UTF-8

  • how can something that feels so right be so wrong?

    From Maurice Kinal@1:153/7001 to Konstantin Kuzov on Tue Feb 28 04:04:18 2017
    -={ 2017-02-28 04:04:18.287688264+00:00 }=-

    Hey Konstantin!

    If presented kludge doesn't match actual used codepage then
    writer of that message hasn't configured his editor right.

    Is this one any better? It makes absolutely no difference here other than this time the kludge and the encoding match ... minus the silly level thingy (^ACHRS: <identifier> <level>) which is '2' in this case.

    For the record my editor still ignores the CHRS kludge and only does ascii and utf-8. No kludge is required for either to work. What for?

    Life is good,
    Maurice

    ...
    --- GNU bash, version 4.4.12(1)-release (x86_64-atom-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Konstantin Kuzov@2:5019/40.1 to Maurice Kinal on Tue Feb 28 16:08:30 2017
    Greetings, Maurice!

    If presented kludge doesn't match actual used codepage then
    writer of that message hasn't configured his editor right.
    Is this one any better? It makes absolutely no difference here other
    than this time the kludge and the encoding match ...

    Yes, it is looking completely fine:

    .. У меня в штанах белка

    You can compare this yourself: https://fido.g0x.ru/?area://UTF-8?msgid=1:153/7001+58b4f6c2

    With this:
    https://fido.g0x.ru/?area://UTF-8?msgid=1:153/7001+58b4d4f3

    minus the silly level thingy (^ACHRS: <identifier> <level>) which
    is '2' in this case.

    Legacy level thing is there just for compatibility reasons. Modern editors could just ignore all trailing information after codepage.

    BTW, Michael's script which posts to this echo goes further. It appends space after the level for whatever reason.

    For the record my editor still ignores the CHRS kludge and only does
    ascii and utf-8. No kludge is required for either to work. What for?

    I had written about this in my previous messages, using only utf-8 and pretending that other codepages doesn't exist isn't a solution to anything. You can do this only because you are mainly using ascii and read ascii messages.

    --- Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
    * Origin: Via 2:5019/40 NNTP (GaNJaNET STaTi0N, Smolensk) (2:5019/40.1)
  • From Michiel van der Vlist@2:280/5555 to Konstantin Kuzov on Tue Feb 28 14:33:05 2017
    Hello Konstantin,

    On Tuesday February 28 2017 16:08, you wrote to Maurice Kinal:

    BTW, Michael's script which posts to this echo goes further. It
    appends space after the level for whatever reason.

    Thank you for pointing that out. While I would say that decent sofwtare should not have problems with it under the "be strict when writing, but forgiving when reading", you have a point in that there should be no trailing space. If all goes well, there will be no trailing space next Friday.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Blóf Tønón (2:280/5555)