[haiku-doc] Re: Another try at user guide translations
- From: Humdinger <humdingerb@xxxxxxxxxxxxxx>
- To: haiku-doc@xxxxxxxxxxxxx
- Date: Mon, 20 Jul 2009 16:57:35 +0200
Vincent Duvert wrote:
> > One way to simplify the process would be to provide documentation
> > authors a web interface similar to the translate interface, where
> > small changes could be done ("big" changes would still be made by
> > directly editing the file).
It may prove a better idea to get a separate SVN repository for the documentation that's
only write-accessed by your db. All changes big and small are then done online making it
easier to keep track of "inexact" translations and being in total control at all times. At
the same time we get the versioning advantages of the SVN.
Question: Can your system handle providing authors (of the original English pages only)
with one big editor view of the whole HTML document where one can do small "intra-block"
changes as well as big "add/remove/move-block" changes? Will all the small changes be
tracked and the translations flagged appropriately?
Are there editor-packages freely available that would provide some more functionality for
creating the English original pages? For the block-editing of translations, a simple text
view like it's now should suffice.
When you create original pages however, it may be convenient to define some buttons to
insert tags, like <span class="key|menu|button|app|cli|path"></span> or opening a panel to
upload images and insert the according <img> link etc. Maybe even a HTML syntax colouring
if we want to get fancy.
This uploading panel could also be used to upload a localized image under the
original-defined name and path into the {LANGUAGE} file hierarchy.
All this can be added over time, it's a low priority.
> > The tool could also provide a checkbox "Translations will not need
> > updates after this edit", to avoid unvalidating translations when the
> > edit was just a typo fix.
Good idea!
> > Comments welcome ;-)
I really think this could work! Amazing. :)
Something else came to my mind: How can we credit the contributors?
Since we can't really add names to every block, how about a contributors page that lists
all users with the number of all their committed blocks. Or better, leave away the
absolute numbers and just sort the names by their commit count, separately for the
different languages.
This page itself should be part of the user guide. Crediting is an important factor to
motivate volunteers.
Regards,
Humdinger
--
--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-
Deutsche Haiku News @ http://www.haiku-gazette.de
Other related posts:
