On Tue, 2008-06-03 at 14:52 -0500, Joshua Facemyer / Impressus Art
It would be most excellent to have your help! I don't know if
any interested Spanish manual translators ATM.
Basically, once we have some finalized text to work with, you'd be free
to translate them. We have yet to begin the actual work, but we will
probably do some preliminary writing before the booksprint.
I wonder if Adam (who is on this list) might give a brief description,
if he has a moment, of how the current translation site works, and what
we might see in the near future for translation tools? I have yet to
look at them in depth and would not want to give an explanation that is
incorrect or, at best, lacking important info.
Thanks Joshua for the invitation to give some detail on the translation
I think I should break this down to a simple explanation and then I have
included some additional information for those that wish to understand
more of the technical details and have a better 'meta' overview of how
it all works. So first the simpler overview - there are really three
* side by side translation
* version tracking of original source vs translation
* status tagging
FM has a very simple but effective translation interface. The interface
shows a side by side view of the original vs the translation. The
original is 'read only', and the translated view is a WYSIWYG editor.
This means you can see the original and translation in one view and
there is no need to switch between document windows. You can have a
sneak peak at one of our chapters as viewed in the side by side
When you view the translation window you always see the same version of
the chapter you are translating against. So if the original version is
updated you will also always see the version that you had originally
chosen. However, there is also a drop down menu that enables you to see
newer versions of the original if they are available. Newer versions
simply load inside the page without refreshing anything so it does not
interrupt your translation session.
When you decide to save your translation you can also decide to change
the status of the document. Each chapter is marked with either
'translated', 'untranslated', or 'published'. We will also add
proofed' and 'proofed' to this. This is a simple status tag so that
contributors can see where in the workflow the material resides, and
what should happen next.
That is the simple explanation! You can also read a little more and see
some screen shots here:
ok...so stop there if you only wanted those details, if you wish to
learn more about the mechanics and concept behind this process then read
FLOSS Manuals (FM) is building a network of language communities. Each
language community has its own localised install of the FM platform (we
base everything on TWiki which we have extended with our own plugins -
these are released GPL to the TWiki repository). This platform is used
by the community for the development of new material in their own
language and translation of material from other language versions of FM.
FLOSS Manuals has built a wiki exchange tool which enables the transfer
of content between the different language platforms/communities. This
enables a community to import manuals in different languages and place
them in a translation work flow. So, if I am working in the French FLOSS
Manuals I can view material from the other languages and import the
manuals/chapters I want into the translation workflow.
You can see a little information about this tool ('Xchange') our own
When content is imported into the translation workflow it is (usually)
marked with 'untranslated'. This will then give the option for
contributors to choose the translation view when contributing to
chapters. The translation view is what I described above.
The translation side by side view shows the original in an ajax iframe
and hence it is viewed 'remotely' - pulled in from the original language
node of FLOSS Manuals. This means we can track changes in the original
and notify the translator that there has been an update that they may
wish to look at.
For the technically minded : We store all material in xml (xhtml) and we
use HTML Tidy on the backend to keep the sources clean. We use Xinha
WYSIWYG editor because it is clean, modular, stable, and offers some
interesting language translations. We were happy to find, for example,
that the Xinha interface has mostly been translated to Farsi which
helped a lot for the building of our Farsi FLOSS Manuals (launching at
the end of June). Lastly, the xchange plugin uses RSS for the transfer
of content between the different languages which also means it is ripe
and ready for syndication of content (eg enabling users to subscribe to
manuals and updates).
Currently we are also building a simple tool for word lists of technical
terms. This will enable translators to choose a language and context and
add items to the list or insert agreed translated terms into the content
by simply choosing the original term from a drop down list. The use and
definition of the translation terms will be up to each community and
discussed through mailing lists.
So, our aim is to build an extensive network of FLOSS Manuals localised
communities. Each producing their own original content which others can
then translate. Our first implementation is a Farsi version of FLOSS
Manuals and we are planning other languages to follow this up in quick
succession. However first we wish to go through the process of getting
Farsi established before moving to the next one. Having said that we
have made some steps towards new languages with interface translation
for Bengali and discussions underway for Finnish, French, and Dutch. Our
aim is to build FM language communities where there is interest - we are
equally committed to 'under resourced' languages as well as larger
languages. We have plunged into this with Farsi which is a
right-to-left text so our tools are UTF8 compliant and can support RTL
We will also build a general translation platform where manuals can be
translated to and from any language - the idea is to build up a body of
content in this 'holding platform' and then when any one language has a
critical mass of content and contributors we would establish a platform
exclusively for that language as part of the FM network. The nice thing
is - we can establish a new language platform very quickly with just
1900 words to be translated in the FLOSS Manuals interface and 7 images
that need translating. We have a nice tool for this also
). What takes
longer however is resourcing and building a community which is a careful
process and takes time.
ok!...so that is the overview...we will have the general translation
platform in place for the Book Sprint in July and very happy if it can
be used for translation of the manual into more languages.
Anyway, best thing for now is to monitor the list and participate in the
discussions. If you're interested in coming in person, we'd love to
> I'd really like to activerly participate in translation and style
> proofreading into Spanish. How to?
> On Mon, Jun 2, 2008 at 3:04 PM, Joshua Facemyer / Impressus Art
> <faceman@...1... <mailto:faceman@...1...>> wrote:
> A short time ago, those of us who had been actively discussing the
> manual on the inkscape-docs list agreed that FLOSS Manuals
>) was our best
> for keeping an official manual up-to-date while encouraging
> non-technical users to contribute. It has a simple interface, is
> available (it is a web application), and there exist translation tools
> which are being actively developed to provide a usable translation
> interface. There are many other benefits to using FLOSS Manuals
> (FM) as
> well: we would have the ability to organize different setups of
> / how-tos by arranging existing content into new "manuals"; to
> manuals in different distributable formats (export as pdf, html, and
> even print online with lulu.com
;, et cetera).
> These powerful capabilities
> create an exciting possibility to build and maintain a dynamic manual
> with minimal effort.
> Recently, FM has received a small grant from Google to host a "book
> sprint". Adam Hyde of FM has personally invited some of the
> members from
> the inkscape-docs list to join him for the book sprint in order to
> out a basic, up-to-date manual using the FM tools. (If you have
> not seen
> how this works yet, you can go to the website and check it out. Since
> our manual has only some test material in it, you cannot yet view
> it as
> a manual, but if you set up user account, you can view it in the edit
> While FM has certain guidelines which the book sprint must follow and
> goals to accomplish, we will be discussing on inkscape-docs the
> particulars which we want the book sprint to produce in order to
> make it
> most productive for both FM and Inkscape. Adam will be active in this
> discussion, and help guide it so that it proceeds toward both FLOSS
> Manual goals and Inkscape Docs goals. Anyone who would like to
> participate in this discussion is welcome and encouraged to do so.
> Also, anyone is welcome and encouraged to take part in the actual book
> sprint itself, which will be taking place from July 5^th through the
> 12^th in Paris. Participants are welcome either in person, if you are
> able, or else by internet. (Details will follow on inkscape-docs
> as they
> are worked out.)
> The committed participants thus far are:
> Adam Hyde (from FLOSS Manuals)
> Brianna Laugher from Wikimedia (http://brianna.modernthings.org
> CÃ©dric Gemy (pygmee)
> Elisa de Castro Guerra (yemanja)
> Alexandre Prokoudine
> and I (Joshua Facemyer)
> We are all looking forward to spending some time getting to know each
> other better, seeing Paris (those of us who don't live there ;) and,
> most importantly, putting together an Inkscape Manual for the
> of the Inkscape community!
> This SF.net
email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> Inkscape-devel mailing list
> Favor no cambiar el ASUNTO
> Please don't change SUBJECT
email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Inkscape-docs mailing list
+ 31 6 2808 7108