|
From: <las...@Su...> - 2001-05-17 09:41:13
|
Hi, I sent out an email a while ago saying that I moved Scrollkeeper to libxml2. I think for the near future at least we might need to consider the migrated version wildly incompatible with previous releases. This is because of the libxml2 library, mainly the SGML parser built into it. There are two problems: 1. The SGML parser is not perfect, there are DocBook tags it doesnt know about. This is easy to fix though, I already sent a couple of patches to Daniel and I will send more. 2. This is more serious, libxml2 expects either UTF-8 input or encoding specified. There are loads of SGML docs out there that are not UTF-8 and while in XML it is possible to specify the encoding in the header, this is not in SGML (AFAIK). So libxml2 expects the encoding to be passed in by the caller. This means we would need to come up with some way of detecting the encoding based on the contents of the SGML file. Both problems flood the screen with error messages when run on a variety of SGML files from various locales. Any ideas? Laszlo |