From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Canonical Historic Approach to iconv(1)
Date: Thu, 28 Nov 2024 00:07:56 +0000 [thread overview]
Message-ID: <GmJWCJWLq-0D-zatfNA0dFlIRcxJTH135IZeTs62_bp9WJ4IgHkIVhYC5FWlcdd0TLN6YmRRk3XZzzCFqQSZZRirwbNAgnEE04hVQT_zYjM=@protonmail.com> (raw)
In-Reply-To: <CAEdTPBdDzQRwbtockQqnM=8XEVFLE542EtOKUqzPfKoqO0AB0g@mail.gmail.com>
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.
next prev parent reply other threads:[~2024-11-28 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 18:56 [TUHS] " segaloco via TUHS
2024-11-27 19:08 ` [TUHS] " Henry Bent
2024-11-28 0:07 ` segaloco via TUHS [this message]
2024-11-28 0:57 ` Greg A. Woods
2024-11-28 3:04 Rudi Blom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='GmJWCJWLq-0D-zatfNA0dFlIRcxJTH135IZeTs62_bp9WJ4IgHkIVhYC5FWlcdd0TLN6YmRRk3XZzzCFqQSZZRirwbNAgnEE04hVQT_zYjM=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=segaloco@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).