- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2018 10:40 AM
I am in the process of translating our service portal to French and German. I have most of complete, except translating the service catalog items.
I need to translate sc Categories, sc Catalog Item, sc Order Guide and sc Category Page. I know that it's a string and I need to put the translated phrase in Messages. Do I need to do anything else?
sc Category Item page displays forms. Variables on these cat items also need to be translated.
Any ideas?
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2018 09:43 AM
I finally finished all translations on our portal...
The easiest way to determine how to translate variables and variable choices on a form is to r-click the variable and go to 'show'. (You may have to do this on the catalog item, record producer, etc) When you do this, it tells you the table, field name (element) and which type. Type determines whether you put your translations in 'Translated Text' or 'Translated Name / Fields'.
When putting translations into Translated Text, you have to determine the correct document. I added a couple of fields and was able to find the correct document each time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2018 11:44 AM
Hey cindylove,
As per my knowledge the only way for translations using messages i.e.. internationalization(i18).
just a hint: if you gonna translate the new Service Portal, you can do it by switching the language, similiar to Service Catalog and Catalog Item translation. But these translation wont be transported with Update Sets. So you have to do it on Prod again.
Please refer:
I18N - Knowledge internationalization
Thanks,
Rajashekhar Mushke
Rising star : 2022 - 2024
Community Leader -2018
Connect me on LinkedIn : Rajashekhar Mushke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2018 02:34 PM
Hi Rajesh,
Thanks for the articles on Internationalize a widget and I18N - Knowledge internationalization. These articles seem to have some useful information.
The big issue is finding the portion of the server script to update. We've found a way to update the Name and Short description on SC Catalog Item. We're working on the ability to translate SC Categories. Both of these have to update the server script and add the translation in the Messages table.
I'm currently working on adding translations for annotations in the forms. It seems to a be a laborious task. I wish there was more straightforward documentation on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2018 09:43 AM
I finally finished all translations on our portal...
The easiest way to determine how to translate variables and variable choices on a form is to r-click the variable and go to 'show'. (You may have to do this on the catalog item, record producer, etc) When you do this, it tells you the table, field name (element) and which type. Type determines whether you put your translations in 'Translated Text' or 'Translated Name / Fields'.
When putting translations into Translated Text, you have to determine the correct document. I added a couple of fields and was able to find the correct document each time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2018 11:12 AM
All the language translations were put into update sets and moved from one instance to another. There were no issues with that.