× 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.


  • Subject: Question on Code Page differences (Phil Hall)
  • From: "Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Mon, 14 Aug 2000 15:24:38 -0500

A while ago I posted a problem where some software we wrote would mess up
characters.  Phil Hall was a big help (and I'm looking for input from him as
well) and I would like to run something by him.

The character in question was the bracket.  "[".  It was converted wrong,
making the data wrong.

Would this work?

In my data, instead of a bracket, I use something that doesn't change hex
codes between CCSIDs, like //BRACKET//.

Then, in a file, I have the user on the machine enter in the literal value
for the bracket and store it in a file.

When I write data to a file, I scan for //BRACKET// and replace it with what
they typed in.  So "//BRACKET// value" would be replaced with "[ value" when
written.

Will this work?  Other solutions are simply too involved for this
application it seems.  My concern is if the file is external and I ship it
to them the CCSID wil be 37 and may mess things up.

Thanks!

Brad
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.