[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: BoF meeting at aKademy
From:       Sander Koning <sanderkoning () kde ! nl>
Date:       2006-09-30 15:22:15
Message-ID: 20060930152215.GG20939 () macedon ! demon ! nl
[Download RAW message or body]


Philip Rodrigues wrote on 2006-09-30 15:53 +0100 regarding Re: BoF meeting at aKademy:
> Hi,
> 
> Firstly, thanks for the summary, Jens.
>  
> > We had a long discussion about the translation of documentation. It is
> > already difficult to find people who can translate but having them to deal
> > with docbook seems to be an additional burden for some. There was the
> > suggestion to move to a wiki for documentation but there where also many
> > arguments why this would be not a good idea.
> > Basicly this is an open point for the future and there was no decision
> > made.
> 
> Would anyone who was at the BoF (or any other translators) like to expand on
> this point? I'm interested in feedback from translators about any aspect of
> the documentation (and I'm sure the rest of the docs team are interested
> too!). Especially since now is a good time to discuss this: we have time to
> decide on the direction of the documentation for KDE 4, and translator
> input is important for this.

A possible solution that a team coordinator could choose, is having the
translators work with the online documentation, and applying the docbook markup
later. A positive side-effect of this is an extra proofreading of the
translation when the messages are given their markup :)

> > There was a wish to be able to generate documentation of partly translated
> > documents. The idea was that a document where just one paragraph is still
> > in English is already usefull for the users.

Yes, exactly. Especially in documents that have technical sections, one might
want to leave those untranslated and have the most important things done first.

> This sounds very reasonable. Is there someone working on the translation
> tools for KDE 4? I can think of at least one other thing that would benefit
> both the documentation team and translators, which is:
> 
> Have a way to mark an SVN commit as "this changes strings, but only corrects
> English grammatical errors, so automatically mark all fuzzies created by
> this commit as done."

Ooh, that would be nice... Makes string freezes a lot easier :)

> Does anyone have an idea how easy/hard this would be to implement with the
> KDE 4 translation system?
> 
> > There was also a wish from the HCI working group to improve the
> > cooperation between the translators and the working group for issues that
> > are important for both sides. There was no immediate respond to this wish.
> 
> I can't speak officially for the HCI team, but I think all you need to do to
> help is subscribe to kde-hci@kde.org (it's quite low traffic) and mention
> any issues that affect translators.

I've talked to Ellen Reitmayr from the HCI group earlier today and am now
subscribed, Albert Astals Cid also subscribed recently.

Cheers,
-- 
Sander Koning  (askie)   |   sanderkoning -@- kde -.- nl
KDE Nederland            |   http://www.kde.nl/
KOffice & Krita          |   http://koffice.org/  &  http://koffice.org/krita/
KDE documentation        |   http://docs.kde.org/
------------------------------------------------------------------------------


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]