Re: Problem upgrading PEAR

Mark Wiesemann wrote:

Hi Matteo, Matteo wrote:

Hi, i can't search any remote packet! I follow the simple step on PEAR site to upgrading pear but now, if I try to search a packet, for example contain the keyword "DB" the result is: matteo@lupin:~$ sudo pear search DB Retrieving data...0%....50%...Invalid xml downloaded from "http://pear.php.net/rest/p/validate_be/info.xml": XML Error: 'Invalid character' on line '17'

[...] This is a "bug". The package description for Validate_BE contains the word "sécurité", without having the special characters written as entities. I send a copy of this message to Christophe Gesché and Bertrand Gugger, the maintainers of this package. They need to use entities in the description, and might need to make a dummy release to update the auto-generated info.xml file (not sure about when this is done).

OK, I have updated the package page, http://pear.php.net/rest/p/validate_be/info.xml seems correct now, BUT this looks not fine on http://pear.php.net/package/Validate_BE/ as the & is transformed in & I guess that's the reason why Christophe did let it in ISO. This rule is idiot, PEAR privileges the machine side and not the human. Could not the stuff care to do the conversion for the xml ? You are perhaps not sensible to this fact, but for us "securite" has no meaning, "sécurité" does ... and sérité or sécurité means even less. Maybe I'm missing something here, or maybe the pearweb does it bad. Other point, this was on this way since ever, that's PEAR which changed. Can you point me out to the pear rule specifying that ? Where is the general mail asking the maintainers to conform to pure ascii in the info page ? btw, why is not PEAR taking it in package.xml which is a pure machine dedicaced stuff ? Here the extracted text looks awfull Please, anybody, avoid to answer me I am a troll. Thanks for the head up, Mark. -- toggg