Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||bullets turn into > when file imported from Word v.X is reexported to v.X|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|OS:||Mac OS X, all|
|Issue Type:||DEFECT||Latest Confirmation in:||---|
|Issue Depends on:|
Description Unknown 2003-11-16 19:51:24 UTC
Create a file in the OS X version of Word. Simple file: * 1 * 2 import into OO 1.1 (version in contrib directory). Export to .doc format again. The resulting file is OK on Windows version of Word, but if you open in OS X Word, the bullets have turned into }. Note that this has nothing to do with starsymb or opensymbol. Word uses Symbol. I have a converted version of Symbol in OO. It looks fine in OO. However if I look at the definition of the bullet in OO, the Symbol font looks different from the contents of the actual font: in addition to the glyphs that are actually there, OO claims that there's a duplicate set of glyphs at F000 + the actual value. The bullet is shown as F0B7. Note that OS X Word doesn't understand Unicode. I wonder whether the bullet is being written out as F0B7. If so, Windows Word would understand, but Mac Word might not. However I have no way to look at the binary Word file, so I can't tell what is going on. If I export to RTF and bring it back into OS X Word, the bullets are right. However the spacing is now wrong: the first line text starts right after the bullet, rather than being tabbed properly. I can give you example files, but this is easy enough to reproduce. When I author within OO, this is easy to fix. Rather than fighting with the problems of the various symbol fonts, I set the bullets to be the bullet character from my text font. I think that's the right default anyway: the designed of the font presumably chose a bullet of the size that he thought would look right with his font. Why go to some other font that may or may not work? I think that would be an easier solution than embedding opensym or some of the other things I've seen discusssed in the reports here. But that doesn't solve the problem of files imported from Word. You don't want to change those to a different font that may not look the same. Incidentally, if you need any magic done in the fonts to help with this, I'd be happy to help. I have a copy of Fontlab, and I'm fairly familiar with fonts. I have access to Windows, Mac and Linux. But I doubt that this is an issue with the font. I suspect the OO code itself is doing something inappropriate with the font encoding. If you want to contact me, my email address is firstname.lastname@example.org.
Comment 1 terryt 2003-11-17 09:17:13 UTC
oooqa keyword added. I will try to reproduce when I get a chance. Thanks for the helpful info.
Comment 2 terryt 2003-11-23 03:57:11 UTC
I have reproduced the problem using MS Word for Mac OS X v.X, and OOo 1.1(rc5) pre-release for Mac OS X. I will attach the sample documents. And just to be clear when the reporter says import/export to/from OOo he means open/save.
Comment 3 terryt 2003-11-23 03:58:35 UTC
Created attachment 11469 [details] Original MS Word for Mac OS X v.X sample document
Comment 4 terryt 2003-11-23 03:59:57 UTC
Created attachment 11470 [details] Same document imported into OOo 1.1 and saved back as MS Word
Comment 5 h.ilter 2003-11-24 10:38:49 UTC
HI->MRU: See Platform.
Comment 6 stefan.baltzer 2003-11-28 16:00:40 UTC
SBA: Target set to 2.0.
Comment 7 michael.ruess 2004-05-07 10:02:29 UTC
MRU->CP: I checked this with Win/Linux. It seems to be MAC only problem, please reassign to correct developer. Thanks.
Comment 8 christof.pintaske 2004-05-11 18:25:12 UTC
cp->Dan: I have no idea about this one (we don't have MS Office for Mac here)
Comment 9 stx123 2005-02-18 15:35:14 UTC
Greetigs Dan, are you going to work on this issue in the 2.0 timeframe Martin described on releases? http://development.openoffice.org/releases/OpenOffice_org_2_x.html If not I would like to change the target milestone. Thanks, Stefan
Comment 10 pavel 2005-07-29 12:06:55 UTC
Retarget to OOoLater.
Comment 11 Rob Weir 2013-07-30 02:24:02 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.