From: already5chosen@yahoo.com   
      
   On Wed, 24 Dec 2025 01:41:30 -0600   
   Lynn McGuire  wrote:   
      
   > On 12/24/2025 12:22 AM, Keith Thompson wrote:   
   > > Lawrence D’Oliveiro  writes:     
   > >> On Tue, 18 Nov 2025 14:27:53 -0500, James Kuyper wrote:     
   > >>> Could you identify which document guarantees that every Unicode   
   > >>> locale contains "UTF-8"?     
   > >>   
   > >> How else would it work? Bytes have to be 8-bit.     
   > >    
   > > I can't figure out what point you're trying to make.   
   > >    
   > > Obviously bytes in C have to be *at least* 8 bits, but I don't see   
   > > the relevance.   
   > >    
   > > Take a look at the article to which you replied.  How does your   
   > > followup have anything to do with it?   
   > >    
   > > One of several points that you snipped is that locale names can   
   > > contain the string "utf8", not "UTF-8".     
   >    
   > Did C never work on the 6 bit machines such as the Univac 1108 (36   
   > bit) or the CDC 7600 (60 bit) ?   
   >    
   > Lynn   
   >    
      
   It depends on definition of the word C.   
   The requirement for CHAR_BIT > 7 was not present in K&R C. IIRC, it   
   first came in C90.   
      
   Also, what prevents C90 compiler from using 36-bit char on Univac 1108   
   and 60-bit bytes on CDC 7600? Methinks, it would be very reasonable.   
   By chance, that* was a choice made both by TI and by Analog for C   
   compilers of their word-addressable DSPs.   
      
      
   * - not specifically 36 or 60 bits, but CHAR_BIT = native word width.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)