Re: Problem upgrading PEAR

bertrand Gugger wrote: [...]

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. [...]

What you describe seems to be a bug in pearweb. Using entities makes sense (in XML), but making the entities visible on the package's page is obviously wrong.

btw, why is not PEAR taking it in package.xml which is a pure machine dedicaced stuff ? Here the extracted text looks awfull

It does (at least some kind of): On every new release, the package information like maintainers, description etc. are synced from package.xml to the website database. I guess that there a lot of things that can be optimized in this regard. But these things need to be identified and need to be reported, otherwise nobody will work on them (of course). Regards, Mark -- http://www.markwiesemann.eu