Re: [RFC] i18n and documentation
On Fri Jun 14 at 00:40 +0200, Denis Barbier wrote:
> A. Requested features
> ======================
8) Layout and contents shouldn't be mixed
Translator shouldn't bother of layout code changes. If author
adds a class attribute to a HTML page because they want that
spcific paragraph to be displayed in red, translator should
have no work to do.
9) Reader should be warned of outdated translation
If a translation is not sync'ed on the original doc, the reader
should be warned by mean of a message in their native language
and provided of a link to the original text.
> B. Examples
> ============
WML used in Debian site provides a way to dealt with multiple languages
HTML pages in the way described in (7) (see lang module).
Some time ago I had a chat with one of the TP robot mantainer. Here it
is what I think about the writing-translatin-reviewing cycle.
Basically, there are three actors, from my point of view, that play
their role in translating a document:
1. the author
One or more people who wrote a document. Their aim is to see their
document available to anyone and translated to as many languages as it's
possibile. They should commit their work and get back (after a while
;-) the translated versions. It'd be good if the server would put the
transltaed documents there where the author wants to.
2. the translator
Most probably a team of people whose aim is to translate a document from
one language to another. They pick up a document from a list of
documents, translate it and commit back to the server. They need a
person as a coordinator and like to be notified of new document
versions.
3. the reviewer
To assure a good quality of translation, any document should be cheked
by one or more people who speak the language the document has been
translated into. This avoids the most common mistakes and a more fluid
translation. The reviewer likes to be notified of new translation, too.
In the middle of these three group there are the documents
hosted/managed by a server.
Documents are written as text, plain or formatted (HTML, SGML, LaTeX,
and whatever your immagination suggets). A document comprises one or
more files, each of which has got one or more authors, one or more
translators per language, and one or more reviewers per language.
The server should be able to provide administration facilities to all
the three actors: user subscription, document subscription, new version
notification, group coordination.
--
email: L.Cappelletti@mail.com
Jabber: lolo@tipic.it
Homepage: http://www.ir3ip.net/~iw3axl/
Fingerprint: 8CDD 3408 53B2 6122 99DA EE37 1523 68FC D906 4C08
--
To UNSUBSCRIBE, email to debian-i18n-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: