User talk:Walter

From Sugar Labs
Revision as of 22:07, 29 May 2008 by Dfarning (talk | contribs) (move thoughts on wiki to the wikiteam)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

First to type on your user:talk page, what an honor. When it all seems like too much, as I'm sure it must, I've left something here that I hope you might find amusing. Cjl 20:56, 15 May 2008 (UTC)

Thought on translations

Before you spend a lot of time on translations via the translations template, consider the potential of the GoogleTrans-xx templates I'm starting to develop/deploy on OLPC wiki. Note, it will require the same plugin/extension magic-dust currently installed on the OLPC wiki to be sprinkled here before they will work.

  • GoogleTrans-en for starting from English page (example). Click on Spanish and continue browsing rest of wiki in espanol inside Google frame.
  • GoogleTrans-es for starting from Spanish page (example). Click English and see that page and any linked lang-es page in English.
  • 20-odd other variations possible

The idea is that you want to lower language barrier, but you don't want your most valuable trilingual (1 lang-en, 2 lang-xx, 3 wiki/Python/C/Linux/Sugar/etc.) assets spending a lot of time on keeping up with rapidly evolving edits. By the time a page becomes stable, it's probably too late to get meaningful input from a mono or bi-lingual non-lang-en audience (like teachers, local coders, etc.).

For wiki pages, I think that any translation now is better than a great translation later. Allows you to lower language barrier immediately (in a usually good enough manner) and reserve human translation effort for Pootle and tech-phrasing sensitive pages. Try the provided links to OLPC wiki and let me know what you think. Cjl 19:39, 20 May 2008 (UTC)

I was playing with it on the OLPC site earlier today. I agree, it is a decent compromise that is resource-efficient. --Walter 21:23, 20 May 2008 (UTC)