Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #395937
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Unicode... |
| Date | 2025-12-24 11:24 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <20251224112404.000015df@yahoo.com> (permalink) |
| References | (1 earlier) <10fgc9g$17a9o$1@dont-email.me> <10fihbp$7jbe$1@dont-email.me> <10ig0i8$qjm9$3@dont-email.me> <878qes8kll.fsf@example.invalid> <10ig5fa$rra5$1@dont-email.me> |
On Wed, 24 Dec 2025 01:41:30 -0600 Lynn McGuire <lynnmcguire5@gmail.com> wrote: > On 12/24/2025 12:22 AM, Keith Thompson wrote: > > Lawrence D’Oliveiro <ldo@nz.invalid> 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.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar
Re: Unicode... Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-24 06:17 +0000
Re: Unicode... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-12-23 22:22 -0800
Re: Unicode... Lynn McGuire <lynnmcguire5@gmail.com> - 2025-12-24 01:41 -0600
Re: Unicode... Michael S <already5chosen@yahoo.com> - 2025-12-24 11:24 +0200
Re: Unicode... scott@slp53.sl.home (Scott Lurndal) - 2025-12-24 17:11 +0000
Re: Unicode... Lynn McGuire <lynnmcguire5@gmail.com> - 2025-12-25 02:00 -0600
Re: Unicode... Michael S <already5chosen@yahoo.com> - 2025-12-25 10:49 +0200
Re: Unicode... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-12-25 10:22 +0100
Re: Unicode... scott@slp53.sl.home (Scott Lurndal) - 2025-12-26 16:28 +0000
Re: Unicode... Lynn McGuire <lynnmcguire5@gmail.com> - 2025-12-27 00:25 -0600
Re: Unicode... Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-29 23:34 +0000
Re: Unicode... Lynn McGuire <lynnmcguire5@gmail.com> - 2025-12-27 00:29 -0600
Re: Unicode... Michael S <already5chosen@yahoo.com> - 2025-12-27 18:08 +0200
Re: Unicode... Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-29 23:38 +0000
Re: Unicode... scott@slp53.sl.home (Scott Lurndal) - 2025-12-27 19:17 +0000
Re: Unicode... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-12-27 20:47 +0100
Re: Unicode... Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2025-12-27 20:03 +0000
Re: Unicode... Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2025-12-27 20:05 +0000
Re: Unicode... Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-29 23:39 +0000
Re: Unicode... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-12-27 22:43 +0100
Re: Unicode... James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-12-31 18:04 -0500
Re: Unicode... Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-31 23:11 +0000
Re: Unicode... James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-12-31 18:36 -0500
csiph-web