Translations

Hi all.

A short one to inform you that, to my advice, the french
translation is complete and opened to constructive criticisms.
Some problems may arise from commonly adopted
anglisisms like shaders and morphing, not to tell about
"Load".

I would like to see it and other recent translations
included in the coming 0.9.1 release to extend
the audience.

Cheers,

Louis

A short one to inform you that, to my advice, the french
translation is complete and opened to constructive criticisms.

Great!

Some problems may arise from commonly adopted
anglisisms like shaders and morphing, not to tell about
"Load".

Are there places were the strings for translation need more context to
avoid anglicism? We can add “hints” that one means “open a file” vs.
another meaning.

The problem is that as native English speakers, we usually make the
mistake that all the strings are the same. :slight_smile:

I would like to see it and other recent translations included in the
coming 0.9.1 release to extend the audience.

It will certainly be in the upcoming 0.9.2. I checked Launchpad before
the 0.9.1 release, and synced recent changes today. I’ll continue to
do that until we have a more automated solution.

I’m hoping that as we get closer to 1.0.0, we can have a “string
freeze” to let translations catch up with development. There will be a
few changes soon because I’m throwing out a lot of non-visible strings.

Thanks!
-Geoff

Hi Geoff.

The problem is that as native English speakers, we usually make the
mistake that all the strings are the same. :slight_smile:

In my opinion, the real problem is that English speakers tend to
use perfectly meaninful shortcuts that require lenghty translations,
in french especially. This may cause display problems in menus.
Nothing to propose about this.

Are there places were the strings for translation need more context to
avoid anglicism? We can add “hints” that one means “open a file” vs.
another meaning.

This is another problem. People tend to use english terms in french
text.
I have a “québecois” bias. Sorry. It may well be preferable to keep
"shader" for instance: it would carry more meaning to many than
"ombrage",
whose choice I am uncertain about.

I’m hoping that as we get closer to 1.0.0, we can have a “string
freeze” to let translations catch up with development. There will be a
few changes soon because I’m throwing out a lot of non-visible
strings.

This is another issue. It would require allerting translators that new
strings need attention. A mailing list ?

Anyway, a great coming beta release!

Cheers,

Louis