Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Dave Froble <davef@tsoft-inc.com>
Newsgroups: comp.os.vms
Subject: Re: C and C++, promotion, stabilization, migrationFor embedded
Date: Sun, 25 Aug 2024 11:45:13 -0400
Organization: A noiseless patient Spider
Lines: 54
Message-ID: <vafji9$1ugno$4@dont-email.me>
References: <va22kr$3ce14$2@dont-email.me> <vaaa1j$v7rp$1@dont-email.me>
 <vab69p$1356i$1@dont-email.me> <vae3v7$1nt1p$1@dont-email.me>
 <vae5hg$1j523$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 25 Aug 2024 17:45:14 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="604ae1de513023e840ca2c0e3def866c";
	logging-data="2048760"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+vLQ9BD5FP5N/wOlMBob7Czc4geSB6l/4="
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
Cancel-Lock: sha1:qcc5Ej1C9lAbjUZN2T4xj7BRZF0=
In-Reply-To: <vae5hg$1j523$2@dont-email.me>
Bytes: 3363

On 8/24/2024 10:39 PM, Arne Vajhøj wrote:
> On 8/24/2024 10:12 PM, Stephen Hoffman wrote:
>> On 2024-08-23 23:34:18 +0000, Arne Vajhøj said:
>>> On 8/23/2024 11:32 AM, Stephen Hoffman wrote:
>>>> OpenVMS has ~no concept of languages, either. Yeah, the C abd C++ I18N
>>>> giblets, Java and its own little world, maybe using the existing and older
>>>> ICU or maybe you ported a newer ICU, and the deprecated Terminal Fallback
>>>> Facility (TFF) and National (Replacement)  Character Set (NCS) giblets,
>>>> sure. All of which make things more interesting for apps that want or need
>>>> to deal with the UTF-8 and post-ASCII world.
>>>
>>> Regarding UTF-8 support, then  my take is that:
>>>
>>> UTF-8 in file names, in usernames, in logicals, in identifiers and in
>>> programs/scripts: not really needed.
>>
>> UTF-8 filenames — poorly documented — already exists and was necessary for a
>> key app or two, though the rendering is ugly.
>>
>> Working on a system that supports UTF-8 ~everywhere including within the shell
>> and within various languages and apps makes things easier.
>>
>> Systems that don't provide that support mean more work. It's feasible, but
>> it's work.  Or it gets ignored, or implemented elsewhere.
>
> I fully get the need for UTF-8 support in anything data related.
> For console/HTML/XML/JSON/YAML input/output then there is a functional
> need for UTF-8 support.
>
> But for all the implementation then I believe in keeping things
> English and ASCII.
>
> Filenames, database tablenames and fieldnames, program/script
> identifiers, VMS logicals etc.. Even comments should be
> in English (even though they may to use a little UTF-8 to
> reference various things).
>
> That is the safe choice for it being displayed correctly
> everywhere and being understandable by all future maintenance
> programmers.
>
> Arne
>

+1

Why buy more trouble, when you already have more than enough?

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486