Re: [Dolibarr-dev] Shipping statuts, Demand Reasons are hardcoded.

[Destailleur Laurent]

"put them in llx_c table with unique key, and
      use this key for translation."

This is the good direction.
The key to use must be the "code" field into llx_c.
And translation should be with a key
XXXXX_ZZZ=text translated

where XXXX describe the dictionnary and ZZZ is the code

However, this should be already done like this for demande reason, shouldn't it ?

For shipping status this is different. It can't be inside a dictionnary table because status there is business code and user interface reacton that depends on status. So this can't be free.

2011/8/16 CF <address@hidden>

Hello,

I need to change the demand reason (propal) and shpping status (need to add one).

I notice demande reasons are defined in dict.lang, while shipping status are hardcoded.

I was ready to put them in a llx_c but i wonder if there are hidden goals (especially in using dict.lang file) and how you want i code this change.

My first approach: put them in llx_c table with unique key, and use this key for translation. Any objections ? :)

_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev