26 Sep
2008
26 Sep
'08
10:33 p.m.
Bey Youcef wrote:
Hi Paul,
On Fri, Sep 26, 2008 at 9:17 AM, Paul Libbrecht <paul(a)activemath.org> wrote:
Using such a in-wiki document is helpful while building the resources,
as you don't need to restart the container every time you change the
document, changes are automatically reloaded. After you are satisfied
with the translation, you can place it in an
ApplicationResources.properties file.
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.
Translated content can also be made available for download, but not as
ApplicationResources files, but as importable .xar archives. Currently
we are not distributing translations of the wiki content, since we don't
have enough stable contributors to maintain the translations up to date,
and these files tend to change quite often, since we are refactoring
both the underlying java platform and the applications that make up the
wiki content. Once we will have pretty stable content, we will consider
translating each application, not as a whole big package, but each
application on a time.
However, if you manage to translate most of the content, you will be
able to upload it on code.xwiki.org, so that other users can use it.
Another important things related to its localisation, It is known that
Ok.
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. How about the translation of installation Wiki
pages? They are not
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.
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. > [...] 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?
The encoding of the files is pure ASCII, but it uses unicode escapes to
cover the whole unicode range (see
http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html#100…
and
http://en.wikibooks.org/wiki/Java_Programming/Syntax/Unicode_Escape_Sequenc…),
which means that you should write the file with any character, then use
native2ascii to transform non-ascii characters in the file to their
equivalent unicode escapes.
> 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.
We have considered this issue, but unless we have some external
contributions in this area, it is not a priority. The changes are not
substantial, most of the interface is ready to be displayed R2L, there
are some CSS fixes that are needed, and a few template corrections where
things weren't properly done.
Thank you very much.
I'll let you know as soon as I do progress.
-- Youcef
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--
Sergiu Dumitriu
http://purl.org/net/sergiu/