XPost: news.software.readers   
   From: oneingray@gmail.com   
      
   >>>>> Barry Margolin  writes:   
   >>>>> Ivan Shmakov  wrote:   
      
   [...]   
      
    >> --cut: urn:ietf:rfc:5537 --   
      
    >> Transports for Netnews articles MUST treat news articles as   
    >> uninterpreted sequences of octets, excluding the values %d00 (which   
    >> may not occur in Netnews articles), %d13, and %d10 (which MUST only   
    >> appear in Netnews articles as a pair in that order and which,   
    >> together, denote a line separator).  [...]   
      
    >> --cut: urn:ietf:rfc:5537 --   
      
    > Those restrictions make it practically impossible to transmit raw   
    > binary files without encoding.  While a submission agent could scan   
    > the file to see if it contains any of these bytes, and send it   
    > unencoded if not, I'd find such an implementation very surprising.   
      
   	So would I.   
      
   	My point was, however, that it doesn't make \xFF impossible, or   
   	even unlikely to happen, within an article's body.  Especially   
   	should one consider a non-English newsgroup.   
      
    >>> There shouldn't be any \xFF octets.   
      
    >> Specifically, while UTF-8 doesn't seem to use \xFF, ISO-8859-1   
    >> assigns it for LATIN SMALL LETTER Y WITH DIAERESIS, windows-1251 for   
    >> CYRILLIC SMALL LETTER YA, and so on.   
      
   	Consider, e. g.:   
      
   news:MSGID_2=3A5030=2F830.57=40fidonet_514db775@fidonet.org   
   news:58bet9-oeb.ln1@news.russian-z1.org   
      
   --   
   FSF associate member #7257	http://hfday.org/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)