discuss: Translation effort workflow
Subject:
Re: [discuss] Translation effort workflow
From:
Machtelt Garrels ####@####.####
Date:
11 Oct 2005 10:37:53 -0000
Message-Id: <Pine.LNX.4.44.0510111033550.14638-100000@cobra.xalasys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 9 Oct 2005, Daczi László wrote:
> Hi all,
>
> > > If you find Linuxdoc or Docbook too difficult, it is not the end of the
> > > world. Simply translate the text of the original document, and other
> > > volunteers in the Documentation Workgroup will add markup to the
> > > document. Do note, however, that this may mean that your document does
> > > not get to benefit the general public quite as quickly.
> >
> > This is not a good idea. Taking the text and putting it back in DocBook
> > or LinuxDoc is a huge work, while translating in source format is only
> > slightly more work for the translator. It will also be more difficult to
> > find volunteers for that, as it is a very boring job.
> Use format highlighter editors, such as jEdit (http://www.jedit.org/) or an xml
> editor, such as XMLMind (http://www.xmlmind.com/). Really I'am working on a
> translation memory tool now (this is my last test in the college). It can
> import/export markup language documents (linuxdoc/docbook among these). You can
> found detailed information at http://tldp.fsf.hu/s3po/en/index.html or ask me.
> (Unfortunately I havent't got any free time, so please wait...)
As a translation coordinator for LPI, I also deal with this sort of stuff
a lot. One thing we have, apart from the translation memory, which stores
common word groups and sentences, is some sort of glossary that lists
words and terms that should not be translated. It might be a good thing
to have consistency of these non-translatable terms across documents.
I would also suggest to translate the source and do no conversions during
the translation process. Even vim has very good markup highlighting.
It is also a good idea to plan the translation process and to set dates
when things will be done. Most likely you will pass the deadlines, but
that is no problem :) The dates are set so as to motivate people. I've
seen many translators, for instance, starting translation of the Intro to
Linux or Bash Beginner's Guide, and while everybody starts with good
intentions, only a minority gets through to the end, because they set
themselves dates, like "I will translate this chapter by next week, and
then the week after that I will translate the next chapter". Make sure
that you don't make these dates too tight, after all we are all
volunteers, but not too loose, either. Like "Oh, somewhere next year" is
not good.
Tille.
- --
Machtelt Garrels ####@####.####
Review Coordinator http://www.tldp.org/authors/
My Penguin, my freedom. http://tille.xalasys.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFDS5cQsIIUbMXbBA8RAmHsAJ9YzAALoFGHnxwTU7SxuZvy1oUrAACeK0t8
WfOz7jfhFhL+WytCQsOVnbY=
=2up0
-----END PGP SIGNATURE-----
