I guess I still dont understand your gripe.
You have available to you the Hyperion git repository on github. You can
download the source code, build your own version of hercules and voila ...
codepage commands are ready and waiting for you to use.
So, what you want is already available. Just grab the brass ring, download
it, and use it. If you dont like it as is, modify the source, build it,
test it, and make the case for the changes to the 4.0 development community.
Post by ***@yahoo.com [hercules-390]
What I have in mind is not "reinventing the wheel".
I do know about code pages. The ICU Project - International Components
for Unicode - define thousands of code pages, notably in the form of UCM
files - Unicode Character Mappings. When two UCM files are referenced
together, you can create translation tables between two systems, using
Unicode as the go-between.
In contrast to the thousands of UCM files that exist from IBM, Apple, HP,
The GNU Project and others, Hercules defines just 21 translation tables,
including the 7-bit default Ascii version.
If a Hercules user wanted a translation table OTHER than the predefined
set of 21 tables that exist now, what choice do they have? There are only
1. Accept what's available and change your data to match; the "do nothing" approach
2. Write a program that will scan the Hercules executable looking for the
256-byte spans containing these translation tables and replacing one or
more of them with your own tables.
3. Beg and plead for someone to add the table you want to use into the
source code of codepage.c and hope that someday - maybe - it will be
adopted. There actually was that kind of hope, once, but now that Hercules
development is divided, that hope is mostly gone.
4. Put into production the CODEPAGE MAINT commands, so that any user can
create their own tables.
This is not "complex". The work has already been done; the code exists
and it works. All I am asking is that it be made available to all users.
I have been waiting 5 years for this; it's not like I haven't been patient.
Mike, I know that different code pages are written for different reasons.
I could not agree more. That is the very reason I want this. I have a
present need for a code page that is NOT one of the predefined 21
translation tables in Hercules.
The shame is, the CODEPAGE MAINT commands and all the work of the ICU
project have already be "invented", but Hercules users have up until now
been denied the benefits of it. To use the illustration of supposedly
"reinventing the wheel", it is like the wheel is well-past being invented,
but all the wheel stores are closed and padlocked.
P.S. As for using UTF-8, I don't see that as feasible. The main use of
translation tables in Hercules in the first place is for translating unit
record I/O. Although the current CODEPAGE command says that UTF-8 is used
with "I-Conv" translation, which is a Unix//Linus feature, I have never
seen this done myself as a Windows user. For instance, if I run DOS/VS and
send a print file to my PC, DOS/VS has created its file in EBCDIC so I need
it in ASCII to view or print it locally. So there is a single-byte
character set (SBCS) in EBCDIC getting translated to an SBCS in ASCII.
When or how would UTF-8 get involved? I don't see how it would.
Mike A Schwab wrote,
There are several different codepages for EBCDIC, because different
programs need different special characters.
And they usually translate to different ASCII codepages for the same reason.
Any chance of using UTF-8?
John P. Hartmann wrote,
I wish you would know about code pages and the various efforts rather
that to reinvent something rather complex.