Is it safe to use
­ now? I remember there were problems with this entity, such as rendering it everywhere (instead of only when the web browser decides to split a word), or splitting a word without rendering it.
Is it safe to use
Based on this article I don't think so. Apparently the browsers all handle it differently and still have issues with it (chrome, opera). The fact that the specs for it are conflicting probably doesn't help any.
I don't know how many times I've looked at this, but it is quite appalling it is still ongoing. It seems to me there are two basic issues:
The first issue is fairly straightforward ... line breaks at whitespace, at hard-hyphens and to indicate other places we need a NON-DISPLAYING character. The second also seems fairly simple - and I would have assumed (but it doesn't) that in css I can specify how to break words and the character (or none) to display at a break. So, e.g. I could have BIGLONGWORD~ or BIGLONGWORD-
Better still, would be some css rules like:
In other words, this says that I want the browser to automatically insert breaks IF NECESSARY in words longer than 7 characters (with a least two characters before and after break), at hyphens and at "
So, going back to the original definition that "
In contrast, the above "css" would have changed it to a hard character which would be copied as is.
There is also the non-standard "
And for info, there is also
However, until things are sorted out (and remember many new mobiles are even less compliant with the latest standards than PC browsers), it seems that "
The only solutions that is going to work on all browsers is to pre-process the text and insert line breaks IF NEEDED in long words at a set number of characters with a fixed-width font OR to use a proportional font with ample room to fit a line with all the widest characters (or use a massive table of character widths).
And if you are displaying on a mobile, you will probably not know the width - so there is literally no solution.