Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #82871
| From | Paavo Helde <eesnimi@osa.pri.ee> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: Hello World in Russian |
| Date | 2022-01-30 14:26 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <st6058$ri2$1@dont-email.me> (permalink) |
| References | <i6GdnUGdpJgzJGn8nZ2dnUU7-KnNnZ2d@giganews.com> <st362k$ham$1@dont-email.me> <st3n3o$cn4$1@dont-email.me> <st5rkq$25sa3$1@gwaiyur.mb-net.net> |
30.01.2022 13:09 Marcel Mueller kirjutas: > > In HTTP LF w/o CR is not officially supported. ;-) Fixed encoding is better than random encoding. In HTTP headers one must indeed use CR LF. But the (text) files themselves are sent as HTTP bodies and there is zero reason to convert them to some other representation than they have on the server disk. > >> I predict the same will happen with backslashes as well, but this >> might take another 20 years. All the backslash madness in Windows is >> about to avoid typing a single space after the command name, it's >> about time to get rid of this. > > ntosknrl as well as its predecessor os2knrl can deal with '/' as path > separator for a long time too. Basically the same as with line ending: > they are tolerant. > But the command line parsers of may programs can not handle this since > the use '/' as escape character to denote an option. This makes the use > of forward slash unhandy. The slash can be still used as an option, there is no need to change that. One just needs to start to demand to separate options by spaces, something what a sane person has always done anyway, so that dir C:/B would list the file B in the root folder and dir C: /B would list all files in cwd of C: in bare format. > > And although UTF-8 is quite common nowadays it raises several problems > in certain situations. E.g. database fields with restricted length > accept different string lengths depending on the number of characters > with longer UTF-8 encoding used. No user will ever understand this. In real world UCS-2 is rarely used. Windows SDK, Java et al are using UTF-16, which has the same string length problem. And UCS-4 is definitely wasting space. > In Chinese and several other "non-ASCII" languages the UTF-8 encoding is > furthermore less compact that UCS2. I have heard this claim is not supported by actual data. In real usage Chinese is most often heavily interspersed with punctuation, numbers and English keywords so that there is little or no benefit in using UCS2 over UTF-8. > And well the fact that on Unix-like OSes file names are just binary > blobs rather than a string with a known encoding raises further problems. This has actually helped to standardize them all to UTF-8 in practice.
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Hello World in Russian Joseph Hesse <joeh@gmail.com> - 2022-01-29 05:51 +0200
Re: Hello World in Russian James Kuyper <jameskuyper@alumni.caltech.edu> - 2022-01-28 23:27 -0500
Re: Hello World in Russian Muttley@dastardlyhq.com - 2022-01-29 10:21 +0000
Re: Hello World in Russian Andrey Tarasevich <andreytarasevich@hotmail.com> - 2022-01-28 22:42 -0800
Re: Hello World in Russian David Brown <david.brown@hesbynett.no> - 2022-01-29 13:01 +0100
Re: Hello World in Russian "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2022-01-29 14:12 +0100
Re: Hello World in Russian David Brown <david.brown@hesbynett.no> - 2022-01-29 17:34 +0100
Re: Hello World in Russian James Kuyper <jameskuyper@alumni.caltech.edu> - 2022-01-30 14:17 -0500
Re: Hello World in Russian Andrey Tarasevich <andreytarasevich@hotmail.com> - 2022-01-30 20:17 -0800
Re: Hello World in Russian "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2022-01-29 11:48 +0100
Re: Hello World in Russian Paavo Helde <eesnimi@osa.pri.ee> - 2022-01-29 17:39 +0200
Re: Hello World in Russian "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2022-01-30 09:18 +0100
Re: Hello World in Russian Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-01-30 12:12 +0000
Re: Hello World in Russian "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2022-01-30 14:02 +0100
Re: Hello World in Russian Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-01-30 14:45 +0000
Re: Hello World in Russian "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2022-01-30 21:53 +0100
Re: Hello World in Russian Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-01-30 21:00 +0000
Re: Hello World in Russian James Kuyper <jameskuyper@alumni.caltech.edu> - 2022-01-30 14:02 -0500
Re: Hello World in Russian Muttley@dastardlyhq.com - 2022-01-31 10:23 +0000
Re: Hello World in Russian scott@slp53.sl.home (Scott Lurndal) - 2022-01-31 16:11 +0000
Re: Hello World in Russian Muttley@dastardlyhq.com - 2022-01-31 16:36 +0000
Re: Hello World in Russian Paavo Helde <eesnimi@osa.pri.ee> - 2022-01-31 20:20 +0200
Re: Hello World in Russian Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-01-31 16:12 +0000
Re: Hello World in Russian Muttley@dastardlyhq.com - 2022-01-31 16:39 +0000
Re: Hello World in Russian Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-01-31 23:47 +0000
Re: Hello World in Russian Manfred <noname@add.invalid> - 2022-01-31 16:45 +0100
Re: Hello World in Russian Andrey Tarasevich <andreytarasevich@hotmail.com> - 2022-01-31 10:10 -0800
Re: Hello World in Russian "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2022-01-31 19:25 +0100
Re: Hello World in Russian Marcel Mueller <news.5.maazl@spamgourmet.org> - 2022-01-30 12:09 +0100
Re: Hello World in Russian Paavo Helde <eesnimi@osa.pri.ee> - 2022-01-30 14:26 +0200
Re: Hello World in Russian Richard Damon <Richard@Damon-Family.org> - 2022-01-30 08:59 -0500
Re: Hello World in Russian Paavo Helde <eesnimi@osa.pri.ee> - 2022-01-30 18:21 +0200
Re: Hello World in Russian Richard Damon <Richard@Damon-Family.org> - 2022-01-30 12:56 -0500
Re: Hello World in Russian Vir Campestris <vir.campestris@invalid.invalid> - 2022-02-07 21:05 +0000
csiph-web