-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/26/2010 04:41 PM, Ruediger Landmann wrote:
On 05/27/2010 03:27 AM, Eric "Sparks" Christensen wrote:
>
> The easy way to do this is to publish all documents in all languages.
> That way the guide would be available in English no matter if the text
> was translated or not.
>
> Of course this would mean partial translations would be published which,
> in my opinion, are better than no translation.
>
Actually, we can do it slightly smarter than that; Publican has an
option for exactly this use-case: the "ignored_translations" parameter
in the publican.cfg file.
For example, if "ignored_translations" in the Installation Guide was set
for Italian and Spanish, then when you built the book for those
languages, it would ignore any PO files available and just build the
book using the English strings. For very incomplete translations, I
think this is better than a book mostly in English with a paragraph
here-and-there in a translated language, but translation teams might
have other ideas?
So we would have to manually enter all the languages that we don't want
translated?
I can see two downsides though:
1. It seems wasteful to have multiple copies of exactly the same content
stored on the server. It will also make maintaining the site much more
difficult if the site image (web.git) grows to something like 40 times
its current size. (although this will no longer be a problem when we
move to a fully automated publishing system shortly)
Well, we should plan on that kind of space, anyway. If (when) all the
guides get completely translated we'll need that kind of storage.
2. At the moment, when you see a book in a language menu, you know that
it is translated. The situation is not so bad for widely translated
languages, but for less widely translated languages, users will click on
links and most will be in English; they might not even discover that
*any* books have been translated into their language, so the hard work
of the translation team gets lost in a sea of English.
Maybe you tint the non-translated versions down to a gray. You can see
them but they don't stand out like the translated versions.>
Cheers
Rudi
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMAEmDAAoJEDbiLlqcYamx6NsP/37U+BqiamPNQLnUGXak2k8P
uLbgcjuLq5ogLl1+3GTjhTUB6uTDWr3AOgfTr2dEQN3EHVT53edVxkK5wfOqDBgD
uDwytAJhjiZJgZTREma1QBr7hmX42S0UM4wnhUdPwH67tGp8HNsY4ZGlOPCB7pP5
obvIa0o3Inf6ZTMj21sR37Z54COk1j894Hm7WfFY0a5oF2655U+xnNZlyq17o4Z2
6qnoTHZGwYfpRDmgT9xd1hzR4ku/tpNJw38vguJntijFuHsYwPxzv0UJxKZ1jdCr
tWGqR1kuF7vgyzqNc9YO2fB5Dyh3G8Ilr6W8RoH1c11SJ1R4YumO8j7ooahNhNC/
uEd6IBPmxwXBnPtwZ0XrD1M0mRdsccMppFghqQycpKoyVgWGGPG3+Ku43YDd41FH
mnKTtnCWRF+z2jKvQkNdTfvHdwuMjeQ5q+y7PkRHfkE6YPNoZkNsA+4+DgaAq2M2
uZRLLtgxpDb21039o1/YsZdz9UJYHccEZbx/HTcPaMTb1l+CSfaqSmJSLhIwXdGR
a4cAke37vg4ex0EEeTDqg8TEq0iocfW5MKNSBXnDQdBwdrjpFuLawz12IeyUN+Bp
ZJc1vlqvdZhPpsoJYMbfgJ5xuMj7JPx+y/6QjkEJHKbhQiVSEHhz1f+75RvzkYDT
58+GwEER8+OKfQBfHvBO
=hIgf
-----END PGP SIGNATURE-----