Translations and localization

[ian]

A contributor sent an Italian translation, it's in the SVN. A Spanish translation is in progress.

A bunch of text is still in the program files, I might work on moving it to the translation file this week.

[Pastus aka Alessandro]

Hi.
I'm Alessandro, the italian translator (and I hope the spanish translator starter)
If you have any question and contribution about this two translation keep in contact!

Thank you

[ian]

I'm trying to figure out some compiler directives that will help with the translations.

Basically, I want a #redefine command (not present in C30 compiler) so the default language is English, but the translation file can replace those defines. The point is to not need to add new/missing #defines to every translation file just to get it to compile.

The best solution I can up with is #ifndef TERM #define TERM "Value" #endif, but this only works on separate lines, like this:

#ifndef TERM
#define TERM "Value"
#endif

That's a little unwieldy for the translation file. I tried making a macro with macros, but the compiler didn't like that.

[ian]

I moved almost all remaining text to the translation file. The only text still in code files is in the JTAG library and self-test, which I didn't want to deal with right now.

I also made the us_EN version prettier, and removed most of the CAPS stuff.

Version RC3 nightlies for all versions are in the SVN.

[Remorilla]

I think the spanish translation needs some major corrections, and probably I work in it soon. So becouse I'm not familiar with de C30 compiler, there is any limitation with special characters?

[ian]

I committed updated Spanish compiles for v2go and v1, they're in the SVN under nightlies. We did have a problem with a bunch of spacial characters, but hopefully this fixes it. Could you let me know if there's an improvement in the character handling?

The latest Italian translation is missing OUMSG_AUX_PWM_NOTE, I don't want to update it because I'm worried about ruining the character set again.

[Remorilla]

Hi Ian, to prevent any missing message I'm using the en_US translation file as guide, is that right?
Your request me about the improvement of the character handling, is not posible to compare right now becouse all the special characters used on the previus translation were wrong (I think the italian keyboard map, used by Pastus, can't handle the spanish characters) so you'll need to wait for the first revision (perhaps today).

Also, when done, how can I upload the file?

[ian]

@remorilla - Yes, the en_US version is the one used for development. It has the latest text definitions.

You can click 'reply', and select more options to attach a file to your post in this forum. You can also email it to me, or I can give you SVN access if you want to use it.

[ian]

The Spanish translation should be better now, new compiles for v1 and v2go are in the SVN nightlies folder.

We should try to fix the character set on the Italian translation if it is still having problems. Remorilla and I found that the best way to send the translation file in correct and plain ASCII is to send it in a plain text e-mail.

[Scorpia]

not sure if it help but i also found a good way to send txt files unmodified was to zip the .txt file.

not sure why they get modified when they are attachments but they sure seem to.

[yaba]

This is my translation to Portuguese (Portugal)
Feel free to change if you consider it's not correct.

[ian]

Thanks yaba, I'll get this into the next version and make a Portuguese compile.