Issue 97248

Summary: Unicode spaces (Hex: 2000-200A) are not treated as spaces
Product: Writer Reporter: mrmacphisto <fdouw>
Component: editingAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P4 CC: frank.meies, hdu, issues, michael.ruess, stefan.baltzer
Version: OOo 3.0Keywords: oooqa
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on: 107419    
Issue Blocks:    
Description Flags
Sample document none

Description mrmacphisto 2008-12-14 17:09:41 UTC
Spaces in the Unicode range 2000-200A (hex) are not treated as spaces by OOo
Writer.  This becomes apparent when the space is at a line end, where it does
not disappear like a normal space, or when a curly quotation mark is inserted
after the space, the quotation mark will curl in the wrong direction.

I have tested this in OOo 3.0.0 on Windows Vista and OOo 2.4.1 on Ubuntu Linux 8.04.
Comment 1 eric.savary 2009-04-09 12:30:03 UTC
Please attach a sample document.

@HDU: any idea?
Comment 2 2009-04-09 12:37:02 UTC
Yes, I agree that the Writer engine should treat U+200x as spaces.
Comment 3 mrmacphisto 2009-04-10 09:39:22 UTC
Created attachment 61505 [details]
Sample document
Comment 4 xaliger 2009-08-25 15:23:06 UTC
This is very visible with RTF import of Word created document containing impit 
fields (word often writes empty field value as


that is five 2002 spaces.

Quite common case, very ugly in OOo.
Comment 5 Oliver-Rainer Wittmann 2009-12-02 14:03:57 UTC
setting target.

OD->MRU: Any input from your side on this issue?
Comment 6 michael.ruess 2009-12-03 11:56:02 UTC
This problem does not arise this commonly. I would even tend to say that this is
"Enhancement" request...
Comment 7 xaliger 2009-12-03 12:12:50 UTC
As I comment already, this is pretty common case, when working with MSWord-
created forms saved to RTF. Word writes empty fields as 5 U+2002 spaces. OOo 
shows that as 5 boxes which looks realy badly. 

Atleast 2 organizations I know of, stopped using OOo because of that.

Of course, this could be solved by tweaking rtf import filter converting 
Unicode spaces to normal spaces (I think .doc import do something like that).
Comment 8 stefan.baltzer 2009-12-03 17:13:36 UTC
Beside matching the mentioned Unicode range to spaces, what about "the correct
ones"? They all do differ in width and more-often-than-not, spaces are used to
format documents. "No squares" is cool, but "spaces with the correct width"
would be even better. To get this working in OOo on all systems, the OpenSymbol
font coming along with OOo must have them included because too many fonts on too
many systems do not.

I wrote issue 107419 (Add characters to OpenSymbol font (spaces, dashes,
formatting characters).

SBA-> Xaliger: Please note that the threat "XYZ stays with MS Office because of
this issue" is neither new nor effective. We recently celebrated 100 Million
downloads of OOo Version 3 although this very issue exists. :-)

Note that those who bring on the developer resources, decide what these
resources will do. I have seen them doing weird things like prioritizing issues
and follow these priorities. Thank you for your comprehension.
Comment 9 Marcus 2017-05-20 11:17:44 UTC
Reset assigne to the default "".