Loading ...
Sorry, an error occurred while loading the content.

Re: [sgf-std] question about encoding

Expand Messages
  • Arno Hollosi
    ... This is actually not a WinIgc coding, but a quoted-printable encoding used in emails. It looks like your email program (or some other program) didn t
    Message 1 of 2 , Jan 30, 2003
    • 0 Attachment
      > (;GM[1]FF[4]DT[2003-01-22]PB[tontonlolo]PW[ken008]BR[ 2k*]WR[ =
      > 1k*]HA[0]KM[0.5]SZ[19]AP[WinIGC:1.04]C[I say: =
      > hi];B[pp]BL[27];W[dd]WL[58];B[cp]BL[22];W[pd]WL[55];B[iq]BL[19];W[dm]WL[5=
      > 3];B[ep]BL[16];W[dj]WL[52];B[qf]BL[13];W[qn]WL[50];B[ql]BL[599];W[qq]WL[4=
      >
      > WinIgc seems to use some encoding for line ending and other special
      > chars, but it isn't specified
      > on the header. How must a good sgf reader handle this case ?

      This is actually not a WinIgc coding, but a quoted-printable encoding
      used in emails. It looks like your email program (or some other program)
      didn't handle the SGF correctly and you got the "raw" email text of the
      SGF encoded in quoted-printable.

      More information see RFC1521 at e.g.
      http://www.freesoft.org/CIE/RFC/1521/6.htm

      Speaking from my experience such SGF files appear every once in a while
      (usually happens while forwarding emails, posting to newsgroups, or
      saving the email instead of the SGF attachment).

      /Arno
    Your message has been successfully submitted and would be delivered to recipients shortly.