MST Clearinghouse

Sustainability American Native Non Profit Enterprises

Welcome to Maka Si Tomni Clearinghouse!  American Indian Services, Inc has operated for 34 years in the Sioux Falls community is the 501 (c) 3 sponsoring the development of Maka Si Tomni Clearinghouse.  We offer the following services: 1) Business design and planning services for 501 (c) 3. 2) Fund Raising capabilities. 3) Management, accounting and reportin ...learn more

GROUP DETAILS

Created: Mar 09, 2008

Updated: Mar 09, 2008

Membership: Open

Semi-Private

 
Created: Oct 09, 2009
Updated: Nov 20, 2009
Viewed: 47 times
Page Status: active
  •  
Not Yet Rated

Translations - SoW (Draft)

Access Privileges

Access is currently restricted to the following group(s):

 

------ TECHNICAL TO DOs ------

 

1.    Display interface in different languages
    ⁃    Track down all instances where translatable text has not yet been ported over [DONE]
    ⁃    Put in global map icon in upper right to indicate where interface language can be changed
    ⁃    Create drop down/expand menu showing languages as jpg pictures rather than characters to avoid any font issues
    ⁃    Sort out issue with database table text - untranslated, not in the LaunchPad file (i.e. Pull out tables and turn them into .yml/xml files instead)

Comment: Drop-down language menu for record language selection will stay the same, as there isn't much we can do there


    2.    Ability for any users to create content in different languages
    ⁃    Ability to select a language when a user is about to create a new piece of content

    ⁃    Allow users to change the selected language after having created a new piece of content

 

Will users be able see what different languages the content is available in - need main menu for languages? CB


    3.    User preferred language
    ⁃    Change default language to automatically match browser upon arrival to homepage. This is over-ridden by cookie set using GlobalMap.

 

    4.    Search results
    ⁃    Show results sorted by default language, followed by results in all languages

    -   Allow two-bit character searching by Sphinx by patching PHP

   ⁃    Differentiate results that are in default language versus results that are in all languages by using a divider

    ⁃    Ensure that content with new language setting is searchable by Sphinx using language selection dropdown


    5.    Browse results
    ⁃    Allow members to filter results to a single language using a dropdown

 

My preference is that rather than have no results show up - that it says 'no results in your chosen language', 5 results in English - or show the results in the other languages automatically so the search results are never blank. cb


    6.    Homepage
    ⁃    Ability to have multiple pages - we need to talk about how we are going to manage the home page when it's in multipled languages - e.g. will we have an automated home page queue to allow admins to upload relevant groups/people in their language weekly ...that would be great as the current site gets updated when we can, which isn't often enough

    ⁃    Display homepage in different languages according to language preference or based on browser language

    ⁃    Automate what is shown on the homepage to feature content relevant to specific language, Editors may be able to select what is queued for viewing


    7.    AOFS

    ⁃    Import translation of name, definition, and keywords into all languages. This may require new fields for AoFs (not sure if name, definition, and keywords are fields)


    8.    Culture

  • Images and colors: issues of comprehensibility and cultural appropriateness
  • Names and titles
  • Government assigned numbers
  • Telephone numbers, addresses and international postal codes
  • Currency (symbols, positions of currency markers)
  • Weights and measures
  • Paper sizes


    9.    Writing Conventions

  • Date/time format, including use of different calendars
  • Time zones (UTC in internationalized environments)
  • Formatting of numbers (decimal points, positioning of separators, character used as separator)

 

----  USE CASES----

Use Case 1: A non logged in user comes to WiserEarth from France and does a search

Jean is from France and visits WiserEarth.  By default the language matches his browser, which is set to French.  He sees the WiserEarth interface in French and types in a search term.

His search results could be shown in one of two ways (we will likely create some mockups and do user testing to see what works best):

Option 1)
His search results are sorted first by language, then by relevancy.  So, he will see results matching his default language first, and then a divider that lets him know there are more search results in other languages.  


So in Jean's case, Jean's search shows him results in French first.  When he reaches the bottom of the last search page, he will see a divider that lets him know search results falling below this line are search results in All languages.  GREAT CB

a) Another option is to hide the results in All languages, so that only the French set is shown.  Prefer not CB  At the end of the French search results, there would be help text (similar to Google's) saying "per your language preferences, we have only shown results in French.  To see search results available in "All languages, toggle your search options's language menu on the left hand side"

At the top of the first page of search results, Jean would see some help text guiding him to know we have opted to show him his results in French first, but if he would like to return results in all languages, how to goggle the search options panel to do so.  

Option 2) Search results are returned in "All languages" and sorted by relevancy.  Jean would see help text at the top of the search page indicating that "Your search results have been returned in All languages.  If you would like to restrict your search to show results only in your preferred language, change the language field in the Search Options panel"

 

Use Case 2: A logged-in user comes to WiserEarth and decides to change his language of preference
Jean is logging in from France, but his native language is really Spanish.  He notices the map icon on the top right and chooses "Spanish | Espanol" from the choices.  The page refreshes and he sees the interface in Spanish.   This should set a cookie on Jean's computer so that when he returns to WiserEarth, it'll remember his last chosen language and display the interface accordingly.


Use Case 3: A logged-in user comes to WiserEarth and creates a new organization profile
Jean searches for the name of an organization in French.  Does not see it, but sees the help text prompting him to create the organization listing if he hasn't found it.  Clicks on the create org wizard and sees that in the Language field for the content creation page, it's automatically been selected to match his default language.  If he had changed it to a different language, then the language field automatically matches whatever has been set in his cookie.


Comments (1 - 3 of 3)

Login to Post a Comment.
Sm_avatar

Auto-translation / machine translation

 

Do we need to use something like Google Translate to enable auto-translation of content (as opposed to interface language switching via the global map icon)?

 

This could be useful for several scenarios:

 

1. An editor monitoring content posted in a language s/he is not proficient in. Selecting from a translation menu will reduce the hassle of copy-pasting the URL to Google Translate's website.

 

2. Allowing content creator to understand discussion or comment thread with comments written in various languages.

 

3. I wonder how searching for "systems thinking" will also display pages containing that phrase written in another language? This would be useful to facilitate cross-language knowledge sharing/discovery. If our current platform can not support this, would plugging in to Google Translate's API be possible and useful? This is Google's answer for this btw --> http://translate.google.com/translate_s?hl=en

 

4. Coupled with the interface language switch, can/should we display all content to match the interface using google translate's API? Need to provide indication when/if content is translated 'imperfectly' using GT. Exception is when content language is the same as interface language, which should be detectable by the API.

 

Manual, in-page content translation

 

Are we thinking of enabling this at all in the near/far future? If yes:

  • Is there an easy way to code this? ... or integrate existing tools like Google Translator Toolkit and Ebiwrite somehow?
  • How would this effect the current SoW? i.e. is there something to prepare from the start to support this in the future?
Sm_avatar
Can you add another section (8?) on the impact of the localization for future code release? Basically, every time there will be a new code release, there may be the need for some immediate translations.
Sm_avatar
It seems like this is a great start. Shouldn't we have user case scenario for each goals? Also as we move forward, it would be great to identify the "must have" or is this basically that list?
1 to 3 of 3 Comments


Contributors to this Page