> 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? configure runs scripts/missing-entities.php and produces entities/missing-entities.ent for the configured language, checking for the usage of undeclared entities from global.ent in the configured language-tree. As long as the entities definded in the global.ent they are _not_ missing. Therfore the legacy.ent would be usefull. My intention was: run entities.php on the en-tree to produce a legacy.ent from global.ent. Move the unsused entities in en from global.ent to legacy.ent. This forces to end up all unused entities for the translations in entities/missing-entities.ent. The implication: all entities in global.ent should be used in the manual, means we can't have entities in this file we don't actually use or plan to use :-) I think translators never look at missing-entities.ent :-) >> 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. :) Hey, stay cool, I have no "plans" to delete anything :-) > I think we all should help give Goba time to create the > legacy.ent, what can we do to help Goba? :) +1 Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
