Vineet, you make it sound as if there’s some mistake or something wrong with translating “ ” into a non-breaking space instead of just an ordinary blank space. But that is exactly what “ ” means — “Non-Breaking SPace”. (What did you think the characters N, B, S, and P in the entity stand for?)

If there is a problem, it is absolutely not with converting “ ” to ASCII 160, but with trim() and Java functions like it — if anything should change, then those functions should be changed to handle valid characters correctly, not the perfectly correct conversion.

Or, hey, come to think of it, maybe it’s just your expectations that are wrong: Since “ ” is explicitely intended to be _Non-Breaking_, why on Earth would you think it should be handled like an ordinary space by “trim()”? The whole point of a Non-Breaking Space is that it is NOT to be considered a word boundary, but left intact with the letters to either side of it, just like an ordinary letter.

Or, in other words: NOT to be handled like an ordinary space is exactly what “ ” IS FOR. So for the conversion to convert it to ASCII 160, and for trim() NOT to trim that character, seems to me (from your terse description) to be precisely the correct behaviour.

HTH!