>> >> I am going to remove url.icap from global.ent, because icap is >> >> deprecated and the code no longer available. This will affect the >> >> translated manuals CZECH, FR, KR, ES (as far as I could find out). >> >> Solution: Either the mentioned lamgiuages are updating there >> >> translation or they delete the reference.xml to get the actual english >> >> one, where url.icap is now longer used. >> >> > If the code is no longer available, the question is if the documentation >> > is still needed (how many setups are using ICAP). >> >> No clue, but still some functions are even not documented. I can't >> imagine anyone uses icap, no sources, no support, lack of >> documentation and at last indicator anly a few user notes. >> >> I'll vote for deleting icap from the documentation.
> OK, so then all the translation groups should be informed > (via the doc-XX mailing lists). > Then the doc can be deleted... > BTW if you simply delete &reference.icap.reference; from manual.xml.in, > there will be no problem with the translations, even if you delete > that entity. And that's what is going to happen I guess. I think removing &reference.icap.reference; is a good choice :-) Is it still necessary to inform the other lists? I think they all get en? > Or would > you like to provide this page with only the information that it won't > work anymore? Not really. If someone complains about missing icap docs we could do so or just switch back. But just only my 2 cents. open to suggestions, but as said before: its not as urgent (but will speed up checkent.php :-)) Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
