https://bugs.freedesktop.org/show_bug.cgi?id=49629

Caolán McNamara <caol...@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|libreoffice-b...@lists.free |caol...@redhat.com
                   |desktop.org                 |

--- Comment #9 from Caolán McNamara <caol...@redhat.com> 2012-07-13 14:45:32 
UTC ---
Well, I munged all the available bug reports into test cases anyway. 

Much of the trouble here is that 0x0002 is stuffed in as a code point which can
appear in a "word" in the source/breakiterator/data/*word*.txt rules. But
0x0002 doesn't appear as a code point that is non-whitespace in the skipSpace
rules so its inconsistent.

Having 0x0002 as a code point than can appear in a word gives all sorts of odd
results in writer for word counting, character counting word skipping etc.

I'm inclined to remove the special handing of 0x0002 down in the breakiterator
rules and go back up to writer (which I presume is the only thing with the
rather mad 0x0002 usage) and handle it specifically there when necessary, e.g.
expanding it out to its display text for the purposes of character and word
counting

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to