Show posts
Can't think of anything really easy.
If you only have a few languages perhaps you could add all the model names for each language in the model field and pick out the appropriate one before you use it? (You would have to extend the size of the products_model column in the database to use this technique as it's only varchar(12) by default).
Another possibility could be to use the product custom fields to store these. A possibility would be to store some kind of structure (perhaps XML?) that held a model name for each language. You can save these in custom fields - but you may need to extend the size of the chosen column in the database.
Another possibility would be to use the first 12 characters (or whatever you choose) of the product description where there is always one for each language.
Another possibility would be to introduce a new level of indirection by looking up the model name for the required language using what you place in the model field as the key. You would have to create a table with columns model-key, language-id and model-name yourself. You would have to also write some custom code to look up these values at the appropriate times by these things are all possible - Check the User Guide for details on all the various customisation techniques.
If it all seems like too much trouble why not just use a code for the model that would be acceptable in all languages and put anything that's language specific in the product description. This would seem to be the simplest approach.
If you only have a few languages perhaps you could add all the model names for each language in the model field and pick out the appropriate one before you use it? (You would have to extend the size of the products_model column in the database to use this technique as it's only varchar(12) by default).
Another possibility could be to use the product custom fields to store these. A possibility would be to store some kind of structure (perhaps XML?) that held a model name for each language. You can save these in custom fields - but you may need to extend the size of the chosen column in the database.
Another possibility would be to use the first 12 characters (or whatever you choose) of the product description where there is always one for each language.
Another possibility would be to introduce a new level of indirection by looking up the model name for the required language using what you place in the model field as the key. You would have to create a table with columns model-key, language-id and model-name yourself. You would have to also write some custom code to look up these values at the appropriate times by these things are all possible - Check the User Guide for details on all the various customisation techniques.
If it all seems like too much trouble why not just use a code for the model that would be acceptable in all languages and put anything that's language specific in the product description. This would seem to be the simplest approach.