There aren't any localization for this:
- Payment method name
- Day,Month,Year string in Birthdaydate section
- Country name
- Currency name
- Language name
I think its necessary for the real localization.
What will you plan with it?
2.0 Issues, Bugs etc.
- 657
- 7576
- 10/08/2011
- United States
Csaba_20 wrote:
This is a big task, the simplest approach would be to add a new column for each of those tables and make that the resource key. Someone would need to add all those resources to the languages available. The birthday section would have to be handled differently since the values those are driven off of are probably not stored as records in the database (the user selected date is, not the available dates).
It is a good find and suggestion Csaba_20. I would guess the nop development team are aware and weighing the value added versus the other outstanding bugs/features.
There aren't any localization for this:
- Payment method name
- Day,Month,Year string in Birthdaydate section
- Country name
- Currency name
- Language name
I think its necessary for the real localization.
What will you plan with it?
- Payment method name
- Day,Month,Year string in Birthdaydate section
- Country name
- Currency name
- Language name
I think its necessary for the real localization.
What will you plan with it?
This is a big task, the simplest approach would be to add a new column for each of those tables and make that the resource key. Someone would need to add all those resources to the languages available. The birthday section would have to be handled differently since the values those are driven off of are probably not stored as records in the database (the user selected date is, not the available dates).
It is a good find and suggestion Csaba_20. I would guess the nop development team are aware and weighing the value added versus the other outstanding bugs/features.