Re: [Dolibarr-dev] Translations fallback language

Hi all,

Marcos : you mean MAIN_FEATURES_LEVEL ? Users could wish to use dev feature but not to see that a translation string is not set.

I’m agree for a fallback language and also a dev constant which disable the fallback. In fact, should be great that not found string are displayed in red. You could easly see it ;)

I’m also agree with Charles for decreasing “woodoo” setting ;)

Have a good day

Cedric

De : address@hidden [mailto:address@hidden De la part de Marcos García
Envoyé : mardi 5 août 2014 13:20
À : Posts about Dolibarr ERP & CRM development and coding
Objet : Re: [Dolibarr-dev] Translations fallback language

What about using the actual constant that shows the development features instead of creating a new one?

Regards,

Marcos García

address@hidden

2014-08-05 12:20 GMT+02:00 <address@hidden>:

I have added on the wiki global option

http://wiki.dolibarr.org/index.php/Setup_Other#Global_options

the description of the language override MAIN_FORCELANGDIR

Global option is a method for lazy guy – so good developer, but they give to Dolibarr a picture of “made for insiders“

And too much hidden option make we don’t know it all

Propose for the next version of Dolibarr to create some additional setting screen and decrease the option to only dangerous setting…

Bien cordialement,

Charles-François BENKE

De : dolibarr-dev-bounces+charles.fr=address@hidden [mailto:dolibarr-dev-bounces+charles.fr=address@hidden] De la part de Doursenaud, Raphaël
Envoyé : mardi 5 août 2014 11:02

À : Posts about Dolibarr ERP & CRM development and coding

Objet : Re: [Dolibarr-dev] Translations fallback language

Hi Charles,

Thanks for you input.

I like the idea of having a DEBUG_TRANSLATIONS configuration entry to only display tokens.

Language override has already been discussed here : https://lists.gnu.org/archive/html/dolibarr-dev/2014-04/msg00000.html

Maybe it is of interest for you.

Cheers,

2014-08-05 10:46 GMT+02:00 <address@hidden>:

When i develop, i prefer see the translation token but when I’m in production see a default translation if exist is better

Maybe add a DEVELOP_MODE_DISPLAY value to select the desired display and maybe some other debugging infos

Other thing about the translation, add a specific langfiles for personal translation

If the file exist, we load it at last and use the value inside instead of classical used value

Like this we stop to change value in the langfiles

Bien cordialement,

Charles-François BENKE

De : dolibarr-dev-bounces+charles.fr=address@hidden [mailto:dolibarr-dev-bounces+charles.fr=address@hidden] De la part de Doursenaud, Raphaël
Envoyé : mardi 5 août 2014 10:25
À : Posts about Dolibarr ERP & CRM development and coding
Objet : [Dolibarr-dev] Translations fallback language

Hi all,

When using a language for which translations are unavailable, Dolibarr displays the translation token instead (At least in external modules).

It would be better if it used a fallback language instead (let's say en_US) so it displays human readable informations instead of -sometimes- cryptic tokens.

What's your take on it?

Cheers,
--

Raphaël Doursenaud

Directeur technique (CTO)

Expert certifié en déploiement Google Apps

+33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10