Hello, all. I'm new to 18030 and was hoping that someone could verify this. We're implementing a browser-delivered database application and would like to support 18030.
One fairly straightforward way of implementing this seems to be to accept 18030 at the browser and then transcode to Unicode when the data first reaches the server. When sending data back to the browser, we'd transcode back to 18030. OK so far, right? Unicode fonts don't support all characters in 18030, correct? Let's assume our client makes use of 18030 characters not in unicode fonts. What font could we use for a 3rd party reporting tool that read data straight from the unicode db, bypassing our transcoding layer? Thanks you for your time; I've learned a lot reading through the archives of this maillist. --Erik Ostermueller [EMAIL PROTECTED]
