Re: cvs: phpdoc /entities global.ent

The only problem left is this means 404's will remain. During 'make test' it would be nice if it said something like: "Warning: file foo.xml is using a link from legacy.ent, please update it to reflect the en/ version" Something like that, it would check more than just links I guess. Anyway it's a good idea but I fear some 404's will remain for a long time and may go unnoticed. Also, the script checkent.php could be updated to check all this. Regards, Philip On Mon, 2 Dec 2002, Gabor Hojtsy 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 > >