Hi Paul,
On Fri, Sep 26, 2008 at 9:17 AM, Paul Libbrecht <paul(a)activemath.org> wrote:
Hello Youcef,
Le 26-sept.-08 à 02:42, Bey Youcef a écrit :
I installed the
"xwiki-workspaces-distribution-hsqldb-1.0" version with
windows installer. As I'm using XWiki since many years, I'ven't faced any
problems with new versions.
But I'm trying to find the application resources that you pointed out in
your mail. I couldn't found them. May I have to download and install them
to
get the localized version.
It's in (webapps)/xwiki/WEB-INF/lib/xwiki-core-xxxx.jar
I think that it's easy for you to expand this jar, copy the properties
files there to WEB-INF/classes and edit them there.
I believe a restart is needed at every change.
Note that you can also define in the administration-settings XWiki
documents that are resource-bundles, they will override the things below.
Somewhere close to these settings you can also define the supported
languages (and define whether it's multilingual!).
Thanks so much.
Translating all strings is time-consuming, the best way thus to get quick
idea about the arabic localization is MT (Machine Translation).
The MT can be used for the experimentation.
Another important things related to its localisation, It is known that
localization is not only limited on the
translation of resources files
(Key=Value). The process is little bit more complex: How about the
consistency between documents and GUI strings and those of the system
messages?
XWiki tries its best... it is not fully achievable though depending on the
availability of content.
Ok.
How about the translation of installation Wiki pages? They are not
in the resources! For example, where could we
find strings of the main
pages
when XWiki is installed for the first time?
The web-pages are content, they are wiki-editable.
Once multilingual, your wiki always offers you the possibility to translate
a page at editing time, that's what you want to use.
This mean that the end-users have to translate these pages? I don't thing
so! Not all of them are translators or willing to translate.
The localization, once done, it must be done for all text in documentation
and GUI.
[...] The encoding of these files are not UTF-8, then how it will be
possible to
manage multilingual content by shifting from one language to another
during
runtime?
You definitely should make sure everything is utf-8 (e.g. in xwiki.cfg).
Note that IRIs are not fully achieved though so document names with some
arabic letters will give very ugly URLs (and may often fail) (note: URL is
not title!).
For some old legacy reasons there are still xwiki distributions that run
other encodings, in particular iso-8859-1, but you should not take these in
account or?
There's one more dimension of Arabic translation
which may byte and I am
interested to see if that one is doable:
left-to-right layout.
I do not think XWiki developers have considered it thorougly thus far and
only a good translation first approach can see what are the limits. The
velocity files may need to be changed I think.
Thank you very much.
I'll let you know as soon as I do progress.
-- Youcef