> > eyes, where people only need to translate small XML files to > > have function descriptions translated... As this change will cause > > I won't care. But IMHO it is easier for beginners to translate small > files instead of large ones.
Easier to update, and easier to plug in new functions in translated versions, as you need not copy any untranslated parts from the en files, but you still have the functions in your languages doc. > > many more diff mails on the phpdoc list, we also discussed breaking > > the phpdoc list into language specific lists, such as (phpdoc-de, > > phpdoc-hu and so on), where people only get the commit messages > > from that specific language and can discuss that languages problems... > > IMHO this is not so good. So you disagree with separate lists for separate commits. Are you interested in it, ja, kr or ru commits? IMHO no. Are you interested in discussions like this? IMHO yes. So then you would sucsribe to the main (en) list with general language independent discussions, and "en" commits, and to your own list... You are not interested in changes, updates in the hu tree, and discussion in Hungarian... > ACK. I myself will find help on IRC very quick. But others will "spam" > mailinglists aksing things which should be in the manual. PHP is very > good documented, but the manual lacks of a real help on the installation. Well, from inside, I see that even while PHP is very good documented, there are many things we can advance our manual. > > This would address Egon's conserns about people hardly find the > > things they are looking for, as if you are interested in database > > specific things, you only need to look at the databases part in > > the manual, where you find feature descriptions, like persistent > > connections, configuration options helping you set up a database > > extension, and functions you can use. > > This would be great! People often search for subject specific things, for example database information. IMHO they will esaily find things, if we structure information by subject (eg. database, ecommerce...) and not by category (eg. separating features from functions)... > > String replacing: str_replace(), preg_replace(), preg_replace_all(), > > ereg_replace()... > > Well this need to be in a sophisticated format... :)) > > Yes, but it would be easier for the people searching for help. > Work from the view of a what we Germans call "DAU", someone > like a newbie. Don't work from the view of a pro. IMHO this would be good for a pro too. The question is who we call a pro. If you are a pro at dinamic website programming but have not worked with gd images before, you will find this type of index useful, as you'll find "Image creation", "Text on image functions", ... categories useful. Well you can say in that case, that person is a newbie for images, so he is a newbie :)) > > You may start this new configuration part in a separate > > directory, and we can move the thing to the parts when this > > structure will be ready and working. I think it is a dead > > idea to put this thing in a separate CVS, as we have people > > here who would contribute to this thing at least ocassionaly... > > So, you mean something like phpdoc/en/configure ? Yes, you can start off with creating phpdoc/en/configure IMHO, so people will be able to contribute, and translate as soon as it will be ready for inclusion in the manual. > > I have asked Hartmut if he needs any help in preparing for > > this change, but I've got no reply. :(( Currently a "migration > > to DocBook 4" project is under the hood, so this may put > > this huge project on hold. > > Hartmut should be on holiday. I hope he will read our mails when he get back ;) Goba
