firebird character set iso88591 is not installed

However, just to mess with them - make sure to test it where the client has a different character set then the database. I don't see it fitting into we8iso unless they use RAW in which case it is just bytes, not characters at all.Ģ) tell them to show you this. It has more then, way more then 255 characters. Korean data requires a multi-byte character set - each character could be 1, 2, 3 or more bytes. Please let me know your thoughts on the same. Īlso if I were to export WE8ISO8859P1 db data to UTF8 db, then do I have to set the NLS_LANG=UTF8 prior to exporting the database(as opposed to the original Db char), so as to avoid the IMP-00016 error during import ? Is it the right way ? The Java guys also claim to have seen a system using a WE8ISO8859P1 database to store Chinese Data, the system would perfectly store, retrieve and display data in Chinese ?ĭoes this prove a point or am I missing out on something very significant ,like my basics on NLS support ?Īlbeit, this issue has totally obfuscated me, I still feel very strongly that having a UTF-8 database is the perfect,long term solution. Maybe it sounds absolutely inane, but it just occured to a few of my colleagues (Java Guys), that this was a possibility. Can the data being pushed from the Browser (Lets say Korean data) be encoded in UTF-8 using the encoding mechanisms available in Java, and stored in the WE8ISO8859P1 Database ,is so then does it mean I have UTF-8 format data inside ?

īefore I opt to have a new UTF-8 instance, I need to clarify on a few points.ġ. The existing Database (WE8ISO8859P1 Char Set) needs to cater to English ,Chinese,Japanese and Korean as well. I am always here when I need to get that 100% right answer and so here is my question.

Firebird character set iso88591 is not installed