From: Nuno L. <lu...@nl...> - 2004-09-24 12:54:12
|
I don't think people understand the problem here. All we want is to avoid to have people complain colinux isn't booting because of a mysterious error (can't load file). To achieve this goal we have (at least) the following options: 1- Follow the XML specification: 1.a) Use another XML library that would give us a standard compliant implementation. 1.b) Patch the XML library ourselves. 2- Don't follow the XML specification: 2.a) Just handle the few issues users face with small correction code. 2.b) Stop using the XML library and use other formats (like basic .rc files or even .ini files). IMHO, I would never go for 1.a), because I don't see why we should need a 1MB library (I'm exaggerating, off course) just to read config files. 1.b) would be just dumb, as we would never make it to full compliance without very hard work and probably resulting in 1.a). 2.a) was the intention of my patch: just make sure we don't get users complaining by ignoring the UTF-8 BOM. If users decide to use UCS-2, UTF-16 or UTF-32, that's their problem as they should know better. 2.b) would be the middle-term solution, but I don't see any reason to modify the code just for this. If anyone feels it's a must, they are always free to send a patch. Regards, ~Nuno Lucas |