> May I suggest you just duplicate the entire current manual structures for > the new manual(s) and don't add any translation directories. That way when > someone decides they have to have the new manual in their native language > you don't have to work so hard to support it. They will eventually...
Uh, it's not that easy. We have separate mailing lists for translations and separate CVS modules for every translation. Well, if we duplicate all these, we get a huge mess... If we push all users manual content one subdir down and make a new subdir for developers manual content (in all phpdoc modules), then we get a huge mess (there will be no CVS history for files, updates will get even harder). Actually I don't think so that someone can write a PHP extension if he even don't know English... PEAR, PHP-GTK, TSRM and other projects also copied the build system, so we have quite differently evolved build systems everywhere. Copying the build system does not help IMHO, but increases confusion, as different projects modify that initially same build system to their needs in different ways, so you cannot just jump in and work with another build system. For example the PEAR system uses XSL sheets exclusively, while we are just in the testing phase of converting to XSL sheets, and still use DSSSL ones, which require completely different conversion tools... Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
