Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #401962
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Subject | Re: Support of Unicode characters in various places (was Re: c needs this sign) |
| Newsgroups | comp.lang.c |
| References | (8 earlier) <117v6hh$1ls9s$3@dont-email.me> <117v8ut$2bom8$2@kst.eternal-september.org> <A%FoS.1100$eHD8.109@fx38.iad> <117vc3m$2d806$1@kst.eternal-september.org> <1180ivh$2peag$1@dont-email.me> |
| Message-ID | <q_VoS.25334$FT1.22540@fx10.iad> (permalink) |
| Organization | UsenetServer - www.usenetserver.com |
| Date | 2026-09-11 16:28 +0000 |
bart <bc@freeuk.com> writes:
>On 10/09/2026 23:48, Keith Thompson wrote:
>> scott@slp53.sl.home (Scott Lurndal) writes:
>>> Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
>>>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>>>> [...]
>>>>> I've yet to hear that anyone actually used trigraphs. - Weren't they,
>>>>> because of that, even removed from recent "C" (or C++) standards?
>>>>
>>>> I've used trigraphs, but only in deliberately obfuscated code. I'm not
>>>> aware of any code that uses trigraphs because they're useful.
>>>>
>>>> Part of the point of trigraphs was to enable the use of C on
>>>> EBCDIC-based systems that don't have all the characters C requires,
>>>> including '{' and '}'. (There are EBCDIC code pages that do have those
>>>> characters, but they're outside the "invariant subset".)
>>>
>>> The other part may have been for those still using ASR-33 teletypes
>>> which were missing several characters required in C, including
>>> curly braces, vertical bar, backtick and tilde.
>
>
>(Where does C require backtick?)
>
>> Apparently the ASR-33 generated 7-bit ASCII, but didn't support
>> lowercase letters.
>>
>> The stty command had (and still has, at least in some versions)
>> options to map uppercase characters to lowercase, and to generate
>> uppercase with a '\' prefix, so Hello would be entered as \HELLO.
>> I suppose a C programmer would likely be using a line editor like
>> "ed" to edit code, which would be subject to the current tty
>> settings, and since C is mostly lowercase the translation would
>> make it tolerable.
>>
>> I wonder how many ASR-33s were still in use for C development by
>> the time <iso646.h> and trigraphs were introduced in 1995.
>>
>
>I used ASR33s and other terminals with various limitations from 1976.
>The first computer I /made/ used 6-bit (I think, ASCII codes 32 to 95
>offset to be 0 to 63, so upper-case only), in 1981.
>
>How did people even write C on such systems?
Did you read what you replied to? The Unix systems that most
C programmers were using had a terminal driver that would
translate upper-case to lower-case automatically, if so
configured. The stty(1) command was used to change terminal
driver confgurations. The login(1) command would automatically
set that flag if the username was typed in upper-case.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
c needs this sign fir <profesor.fir@gmail.com> - 2026-09-07 15:53 +0200
Re: c needs this sign David LaRue <huey.dll@tampabay.rr.com> - 2026-09-07 19:21 +0000
Re: c needs this sign Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-08 01:10 +0200
Re: c needs this sign Dan Purgert <dan@djph.net> - 2026-09-07 23:13 +0000
Re: c needs this sign Lane W <cactus_DAC@yahoo.com> - 2026-09-07 17:26 -0600
Re: c needs this sign David Brown <david.brown@hesbynett.no> - 2026-09-08 10:40 +0200
Re: c needs this sign Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 10:49 +0200
Re: c needs this sign David Brown <david.brown@hesbynett.no> - 2026-09-09 13:21 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-09 13:33 +0200
Support of Unicode characters in various places (was Re: c needs this sign) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 21:37 +0200
Re: Support of Unicode characters in various places (was Re: c needs this sign) David Brown <david.brown@hesbynett.no> - 2026-09-10 09:01 +0200
Re: Support of Unicode characters in various places (was Re: c needs this sign) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-10 23:13 +0200
Re: Support of Unicode characters in various places (was Re: c needs this sign) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-10 14:54 -0700
Re: Support of Unicode characters in various places (was Re: c needs this sign) scott@slp53.sl.home (Scott Lurndal) - 2026-09-10 22:17 +0000
Re: Support of Unicode characters in various places (was Re: c needs this sign) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-10 15:48 -0700
Re: Support of Unicode characters in various places (was Re: c needs this sign) bart <bc@freeuk.com> - 2026-09-11 10:51 +0100
Re: Support of Unicode characters in various places (was Re: c needs this sign) David Brown <david.brown@hesbynett.no> - 2026-09-11 12:49 +0200
Re: Support of Unicode characters in various places (was Re: c needs this sign) scott@slp53.sl.home (Scott Lurndal) - 2026-09-11 16:28 +0000
Re: Support of Unicode characters in various places (was Re: c needs this sign) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-11 02:03 +0200
Re: Support of Unicode characters in various places (was Re: c needs this sign) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-10 17:13 -0700
Re: Support of Unicode characters in various places (was Re: c needs this sign) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-11 02:24 +0200
Re: Support of Unicode characters in various places (was Re: c needs this sign) David Brown <david.brown@hesbynett.no> - 2026-09-11 09:42 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-09 23:59 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 00:04 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 00:16 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 00:30 +0200
Re: c needs this sign bart <bc@freeuk.com> - 2026-09-09 23:44 +0100
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 00:55 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 01:09 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 01:21 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 01:36 +0200
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-10 01:45 +0200
Re: c needs this sign Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-15 07:23 +0000
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-08 11:56 +0200
Re: c needs this sign bart <bc@freeuk.com> - 2026-09-08 11:14 +0100
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-08 12:28 +0200
Re: c needs this sign Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-09-08 03:54 -0700
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-08 13:13 +0200
= vs. == (again!) (Was: c needs this sign) gazelle@shell.xmission.com (Kenny McCormack) - 2026-09-08 14:39 +0000
Re: = vs. == (again!) (Was: c needs this sign) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-10-14 23:36 -0700
Re: c needs this sign Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-09-09 11:13 +0200
Re: c needs this sign Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-09 00:29 +0000
Re: c needs this sign "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-09-10 13:42 -0700
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-08 15:12 +0200
Re: c needs this sign Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-08 03:33 +0000
Re: c needs this sign fir <profesor.fir@gmail.com> - 2026-09-08 12:02 +0200
Re: c needs this sign Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-09 00:27 +0000
csiph-web