[kde-doc-english] Sorting out backports/string freeze schedule

[T.C. Hollingsworth]

On 08/17/2011 01:09 PM, Burkhard Lück wrote:
> I really appreciate that you care for the translators, but they do not need
> the same file layout for two docs with similar/identical strings to translate.
>
> With the current situation of kate (several docbooks) / kwrite (one docbook)
> translated docmessages can be either reused via the translation memory of
> Lokalize or with summit
> (http://techbase.kde.org/Localization/Workflows/PO_Summit)

Awesome!  I think I'll err on the side of completeness with the Kwrite 
docs then, since I'm fairly confident now that there won't be any 
unnecessary duplication of effort.

> The only real impovement for translators (and documentation maintainers) would
> be to split off one or several parts of the kate/kwrite docs (sect, chapter
> etc) into docbooks, which are pulled in by both docs.
> Digikam and showphoto eg share one docbook and on my todo list is something
> similar for the shared parts of konquerors/dolphins documentation-

Hmm, doing what showfoto/digikam does with kate/kwrite the way they're 
laid out now seems trivial.  I'll have a go at that right now.

>  From my pov as translator I'd say try to keep the docs layout as simple as
> possible for you as doc mantainer and then we (translators) will follow that,
> beeing happy to have up to date documentation to translate.
>

Thanks,
T.C.