Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uiucdcsb.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcsb!bertram
From: bertram@uiucdcsb.UUCP
Newsgroups: net.micro
Subject: Re: Wordstar Question
Message-ID: <4400082@uiucdcsb.UUCP>
Date: Sun, 24-Feb-85 00:40:00 EST
Article-I.D.: uiucdcsb.4400082
Posted: Sun Feb 24 00:40:00 1985
Date-Received: Tue, 19-Feb-85 07:56:19 EST
References: <8300@brl-tgr.UUCP>
Lines: 23
Nf-ID: #R:brl-tgr:-830000:uiucdcsb:4400082:000:991
Nf-From: uiucdcsb!bertram    Feb 16 23:40:00 1985





	This information comes from Version 3.0 of Wordstar so it may be
out of date for your version but here's what I found.
	In non-document mode (that is files opened with n rather than d)
Wordstar puts actual tabs (hex 09) in the file and these can be searched for
and replaced quite successfully.
	On the other hand when in document mode Wordstar puts in real spaces
when a tab ctrl-I is entered from the keyboard and then searches for tabs
will fail since there are none in the file.
	In regard to WS files I assume that you mean the text-files that
Wordstar produces.  To my knowledge these are pretty much Ascii text unless
you use fancy formatting commands which will set the high bits on some
characters for printing under the control of Wordstar.  You can
probably find a utility like CPM's DUMP which will display the contents
of a file on the console in hexidecimal to investigate what these special
characters are for different formatting requests.


Fred Bertram
bertram@uiucdcs