Hi Jim, On Mar 6, 2008, at 11:10 PM, Dowson_Jim(a)emc.com wrote: Sure. See http://platform.xwiki.org/xwiki/bin/view/Features/I18N Thanks -Vincent

But also note that: - XWiki supports interwiki links, like Wikipedia does, meaning that you can install several instances of XWiki, put interwiki links in the document content, and create a panel that lists these links. - Better than that, XWiki supports virtual wikis, meaning that the same server and the same XWiki instance can host more than one wiki at different addresses (like en.company.com, fr.company.com, de.company.com) and linking between them is really easy, without any additional setup, instead of linking to [Some.Document] you link to [fr:Some.Document]. You can also write a snippet that creates automatic links if a document with the same name exists in another wiki, something like: foreach existing wiki, if wikiprefix + ':' + this document's name exists, then write a link to it - Even better, you can write an RelatedDocs XClass, so that the links are not written in the document content, but in attached XObjects. And a custom panel can be used to display these objects as links and add a new one. In many ways, XWiki is much more powerful than mediawiki. It just requires some knowledge about how to master it. Ludovic Dubost wrote: -- Sergiu Dumitriu http://purl.org/net/sergiu/

Hi Jim, Yes it is by clicking the language link at the top that you switch languages. Then your prefered language will be remembered in a cookie. You can try this from a user perspective on http://www.xwiki.com Ludovic Dowson_Jim(a)emc.com wrote: -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

Hi Jim, On Mar 7, 2008, at 12:10 AM, Dowson_Jim(a)emc.com wrote: I've updated it on http://platform.xwiki.org/xwiki/bin/view/Features/I18N . I hope it's better now ;) Thanks -Vincent PS: Guys, it would be cool if we all had the habit of improving the documentation before answering to someone so that the time we take in writing the email with the answer is actually spent on improving the doc since that'll help everyone at the same time without costing much. If we can do this for all user's questions we'll have rock solid documentation on xwiki.org ;)

On Mar 7, 2008, at 9:24 AM, [Ricardo Rodriguez] Your EPEC Network ICT Team wrote: Yes this is true for objects. There's no translation system for objects and since Panels are objects there are no translations for them. However it's possible to find workaround. One possibility is to have one object per language and write some script to choose the correct panel. -Vincent

Vincent Massol wrote: Thanks Vincent. I have adopted the first strategy (better, just a number of if/then structures in the panel code) here: I have to deliver a small sample supporting panels in several languages by Monday. I will then try to catch up with Sergiu proposals. I can't go ahead with XWiki here without a solution to this issue. Of course attachments and comments will be quickly required if we get solved panels... Cheers, Ricardo -- Ricardo Rodríguez Your EPEC Network ICT Team

On Mar 7, 2008, at 10:56 AM, Guillaume Lerouge wrote: BTW this is all documented here: http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica… -Vincent

Guillaume, Sergiu, Vincent, all, Thanks for the tips. Nice stuff! Please, just to be sure I am correctly understanding how bundles and ApplicationResources_??.properties files. 1. I can use $msg. to get strings defined/declared in a document included in ... 2. I can use $!msg.get() to call strings defined in ApplicationResources.properties or ApplicationResources_??.properties files from any *.vm. It is not possible to use $msg. because how *.vm are parsed. I think these are two easy questions... for whom know how does XWiki work! I am on my way :-) Thanks for your help, Ricardo -- Ricardo Rodríguez Your EPEC Network ICT Team