Great, I like this new feature. I suppose it is a new feature for all the SF editions? (except for the SBS)
Maybe another service to consider is http://www.icanlocalize.com?
Question: how will this be integrated with the current localization, e.g. Labels & Messages? If this will be integrated, then it will make translating static text etc. much more easy with XLIFF editors.
In Sitefinity we are starting the work on a Translations module, which will ease the collaboration with external translation agencies. The module will included ability for XLIFF export/import and direct integration with external translation services.
We are ready with version one of the wireframes, and will be happy to know what you think about the proposed solution. Are there any specific requirements or requests, which you would like us to address?
We look forward to receiving your feedback!
Updated on 1st April, 2015
Users can enable Translations modules per site and get the ability to:
TRANSLATION PROCESS (PAGES)
This section queues items ready for translation so that they are sent together. There:
For consideration, if you are doing this for all sitefinity data types (pages, news, events, module builder types), can you consider a generic import/export function as well?
We have just had to migrate from an old site (which had to be re-created, not upgraded for a variety of reasons), and the inability to export and reimport ANYTHING was a huge impost, and we had to write a lot of code to do this in a custom way.
It seems to me that this kind of function will cover a lot of the underlying technology stack to enable this to be a feature. It's not completely the same, so sorry if this is slightly off-topic.
Will there be a provider model for this so that we can plug-in our own translation service?
Also, is this just for pages, or will other content types be included?
I updated the original post to include a revised version of the wireframes (above).
As to your questions:
@Daniel, at this point the plans are to include the feature in Enterprise edition only. We are considering providing sample for integration to translations.com but we can review http://www.icanlocalize.com as well.
We have no plans to cover Labels and Messages in this iteration. However, I will log this task for future plans.
@Turnos, export/import is a very popular request and we will consider it for
@ Craigm the architecture will allow the easy plug in of other translation services. Most content types will be supported (we used the examples with Pages for illustration only)
Thank you all for the feedback, it is highly appreciated!
I agree with Daniel...localization is available out of the box everywhere, to lock this just to ENT is a crap deal. We already have to pay for the translation service, do you really need another feature to sell ent...
At the very LEAST could all versions get export/import...common