Hi Stephan,

As part of answering your intial question I also raised this request to the Studio product team for inclusion in their future planning.  I will feed back when I have something to report but for the forseeable future only 2011 packages can be created via the API.

Stephan

While it seems to be useful to do this, I would like to draw your attention onto the fact that this capability is limited and should only be used for a (hopefully short) transition period. It should not become standard to create 2009 packages from within Studio 2011 because this is only a kind of workaround wiht limited functionality.

A 2009 package created in 2011 will open in Studio 2009 and will allow the user to translate the files contained in it using the Editor. However, he might face problems when trying to preview some of the files or save them as target. This is due to the fact that the conversion filters used in 2011 are not fully compatible with those installed with Studio 2009. This means that the "Save as target" needs to be done by the package creator once he has received the return package.

I think this limitation and the provisional character of the function will not justify the development of an API for this.

Walter

Okay, I thought it would just be a little thing to add a single method to the API. But if any client will ask for that I can tell him about the limited possibilities. Thanks.

Hi there,

Just to chime in from a product management perspective - in addition to what Walter said it is likely that this integration will be typically picked up by 2011 users (so 2009 packages won't be a problem). We are seeing very significant traction with users picking up Studio 2011 so by the time we are starting to offer the integration it will in all likelihood not be regarded as a limitation/issue. Having said that it is always good to see user feedback - and if there will be significant pressure from the field then we can take another look if needed. The expectation is that this is unlikely, however.

Thanks,

Daniel