Miriam Berg
Mega Guru

Changing field type to Translated text immediately solved the problem (same code!), and retained the HTML formatting too. Feels like there's a bug with the Translated HTML field type that is doesn't show translations properly.


I feel like this is good enough, even though it would be easier to administer the Translated HTML field.


Hi Miriam!



I am looking for same thing - could you please tell me where you changed the field type to Translated Text?  



IA


Hi Anita,



A simpler way to translate the HTML would be to user ServiceNow's built-in message functionality.



In many places in ServiceNow you show a translated message by using dollar curly brackets ${ your text here }. So instead of trying to translate text in the HTML option (which doesn't work because it is stored in a JSON field) you wrap your text in dollar curly brackets, and translate it through System Localization > Messages.



For example, if you have a very simple HTML code today, that you entered in your "HTML" widget instance:


<p>Welcome</p>


<p>Add your comment</p>



You would translate it by using the same widget instance and just change the code to:


<p>${Welcome}</p>


<p>${Add your comment}</p>



And then make sure there are translations in System Localization > Messages for each separate message:


find_real_file.pngfind_real_file.png


View solution in original post

Thank you Miriam! that worked brilliantly


olivier_queyroi
Kilo Explorer

Hi ,

Could you please inform me  where to find the local message in system localization :

Ex message  in fr : bla bla bla I do'nt arrive to reach it in the Back end

Thanks