Re: Updated: antiword-0.34-1 (was: Re: antiword-0.34)
Hi Christopher, Uploaded. Please send an announcement once the packages show up in your local mirror and you have had a chance to verify correct installation with setup.exe. While looking for the owner of antiword to ask them to investigate the problem reported in the cygwin list, I noticed that there was never an announcement of its availablity after it was uploaded. For shame. Oops, I'll announce for the next update/release then. In any event, Gerrit, can I assume that you are looking into the problem reported in the cygwin list? Obviously there are users out there, great to hear, I'll see what I can do about the problem. Gerrit -- =^..^=
Re: Updated: antiword-0.34-1 (was: Re: antiword-0.34)
On Fri, Oct 10, 2003 at 01:33:55PM -0400, Daniel Reed wrote: On 2003-10-10T13:25+0200, Gerrit P. Haase wrote: ) Daniel schrieb: ) On 2003-10-08T12:33+0200, Gerrit P. Haase wrote: ) ) Otherwise the package is good to go, IMO. ) ) Igor ) Just went to push and the last check didn't find a Cygwin-specific README. ) I've updated the antiword package. It includes a README now. ) http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 ) http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 ) http://familiehaase.de/cywgin/antiword/setup.hint Uploaded. Please send an announcement once the packages show up in your local mirror and you have had a chance to verify correct installation with setup.exe. -rw-rw-r--1 192 2003-10-06 13:17:32 + antiword/setup.hint -rw-rw-r--1 134737 2003-10-10 11:26:05 + antiword/antiword-0.34-1.tar.bz2 -rw-rw-r--1 274374 2003-10-10 11:26:19 + antiword/antiword-0.34-1-src.tar.bz2 While looking for the owner of antiword to ask them to investigate the problem reported in the cygwin list, I noticed that there was never an announcement of its availablity after it was uploaded. For shame. In any event, Gerrit, can I assume that you are looking into the problem reported in the cygwin list? cgf
Re: Aupdated: antiword-0.34-2, please upload
Daniel schrieb: On 2003-10-15T16:44+0200, Gerrit P. Haase wrote: ) I've updated antiword, now the annoying syntax Error in: ... messages ) (which actually aren't errors) are gone, please upload: ) ) http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2.tar.bz2 ) http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2-src.tar.bz2 I'll hold off until you give me another go-ahead. Thanks, I'll tell you later. Gerrit -- =^..^=
Re: Aupdated: antiword-0.34-2, please upload
On Wed, 15 Oct 2003, Gerrit P. Haase wrote: Igor schrieb: On Wed, 15 Oct 2003, Gerrit P. Haase wrote: Hallo PPLMAPU, I've updated antiword, now the annoying syntax Error in: ... messages (which actually aren't errors) are gone, please upload: http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2.tar.bz2 http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2-src.tar.bz2 Thanks, Gerrit Gerrit, I'm sorry to say this, but I'm still getting the error: You are too fast;-) I just saw, that the patch does not apply. I have no idea why, I'll try again now. Gerrit Check for DOS line endings... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: Aupdated: antiword-0.34-2, please upload
On 2003-10-15T16:44+0200, Gerrit P. Haase wrote: ) I've updated antiword, now the annoying syntax Error in: ... messages ) (which actually aren't errors) are gone, please upload: ) ) http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2.tar.bz2 ) http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2-src.tar.bz2 I'll hold off until you give me another go-ahead. -- Daniel Reed [EMAIL PROTECTED] http://naim-users.org/nmlorg/ http://naim.n.ml.org/ If nature has made you a giver, your hands are born open, and so is your heart. And though there may be times when your hands are empty, your heart is always full, and you can give things out of that. -- Frances Hodgson Burnett, Novelist
Updated again: antiword , please upload (was: Re: Aupdated: antiword-0.34-2, please upload)
Hello Igor and Daniel, I'm sorry to say this, but I'm still getting the error: You are too fast;-) I just saw, that the patch does not apply. I have no idea why, I'll try again now. Check for DOS line endings... Igor Hmmpf, patch is somewhat broken regarding this... Ready now, same URLs as before: http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2.tar.bz2 http://anfaenger.de/cygwin-1.5/antiword/antiword-0.34-2-src.tar.bz2 Gerrit -- =^..^=
Updated: antiword-0.34-1 (was: Re: antiword-0.34)
Daniel schrieb: On 2003-10-08T12:33+0200, Gerrit P. Haase wrote: ) Otherwise the package is good to go, IMO. ) Igor ) Hey, Daniel, there were three votes and a positive review, lets push it ) on the mirrors;-) Just went to push and the last check didn't find a Cygwin-specific README. I've updated the antiword package. It includes a README now. I also tried to fix the problem Igor reported. Igor, if you could try again with your settings and your special text document, how does it acts now when hitting an undefined character? Many thanks to Benny for the hint where and what to fix. http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint Gerrit -- =^..^=
Re: Updated: antiword-0.34-1 (was: Re: antiword-0.34)
On Fri, 10 Oct 2003, Gerrit P. Haase wrote: Daniel schrieb: On 2003-10-08T12:33+0200, Gerrit P. Haase wrote: ) Otherwise the package is good to go, IMO. ) Igor ) Hey, Daniel, there were three votes and a positive review, lets push it ) on the mirrors;-) Just went to push and the last check didn't find a Cygwin-specific README. I've updated the antiword package. It includes a README now. I also tried to fix the problem Igor reported. Igor, if you could try again with your settings and your special text document, how does it acts now when hitting an undefined character? Many thanks to Benny for the hint where and what to fix. Gerrit, Unfortunately, I still get the warning (i.e., no change). There is no need for a special document, even -- simply run antiword -m cp1251 (yes, with no document). Apparently, the warning shows up while parsing the mapping file, so I doubt it's particularly important, in any case... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: Updated: antiword-0.34-1 (was: Re: antiword-0.34)
Igor schrieb: On Fri, 10 Oct 2003, Gerrit P. Haase wrote: Daniel schrieb: Just went to push and the last check didn't find a Cygwin-specific README. I've updated the antiword package. It includes a README now. I also tried to fix the problem Igor reported. Igor, if you could try Unfortunately, I still get the warning (i.e., no change). There is no need for a special document, even -- simply run antiword -m cp1251 I contacted the Author about this issue, hopefully he will fix it. Gerrit -- =^..^=
Re: Updated: antiword-0.34-1 (was: Re: antiword-0.34)
On 2003-10-10T13:25+0200, Gerrit P. Haase wrote: ) Daniel schrieb: ) On 2003-10-08T12:33+0200, Gerrit P. Haase wrote: ) ) Otherwise the package is good to go, IMO. ) ) Igor ) Just went to push and the last check didn't find a Cygwin-specific README. ) I've updated the antiword package. It includes a README now. ) http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 ) http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 ) http://familiehaase.de/cywgin/antiword/setup.hint Uploaded. Please send an announcement once the packages show up in your local mirror and you have had a chance to verify correct installation with setup.exe. -rw-rw-r--1 192 2003-10-06 13:17:32 + antiword/setup.hint -rw-rw-r--1 134737 2003-10-10 11:26:05 + antiword/antiword-0.34-1.tar.bz2 -rw-rw-r--1 274374 2003-10-10 11:26:19 + antiword/antiword-0.34-1-src.tar.bz2 Thanks, -- Daniel Reed [EMAIL PROTECTED] http://naim-users.org/nmlorg/ http://naim.n.ml.org/ It is so easy to miss pretty trivial solutions to problems deemed complicated. The goal of a scientist is to find an interesting problem, and live off it for a while. The goal of an engineer is to evade interesting problems :) -- Vadim Antonov [EMAIL PROTECTED] on NANOG
Re: antiword-0.34
Hi Gerrit, Gerrit P. Haase [EMAIL PROTECTED] writes: cp1250.txt:0x81 #UNDEFINED Undefined is meaningfull. Think of the difference of NULL and '0' (e.g. in SQL). Why does Word makes use of undefined characters? Are you sure it does? The error messages seems to come from the routine that parses cp1250.txt etc (chartrans.c, bReadCharacterMappingTable() in the older sources that I have here). That routine should be fixed to recognize this syntax with the missing mapping, I guess. benny
Re: antiword-0.34
Igor wrote about: http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint [...] One small problem I noticed (and this may be an upstream one) is that I'm getting a Syntax error in: '0x98 #UNDEFINED' error when viewing a Word97 file with the cp1251.txt mapping. The document then displays ok. A grep UNDEFINED *.txt in usr/share/antiword shows cp1250.txt:0x81 #UNDEFINED cp1250.txt:0x83 #UNDEFINED cp1250.txt:0x88 #UNDEFINED cp1250.txt:0x90 #UNDEFINED cp1250.txt:0x98 #UNDEFINED cp1251.txt:0x98 #UNDEFINED cp1252.txt:0x81 #UNDEFINED cp1252.txt:0x8D #UNDEFINED cp1252.txt:0x8F #UNDEFINED cp1252.txt:0x90 #UNDEFINED cp1252.txt:0x9D #UNDEFINED I think these may need to be substituted by a meaningful character (e.g., space). Hmm, I thought about upgrading the whole package to Unicode 4.0. Will talk about it to the author. Otherwise the package is good to go, IMO. Igor Hey, Daniel, there were three votes and a positive review, lets push it on the mirrors;-) P.S. The script creates the distribution tarballs only, which is rather annoying. Is there a particular reason you didn't want to use the generic-build-script? In my opinion it is overkill for a small package when there are just some files to compile or no compilation (e.g. perlscript help2man). I have hacked the script to compile a package just to deliver it to myself and then I thought, hey, why not include this little package in the netrelease? Usually you're right, I should use the One-Script-Fits-All generic script and the generic readme. And I decided to upgrade to the OSFA for the next release. Gerrit -- =^..^=
Re: antiword-0.34
On 2003-10-08T12:33+0200, Gerrit P. Haase wrote: ) Otherwise the package is good to go, IMO. ) Igor ) Hey, Daniel, there were three votes and a positive review, lets push it ) on the mirrors;-) Just went to push and the last check didn't find a Cygwin-specific README. Looks like the package has: usr/bin/antiword.exe usr/share/antiword/* usr/share/doc/antiword-0.34/* usr/share/man/man1/antiword.1 but no usr/share/doc/Cygwin/antiword-0.34.README or usr/share/doc/Cygwin/antiword-0.34-1.README (it checks for either of those). -- Daniel Reed [EMAIL PROTECTED] http://naim-users.org/nmlorg/ http://naim.n.ml.org/ A man that is truly great is he who makes the world his debtor.
Re: antiword-0.34
On Wed, 8 Oct 2003, Gerrit P. Haase wrote: Igor wrote about: http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint [...] One small problem I noticed (and this may be an upstream one) is that I'm getting a Syntax error in: '0x98 #UNDEFINED' error when viewing a Word97 file with the cp1251.txt mapping. The document then displays ok. A grep UNDEFINED *.txt in usr/share/antiword shows cp1250.txt:0x81 #UNDEFINED cp1250.txt:0x83 #UNDEFINED cp1250.txt:0x88 #UNDEFINED cp1250.txt:0x90 #UNDEFINED cp1250.txt:0x98 #UNDEFINED cp1251.txt:0x98 #UNDEFINED cp1252.txt:0x81 #UNDEFINED cp1252.txt:0x8D #UNDEFINED cp1252.txt:0x8F #UNDEFINED cp1252.txt:0x90 #UNDEFINED cp1252.txt:0x9D #UNDEFINED I think these may need to be substituted by a meaningful character (e.g., space). Hmm, I thought about upgrading the whole package to Unicode 4.0. Will talk about it to the author. Huh? The files are just mappings from different charsets to Unicode. Some characters are apparently not defined in some charsets. I don't quite see how switching to a newer version of Unicode will allow you to define a character *in a particular charset* that you weren't able to define with the previous version... Otherwise the package is good to go, IMO. Igor Hey, Daniel, there were three votes and a positive review, lets push it on the mirrors;-) P.S. The script creates the distribution tarballs only, which is rather annoying. Is there a particular reason you didn't want to use the generic-build-script? In my opinion it is overkill for a small package when there are just some files to compile or no compilation (e.g. perlscript help2man). I have hacked the script to compile a package just to deliver it to myself and then I thought, hey, why not include this little package in the netrelease? Usually you're right, I should use the One-Script-Fits-All generic script and the generic readme. And I decided to upgrade to the OSFA for the next release. Gerrit One advantage of the generic-build-script is that it allows partial actions (e.g., prep, then conf, then make, and you're ready to debug). BTW, in your script, you could use ln -fs instead of rm -f ...; ln -s. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: antiword-0.34
Hi Igor, One small problem I noticed (and this may be an upstream one) is that I'm getting a Syntax error in: '0x98 #UNDEFINED' error when viewing a Word97 file with the cp1251.txt mapping. The document then displays ok. A grep UNDEFINED *.txt in usr/share/antiword shows cp1250.txt:0x81 #UNDEFINED cp1250.txt:0x83 #UNDEFINED cp1250.txt:0x88 #UNDEFINED cp1250.txt:0x90 #UNDEFINED cp1250.txt:0x98 #UNDEFINED cp1251.txt:0x98 #UNDEFINED cp1252.txt:0x81 #UNDEFINED cp1252.txt:0x8D #UNDEFINED cp1252.txt:0x8F #UNDEFINED cp1252.txt:0x90 #UNDEFINED cp1252.txt:0x9D #UNDEFINED I think these may need to be substituted by a meaningful character (e.g., space). Undefined is meaningfull. Think of the difference of NULL and '0' (e.g. in SQL). Why does Word makes use of undefined characters? Well, if there are these symbols, the program should know it and don't report an error. Hmm, I thought about upgrading the whole package to Unicode 4.0. Will talk about it to the author. Huh? The files are just mappings from different charsets to Unicode. Some characters are apparently not defined in some charsets. I don't quite see how switching to a newer version of Unicode will allow you to define a character *in a particular charset* that you weren't able to define with the previous version... There are no newer versions of the mappings available anyway. One advantage of the generic-build-script is that it allows partial actions (e.g., prep, then conf, then make, and you're ready to debug). And I decided to upgrade to the OSFA for the next release. BTW, in your script, you could use ln -fs instead of rm -f ...; ln -s. Igor Yes, I see, thanks, Gerrit -- =^..^=
Re: antiword-0.34
Hallo Igor, http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint I've looked at the binary and source packages. In the binary package, is there a reason antiword.1 is duplicated in both usr/share/man/man1/ and usr/share/antiword-0.34/? Fixed. The script in the source package doesn't give you any options for partial make, and doesn't accept the parameters of the generic_build_script (e.g., all, conf, prep, make, etc). I don't know how important that is, but thought I'd mention it. Another, much more important thing is that the script builds files on top of the root filesystem (i.e., installs directly into /usr/bin, etc) -- IMO, the source package should NOT place anything in the root hierarchy, that's the job of setup.exe; the source build should be contained in the source directory. Because of the latter I didn't build from the source. Fixed. Oh, and the script is not space-in-filename friendly. Fixed. FWIW, I had to make a change to the wtf Makefile to allow the DESTDIR parameter in the install rule, so I know it's not that much work. Especially since you're providing a Makefile.Cygwin yourself in the patch. I'm attaching a preliminary patch to your script and patch -- I tried to catch all the places that modify the global hierarchy, but please verify that. HTH, Igor All fixed. Many thanks for your review and the patch. I'll remember to address these issues in future. Gerrit -- =^..^=
Re: antiword-0.34
On Tue, 7 Oct 2003, Gerrit P. Haase wrote: Hallo Igor, http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint I've looked at the binary and source packages. In the binary package, is there a reason antiword.1 is duplicated in both usr/share/man/man1/ and usr/share/antiword-0.34/? Fixed. The script in the source package doesn't give you any options for partial make, and doesn't accept the parameters of the generic_build_script (e.g., all, conf, prep, make, etc). I don't know how important that is, but thought I'd mention it. Another, much more important thing is that the script builds files on top of the root filesystem (i.e., installs directly into /usr/bin, etc) -- IMO, the source package should NOT place anything in the root hierarchy, that's the job of setup.exe; the source build should be contained in the source directory. Because of the latter I didn't build from the source. Fixed. Oh, and the script is not space-in-filename friendly. Fixed. FWIW, I had to make a change to the wtf Makefile to allow the DESTDIR parameter in the install rule, so I know it's not that much work. Especially since you're providing a Makefile.Cygwin yourself in the patch. I'm attaching a preliminary patch to your script and patch -- I tried to catch all the places that modify the global hierarchy, but please verify that. HTH, Igor All fixed. Many thanks for your review and the patch. I'll remember to address these issues in future. Gerrit Gerrit, Indeed, it all seems fixed. The binary version seems to work ok, as does the one I built from source. One small problem I noticed (and this may be an upstream one) is that I'm getting a Syntax error in: '0x98 #UNDEFINED' error when viewing a Word97 file with the cp1251.txt mapping. The document then displays ok. A grep UNDEFINED *.txt in usr/share/antiword shows cp1250.txt:0x81 #UNDEFINED cp1250.txt:0x83 #UNDEFINED cp1250.txt:0x88 #UNDEFINED cp1250.txt:0x90 #UNDEFINED cp1250.txt:0x98 #UNDEFINED cp1251.txt:0x98 #UNDEFINED cp1252.txt:0x81 #UNDEFINED cp1252.txt:0x8D #UNDEFINED cp1252.txt:0x8F #UNDEFINED cp1252.txt:0x90 #UNDEFINED cp1252.txt:0x9D #UNDEFINED I think these may need to be substituted by a meaningful character (e.g., space). Otherwise the package is good to go, IMO. Igor P.S. The script creates the distribution tarballs only, which is rather annoying. Is there a particular reason you didn't want to use the generic-build-script? -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: [ITP] antiword-0.34
This has my vote On Sat, Oct 04, 2003 at 11:46:08AM +0200, Gerrit P. Haase wrote: Hallo, How about including Antiword in the netrelease? Home - http://www.antiword.org/ # antiword sdesc: A free MS Word reader ldesc: Antiword converts the binary files from Word 2, 6, 7, 97, 2000 and 2002 to plain text and to PostScript TM. requires: cygwin http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint $ antiword -h Name: antiword Purpose: Display MS-Word files Author: (C) 1998-2003 Adri van Os Version: 0.34 (25 Aug 2003) Status: GNU General Public License Usage: antiword [switches] wordfile1 [wordfile2 ...] Switches: [-t|-p papersize|-x dtd][-m mapping][-w #][-i #][-Ls] -t text output (default) -p paper size name PostScript output like: a4, letter or legal -x dtd XML output like: db (DocBook) -m mapping character mapping file -w width in characters of text output -i level image level (PostScript only) -L use landscape mode (PostScript only) -s Show hidden (by Word) text Thanks, Gerrit -- =^..^= -- Tom's hungry, time to eat lunch.
Re: [ITP] antiword-0.34
On Mon, Oct 06, 2003 at 10:16:34AM -0400, Igor Pechtchanski wrote: On Mon, 6 Oct 2003, Gerrit P. Haase wrote: [snip] http://familiehaase.de/cywgin/antiword/antiword-0.34-1-src.tar.bz2 http://familiehaase.de/cywgin/antiword/antiword-0.34-1.tar.bz2 http://familiehaase.de/cywgin/antiword/setup.hint And it is not reviewed yet (IIRC). Would some kind soul take a quick look (it is really a tiny package which compiles in a minute)? Gerrit Gerrit, I've looked at the binary and source packages. In the binary package, is there a reason antiword.1 is duplicated in both usr/share/man/man1/ and usr/share/antiword-0.34/? The script in the source package doesn't give you any options for partial make, and doesn't accept the parameters of the generic_build_script (e.g., all, conf, prep, make, etc). I don't know how important that is, but thought I'd mention it. Another, much more important thing is that the script builds files on top of the root filesystem (i.e., installs directly into /usr/bin, etc) -- IMO, the source package should NOT place anything in the root hierarchy, that's the job of setup.exe; the source build should be contained in the source directory. Because of the latter I didn't build from the source. Oh, and the script is not space-in-filename friendly. I hadn't noticed that (either one: changes-to-rootfs and not-space-friendly). I'll add it to my checklist for my next reviews :) BTW: would it be a good idea to keep a canonical checklist for Cygwin package candidate reviews (CCFCPCR)? This might be handy for newbie reviewers (such as myself) and for new package maintainers to avoid common loopholes.. I'd be willing to maintain such a list, if need be. rlc
Re: [ITP] antiword-0.34
On 04.10.2003 11:46, Gerrit P. Haase wrote: Hallo, How about including Antiword in the netrelease? Home - http://www.antiword.org/ # antiword sdesc: A free MS Word reader ldesc: Antiword converts the binary files from Word 2, 6, 7, 97, 2000 and 2002 to plain text and to PostScript TM. requires: cygwin It has my vote. Regards. -- +---+ | Marcel Telka e-mail: [EMAIL PROTECTED] | |homepage: http://telka.sk/ | |jabber: [EMAIL PROTECTED] | +---+
Re: [ITP] antiword-0.34
On Sun, 5 Oct 2003, Marcel Telka wrote: On 04.10.2003 11:46, Gerrit P. Haase wrote: Hallo, How about including Antiword in the netrelease? Home - http://www.antiword.org/ # antiword sdesc: A free MS Word reader ldesc: Antiword converts the binary files from Word 2, 6, 7, 97, 2000 and 2002 to plain text and to PostScript TM. requires: cygwin It has my vote. Ditto. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
