Re: Add Translations and the howto
| From: | Gabor Hojtsy | Date: | Sat, 24 May 2003 18:35:35 +0000 |
| Subject: | Re: Add Translations and the howto | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969353853@lists.php.net to get a copy of this message | ||
You see Wolfgang, Jochen's answer I am replying to is not standing alone. There are many guys without any Linux knowledge who would not like to tune themselfs in into XML or CVS. Those two acronyms are enough to scare many people off the whole translation stuff.
Yes, those who are used to it [XML, CVS] know that it is not a big business at all. But those who don't know much of it are often scared.
PHP has a very low entry level for programmers to use. Many of them would be happy to add examples, more explanation to the documentation in case they would have a simple and easy to use system. The goal is not to move the whole phpdoc stuff to use some silly editor. Those who know XML and CVS will be able to work on that level anytime I think. But by providing a simpler interface, we can get more people involved with some litter contributions which would make our manual even better.
Look, Hans [the president of the New York PHP user group] posted some mails here before that he would be happy to get a txt version of the ncurses docs, and submit patches for that txt version. Because he would like to concentrate on the content, instead of learning CVS and our XML stuff first.
I think this question is much like the hand coded HTML / visual editing question. Some can develop with one method faster, some praise the other one. That is a question of preference. But for many guys out there CVS and XML is a high enough level that they are not going to join in.
Some kind of 'user friendly' translation / editing interface is to broaden the possibilities for those who would like to join and not to limit the work of those who will always use CVS and XML on the source level anyway :) The big question is how can we integrate some visual editor to the CVS system. Probably with precommit approval / editing and the like.
I don't know if you can make it to Linuxtag this year, but as it seems, we are going to have a meeting on documentation issues, and this is one of the questions. I think it is going to be an interesting part, especially if Sandro can show us some impressive tools they already developed for web based docbook editing.
Goba