out of the box servicenow provide 22 langugae and romanian language is not their, and we want that language in out production so what steps we can approach

[shweta urmaliya]

out of the box servicenow provide 22 langugae and romanian language is not their, and we want that language in out production so what steps we can approach.

[Musab Rasheed]

Hi Shewtha,

Check this below link

https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/localization/task/self-localize.html

Regards

[scott barnard1]

Hi Shweta

We also use Romanian and Slovakian languages that are not supported by SN. You can add new languages to the platform but it involves a lot of data to be updated.

So there are some thoughts to have before you start.

1. Will this be for process users as well as end users. End users see very little of the back office and you can avoid a lot of work if this is end user only.

2. You will need to be aware of all of your customisation's on the main forms.

3. Custom notification email scripts can prove problematic to translate as they process as system and not a user. This can be handled but check if you use them

4. Pay careful attention to your portals and any custom widgets that you have.

So under the System Localization menu there is  Languages.

You will need an Entry here for Romanian. The text direction will be left-to-right and it needs to be active. You need an ID and I suggest that you follow the standard and use "ro".

SN makes language packs available infrequently and they will appear in the data source table. There is a transform map for each of the translation tables. (These appear in the System Localization Menu)

Translated Name / fields

Messages

Field Lables

Choices

Translated text   

So if you look at the Polish language pack as an example you will see a data source that will stretch to circa 200k records. If you want to to a complete translation you need to cover all of these records AND all of your customisation.

Personally even back end users tend not to use all of the system so we used the I18N Debugging feature to identify all of the main use translations and assembled them into a set of sheets and employed a couple of graduate students to populate the sheets. Then you can either update manually, or use SN transform maps

So you end up with 5 sheets 1 for each transform map. To make it simpler use a template from the import set table.

Regards

[Alex Coope - SN]

@shweta urmaliya,

I can confirm that we don't provide a Language Pack for ootb UI translations in Romanian. However, we have a whole bunch of resources that will help you with what is often referred to as "Self-Localization".

We have a dedicated CSC page with a bunch of materials available here. The Globalization Guide is our maintained list of what is translated ootb into what languages. We also have a fully training path on NowLearning to teach how UI translations work in the platform. And we also have a dedicated forum here on community that goes into some very technical aspects, where I post quite frequently,

As a starting point, check this post specifically to give you an idea of what you go through,


Many thanks,
Kind regards