Menu
▾
▴
[Rlib-devel] 1.1.8 TEST 4 is available, plus notes about new locale implementation
|
From: Chet H. <che...@si...> - 2004-03-10 21:55:31
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title></title> </head> <body> Hi all,<br> <br> I put a new test version on my website <a href="http://elmo.sicompos.com/%7Echeilman">Chet's RLIB Homepage</a>. This fixes crashes with non ascii characters in 8859-1 and some other problems.<br> <br> Version 1.1.8 has been changed internally to work with utf8 rather than 8859-1 directly. This allows almost any character set to be used. libxml which parses the input xml, converts the native character set of the xml into utf8. RLIB versions prior to 1.1.8 converted the input back to 8859-1 and then operated internally using this. 1.1.8 and later versions operate internally with the utf8, thus the output can be converted to any character set. <br> <br> Cpdf which provides the pdf generation for RLIB does not work with all encodings. It has partial support for utf8 for certain asian languages. This is why there are two different output encoding functions in RLIB. The encoding that is passed to the set_pdf_font function is the encoding that is used for pdf generation. If "" is passed, the native encoding of the font is used. Default is WinAnsIEncoding which is similar (but not identical to) 8859-1. (This was the ONLY encoding for PDF in versions prior to 1.1.8). <br> <br> For HTML reporting, the encoding (rlib_set_output_encoding) is best set to UTF8, since most browsers can easily handle this. This value defaults to the encoding used by the current locale.<br> <br> Data coming from the datasources (MySql, Postgres, ODBC, etc, and other functions, including the set_parameter function) should be encoded in UTF8. This is currently assumed by RLIB. If this is NOT the case, we will need to provide functions for setting up and doing these conversions.<br> <br> <br> Chet<br> <br> <br> <br> <br> <br> <br> <br> </body> </html> |
