× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 28-Sep-2016 11:51 -0500, Kevin Adler wrote:
On 09/27/2016 14:47:53 CRPence wrote:
On 27-Sep-2016 13:18 -0500, James H. H. Lampert wrote:
[…] given that hex'0A' has been entrenched in the application
for over two decades, changing the application is not an option.

If the code point 0x0A is required to be stored in the EBCDIC
application data [to avoid changing the application], then
consider:

That 0x0A is the Repeat (RPT) control character in EBCDIC, into
which the Single Shift Two (SS2) control character should translate
from the code point 0x8E in ASCII.

There is no 0x8E in ASCII. ASCII is 7-bit and has a range of 0x00 to
0x7F. There are various 8-bit extended ASCII code pages, though (such
as ISO-8859-1).

Sure. But both of those sentences used ASCII; little different than what I wrote. I pointed to the ISO-8 [i.e. 8-bit] control characters page; the onus is on the reader to understand any limitations. Most people already will not take the time to read what I write; tl/dr ;-)

Remember that PHP runs in PASE, which will be using some 8-bit
extended ASCII code page or UTF-8 depending on how it was started. So
just be aware that this hack of using 0x8E to convert to EBCDIC 0x0A
is not foolproof or completely portable.


I *should* not have written *should*; I *should* have written *might*. But the caveats were implied, and conspicuous; e.g. I "loathed" suggesting it and I only gave a URL in support, offering only ISO-8->EBCDIC.

I figure the likelihood is relatively high because as I recall, the typical translate tables for ASCII->EBCDIC on the IBM i had long included 0x8E->0x0A; history carries a lot of weight, with that lots of momentum. Notably, FTP and *TBL QEBCDIC. And the spineless are eager to please, irrespective of /correctness/; I have seen plenty of defects carried over versions and releases -- they get to be called /features/ although we used to jokingly call them .feetures. or some such [somehow that purposeful misspelling does not look so familiar] ;-)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.