Translations

Andrew Whitworth wknight8111 at gmail.com
Thu Dec 16 15:10:53 UTC 2010


As part of GCI we have several translations of README available now,
many of which are being kept in branches until we figure out where to
put them. I would like to discuss that topic here.

I would like to create a folder docs/translations/ to hold
translations. That way we don't fill up the root and other important
directories with a million translations of things. So we would have a
folder structure like this:

docs/translations/fr/
docs/translations/ru/
docs/translations/pt/
docs/translations/pt-BR/

...and so on. We can talk about how to organize dialects like pt vs
pt-BR. I have no particular opinion on whether we want each dialect to
have it's own folder or to utilize subfolders. Either approach would
work fine in the short term and it would be easy enough to change back
and forth if we wanted.

In each translation folder, we can have translated files. Translations
that have not been reviewed by a native speaker can be suffixed with
".DRAFT" to mark those things that we haven't verified. Once something
has been verified by a native speaking dev, we can drop the ".DRAFT"
suffix.

So what I would do right now is move some of the existing translations:

README.espanol -> docs/translations/es/README.DRAFT
README.deutsch -> docs/translations/de/README.DRAFT
README.polski -> docs/translations/pl/README.DRAFT

This also gives us a convenient place to dump new translations that we
receive of any file, not just README.

Another thing I suggest we do, and soon, is add a clause to the
english README to say that only the English version of the
documentation is "official", and translations might be up-to-date.
Then we make sure that this clause is included in any translated
README to set the tone for all other documents which may be
translated.

Input welcome.

--Andrew Whitworth


More information about the parrot-dev mailing list