Translate products (and pages)

cyjem

2008-12-28 14:42

Is there a way to translate products (and maybe pages) so that the two products are associated together (eg. the one is the translation of the other and not just a product in another language)?

» Quick.Cart v3.x

beholder

2008-12-29 00:55

I have made a small mod for a customer that allows you to add a certain product to several languages AT ONCE, by a push of a button (the administrator then translates the other language later). The customer didn't seem to complain later, so I reckon the modification is working ok.

But what you want is a bit different, you probably want 2 edit fields where 1 is original lang and another is the translation. That is just too much to do, IMO.

And as far as I know, there is no way to associate the same products in 2 different langugages together. The languages could as well contain totally different products and be totally different webshops.

cyjem

2008-12-29 08:20

This is a good idea to intorduce a button for creating a product in all languages at once and translating it later. When this is the only way to *create* a product they will all have the same id and thus be easier to identify for the seller (without adding SKU-field). It will also be easier to translate into three languages than having three times N fields on the screen.
The shop should have the same products in different languages (it is for switzerland ;)

Didier31

2008-12-29 10:40

cyjem : I'm currently implementing this.
Stay tuned.

26 years of DEC support, that is a wonderful job.

beholder

2008-12-29 17:32

cyjem >> the problem is in the underlying functions that actually add and save products. They use the damn CONSTANTS instead of variables (I have no idea why this is, it should be rewritten since now it is very difficult to work with several languages at once). So when there was a certain constant used, I had to use a variable that then actually changed with language. The whole process of changing constants into variables is not difficult but it is quite elaborate considering scope of 3.2 ext plugins.

Didier31

2008-12-30 08:45

my strategy is to just remove language sensitive token in db filenames. If I succeed, all saved data will be written in unique files, whatever language the user selected.

Of course, the next step is to make the architecture, then the design language independent, but here I'm moving to an OpenSolution developper position and noone asked me at OpenSolution Engineering Group to do so :-)