Posted by
Robin Millette on
Mar 27, 2006; 2:03am
URL: http://civicaccess.416.s1.nabble.com/trying-to-finish-up-tp374p399.html
On 3/26/06, Stephane Guidoin <
[hidden email]> wrote:
> Here is want I'll try to do :
> - I asked Robin if we could modify the template easily to add a small navigation menu (like what they add on their FACIL website. A navigation menu would help to sort the content and could solve a part of the content organization problem we have.
Should be doable, I'll try and find the time tomorrow to take a better
look at this.
> - The language issue really p*** me off. I'm french (not french canadien/quebecer) so my opinion may not be representative : to me many french canadians might be able to understand that we don't have a lot of resources to translate all the content and when we want to bring people from all over the country, english is the language. We try to put some content in french as we can. Then we should put to much emphasis on french. For example, the title of the page (which is also the URL) must remain in english only (and simple).
First, we have to make a disctinction between the wiki and website.
Generally, I prefer english only URLs and the content in whatever
language the browser/user requests. For the wiki though, using
moinmoin, we don't really have a choice to distinguish the language of
the page, mostly because of the nature of wiki words.
> - Language auto-detection : The wiki software has this ability. When a french-configured browser arrives on the website, the wiki provides the webpage "Page D'Accueil (
http://www.civicaccess.ca/wiki/PageD%27Accueil) which is for the moment forwarded to the common frontpage. We could remove that forward and copy the french version to the "Page d'accueil" page. In fact it's already done but I leave the french version in the FrontPage for the moment.
Yes, with moinmoin, you specify the language of each page at the top.
Then you have another page (a dictionary) enumerating all the pages
and their language equivalents. I think, with a little prodding, we
can keep both official languages mostly up to date. At the very least,
we need the infrastructure now to support it. If we can't keep up with
the content in two languages down the road, we can revise our position
then or double our efforts.
One last note about the wiki / website distinction. If, like FACIL, we
pick a wiki as a tool to edit our website collectively, we will get a
website in the end, and not something that looks or smells like a
wiki. I'm not saying we have to use a wiki for our website, far from
it. Whatever tool we pick, it should let more then one person edit the
content, and wikis are pretty good at that, regardless of the content.
--
Robin 'oqp' Millette :
http://rym.waglo.com/Président de FACIL :
http://facil.qc.ca/