Decode HTML Entities when importing XLIFF file

Is there any way to tell Crowdin to decode HTML Entities when importing XLIFF file? So to see raw symbols like > instead of > in editor during translation phase but then encode them back when downloading translations?

Hi Tudzer! The thing is that it’s a default behavior that those symbols are considered as tags and are converted like that. During translation in Editor, you may use the Copy Source button and just substitute source text with translation. On export you should again see signs “>”

Yeah it’s just less readable the way it is now, but it’s indeed highlighted as tag so not super crucial when reading the line.

Got you. However, if you can use the Copy Source - that’s great :slightly_smiling_face:

1 Like