home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 5 Edit
/
05-Edit.zip
/
catdo_35.zip
/
README.OS2
< prev
next >
Wrap
Text File
|
1999-12-18
|
2KB
|
65 lines
README for catdoc on OS/2
-------------------------
Stefan Schwarzer <s.schwarzer@ndh.net>
----- What you need --------------------
The binary was compiled as an OS/2 32 bit program with Watcom C 11.0,
so you will not need the EMX runtime package (though I assume, you have
it on you system, anyway ;-) ).
To run this program under OS/2, you only need the binary catdoc.exe.
No additions to config.sys etc. are needed (though I recommend to put
the executable in a directory that is contained in the PATH).
To compile the source, the file catdoc0_35s.c is sufficient;
catdoc.wpj and catdoc.tgt are only added for conveniance if you use
Watcom C.
----- Files ----------------------------
Files of the original distribution, catdoc-0.35.tar.gz, which I
received, are:
- catdoc.c (source code)
- README.catdoc (original readme file)
- catdoc.1 (manpage)
- wordview (a graphical interface script using Tcl/Tk)
I added:
- catdoc0_35s.c (source with my changes)
- catdoc.exe (binary for OS/2)
- README.OS2 (this file)
- COPYING (since it's a GPL program according to README.catdoc)
- tables.py (small script to help producing the map tables for cp437
and cp850)
- catdoc.wpj (project file, only used by Watcom C)
- catdoc.tgt (target file, only used by Watcom C)
----- Changes --------------------------
I made the following changes to the source file catdoc.c (mine is named
catdoc0_35s.c):
- made the usage of latin1 codepage the default (i. e. no cyrillic
fonts, in contrast to the original author),
- changed the codes for the opening and closing double quotes in the
"specs" array, because they seemed to be wrong for the Winword files
I tested,
- added support and switches for the conversion of latin1 to either
codepage 437 (switch -4) or 850 (switch -8). I found this to be very
useful, since these are the most commonly used codepages under OS/2.
----- Bugs -----------------------------
I didn't test the program much, especially not the TeX mode, so please
don't blame me if something doesn't work ;-) . However, I tried to
keep the changes to the original code at a minimum (which explains
some "mixed" approaches).