Ubercart

This is really just a limitation of i18n in Drupal 5 (not sure about D6). User defined strings like that aren't easily translatable, if at all. I know others have made it work in the past, so there might be something in the forums about it, but I really wouldn't know where to point you.

Hmmm, and what about the idea to display the attribute in a t() function.

It should be available for translation in the locale module, even if it's a variable that you get in the database isn't it ?

Well, that technically would work, but it really is just a hack. The function is only supposed to be used with string literals, and we're trying to stick to the coding standard on issues like this.

Hmm I see,

I will try to search for a viable solution, there is a way to create different attributes for different translations, but I really don't like this way to proceed. You will lost possible synchronization between translated nodes when you edit stock etc.... and it can be easily become impossible to manage if you have a shop in 8 different languages.

I will try to look further with that issue, there is certainly a drupal friendly way (at least provided by i18n or drupal 6) to do that.

Hi,

And it is the same deal with the header of tapir tables column or is there a way to translate them ?

It not, I think this needs a solution with D6 (don't know if it's a part of internationalization battlepan) but there are a lots of little things like that that are hell for multilingual website.

howdy, this is almost a full stop to the attributes_module on multilingual stores... anyone any solution? I've been looking anywhere but attributes / options translations do not work yet... : (

help really appreciated, thx!

PS: Ubercart 2.0, Drupal 6.x

Hey Ryan!
Could you have a look if the following would be a good solution for ubercart i18n?
Keyword-based translation system
This is not meant as a finished solution, but rather as a starting point. Imo the existing Drupal i18n features suck for user-defined strings. So, maybe you can give some feedback and help push this forward.

It would allow to translate attributes, options, payment options, and all the user-defined strings.

File "uc_store.module"

string "$pattern = variable_get('uc_weight_format_'. $unit, $defaults[$unit]);"

change to

"$pattern = t(variable_get('uc_weight_format_'. $unit, $defaults[$unit]));"

))

and translate attributes

Hi
It seems great.
But after that where and how do you translate attributes and options ?
I cant find my options labels while searching in 'translate interface'... No match.
Is there a .po we need to edit or smth like this?
This problem is very annoying : chinese customers wont understand options and I'll become poor...
I cant believe there is no way to translate attributes and options in such a great tool.
It must be very simple, I think.
Please Mr Uber

Could you please merdekiti let us know how and where, after doing this mod in uc_store.module you'll, then, 'translate attributes'.
Please