History: Collaborative_Multilingual_Terminology

View page Show All Versions
Source of version: 142

When completed, this profile will allow a group of users to collaborate on creating a multilingual glossary of terms for a site. This kind of glossary is invaluable to help with the translation of content, and ensure consistent use of terms and their equivalents.

The profile will essentially emulate the HTAGlossary site:

* http://htaglossary.net/

However, as of 2009-06-01, it is not ready for prime time yet.

{maketoc}

!Features & settings
{CODE(caption=>YAML)}
instructions: Get Started with Multilingual Terminology
preferences:
# The whole thing is based on the wiki feature
 feature_wiki : y

#
# Pages for a term must be available in multiple languages
#
 feature_multilingual : y
 feature_translation: y
 feature_multilingual_one_page: y
# Not sure we need the following Two. Quantify changes in particular...
# feature_urgent_translation: y 
# quantify_changes: y 

# User preferences needed so users can specify 
# the languages they are interested in.
 feature_userPreferences: y


#
# Page title only displayed once, so we can't use page title
# to display the term. Instead, ask the user to enter the
# term on the first line.
#
# Actually, as of 2009-06-10, Marc said he will ask LPH
# to make all titles be displayed. Once that is done, will 
# change that feature back to  y.
#
 feature_page_title : n
# Disable that once LPH has made requested change to displa
# titles in all languages
 feature_wiki_description: y

#
# So site can send out email messages to users?
#
 feature_messages: y

#
# Categories can be used to specify domains for terms.
#
# As of 2009-06-10, Category Objects lists all the 
# pages that are tagged with a category. This is WAY too
# long, and takes too much screen real-estate. Need to 
# change code to make list of pages optional
#
# Could also use categorypath, but it is only displayed for
# the first language at the top, and we need it displayed
# for all languages.
#
 feature_categoryobjects: y
 feature_categories: y
 categoryobjects: y
 categorypath: n

#
# Not sure what this is....
#
 wiki_edit_plugin: y

#
# Comments can take too much real-estate. Translators
# mostly want to see the term in source language, and
# its equivalent in target language, and they need
# to visually parse the screen efficiently
# So make comments invisible unless the user
# clicks on it.
#
 feature_wiki_comments: y
 wiki_comments_displayed_default: n

#
# Do we really need freetags?
#
 feature_freetags: y

# Need to be able to search for a term
 feature_search: y

# Enable user watches
 feature_user_watches: y

 feature_print_indexed: y
 feature_mytiki: y

 wiki_comments_displayed_default: n
 wikiHomePage: Get Started with Multilingual Terminology
 allowRegister: y
 validateRegistration: y
 auth_ldap_adminuser: y
 auth_ldap_adminpass: y
 validateUsers: n

 

{CODE}


!Modules
{CODE(caption=>YAML)}
objects:
 -
  type: module
  ref: module_semantic_links
  data:
   name: semantic_links
   position: right
   groups: [ Registered ]
   order: 10
   
 -
  type: module
  ref: module_search_box
  data:
   name: search_box
   position: right
   groups: [ Registered ]
   order: 15
 -
  type: module
  ref: module_quick_edit
  data:
   name: quick_edit
   submit: Create Term
   position: right
   groups: [ Registered ]
   order: 20
  -
    type: module
    data:
      name: last_modif_pages
      position: right
      order: 1
      groups: [ Editors, Registered, Admins ]
 -
  type: module
  ref: module_since_last_visit_new
  data:
   name: since_last_visit_new
   position: right
   groups: [ Registered ]
   order: 30
 -
  type: module
  ref: module_switch_lang
  data:
   name: module_switch_lang
   position: right
   groups: [ Registered, Anonymous ] 
   order: 25
{CODE}

!Wiki

This is where we include some wiki pages
{LISTPAGES(find="collaborative_terminology_platform")}{LISTPAGES}
collaborative_terminology_platform_include_module


{CODE(caption=>YAML)}
objects:
  -
    type: wiki_page
    ref: collaborative_terminology_platform_include_get_started_with_multilingual_terminology
    data:
      name: Get Started with Multilingual Terminology
      lang: en
      content: wikicontent:collaborative_terminology_platform_include_Get_Started_with_Multilingual_Terminology_include
  -
    type: wiki_page
    ref: collaborative_terminology_platform_include_admin_page    
    data:
      name: Admin page
      lang: en
      content: wikicontent:collaborative_terminology_platform_include_admin_page
  -
    type: wiki_page
    ref: collaborative_terminology_platform_include_register_and_set_your_languages
    data:
      name: Register and Set your Languages
      lang: en
      content: wikicontent:collaborative_terminology_platform_include_register_and_set_your_languages
  -
    type: wiki_page
    ref: collaborative_terminology_platform_rss_feed
    data:
      name: RSS feed
      lang: en
      content: wikicontent:collaborative_terminology_platform_rss_feed
      translations: [ $collaborative_terminology_platform_fil_rss]
  -
    type: wiki_page
    ref: collaborative_terminology_platform_fil_rss
    data:
      name: Fil rss
      lang: fr      
      content: wikicontent:collaborative_terminology_platform_fil_rss
  -
    type: wiki_page
    ref: collaborative_terminology_platform_wiki_engine
    data:
      name: Wiki engine
      lang: en      
      content:wikicontent:collaborative_terminology_platform_wiki_engine
      translations: [ $collaborative_terminology_platform_moteur_wiki]
  -
    type: wiki_page
    ref: collaborative_terminology_platform_moteur_wiki
    data:
      name: Moteur wiki
      lang: fr      
      content:wikicontent:collaborative_terminology_platform_moteur_wiki  
  -
    type: wiki_page
    ref: collaborative_terminology_platform_tagging
    data:
      name: tagging
      lang: en      
      content:wikicontent:collaborative_terminology_platform_tagging
      translations: [ $collaborative_terminology_platform_taggage]
  -
    type: wiki_page
    ref: collaborative_terminology_platform_taggage
    data:
      name: taggage
      lang: fr      
      content:wikicontent:collaborative_terminology_platform_taggage

{CODE}




!Permissions
{CODE(caption=>YAML, wrap=1)}
objects:
 -
  ref: Multilingual_Permissions
permissions:
 Anonymous:
  allow:
   -view
   -comment
   -wiki_view_comments
   -post_comments
   -search
   -search_categorized
   -view_categories
 Registered:
  description: Will be ignored because group is already created
  allow:
   -view_categories
 Editors:
  description: Can edit & delete all content
  allow:
   -edit
   -rename
   -admin_categories
 Admins:
  description: Have all rights
  allow: [ admin ]
{CODE}


!Questions to answer

* How do I set up the glossary profile and make it multilingual?
* How do I create a glossary entry in say, French?
* Given an entry in say, French, how do I create the corresponding entry in say, English?
* How do I avoid reinventing the wheel? For example, say I create a French entry for word X, and then want to create the corresponding entry Y in English, but someone already created Y, how do I find out about it and tie the two together. In particular, what happens if the existing Y is a very slight variation on the Y that I am currently trying to create (eg: I am creating the verb form, whereas the existing Y used the noun form)?
* I don't want to change an entry... just comment on it.
* How can I respond to someone else's comment?
* Can I create an entry in French that has more than one English equivalent?
* How do I create a domain hierarchy?


!Unmet needs at the moment

Below is a list of needs that are not well met by the profile, with ideas for how to address them.

!!Need to support more than one equivalent for a term

A term in English like "web browser", will often have more than one possible equivalent in French. For example, "navigateur web" or "fureteur web". When looking for an equivalent to "web browser", I want to see all equivalents in French.

How to do this?

One possible solution is to have page "Web browser" have the most common equivalent "Navigateur web" as its "translation" into French, but list "fureteur web" as a synonym on the page for "navigateur web". 

That will work if we are looking for an equivalent for "web browser". You will find "navigateur web", then see at the bottom of that page that it can also be said as "fureteur web".

But what if I am looking for an English equivalent for "fureteur web"? I would then go to the page "fureteur web", and see that it doesn't have a "translation" (because "web browser" is the translation of "navigateur web", not "fureteur web".).

So, how to deal with this.

A possible solution would be for the search "fureteur web" to be made not only on the page name, but also on the synonyms sections.

BTW: THIS IS REALLY CRUCIAL FOR TRANSLATORS!

^__TODO-LPH:__ 

One possibility is that if you create a synonym in a page, but that synonym does not have its own page, then you would automatically create a blank page for it. Ex, on the "navigateur web" page, I create a synonym link for "fureteur web", eventhough there isn't a page for that yet. When I save "navigateur web", the system automatically creates a blank page for "fureteur web". And we activate the synonyms module, so that if I search for "fureteur web", I get a blank page which lists on the right "navigateur web" as synonym. I can then go to "navigateur web" page and find the equivalent "web browser".

Another possibility would be for the search to search not only in the page name (i.e. the title), but also the synonyms. So if I search for "fureteur web", it would find "navigateur web", I would click on it, and see "fureteur web" in the list of synonyms. So I would know that the translation of "navigateur web" is what I am looking for.

The first solution should probably do the trick for now.
^

For this to work, the user has to be able to see a list of "back-synonyms". For example, on page "navigateur web", the page "fureteur web" has been labeled as a synonym. But the page "fureteur web" is an empty one, and does not specify that IT is a synonym for "navigateur web" (in other words, no __explicit__ backward synonym relation from "fureteur web" back to "navigateur web", just an __implicit__ one). So, if I look for a translation of "fureteur web", all I get is a blank page for that term, with no indication that there might be a translation for it on the page "navigateur web".

But Marc tells  me that there is a module which can display the synonyms of a page (whether specified on that page or on the pages for the synonyms). So, need to activate it.

^TODO-AD: Activate the module to list synonyms of a a page.

See above for reasons why.
^

!!Term should only be specified once

At the moment, you have to use the Description field to enter the type, and to re-enter that term as the name of the page, without accented characters. This is a real pain. Who wants to specify the same term twice? Also, when you rename the page, you have to remember to rename the description also.

My understanding is that this choice was made to avoid having accented chars in the URL. But this hack does not garantee that folks won't enter the page name with accented chars, so it does't really help. In fact, my own experience with that is that the pull of wanting to enter the term (with accented chars) as the page name is really strong, and that even I (AD) forget to not do it.

I suggest we go for an approach where the page name for the term IS the term (with accented chars). In any case, Tiki is smart enough to do URL encoding of the URLs. And most browsers are smart enough to render them prperly in the URL box (i.e., accented chars will appear as accented chars in the browser's URL field, eventhough internally, they are store as %nnn url encoded chars... also, when you copy from the browser's URL field, what gets copied is the %nnn version, not the version with accented chars). Worst case scenario is that some people will see the URL with URLEncoded characters %nnn in the browser's URL box, if their browser is not smart enough about this. But who cares...

One problem with this design is that at the moment, if you go to multilingual page and ask for "all" languages, you only see the title of the "main" page. So, you only see the term in the "main" language. So, need to modify the code so that when "all" languages are chosen, we see the title of all language versions.

^__TODO-LPH:__ Modify the code so that when "all" languages are chosen, we see the title of all language versions..^

!!Shouldn't have to always say I want "all" languages

Right now, everytime I look at a term, I have to re-select "all" languages in the picklist. This is really annoying.

^__TODO-LPH:__ Modify code so that the user's choice of language in the picklist is persistent.

In other words, the language the page is displayed follows the following pecking order:
* Last choice of language made EXPLICITLY BY THE USER by clicking on the language picklist (including the possibility that "all" was selected).
* User's language preferences set for that site in her profile
* User's language preferences set in Firefox

Actually, rather than "all" languages, there should be an option "my languages". If I only speak Fr and En and Es, then I only want to see those 3, not the other 15 languages that may be supported by the site.
^

!!Need to search only on the term name

Say I search for the term RSS feed. Then I only want to find terms that have RSS feed in the term itself. If the entry for a term has RSS feed in the definition of the term, I don't want to have it in the hits (at least, not unless I have asked for a full text search).

^TODO-AD:
Apparently, this can be done as follows:
* Can do this by replacing the Search module with a QuickEdit module configured to search.
* Seems all I need to do is change the action parameter of the QuickEdit module to tiki-index.php (according to LPH).
** http://doc.tikiwiki.org/tiki-pagehistory.php?page=Module%20quick_edit&diff_style=sidediff&compare=Compare&newver=3&oldver=2
* Also, change the label of the QuickEdit module to "Find term".
^

!!Need a quick summary of all target language equivalents for a source language term

When searching for a target language equivalent for a source langauge term, translators need to make a decision quickly, without having to do too many mouse clicks. The current approach of having a term associated to various equivalents through synonyms is awkward, because even the user may need to browse through a series of Source language synonyms, before he finds the one which is associated to a target language equivalent.

One way to deal with this woudl be to have a multilngual terminology module which would show the equivalents of the term in the langauges spoken by the user.

For example, assuming the user specified Fr and En as her languages, and if she is looking at the page "Web Browser", the module would display:

^__Equivalents__
''e'': list of English synonyms for "Web Browser"

''fr'': list of translations for all English synonyms to "Web Browser", and French synonyms for all those translators.^

This terminology module might have forms to carry out the basic terminology tasks:
* Search for a term
* Create a term
* Terminology Help (woudl poitn to the Get Started with Multilingual Terminology page)

^__TODO-LPH:__ Create a terminology module as per the above description.^
!!Recherche limité à une langue donnée

Sinon, il risque d'y avoir des conflits entre des langues similaires (ex: terme qui s'écrit pareil en italien et en  français)


!Misc Todos

* Make it so that comments are invisible by default 
** Pofiling of that feature  does not seem to work.
** For now, just added instructions on the admin guide telling them to do this manually.


* Forms for searching a term, creating  a term, should always be visible
** Right now, you have to go to the Home Page to see them.
** Would be better if they were modules visible at all times.

* First paragraph of the profile should provide a plain English description.

* Put comments in the YAML stuff to document the various decisions made.


* Refactor the instructions pages into one long page called "Guide to collaborative multilingual terminology creation". The guide will have a section for Admins, and a section for Editors.
** Section for editors comes first.
** Section for editors talks about:
*** Searching for a term
*** Creating a new term
*** Creating an equivalent for a term
*** What to do if a same word can mean different things (create different pages which are more explicit, ex: tag -- dog plaque, vs tag -- metadata).
*** Tracking certain pages or the whole site
*** Using categories for domain classification
** Section for admins talks about:
*** Finalising the installation
*** Keeping abreast of new users
*** Approving new users
*** Tracking the whole site

* The guide should provide instructions about using categories to assign domains.

* We should have a template for new terminology entries
** According to this: http://doc.tikiwiki.org/tiki-index.php?page=Module+quick_edit, parameter templateId  allows you to specify a template to use. How do I create such a template?
** Looks like this is how you create a template.


* Guide  should provide instructions about how to manage users.
** Ask for email notification of new users.
** Move new users from Registered to Editors soon after registering.
** What are the different groups and their permissions.

* Guide should bring users attention to the __Last changes__ module as a way to keep track of what others do. Also, explain the page tracking feature.




* Guide should mention breadcrumbs feature.


* Should editors be allowed to control addition, deletion of categories?
** Editors should definitely be allowed to assign categories to pages. But should they be allowed to create new categories, or delete existing ones?

* The guide should provide instructions about how to deal with the situation where a same word can refer to different things. For example, Tag can refer to metadata, to a markup element, or to a dog tag. The solution is to create pages with slightly different names, for example "tag -- metadatat", "tag -- markup", "tag -- identity plaque".

* Add page tracking, and provide instructions in the guide.

* Guide should provide instructions on how to track the whole site (not just individual pages)

* Make it so editors can view history.

* Make it so editors can revert changes.

* Make it so that Anynoymous can see comments (only enabled for admins at the moment)

* Activate breadcrumbs.

* Have a standard template for terminology entry (ex: synonnyms, etc...)

* Make it so that the guide is available in French and English.

* Put a new users dashboard for admins, so they can move new users to the Editors group.

* Limit term search to a particular language. 

* Need language indicator in front of the term in the list of equivalents. Ex: fr: Fil RSS, en: RSS feed.

* Need to prevent users from creating page names that have accented chars in the name. 
** See discussion below about transliterating page names.

* Test profile with non-admin users. Make sure that:
** Can view entries
** Can edit entries 
** Can view history
** Can revert change
** Can track pages
** Can post comment
** Can assign categories
** Anything else?
History

Enable pagination rows per page
Advanced
Information	Version
Wed 17 of Jun, 2009 11:04 GMT-0000 alain_desilets	160 - 163
Wed 17 of Jun, 2009 10:10 GMT-0000 alain_desilets	155 - 158
Tue 16 of Jun, 2009 17:59 GMT-0000 alain_desilets	152 - 154
Tue 16 of Jun, 2009 15:54 GMT-0000 Marc Laporte	150 - 151
Tue 16 of Jun, 2009 13:28 GMT-0000 alain_desilets	148 - 149
Mon 15 of Jun, 2009 20:41 GMT-0000 alain_desilets	147
Mon 15 of Jun, 2009 18:57 GMT-0000 alain_desilets	143 - 146
Mon 15 of Jun, 2009 12:32 GMT-0000 alain_desilets	*141 - 142*
Thu 11 of Jun, 2009 19:23 GMT-0000 alain_desilets	137 - 140
«
1
…
16
17
18
19 (current)
20
21
22
…
25
»
Latest Changes

...more
Like almost all *.tiki.org sites, you can log in with your login from https://tiki.org (register over there)
Search

Most Popular Tags

admin agenda alias antibot antibot captcha app archive articles banning batch blogs calculations calendars cart categories cluster codemirror comments computation contact us datachannel debug debug console dropdown with other error messages features file galleries forums geo geocms geolocation group homepages group watches header i18n images item link items list jquery languages location map maps maths menu menupage multilingual ol3 ol5 openlayers paypal plugin plugin alias plugin datachannel plugin fade plugin tabs plugin trackerlist pretty trackers print project management r r project realnames rss static static text statistics stats structures syntax highlighter tablesorter template trackers user watches visualization watches webservice wiki wiki argument variables wiki structures
History: Collaborative_Multilingual_Terminology

Source of version: 142

History

Menu

Current Profiles

Latest Changes

Search

Most Popular Tags

About Tiki

Community

Documentation

Support

Development

Legal

Tiki Project Sites

Networks

History: Collaborative_Multilingual_Terminology

Source of version: 142

History

Menu

Current Profiles

Latest Changes

Search

Most Popular Tags

Tiki Newsletter

About Tiki

Community

Documentation

Support

Development

Legal

Tiki Project Sites

Networks
