> -----Original Message----- > From: Kimbro Staken [mailto:[EMAIL PROTECTED] > Sent: 25 February 2002 10:23 > To: [EMAIL PROTECTED] > Subject: Re: [bug] encoding problems > > > > On Monday, February 25, 2002, at 02:06 AM, James Bates wrote: > > > > As for getting it fixed in release 1.0, I'd have liked it > too, but Kimbro > > (rightly) prefers to wait, as making UTF-8 the database's internal > > encoding breaks existing datafiules. There isn't really a > reason not to > > just fix the command-line tools though, thus already fixing > Stefano's > > italian problem... > > Kimbro? > > > > How big is the change to fix this and what are the potential impacts > elsewhere in the system? >
minuscule (about 3k). Effects on other parts of system: only command-line tools are affected. Anything using API's would remain as is. XML files you have written in ISO-8859-1 without specifying so (i.e. by omitting encoding="iso-=8859-1" from the XML declaration) will of course no longer load with the command tools (Note that such files are not well-formed XML files according to the XML spec anyway...). I've attached the patch to this message. I still re-iterate though that only solves Stefano's Italian problem. Russian, Greek, etc... will still not load into Xindice because of the database internals... James > > > > Hope that clarifies things, > > James > > > > > Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org > Apache Xindice native XML database http://xml.apache.org/xindice > XML:DB Initiative http://www.xmldb.org > Senior Technologist (Your company name here) > >
cmd-tools-patch
Description: cmd-tools-patch
