Hi Brian, I have only ever used lang groups in order to get the udt xml api to work correctly with utf8/16 encoded xml files. I have to say if you do get it wrong then you can get intermittent errors with xml files, and other api's which is rather hard to trace. So just be careful and make sure you test any udt api's that are in use in the app.
We do take in data with u umlauts, and because most of our output is in html anyway we just convert them to the html entity (ü) at time of acquiring the data, probably not the most elegant or the most efficient storage wise, but it is only the odd character here and there so works fine for us. Or if it does not matter that your data field contains char 252, ie it is not mv or sv then you can just store it as is. You just need to remember what it is down the line tho which did bite us at one point hence why we html encode it. Rgds Symeon. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Brian Leach Sent: 25 July 2009 09:44 To: [email protected] Subject: [U2] UniData and umlauts I'm cross posting this from the website in the hope of finding someone who can respond: Has anyone used NLS English_G2 in order to handle special characters such as the u with umlaut () in UniData? I have a client based in the US, that would like to be able to incorporate umlauts in their name and address fields. They are running UniData 7.1, and my understanding from the 'UniData International' manual is that if we were to switch the language group to English_G2 it would handle this. Has anyone switched language groups in midstream? Or any other ideas as to how to approach this? Thanks all Brian _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
