I was messing around, and I found , on CEX, you can delete all the shop xmls, the tool xmls, the category_sysconf.xml , not sure why we even leave them in normal CFW. Also , I stripped out loads of unused stuff from the used ones, reduced the xmls by over 50% in size overall without removing any features.
You deleted category_sysconf.xml too ? lol, i thought that one was used, good to know
And category_avc_photo.xml ?... not sure right now what does this one
That test reducing sizes is interesting, if you notice some performance improvement dont forget to tell us

I guess you could try to use a timer to meassure the loading times before and after the "fine butchery" of the xml files, but i also guess the meassurement is not going to be much precise, so dunno if im suggesting you to try this, jst mentioning it incase the loading times are very different
And that collection of ripped xml files could be handy for 4.82 han users

They are locked in retail/CEX so no need for the other files for other PS3 models... and the removal of the "dirt" added indiscriminatory by sony (because they hates to delete or cleanup his own code) is something good
I always thought it could be very nice to have some tool to automatize this cleanup, and when thinking in this i found some xml tools that can "merge" "substract" several xml files... and other options like that... are used for manteinance of xml databases
The first problem with that is the PS3 xml code uses some stuff that is not standard (the xml parser complains because there are errors and is not able to fix them), one of them is the
& character that is used in the lines where it tells
Code:
src="xcb://localhost/query?onething=this&otherthing=that&whatever=thing
Everytime the xml parser finds a
& returns an error... so that characters needs to be replaced before processing the xml file with some tool (that follows the xml standards, not the sony ones)... and after the edition should be restored (to return to the sony standards)
The other problem is after the xml is processed... it loses most of the original "sony style" in the way how lines are tabbed, or separated for a better reading.. technically the xml code is fine (ps3 is going to load it fine) but when you open the file it looks a bit weird
Edit:
Also, the xml tool needs to process the xml files with the correct encoding, dont remember if is utf-8 or 16
If done incorrectly... are lost all the unicode identifyers used to make appear the icons from imagefont.bin and things like that