instructions: Guide de l'utilisateur-- profil de terminologie collaborative
preferences:

# The terminology MODULE is designed specifically to work
# on sites where the terminology PROFILE has been installed.
# Preference terminology_profile_installed is hidden and cannot
# be set using the Tiki UI. It can only be set by a profile.
# So, by setting this preference here, we tell the Terminology
# MODULE that the terminology PROFILE has been installed.
 terminology_profile_installed: y

# The whole thing is based on the wiki feature
 feature_wiki : y

# OK to here

#
# Pages for a term must be available in multiple languages
#
 feature_multilingual : y
 feature_translation: y
 # So you can see a term and its translation on same page
 feature_multilingual_one_page: y
 # So users can specify the languages that they 
 # speak
 change_language: y
 # Terminology entries are very short and are usually
 # translated in one go. So no need for the Incomplete 
 # translation notice. That way, users don't have to 
 # do extra operations to erase it, which means they
 # can translate an entry faster with fewer clicks.
 feature_translation_incomplete_notice: n

# OK to here.

 # Support insertion of translated string in wiki markup
 wikiplugin_tr: y


#
# For sites with less than 4 available languages, include all languages
# in the preferred language list. Additional languages will be added at
# the end of the list.
#
 language_inclusion_threshold: 4

# OK to here.

#
# Wiki link format; characters that can be used with Wiki link syntax: ((page name)).
# Since terms will be as wiki pages, let's permit the maximum.
#
 wiki_page_regex: complete

#
# Enable templates, so we can provide user with
# templates for terminology entries
#
 feature_wiki_templates: y

# OK to here.

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

# 
# We need to enable the syntax (alias(aliasname)), so 
# that users can specify that a particular term 
# can be said in different ways.
#
# For this to work, we need both the semantic links 
# AND the backlinks features to be enabled.
#
# AD (2009-10-05): also, automatic redirection 
# (feature_wiki_1like_redirection) must be enabled.
# It's supposed to be enabled by default, but AD had
# some problems with it (it seemed to be deactivated
# after profile installation).
#
 feature_backlinks: y
 feature_semantic: y
 feature_wiki_1like_redirection: y

# OK to here

#
# In tiki-listpages.php, we want to see the language.
# 
 wiki_list_language: y

#
# Page title is the term, so it should be displayed
#
 feature_page_title : y

#
# When we try to access a page which has been aliased to
# two different pages, we want the system to ask us
# which of the aliased pages to go to. This is what
# feature_likePages is for.
#
 feature_likePages: y

#
# Showing source is not very relevant for terminology (unless there is lots of wiki content)
#
 feature_source: n

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

#
# Allow users to undo changes history
#
 feature_wiki_undo: y

# OK to here

#
# Use nicer theme
#
 style: strasa.css

#
# 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

#
# Disable the standard search feature. Users should employ
# the Terminology module to search for terms. 
# When standard search feature was enabled, we found users
# had a tendancy to use that one instead of the Terminology
# search module.
#
 feature_search: n

# Enable user watches
 feature_user_watches: y

 feature_print_indexed: y
 feature_mytiki: y

# OK to here.

##
## Support voting on equivalents for a term
## AD: Not sure which of those features are actually needed.
##     Still experimenting with different voting mechanisms
##
# feature feature_polls: y
# feature_wiki_ratings: y
# wikiplugin_proposal: y
#
##
## Need a forum for asking terminology questions
##
# feature_forums: y 
#
##
## Hum... shouldn't we validate users?
##
# validateUsers: n
# allowRegister: y
# validateRegistration: y
# auth_ldap_adminuser: y
# auth_ldap_adminpass: y
#
##
## Set home page to the terminology help page.
##
# wikiHomePage: User Guide-- Collaborative Terminology profile
#
##
## Often, it can be useful to put a picture of the thing
## a term refers to.
## This section defines how images will be managed.
##
# metatag_imagetitle: y
#