i uploaded a newer version of Translator

this is still just a preview, even it would do most of the planed tasks.

translator_20040412 (application/zip, 172 KB)

Features (so far)
* form based editing of message.properties files
* translation of filebased skins
* storing notes for default skins
* store whether a skin should be translated
* treeView of source files including highlighting of status
* progress bar (jsut for skins)
* basic version control

(this messages was also posted on the [antville-dev] mailling list. so you may track the discussion there.

i uploaded a first version of a future antville translator application. the goal is to provide an easy to use web interface for translators, so they don't have to mess around with .properties and .skin files.

Download:
translator_20040404 (application/x-zip-compressed, 158 KB)
Update: (incl. skin translation)
translator_20040403b (application/x-zip-compressed, 161 KB)

Screenshot:


please don't check the code - it's a mess so far. but you may test it to get a better idea of what i'm working on.

WHAT I HAVE DONE SO FAR:

-->
i started to change the directory and filename structure. (this is a proposal)

instead of l10n we could also name this "localzations" or "lang" or "languages" or "translations"

every directory within l10n that matches ab || ab-AB(C) will be detected as a new language.


app/ --> the = apps/antville most of the time
app/l10n --> the localizations
app/l10n/en --> a two digit language code
app/l10n/en-US --> which may be followed by a country code
app/l10n/en/messages.properties --> language property files always have the suffix .properties
app/l10n/en/skindescriptions.properties --> there may be more than one language.properties file
app/l10n/en/admin.properties
app/l10n/en/skins --> skins may also be translated
app/l10n/en/skins/Story --> prototype name
app/l10n/en/skins/Story/edit.skin --> skin file


-->
as michi proposed i did start to split up the messages files and renamed them to always use .properties as the extension. the advantages are obvious:

* messages.en & co don't just contain messages any more
* files become more handy and readable
* there is the possibility of "extensions" properties files
* your editor will recognize .properties files by it's extension

-->
i also moved the skin files to the localization directory

* i would propose to move .skin files away from code (as gobble does)
* with res.skinpath it's very easy to switch between language versions, and to collect the right skins (you don't need to)


TO DO:
-->
there is no support for skin translation yet!

-->
i'm thinking about an TranslationItem prototype, which would keep track of changes and updates, which can't be stored within the files. (creator, modifier, accepted, versions, ... )

matthias

please post comments to the mailling list.

Hi,

I write following code:

In message.zh: error.test = "someChineseWords"

and

in hac: res.debug(getMessage("error","test"));

It doesn't show Chinese words, some secret code. But if in .hac,

res.debug("someChineseWords");

It shows well...

Maybe getMessage cannot detect encoding...

Hi,

I would like to translate antville into Chinese. I translate some .skin files and message file. I create a message.zh file and use UTF-8 encoding.

It loads .skin files well, but cannot read message.zh file.

I use AntClick package and runs under Windows 2000 box.

Hallo,
gibt es eine komplette deutsche Übersetzung und wo finde ich die?
Danke!

... und zwar einer, endlich mal hier einen Text unterbringen zu können :-)

Hier der Vorschlag, "Du-Anreden" bei den antville-messages zu vermeiden. Weil das in der sandbox nicht richtig dargestellt wird folgt hier das Ganze als Word-Dokument:
antvilleGermanNo_du (application/msword, 32 KB)
und als Textfile (mit unix-linebreaks)
antvilleGermanNo_du.txt (text/plain, 9 KB)