(Nowadays almost all applications use Unicode, but still, the browser has to decode the binary stuff into its internal Unicode representation.) When the browser reads the file, it has to reinterpret the given data and convert it into a native character set. The HTML file is encoded and transfered as binary content. The second point of failure sits in the browser's rendering. (This is caused by Java's character encoding methods.) This is generally easy to spot, and switching the encoding in the report configuration immediatly solves that problem. If you specified to export in an encoding that cannot display all characters of your text, then you will receive question marks for each of the non-displayable characters. In HTML there are two points of failure for the export. For both of these export methods, the cure is different. There are only two output methods that make trouble with encodings: PDF and HTML. Solving encoding problems basicly depends on how you do the export. Using an real XML editor should ensure that. But you will only get valid results, if your XML file is properly encoded as well. If the label displays well, but the text-field doesn't, then your driver is to blame. You can check whether the JDBC driver causes the trouble by adding a static label to the report.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |