[TUHS] Re: Canonical Historic Approach to iconv(1)

[TUHS] Re: Canonical Historic Approach to iconv(1)

[Rudi Blom]

[-- Attachment #1: Type: text/plain, Size: 200 bytes --]

The "man 1 iconv" page on both HP-UX 11i 11.23 (Aug 2003) and 11.31 (Feb
2007) remark that iconv was developed by HP.

Cheers,
uncle rubl

-- 
The more I learn the better I understand I know nothing.

[-- Attachment #2: Type: text/html, Size: 423 bytes --]

[TUHS] Re: Canonical Historic Approach to iconv(1)

[Greg A. Woods]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

At Thu, 28 Nov 2024 00:07:56 +0000, segaloco via TUHS <tuhs@tuhs.org> wrote:
Subject: [TUHS] Re: Canonical Historic Approach to iconv(1)
>
> My mistake, the HP-UX reference was for iconv(3), not iconv(1).  The
> source is the current issue of POSIX, Issue 8 (2024).  Indeed iconv(1)
> is in the SVR4 manuals but only supporting system-provided charmaps.
> Additionally, while in the SVR4 manuals, I didn't spot it on first
> pass through SVID Issue 3 which is the SVR4-era issue.

It is documented in the System V Interface Definition, Fourth Edition,
Volume 2, Pages 211,212.

There's no mention of Unicode or ISO 10646 of course -- they're too new,
at least to be in any system standards by that time!  After all SVID-4
was only getting caught up with POSIX 1003.1-1990.  UTF-8 didn't even
show up more widely until early 1993, and wasn't in force in the IETF
until 1998 so you can't really expect SVID-4 to use it (even in 1995)
for a 1990-based standard.

--
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[TUHS] Re: Canonical Historic Approach to iconv(1)

[segaloco via TUHS]

On Wednesday, November 27th, 2024 at 11:08 AM, Henry Bent <henry.r.bent@gmail.com> wrote:

> On Wed, 27 Nov 2024 at 13:56, segaloco via TUHS <tuhs@tuhs.org> wrote:
> 
> > I started thumbing through my old manuals and noted that iconv(1) is not a historic utility, rather, SUS picked it up from HP-UX along the way.
> 
> 
> I see iconv(1) (and iconv(5)) in the SVR4 sources, but I don't see any references to HP there - what manpages are you looking at?
> 
> -Henry

My mistake, the HP-UX reference was for iconv(3), not iconv(1).  The source is the current issue of POSIX, Issue 8 (2024).  Indeed iconv(1) is in the SVR4 manuals but only supporting system-provided charmaps.  Additionally, while in the SVR4 manuals, I didn't spot it on first pass through SVID Issue 3 which is the SVR4-era issue.  It looks like specifying local charmap files was added to the spec in IEEE 1003.1-2004:

> Issue 6
> This utility has been rewritten to align with the IEEE P1003.2b draft standard. Specifically, the ability to use charmap files for conversion has been added.

- Matt G.

[TUHS] Re: Canonical Historic Approach to iconv(1)

[Henry Bent]

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

On Wed, 27 Nov 2024 at 13:56, segaloco via TUHS <tuhs@tuhs.org> wrote:

> I started thumbing through my old manuals and noted that iconv(1) is not a
> historic utility, rather, SUS picked it up from HP-UX along the way.
>

I see iconv(1) (and iconv(5)) in the SVR4 sources, but I don't see any
references to HP there - what manpages are you looking at?

-Henry

[-- Attachment #2: Type: text/html, Size: 665 bytes --]