Hi Marc!
Although I do think that automatic translation might help in some cases,
it is unlikely that it provides the outcome that is currently claimed.
As I said earlier, if we come to technical terminology within LibO, then
all non-domain specific (or aware) translation tools do more harm than
they do help. At least, sometimes I enjoy reading those translations :-)
Sophie is right when she says, that the communication and the help
between the people speaking a certain language (or, being in a certain
area) helped to grow what we currently experience as "the community".
She is also right, that the approach - and therefore the contents of the
documents - varies between all the native lang groups.
From my point-of-view (given the experience within the OOo project), the
following approach might combine all the positive effects :-)
* Provide the most essential information on LibO and TDF in all
languages, derived from the main language English. The content
for the other languages should be translated "manually".
* Enable the language teams to add own content - independent from
the main language English.
* For non-critical content, provide a way to translate the given
content. I think it would be most helpful for "normal"
conversations like in forums or emails. Besides the already
stated "button" metaphor, make sure that people are aware of
reading a translated text (the rest is an usability problem
which can be solved, happy to help here).
(Oh, I just saw that Michael did already mention this in another mail.
Sorry for sending it another time, but maybe it helps to support his
idea.)
Sophie, thanks for your input here - I'm sure your great experience will
help to make the infrastructure "rock". Also, thanks to Marc and all the
other people that drive the infrastructure topic!
Cheers,
Christoph
Am Montag, den 22.11.2010, 14:16 -0500 schrieb Marc Paré:
A good example where such a tool would come in handy is exactly this
thread. How many more people would contribute to this particular
thread is the automatic translation tools allowed them the opportunity
to view/read these threads. OR for that matter how many more people
would participate on the Drupal Website Development Team if the
translation tools would help.
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/website/
*** All posts to this list are publicly archived for eternity ***
Context
- Re: [libreoffice-website] Re: Update on Drupal Website Progress (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.