🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.mac
Article #28741

FullWrite Pro bug.

#28741
From: Chuq Von Rospach
Date: Wed, 01 Jun 1988 04:36
25 lines
1418 bytes
I found a really strange bug in FullWrite pro (this has been confirmed by
Ashton-Tate, too, although they aren't quite sure what they're going to do
about it...)

Take a Word 3.x document. Import it into FWP. Now, go into the find/change
and try to search for '-'. It won't find any. FullWrite stores dashes
internally as ascii AE. When it imports dashes from Word, however, it
doesn't convert them over -- they remain ascii 2D. They both print the same
and show the same on the screen, but they're separate characters.

The workaround is to select a Word-dash, copy it into the clipboard and then
paste it into the find/change window. They don't seem to really know why the
internal representation is different, or why it isn't converted. 

Strange, but true.

So if you KNOW those dashes are in there, they are. It's just that a dash
isn't a dash anymore. (and then there's optional hypens and en-dashes and
em-dashes and.....)


Chuq Von Rospach			chuq@sun.COM		Delphi: CHUQ

	Robert A. Heinlein: 1907-1988. He will never truly die as long as we
                           read his words and speak his name. Rest in Peace.
Technical Details
Message-ID: <55009@sun.uucp>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!ames!oliveb!sun!plaid!chuq

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!ames!oliveb!sun!plaid!chuq
From: chuq@plaid.Sun.COM (Chuq Von Rospach)
Newsgroups: comp.sys.mac
Subject: FullWrite Pro bug.
Message-ID: <55009@sun.uucp>
Date: 1 Jun 88 04:36:55 GMT
Sender: news@sun.uucp
Lines: 24