Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] requirement

Ed Merks wrote:

That's very informative!  It's in my bookmarks now. :-)

I get the impression that a FIGURE_SPACE is a non-breaking space (from Decomposition <noBreak> SPACE (U+0020)) and hence that makes it a space that is not entirely white.  While ZERO_WIDTH_SPACE sounds like it's intended to be breaking (this character is intended for line break control; it has no width, but its presence between two characters does not prevent increased letter spacing in justification) and hence is entirely white.  So my impression is that Character gets it correct while UCharacter's behavior is questionable.
Even the UCharacter.isSpaceChar() reports false on ZERO_WIDTH_SPACE. Regardless of how 'white' is interpreted, surely, it must be at least a space character? So I'd like to promote the UCharacter behavior form questionable to plain wrong!

Thomas Hallgren


Oberhuber, Martin wrote:
Character and UCharacter dissagree on codePoint=8199
   Character.isWhitespace(8199) == false
   UCharacter.isWhitespace(8199) == true
Character and UCharacter dissagree on codePoint=8203
   Character.isWhitespace(8203) == true
   UCharacter.isWhitespace(8203) == false
CodePoint 8203: ZERO_WIDTH_SPACE
Not sure what to do with this info, though... for FIGURE_SPACE, we get
   Character.isSpaceChar() true
   Character.isWhitespace() false
which seems odd...

_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx

_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx

Back to the top