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:
>>
>> matteolupin:~$ sudo pear search DB
>> Retrieving data...0%....50%...Invalid xml
downloaded from
>> "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

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

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

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php