On 19 November 2012 19:50, Larson, John E. <[email protected]> wrote: > I have been searching and searching (Google, all VM documentation I can find, > pipeline forum and history pages, etc.) for days and can't figure out how to > deal with ASCII UTF-8. > > I've read on one site that codepage 1207/1208 "might" be the way, but of > course I can't find any more specifics about these codepages, and I'm not so > interested in them anyway as they're not supported by XLATE. > > My requirement seems simple enough, update a CMS XML browser to display ASCII > UTF-8 data in displayable EBCDIC, translate back to UTF-8 before saving to > disk or sending the data to a TPF system. > > For example, an input message may contain an extended Latin vowel, say, x'51' > from EBCDIC codepage 1047, and the UTF-8 equivalent of this is actually a > two-byte value of x'C3AA'.
I was thinking of "qpencode" but to my surprise we've never had the need to load the translate table through the secondary stream... > What makes this really unappealing is that I am dealing with a message driver > that sends tens of thousands of messages a second (1K-5K bytes in length for > each message), and I can't help but feel that taking the time for a rexx > routine to do this translation is going to noticeable slow things down. I would certainly invest in writing the stage in PL/j to achieve decent throughput. Once you know the algorithm that will do it, this should not be too hard... Rob
