url.php.bugdosdonts - can be removed because isn't used
url.openasp - should be removed, because the project was descontinued (there
are no dependencies)
url.netcraft-survey - isn't used too
url.chilisoft.asp - can be removed, too, as you deleted the link to this
entity

I think that obsolete entities are kept because of translations. Someone experienced - is it true?

Yes, this is the case. Not saying it's ideal but it's the current reason. Within the TODO are other (preferred) ways for dealing with these issues, but since all translations
use global.ent we would rather have unused entities than
unknown entities when various translations are being built.

IMHO it would be good practice to put all unused entities to the end of global.ent (as some are sorted there), so we can delete them and spot them more easily.


The current missing-entity replacement system works so that it generates entities containing only question marks for nonexistent entities. Therefore if you remove an URL, translations still using that entity will have the links broken. It is a good question if this is a problem or not.... The best of all would be if people removing entities from global.ent would have uptodate checkouts of all translations, and would remove/update the entities from there... But that seems to be too ideal :)

Goba

Reply via email to