1. Forum
  2. Usenet
  3. UK.COMP.SYS.MAC

  • Re: UTF-8?B?UmU6IEFwcGxl4oCZcyBsb25nZXZpdHkgYnkgZGVzaWdu?=

    From TimS@21:1/5 to All on Fri Jul 5 20:43:59 2024
    On 5 Jul 2024 at 21:15:45 BST, "J. J. Lodder" <J. J. Lodder> wrote:

    Snit <brock.mcnuggets@gmail.com> wrote:

    You have done it again.
    And again: Subject: headers should be in god's own ASCII.
    (and they should -not- be changed without a very good reason)

    That whole text string *is* ASCII. Further, I refer you to RFC 2045 and RFC 2047, which, amongst other things, describe the use of character sets other than ASCII, and also how encoded words work, of which this subject header is
    an example. These RFCs, by the way, were published in 1996. Where have you ben since then? Hiding under a bridge?

    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From TimS@21:1/5 to All on Sun Jul 7 10:03:37 2024
    On 7 Jul 2024 at 10:50:54 BST, "J. J. Lodder" <J. J. Lodder> wrote:

    TimS <tim@streater.me.uk> wrote:

    On 5 Jul 2024 at 21:15:45 BST, "J. J. Lodder" <J. J. Lodder> wrote:

    Snit <brock.mcnuggets@gmail.com> wrote:

    You have done it again.
    And again: Subject: headers should be in god's own ASCII.
    (and they should -not- be changed without a very good reason)

    That whole text string *is* ASCII.

    Yes, but not god's own.

    Further, I refer you to RFC 2045 and RFC
    2047, which, amongst other things, describe the use of character sets other >> than ASCII, and also how encoded words work, of which this subject header is >> an example.

    All that works fine for body material, (if not quoted)
    but it fails regularly for headers.

    Only becaus it didn't seem to occur to the authors of those applications to cater for encoded words. And doing that is very simple.

    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From J. J. Lodder@21:1/5 to TimS on Sun Jul 7 11:50:54 2024
    TimS <tim@streater.me.uk> wrote:

    On 5 Jul 2024 at 21:15:45 BST, "J. J. Lodder" <J. J. Lodder> wrote:

    Snit <brock.mcnuggets@gmail.com> wrote:

    You have done it again.
    And again: Subject: headers should be in god's own ASCII.
    (and they should -not- be changed without a very good reason)

    That whole text string *is* ASCII.

    Yes, but not god's own.

    Further, I refer you to RFC 2045 and RFC
    2047, which, amongst other things, describe the use of character sets other than ASCII, and also how encoded words work, of which this subject header is an example.

    All that works fine for body material, (if not quoted)
    but it fails regularly for headers.

    These RFCs, by the way, were published in 1996. Where have you ben
    since then? Hiding under a bridge?

    It is just that I'm not blind to reality, like you seem to be.
    Once again, headers should always be in plain ASCII,

    Jan

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)