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



Thanks Bruce.

My procedure is definitely not converting to upper case like I expected. I will take another look at what I am passing to the API now that I know it should be working correctly. In my previous testing, there were no API errors and the "converted" output data was exactly like the input data.

PS. I like your book.


At 09:51 AM 3/20/2008, you wrote:
The ConvertCase APIs work fine with Unicode data. Just use CCSID 13488 and your graphic fields. Unicode uses the Graphic data type, but it is not DBCS.

Bruce Vining


Dave Murvin <davem@xxxxxxxx> wrote:
Hello,

I have some routines I use such as ToMixed(fieldname) that convert to
upper/lower case and they need to be able to handle Graphic character
fields with CCSID 13488 (UCS-2).

The traditional %Xlate with not do it because there will be multiple
languages (English and German to start). I have also looked at the
QlgConvertCase API, but is says that "This API does not convert
double-byte character data from and double-byte character set (DBCS)
or from a mixed-byte character set". I have tried to converting with
this API and in fact is does not convert by field. This API can
base conversion on a CCSID, but it appears that it does not do this
for Graphic character field (a 10 byte character field takes up 20
Graphic bytes).

Is there another way to do Upper/Lower case conversions with Graphic
UCS-2 fields or am I possibly doing something wrong using the
API. ( When I step through it in debug, it looks okay.)

Do I have to convert the Graphic CCSID 13488 field to normal (us)
CCSID 37 character field, convert the case, then convert back to
Graphic CCSID 13488?

Thanks

Dave Murvin
DRM Enterprises, Inc.

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




Bruce
Bruce Vining Services
507-206-4178
--
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.

Dave Murvin
DRM Enterprises, Inc.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.