Yep, You are right.
'Select Single Node' worked correctly and I am now getting output without those tags.
Good suggestions though on using scriptable objects. The thing is, my overall requirement is very simple. I am fetching simple dialog strings when the player taps on an object - in a point and click adventure game. So nothing crazy like RPG and no complex dialog chains.
So I'd like to keep approach simple as well. An item contains a unique ID and I simply use that ID to seek in the xml to display the correct dialog. Works so far.
However, you have informed that xml is slow, I will have to keep this in check when the xml size gets bigger and especially on mobile. If it is within acceptable range I'll stick to this system else-
Scriptable objects is inevitable for me to use at some point and I will keep this in mind if I see my current approach to be 'limited' and need to add more features.
For now it seems to be sufficient for a quick prototype.
BTW, I loved your XML tutorial on YouTube! With it's help, I was able to make this simple text system for now.
Right now I am using text asset mode.
For localization, I do plan to keep each language version as a separate xml file. Would you please suggest if using xml proxy would be faster, slower performance-wise? and what even is 'in-memory' option?
Thanks as always.