On Fri, 2006-09-29 at 17:00 +0200, Jean-Francois Nifenecker wrote: > Frank Peters a écrit : > > It would be good to have some sufficiently bilingual community > > members to help with getting non-English content into English > > (if we want to see English as "root language"). > > I'll join Alex' choir here: the number of "language-aware" authors is very > little. Adding the time availability criterion would shrink the number to a > handful, to the best. > Second, being able to express oneself on fora doesn't mean that the > translations produced are of sufficient quality. A deep review of the > translations is then due.
I agree.
>
> Also, don't forget that translating some doc into another language implies
> providing screenshots in the same language. This means that the translation
> effort is quite similar to writing a doc from scratch. Having done that once
> for the OOo project ("Calc to base" how-to), I can tell you it's a lot of
> work
> that many would find redundant hence non-motivating.
Again I agree. However, I think that even an announcement of new works
would be a good thing. For example, Sophie's announcement or the ref
cards as a work in progress has raised some interest for something
similar in English. We, at the doc project, also have works in progress.
The important one, a complete rewrite of the VBA to OOo cross-reference,
is not yet ready for its first editorial review, let alone letting
others look. :-( But here you have something that might be of interest
since it will be somewhat technical and likely an easy target for
translation or rewrite.
As to Calc to Base, this will be covered in Chapter 7 of the User Guide
along with all the other stuff one hopefully needs. Unfortunately, the
Guide lives in a issue and started as a sole project so it is awkward to
manage.
>
> > I see what you mean. I know that I am stretching it now but should
> > we have documentation guidelines available for other projects that would
> > help us to leverage existing docs created in other projects?
>
> Yes, I second that.
Me too. I had hoped when we started the Setup Guide project for 2.0 that
it would be included in the distribution like the 1.1.x guide.
However ...
--
G. Roderick Singleton <[EMAIL PROTECTED]>
OpenOffice.org
smime.p7s
Description: S/MIME cryptographic signature
