Re: iConv() questions... SBCS to DBCS

[Bradley Stone <bvstone@xxxxxxxxx>]

Thanks, Scott.

Maybe the wrong terminology, but it was converting hex'71' to hex
'c389' which IS correct..... but everything after that was corrupted.
(it is the accented E character you can find in this chart
http://www.utf8-chartable.de/).

I took your advice and made separate input and output buffers for
iconv and that seems to have fixed it...  So I appreciate the tip!  I
guess I haven't seen any examples like that before so I never would
have thought that was the issue... but in a way it does make sense....
 Maybe V5R3 just didn't have the memory issue like the later versions
do.

Brad


On Thu, Nov 17, 2011 at 2:42 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx> wrote:
> Hi Brad,
>
> I've never had a problem?   Also, 1208 isn't DBCS, it's UTF-8...
>
> Make sure you are using a separate output buffer from input buffer.
> (i.e. don't use the same spot in memory for both input and output.)
>
> Other than that, I can't think of anything that could go wrong -- and it
> has always worked for me.
>
>
> On 11/17/2011 2:12 PM, Bradley Stone wrote:
> > I am using iConv to convert data from 37 to 1208.  The data contains
> > one character (accented capital E) that is converted to DBCS in 1208.
> >
> > I have an issue where I am getting different results on a V5R3 machine
> > vs anything newer than that.
> >
> > V5R3 seems to convert things ok.
> >
> > V5R4 and up the accented E gets converted properly to the right DBCS
> > value, but everything after that (simple letters) are corrupted.
> >
> > Any idea what could be causing this?  Is this a case where I would
> > need to convert each character one by one instead of all at once?
> >
> > Thanks!
> >
> > Brad
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.