[phil65]

since nox 3.0 is released on official repo we can only change the translations when the bugfix release actually got released. (or can they co-exist next to each other without problems? )

[Martijn]

Co-exist.

Not yet sure how skin/add-ons will be handled concern the translation 'teams'.
There is on for xbmc and it can handle different releases.
Perhaps they will be added as sub project or they need their own

[frodo19]

Hello BN/phil65: Hungarian lang updated! THX

"Click here to start download from sendspace"

http://www.sendspace.com/file/dq7g4x

[PatOso]

Spanish strings. Please Update.

http://www.sendspace.com/file/t8l130

Thanks.BN/phil65

[ferent]

Spanish strings. Please Update.

http://www.sendspace.com/file/t8l130

Thanks.BN/phil65

Hello Patoso, I've change some tags in your file, please test.

http://www.sendspace.com/file/07c46c

[PatOso]

Some accents and phrases don't adapt well to the skin.
I take note of the rest.
THX

[frodo19]

Hello BN/phil65: Hungarian lang updated! THX

"Click here to start download from sendspace"

http://www.sendspace.com/file/t7kpz8

EDIT BN: Updated - thx

[Rififi77]

Hi,
update French translation for AEON NOX-3.0.0-pre

strings.xml

@+

EDIT BN: Updated - thx

[filthycatbox]

Are any non-latin alphabet languages supported in this skin?
I'd like to write a translation for one.

[Roman_V_M]

Are any non-latin alphabet languages supported in this skin?
I'd like to write a translation for one.

Non-Latin in general? Does Cyrillic count?

PS. I'm currently playing with transifex.net that is planned to be used for translation of XBMC core language files after moving to PO format, and I actually found out that it can also be used for XML language files too with some caveats that do not affect the result - you can still use all transifex features and get XBMC-compatible XML language files. It's actually a good system. Not great, though, professional CAT tools are still much better, but it is free for open source and simple to use. So maybe it is worth to start Aeon-Nox translation project on transifex.net?
The caveats I've mentioned are the following:
- The English strings.xml should be in utf-8 (AFAIK not a problem for XBMC). Then you can link the source English file on github to transifex, and it will be updated automatically with latest changes that become visible to translators.
- Since transifex.net does not support XML directly, the source files should be parsed as XHTML.
- An XML header and comments are stripped in translated files.
- Downloaded translated language files will have XHTML extension, so you need to change the extension to XML and add a proper XML header:

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

Then the translation files can be used in XBMC.
After moving to PO, project maintainers will need to add a source English PO file, and new PO translation files will be automatically populated with previously completed translations, so no need to repeat the job.
And yes, translators won't need to type already completed translations manually all over again on transifex. They can simply upload their language file and translation on transifex will be automatically populated from the file. They will have to add only missing strings, if any.

[PatOso]

Update Plis.

http://www.sendspace.com/file/b58gn1

[Roman_V_M]

BTW, what does the following string in 3.0 mean?

Code:

<string id="42007">Press RIGHT to select path to wall viz</string>

What's the context?

[CutSickAss]

You have to press RIGHT to choose the folder of the wall visualization, I think.

[PatOso]

Update again, please.

http://www.sendspace.com/file/1z1x6q

[phil65]

Update again, please.

http://www.sendspace.com/file/1z1x6q

added. thx.