Being able to bulk download and import XLIFF files is great!  If we have multiple product tags, is there a way to select the applicable product tag? 

Yes ​@mmarques the product tag selector will be as is at the top in the header section.

Any thoughts on the permission and “on px” localization, which can allow translators to be given access to localizing on PX itself. Users with only localization permission will be able to access the page and update translations.

I love this idea! It would be great if we could toggle this when viewing a list of engagements rather than going to a different section (not sure if this is intended use case or not!)
 

1. What are you excited about? Which feature will help you the most in your workflow?
   1. This is going to help us massively understand where we are with each tour/guide and focus our efforts of localization of others
       
2. Would you prefer localization through an in-app section or use external workflows for it? How does a CSV file impact it?
   1. in-app section would be great! We use a tool called Smartcat to help with translations currently -- would be great if we could integrate that tool with this
       
3. How often are translations done by external vendors? Would you be comfortable sharing the content directly? What verification/approval workflow do you follow?
   1. It’s really a mix depending on workloads. Sometimes we have resources to do it in-house, at times it needs to be outsourced to an external vendor. (Smartcat helps with this as well). We then get a native language speaker to give it a quick once over before we push live
       

Overall I think the design is great - would like to see which are live and published vs not as sometimes we will go live with English first, and then other languages gradually over time.

​@JayS we would love your feedback on this!

This looks great! I agree with ​@aaronhatton’s comment that “it would be great if we could toggle this when viewing a list of engagements rather than going to a different section.”

1. What are you excited about? Which feature will help you the most in your workflow?
   1. I like the color-coding of the language’s progress. Would also like to see which languages have been published versus in-progress.
   2. Would there be a horizontal scroll if there are additional languages? Our products are translated into more than 12 languages now.
2. Would you prefer localization through an in-app section or use external workflows for it? How does a CSV file impact it?
   1. I’m not sure. We currently use the integration with CrowdIn for translations, so don’t do any of that work directly in PX.
3. How often are translations done by external vendors? Would you be comfortable sharing the content directly? What verification/approval workflow do you follow?
   1. All of our translations are currently done using the integration with CrowdIn. Our local-market associates review/correct/approve the machine translation that is completed by CrowdIn.
   2. Using CrowdIn, being able to bulk download and import XLIFF files would be great, as mentioned by ​@mmarques 

​@woodlande, would love your feedback as well.

cc: ​@cunninghams ​@parryk 

​@jmobley  -- will any of this fix the mal-formed XLIFF files? The most essential element for us is to be able to download the xliff files so they can go through machine translation. Numerous posts on the community complain about the formatting, and we have also provided examples. I like the hub, but if the XLIFF is bad then I don’t think it helps very much. Examples:

1. What are you excited about? Which feature will help you the most in your workflow?
   1. Being able to see the localization status of all content is great. Also being able to bulk export and import will help us a lot.
   2. Will the translation status change automatically - how?
   3. How to publish and see what has been published?
   4. It would be nice to see both when the source text was modified and when the translations have been modified.
2. Would you prefer localization through an in-app section or use external workflows for it? How does a CSV file impact it?
   1. I prefer using external workflows because I want to use external CAT tools to leverage the translation memories. Editing translations in-app would not update the translations to the translation memories.
   2. The current XLIFF format does not work well. It would be good to see how the CSV looks like. At least sentences should not be concatenated, and there should be a way to hide the html tags.
3. How often are translations done by external vendors? Would you be comfortable sharing the content directly? What verification/approval workflow do you follow?
   1. We outsource all translations to an external vendor. Sometimes we need to edit the translations in-house.
   2. Sharing the content with external vendors is not necessary, but it might be handy in come cases to share the content for translators to see the context.
   3. We use the QA tools within the CAT tool. In PX, after importing the translations, we do simple review to see how the translated texts look like in the UI. Is the Preview functionality supposed to be used for that purpose?