From: noemail@basdxcqvbe.com   
      
   On Tue, 12 Oct 2021 18:49:32 GMT   
   scott@slp53.sl.home (Scott Lurndal) wrote:   
      
   > "muta...@gmail.com"  writes:   
   >   
   > >It will open a device, such as "COM1" on PDOS/386 or   
   > >"0x10001" on z/PDOS, as "r+b" and start reading characters   
   > >until it hits whatever endless-september uses as end-of-line   
   > >marker (they are the server, they can do whatever the fuck   
   > >they want - I'm pretty sure it is CRLF), and translates from   
   > >ASCII to the local character set.   
   >   
   > You might want to read through this first.   
   >   
   > https://datatracker.ietf.org/doc/html/rfc3977   
   >   
   >   "The character set for all NNTP commands is UTF-8 [RFC3629].   
   > Commands in NNTP MUST consist of a keyword, which MAY be followed by   
   > one or more arguments.  A CRLF pair MUST terminate all commands.   
   > Multiple commands MUST NOT be on the same line.  Unless otherwise   
   > noted elsewhere in this document, arguments SHOULD consist of   
   > printable US- ASCII characters.  Keywords and arguments MUST each be   
   > separated by one or more space or TAB characters.  Command lines MUST   
   > NOT exceed 512 octets, which includes the terminating CRLF pair.  The   
   > arguments MUST NOT exceed 497 octets.  A server MAY relax these   
   > limits for commands defined in an extension."   
   >   
      
   Does he really need to support UTF-8?  I rather doubt it, as NTTP works   
   correctly with Telnet which is ASCII.   
      
   Regarding the quote above, it would be rather interesting if there were   
   any commands that were UTF-8 which were not also ASCII ... i.e.,   
   non-ASCII UTF-8 commands.  So, what is the point of specifying the   
   larger charset of UTF-8 for the commands, but requiring the smaller   
   ASCII subset of UTF-8 for the arguments? ...  Bizarre.  Are there any   
   non-ASCII UTF-8 commands?  I don't happen to see any in the spec.   
   I.e., all NNTP commands appear to be ASCII.  Isn't it useless to support   
   UTF-8 commands if there are none? ...  So far, he only needs to support   
   ASCII, not UTF-8.   
      
   According to the remainder of the document, the NTTP RFC standard   
   requires use of the ASCII subset of UTF-8 and prohibits use of   
   non-ASCII UTF-8 for most things (quoted below).  There is another   
   exception to that (not quoted below), and it is the description of the   
   newsgroup, which may use non-ASCII UTF-8.  So, it seems there is only   
   one place, the newsgroup description, for which UTF-8 may actually be   
   used.  Except, if the warnings against using UTF-8 for other portions   
   of the NNTP protocol are to be actually believed and taken seriously,   
   "8-bit encodings SHOULD NOT be used because they are likely to cause   
   interoperability problems", then UTF-8 can't really be used for   
   newsgroup descriptions either for the same reason.  So far, he only   
   needs to support ASCII, not UTF-8.   
      
      
   "The names of headers MUST be in US-ASCII."   
      
   "Header values SHOULD use US-ASCII ..."   
      
   "At present, 8-bit encodings, (including UTF-8) SHOULD NOT be used   
   because they are likely to cause interoperability problems."   
      
   "Although this specification allows UTF-8 for newsgroup names, they   
   SHOULD be restricted to US-ASCII until a successor to RFC 1036   
   standardizes another approach. 8-bit encodings SHOULD NOT be used   
   because they are likely to cause interoperability problems."   
      
      
   --   
   Donald Trump: No oil rigs off the East coast.   
   Joe Biden: Windfarms off of all our coasts.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)