CS logo  Bandwidth:  hi / med / low   

Visit the Surf Shop!   
   Home    Register    CouchSearch!    My Profile    Messages    Groups    Events    Chat75     Info    Login    
Big PictureParticipateMissionStatisticsWikiContact UsAmbassadorsDonateCollectives

Translation Team Wishlist

The statements and opinions on this page are solely those of its authors and do not necessarily represent the official position of CouchSurfing International.
Translation - Translation guide - Missing languages - Multilingual

Please update this list with your ideas! Include a link to the relevant group thread. If you're unsure how complicated some things are to be done, please leave them unsorted.

Contents

Short Term

  • Have our major bugs resolved - See Translation bugs/features in Mantis
  • Expert Team Description (Eli is on it)
  • Finish updating languages in the general drop-down menu [1]
  • Reorganise/update wiki [2]
  • Priorize and get a tool to priorize pages to be translated. [3] [4] The tool could then give the pages to be translated by priority in the tool. More ergonomic for translators !
  • Give the CUQ Team the heads up and the info they need to collaborate with us efficently
  • Translation guide

Medium Term

  • Ability for members to select default language version: for example, an only French speakers member should have possibility to have his default homepage in French translated version of CS. [5]
  • Locking fields after translations & confirmation to avoid direct over-translations without agreement of the whole translation team --Perilisk 23:32, 16 September 2008 (EDT) Tested the function with Benjamin. Lots of bugs, especially with the translation in context. Would have to be explored more before being put in a bug. [6] [7]
  • For a first translation, make the translation "to be confirmed" appear on the site anyway, while the confirmed one shall be locked. To challenge a confirmed translation one would post about it in their language sub-group. Reason: better to have a poor translation than none !
  • Ability to rebuild all pages at once automatically every couple of months.
  • Ability to rebuilt pages that we can't see. --Perilisk 23:32, 16 September 2008 (EDT) Reported in Mantis
  • Get a list of pages changed recently (see if it's worth rebuilding !) and a rebuild button incorporating both steps.
  • Get Stats about the use of the translated version of the website
  • An Icon on translaters' profile
  • A place to put a timestamped note next to the translation, so that you can communicate sources and reasoning to other translators. [8] [9]

Long Term

  • Search engine to find all occurrences of a word within translated pages of the website, and incorporating the results into a translation page for direct viewing & editing. [10]
  • Access to the translation tool via language-specific group --(Perilisk 19:18, 12 August 2008 (EDT) Not feasible easily according to Jim Stone)

--Perilisk 14:37, 21 September 2008 (EDT)This could tackle Eli's concern: nobody would need to call themselves Expert in a language to translate in it, but rather be part of the appropriate group. Therefore no need to assess your language skill to be expert in that language. A step towards quality management ?

Unsorted

  • Ability to translate contents which are on the wiki instead of being cutted in fragments through translation CS tool. (In fact, tool to find where wiki contents are). Related to the fact that we can't translate some pages on the website [11]--Perilisk 13:13, 21 September 2008 (EDT)Now reported in Mantis [12]--perilisk 20:37, 24 October 2008 (EDT) The more it goes, the more we think of this as a priority [13].
  • See previous translations (at least the last 2 or 3) displayed in the translating tool main view without having to click on a link. [14]
  • A better way to recruit in Translations Team
  • Finalize characters bug fixing and figuring out if there are any bugs with chinese translation again
  • Include questions about the need for a translated website in the next quarterly questionnaire ? Would make it easyer to prioritize languages and assess the needs.
  • Figure out how to deal with translators of poorer quality. Peer review ? Team Leader review ? How to approach them ?
  • Make the Terms of Use translatable [15]

Wishes Granted

  • Get a techie for the Team. [16]
  • Hide languages from tool (prevents accident translation of the wrong variety of language). [17]
  • Tool providing with the Activity Stats of all members of the Translation - General (for Language Ninjas)
  • Add Translations to the Volunteer Dashboard [18]
article history edit