IMHO we should treat the DDP as we already treat the Web server, ok, documents are primarily written in english, but there is an specific area for translation teams and internationalisation teams (w.d.o/international/) where documents are primarily written in other languages (but might get translated to english over time).
Agree with your sentiments.
What would the impact be if you were *require* that prior to publishing each document in it's appropriate location (language/topic/etc) it receive a one-paragraph introduction/summary in English that was stored in the English tree.
You could then also add a machine translation link to the tree in each language area. This would not be any substitute for a human translation, but it would give the reader the opportunity to actually get the gist of the document.
As I see it, the aim of DDP is to give documentation to the people. It is true that a document written in Japanese about rendering characters in X would only be relevant to people who read Japanese, but I think it would be fair to say that one would perhaps start the search for the documentation in English. The above strategy, that of requiring an English placeholder, would assist the person locating the document and would be simple to actually achieve (IMHO).
As an example of machine translation, the above text translated to Spanish with <http://babelfish.altavista.com/>. Not speaking Spanish, can you comment on the translation?
Convenga con sus sentimientos.
Cu�l el impacto fuera si usted era * requiera * �sa antes de publicar cada documento en �l es la localizaci�n apropiada (language/topic/etc) que recibe un uno-p�rrafo introduction/summary en ingl�s que fue salvada en el �rbol ingl�s.
Usted podr�a entonces tambi�n agregar una conexi�n de la traducci�n autom�tica al �rbol en cada �rea del lenguaje. �ste no ser�a ning�n substituto para una traducci�n humana, pero dar�a al programa de lectura la oportunidad de conseguir realmente el gist del documento.
Como lo veo, la punter�a de DDP es dar la documentaci�n a la gente. Es verdad que un documento escrito en japon�s sobre la representaci�n de caracteres en X ser�a solamente relevante a la gente que lee a japoneses, pero pienso que ser�a justo decir que uno quiz�s comenzar�a la b�squeda para la documentaci�n en ingl�s. La estrategia antedicha, de que de requerir un placeholder ingl�s, asistir�a a la persona que localiza el documento y ser�a simple alcanzar realmente (IMHO).
--
()/)/)() ..ASCII for Onno..
|>>? ..EBCDIC for Onno..
--- -. -. --- ..Morse for Onno..
ITmaze - ABN: 56 178 057 063 - ph: 04 1219 8888 - [EMAIL PROTECTED]
