Re: legacy entities was: [PHP-DOC] cvs: phpdoc /entities global.ent

On Mon, 2 Dec 2002, Friedhelm Betz wrote: > > >> > removing dead links, and updating fr doc > >> > >> AHHH, my bad! Didn't take into account all > >> the translations! :( > >> > >> I'm away from my CVS tree right now but if > >> someone doesn't update them all I will > >> eventually. I promise to keep this in mind > >> in the future. > > > IMHO it would be good to move all the EN-unused enties > > from global.ent to a new "legacy.ent", and also include > > that in the build process. So translators will be able > > to spot where they documentation need to be updated > > regarding "unused" entities. We have many EN-unused > > entities listed in globals.ent (at the bottom), which > > are target for deletion, but we never deleted them > > because of translation build problems. I guess most of > > the translators don't know that there are entities for > > future deletion (and moving them to legacy.ent may help > > them to recognize the fact). Just a suggestion though... > > > Goba > > At least scripts/entities.php could be run with make test? > Its not the "final" solution but maybe a point of start. > > Having a legacy.ent would be nice:-) > Here is the actual output of entities.php for the en tree, only the > unsused ones from global.ent: > ENTITY USAGE STATISCTICS It would be nice if it did this opposite of this as entities.php imho wouldn't be useful in 'make test' as it's not a big deal to have unused entities in there. But it is a big deal to use entities that are not declared! Do we have a script that tests this? Anyway, it would basically do the entities.php check on legacy.ent and it would differentiate between each translation. Maybe this is what you mean? [snip] > Don't know how trustworthy the output is, because url.mm is > definitly used in ref/session:-) ( dark in my mind, I can remember > Philip added url.installkits) > > Out of this output a legacy.ent could be produced Don't delete installkits or zend.funcref, I have plans for those. :) I think we all should help give Goba time to create the legacy.ent, what can we do to help Goba? :) Regards, Philip