Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: pozz Newsgroups: comp.lang.c Subject: Re: Simple string conversion from UCS2 to ISO8859-1 Date: Tue, 25 Feb 2025 22:50:49 +0100 Organization: A noiseless patient Spider Lines: 10 Message-ID: References: <87bjuvm68v.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 25 Feb 2025 22:51:43 +0100 (CET) Injection-Info: dont-email.me; posting-host="19024daff0e4a9951ae4d1c7345614cc"; logging-data="2308338"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18KjbHxvcQiwhhzT9N8VHX9t1BHgfONVbY=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:/wkWb8nkHDKUgjEYhNqxqV0QUp8= In-Reply-To: Content-Language: it Bytes: 1709 Il 25/02/2025 21:31, Lawrence D'Oliveiro ha scritto: > On Tue, 25 Feb 2025 15:53:23 +0100, pozz wrote: > >> ... the standard says UCS2 > > Does it mention anything about the surrogates ranges (0xD800 .. 0xDFFF)? > In order for it to be strict UCS-2, they would have to be forbidden. If > they are allowed, then that makes it UTF-16. I'm sorry, but I don't know and I never studied these details.