Martyn Houghton Posted October 2, 2018 Share Posted October 2, 2018 I am in the process of implementing services for a number of different languages and testing via the Customer, though I know I need to add customer translations for elements we specify, but some of the 'standard' elements in the portal are not translated. Example below, the customer's language is set to French. I am presuming there is some manual translations required to be specified in the settings for these standard elements to be translated, but I had expected these to have been included. Also do the default translation get updated as part of builds? i.e. as more of us use the platform in different languages, is the default content updated? Cheers Martyn Link to comment Share on other sites More sharing options...
Steven Boardman Posted October 2, 2018 Share Posted October 2, 2018 Hi @Martyn Houghton The Portals certainly support the languages you have enabled on your instance. You can manually provide the relevant translation for each language for each translation string, or in the admin console you can do this for the different apps that you use and for each language using the Translate Missing button for each language and app - this will be much much quicker. This will go off and use google translate to automatically translate all the translation strings. You can of edit and amend individual translations strings for any which you disagree with google on Recalling of course that service names / catalog items, faq's, progressive capture custom form fields, stages and checkpoints on business processes etc need to be translated manually. Hope that helps Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 2, 2018 Author Share Posted October 2, 2018 @Steven Boardman Thanks for the quick response. The Translate Missing option is failing. This is similar to the error message we have logged a support incident for as we get this when trying translate individual timelines. Looks like something might have changed in Google API? Cheers Martyn Link to comment Share on other sites More sharing options...
Steven Boardman Posted October 2, 2018 Share Posted October 2, 2018 @Martyn Houghton ok, i can see that and replicate it, let me see if there is an issue with the google translate key... Link to comment Share on other sites More sharing options...
Keith Stevenson Posted October 3, 2018 Share Posted October 3, 2018 All, Thanks for the posts. Unfortunately, this (the 400 error) is due to a unannounced change in a Google API service we utilise, the inline translation of comments returns a unexpected error (400). We have now made a change to resolve this, which is working its way through our deployment strategy (https://wiki.hornbill.com/index.php/Continuous_Delivery). Until then the translate option may not function as expected. We will inform you once the fix has been pushed to live. Kind Regards 1 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 3, 2018 Author Share Posted October 3, 2018 @Keith Stevenson Thanks for the update. Any rough idea of timescales? Cheers Martyn Link to comment Share on other sites More sharing options...
Keith Stevenson Posted October 3, 2018 Share Posted October 3, 2018 @Martyn Houghton Thanks for the reply. We can inform you that from dev to live usually takes around 72 hours. Kind Regards Link to comment Share on other sites More sharing options...
Keith Stevenson Posted October 9, 2018 Share Posted October 9, 2018 @Martyn Houghton We can inform you that this was released last night and your instance updated. Kind Regards Keith Stevenson Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 9, 2018 Author Share Posted October 9, 2018 @Keith Stevenson Thanks the for update. We are now processing the translation of Service Manager and Collaboration for our different languages we will be supporting. Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 9, 2018 Author Share Posted October 9, 2018 @Keith Stevenson Not sure it is just a blip, but now getting an different error after successfully translating a for a number of different languages, in this case for German. Cheers Martyn Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now