Multilanguage website ?

I must admit that I have not really thought about taking care of multilingual issues (nor does wildkatana seem to have on the initial code) ... but what do you mean exactly with "bulk create products and translations at the same time"? Do you mean that the bulk creation form should show multiple form fields, one for each language?

Well, I wasn't so much proposing a solution than trying to figure out what you are after ... really, I think that multilingual creation (in an expedient way) should be implemented first independently from bulk creation. Then bpc could pick this up.

Which is to say: True multilingual features are likely a 2.x thing. I am interested, though, as many of the things I work on tend to be non-English sites, many of them multilingual.

Thanks for the pointers, I had not looked into multilingual issues with commerce before.

Here is what I think is the best option: I assume what one wants to do is use proper field translation, and not emulate the "node translation" process and create one product per language which are loosely tied together.
The upcoming alpha will include a small API that allows modules to intervene at various points in the bpc cycle (so as to allow modules to make other fields besides list.module fields 'bulkable' (i.e. used to generate combinations)). One such point will be after saving on submission, so as to allow modules to redirect/display some page before handing control back to bpc. It should then be easy to write a module that checks, at this point, whether there are fields to be translated and displays a form allowing you to do that. Something similar could presumably be done for the product display node creation (here I think a two-button "save" / "save and translate" approach is probably the best way to go).

The possibility I mentioned above (having multiple input fields, one per language) seems to fragile and field-specific to me (e.g. once #1046702: Product and Product display node translation status/technique is fixed, there is, presumably, no need to translate list fields on product creation, but we will still need it for text and possibly other fields).

So I guess the answer is: Not yet. Unless someone else eagerly jumps in to develop the bpc_translation module, I will likely do that myself, as I am working on multilingual sites quite often, so I do have the need myself.

Once #851812: Introducing non-list fields into the add-bulk form as "static values" shared by all created products is in (the next big thing I am working on), there will be a way to set list.module fields to be "static" in which case you can provide only a single value shared by all bulk created problems. (You can, of course, emulate this right now by just selecting only one value for a field.) Then you could a temporary way to do translation in the way you describe---have a language field and bulk-create once per language. Note, though, that then you will not be making use of any of the built-in translation functionality, and the "translations" of a product would not be linked together (except, perhaps, by having the display nodes be translations of each other---but then you cannot use bpcs nifty "save and create display" except for the first language. This is not something I would recommend, but it is one way to live.

Sorry, had not realized that you also were involved in #851812: Introducing non-list fields into the add-bulk form as "static values" shared by all created products ...

After "static" issue, multilang, what is the next step for bpc ? Edition/Deletion capacity ? :-)

Well, as you may have noticed, right now, I don't find too much time to work on bpc, so I am hesitant to make predictions ... still, I have been thinking of a way to do bulk deletion/limited edit functionality (this would be mostly edit functionality for "static" fields, for obvious reasons)---but this is something that requires keeping track of which products were bulk-created together, which is not done right now. I've been thinking that this is something I might want to get in before beta, though.

Hi friends... How can i translate the product title, description and other fields to other language??? My default language is english.. I am playing with 2 languages in my site.. Also I am stuck with taxonomy terms translation.. I am using Drupal 6 :( Please sombody help me... !

@sarath.verve: You are in the wrong place. Commerce Bulk Product Creation (and Commerce in general) are Drupal 7 only projects. You are likely using ubercart, so you should look into multilingual solutions for that.

Hi,
I do not want to hijack this issue, but it would be great if language would be a field to select on the product info, and therefore the product-displays (nodes) which are build inherit this language setting.
Now I have to update language setting all the time for my BPC created nodes.
Greetings, Martijn

Commerce bpc will use a "core like" release management, meaning that new features will go into the 2.x branch (but might be backported).