Missing French (in belgium) on LP Translastion - openobject-addons

hello,

can anyone help me ?

thanks
mra

hello,

Can anyone solve my question ?

thank you,

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

In general, we don't create languages for which there is no definite need for them to exist. It is our understanding that it's exactly the case for fr_BE: it's basically the same language as "fr".

In order for translation effort not to be diluted on superficial differences (i.e. if someone *prefers* a different terminology and he's from a different country, that would be abusing the codes), we start with the smallest set of languages.

Chinese (Hong Kong) is different in the sense that it's entirely different from Chinese (China) because they basically use a different writing system. We've also got another similar case with Portuguese and Brazilian Portuguese (pt, pt_BR) because they use entirely different computer terminology.

So, it's not excluded that we are wrong with regards to fr_BE. If there are real linguistic reasons to have it, I'll be happy to set up a French in Belgium language. Just let me know in this question.

Hello Данило,

Basically what we face is a series of specific business terms that differ, such as the term for "refund" being different in France and Belgium. There are probably not more than a few cases like that, but it makes for quite a different experience for end-users in a Business Application.

I thought I've seen the concept of "default language" or something, where a language is said to be just a special case for another one, with a few terms redefined, and the rest inherited. Would that possible work here?

What do you think?

Thanks!

Hi Olivier, thanks for elaborating on this. In these circumstances, it's probably best to have a separate language in Launchpad. However, since then it will show up everywhere as an option, how do you feel about it being "hidden": i.e. translators would have to be instructed to "hack" the URL and replace "fr" with "fr_BE"?

I.e. to start, they'd have to go to https://translations.launchpad.net/openobject-addons/trunk/+lang/fr_BE (it works already, but French (Belgium) doesn't show up as an option until some translations are added: when first translation is added, it will show up in the list anyway).

One problem with this approach might be that uploading translations (or importing them from code branches) might not work, because our approver doesn't approve against "hidden" languages (I am not sure about this, but it'd need checking out).

IIRC the approver will still approve PO files that have the exact same file paths and names as previously approved PO uploads of the same file. Only new ones need manual approval.

Данило, Jeroen,

Having fr_BE as a hidden language works for us, as long as we can allow translators to reach the translation page with a dedicated URL and have Rosetta export the translated terms in our branches. The automatic import of the PO files is only a bonus, as we tend to use Rosetta only for updating the translations, and only update the POT in the code directly.

Thanks a lot for your help!

By the way, one last point regarding this (and then I go away :-)): is there a way to have Rosetta export automatically the default "fr" translations into the "fr_BE" PO files for all terms not explicitly translated in fr_BE?
Otherwise we'll modify have to modify our software to have a fallback language where untranslated terms are looked up instead of using the untranslated english.

Thanks!

There's no way to copy translations over directly: it would be hard to know which translations were correct Wallonian and which ones were just copied over from French and still need to be reviewed.

But the translation pages do have an option "using [language] as a guide." If you select French there, the corresponding French translations will show up as suggestions. Then all it takes is for a reviewer to approve those where appropriate.

El dc 17 de 11 de 2010 a les 11:59 +0000, en/na Olivier Dony (OpenERP)
va escriure:
> Question #131404 on Launchpad Translations changed:
> https://answers.edge.launchpad.net/rosetta/+question/131404
>
> Olivier Dony (OpenERP) requested for more information:
> By the way, one last point regarding this (and then I go away :-)): is
> there a way to have Rosetta export automatically the default "fr"
> translations into the "fr_BE" PO files for all terms not explicitly
> translated in fr_BE?
> Otherwise we'll modify have to modify our software to have a fallback
> language where untranslated terms are looked up instead of using the
> untranslated english.
>
> Thanks!
>

I don't think Launchpad can do that.

The only way to do it more or less cleanly is to use gettext fallbacks.

You'd have to test this, but I believe 'fr_BE' would already fall back
nicely to 'fr' for untranslated strings in 'fr_BE'.

If not, one can use the LANGUAGE variable to add fallbacks.

Regards,
David.

--
David Planella
Ubuntu Translations Coordinator
www.ubuntu.com / www.davidplanella.wordpress.com
www.identi.ca/dplanella / www.twitter.com/dplanella

Thank you Jeroen and David for the answers!

j'ai besoin d'une traduction en français pour tous les textes ou logiciels