Okay, we all know that OIPI does not run if an application is set to UTF8 mode⦠my question is: UNICODE support is there (and this is a great thing), so why do we still get uncompatible pieces and parts of software whitin the OI development suite? This is not only about OIPI, also the new table builder is not working properly, etc.
Could please anyone (maybe RTI people) tell us if and when should we expect a full functional (in terms of UNICODE) version of OI? Thanks a lot,
Stefano
Stefano-
We're making a broad review of our UTF-8 implementation and trying to make sure it works in every tool for OI 7.0.
Can you tell me of all the areas you know where Unicode characters don't work?
We are working on OIPI and Unicode.
Thanks-
Mike Ruane
Mike,
Is there a discussion list for 7.0 and/or Unicode? I'd like to join.
Here's my current situation regarding Unicode: I'd like to have a larger character set and therefore Unicode. I have no plans for making new apps but would like to Unicode-enable my current app. But all my current programming is made for ANSI data. There's a lot of programming. Converting it to handle Unicode would take months of work. I just hope ANSI isn't abandoned. That would really leave me stranded.
- Oystein -
Mike,
thanks for the answer. As I said in my previous posting, apart from the OIPI stuff, the new table builder does not work properly in UTF8 mode. You can create a new table with some new columns, but you can't make changes to existing ones. If I need to change anything I'm currently using the Database Manager (!).
Stefano