Berkeley CSUA MOTD:Entry 28976
Berkeley CSUA MOTD
 
WIKI | FAQ | Tech FAQ
http://csua.com/feed/
2025/05/25 [General] UID:1000 Activity:popular
5/25    

2003/7/9-10 [Computer/SW/Languages/Misc, Computer/SW/OS/OsX] UID:28976 Activity:insanely high
7/8     Is there a utility to convert MS Word files to PDF from the command
        line?
        \_ Do you really need it from the command line or do you simply need a
           batch convert (even though that may have a GUI frontend)?
           \_ Here's my use case... a secretary needs to post meeting minutes
              online. she can do "save as html" but that kind of sucks. so i
              want to have a webpage that lets her upload the doc and then
              auto-generate html and pdf (or just pdf) links on the site.
              if you have a GUI way to do it, that's fine too (she uses a Mac,
              i have a PC and UNIX, but no X on my UNIX server). thanks. -abe
              \_ If she's using OS X, she can just print to PDF from the
                 print screen of any application. -chialea
              \_ I'd just use OpenOffice 1.1 -- export to pdf.
           anything with a doc with non-mS software won't always result in
           correct output. If your secretary has a budget, and you want
              \_ No X on your unix box??  Install it.  It isn't that big.
                 \_ I don't *want* X and I definitely don't want OpenOffice.
                    \_ What's wrong with X?  You some MacBigot?
        \_ The inards/spec of the "Word" document are secret, so doing
           tried an existing program "doc2html" but it makes even single
           carriage returns into paragraph boundaries </p><p> That wouldn't
           work for me, so I wrote a perl script to turn doc into xhtml,
           but there is junk near and the beginning and end of the file
           that I have to edit out by hand.  Not elegant, but it works.
           I'll send you my code, perhaps you can improve it. mail brett.
           Microsoft does not "play welll with others".
        \_ The inards/spec of the "Word" document are secret, so using
           non-mS software won't always result in correct output. If your
           secretary has a budget, and you want perfect output, she should
           buy Adobe Acrobat, which comes with "Distiller".  that will
           allow her to "Print to PDF".  Otherwise, she could print to a
           postscript file, but that creates other issues with fonts and
           pages and such.  I have a similar task.  I tried an existing
           program "doc2html" but it didn't do quite what I wanted, so I
           anything with a doc with non-mS software won't always totall do
           things correctly. If your secretary has a budget, and you want
           perfect output, she should buy Adobe Acrobat, which comes with
           perhaps you can improve it. mail brett.  Alternatively, you
           could quote:
           "Distiller".  that will allow her to "Print to PDF".  Otherwise,
        \_ Is the Secretary running OS X? If so, she can select File->Print
           then hit "Save as PDF..."
           she could print to a postscript file, but that makes other
           issues with fonts and pages and such.  I have a similar task.  I
           tried an existing program "doc2html" but did't like it, so I
           wrote a perl script to turn doc into xhtml, but there is junk
           near and the beginning and end of the file that I have to edit
           out by hand.  Not elegant, but it works.  I'll send you my code,
           perhaps you can improve it. mail brett.  Microsoft does not
           "play welll with others".
             http://www.gnu.org/philosophy/no-word-attachments.html
        \_ If she has OSX, there's built-in export to PDF.
           \_ I'm thinking about upgrading her to OS X... but I was wondering
              if there were any UNIX equivalents...
              \_ OS9: http://www.versiontracker.com/dyn/moreinfo/macos/126
              \_ OSX *is* Unix.
                 \_ The Open Group does not agree with you.
        \_ best results from print-to-file with postscript printer driver
           from MS Word and then ps2pdf13 to distill it.
2025/05/25 [General] UID:1000 Activity:popular
5/25    

You may also be interested in these entries...
2013/4/9-5/18 [Computer/SW/Mail, Academia/Berkeley/CSUA] UID:54647 Activity:nil
4/8     What's a good free e-mail provider? I don't want to use Gmail,
        Yahoo, Outlook, or any of those sites with features I never use that
        track my personal info and keep changing their interface. I want just
        simple e-mail without privacy issues or all the baggage these large,
        for-profit companies are adding. I might even be willing to pay.
        Recommendations?
	...
Cache (6989 bytes)
www.gnu.org/philosophy/no-word-attachments.html
Word attachments are annoying, but worse than that, they impede people from switching to free software. Maybe we can stop this practice with a simple collective effort. All we have to do is ask each person who sends us a Word file to reconsider that way of doing things. That is unfortunate for them, since Word is proprietary software, denying its users the freedom to study, change, copy, and redistribute it. And because Microsoft changes the Word file format with each release, its users are locked into a system that compels them to buy each upgrade whether they want a change or not. They may even find, several years from now, that the Word documents they are writing this year can no longer be read with the version of Word they use then. But it hurts us, too, when they assume we use Word and send us (or demand that we send them) documents in Word format. Some organizations will only accept files in Word format: someone I know was unable to apply for a job because resumes had to be Word files. Even governments sometimes impose Word format on the public, which is truly outrageous. For us users of free operating systems, receiving Word documents is an inconvenience. But the worst impact of sending Word format is on people who might switch to free systems: they hesitate because they feel they must have Word available to read the Word files they receive. The practice of using the secret Word format for interchange impedes the growth of our community and the spread of freedom. While we notice the occasional annoyance of receiving a Word document, this steady and persistent harm to our community usually doesn't come to our attention. Many GNU users who receive Word documents try to find ways to handle them. You can manage to find the somewhat obfuscated ASCII text in the file by skimming through it. Free software today can read some Word documents, but not all--the format is secret and has not been entirely decoded. Palladium or some other "treacherous computing" facility in a new version of Word format, to make it utterly hopeless for any software to access the files without Microsoft authorization. There are also reports that Microsoft is planning to use patented extensions to XML as the basis for a future Word format; If you think of the document you received as an isolated event, it is natural to try to cope with it on your own. But when you recognize it as an instance of a pernicious systematic practice, it calls for a different approach. Managing to read the file is treating a symptom of a chronic illness. To cure the illness, we must convince people not to send or post Word documents. For about a year, I've made a practice of responding to Word attachments with a polite message explaining why the practice of sending Word files is a bad thing, and asking the person to resend the material in a nonsecret format. This is a lot less work than trying to read the somewhat obfuscated ASCII text in the Word file. And I find that people usually understand the issue, and many say they will not send Word files to others any more. People who disregard one polite request may change their practice when they receive multiple polite requests from various people. We may be able to give "don't send Word format" the status of netiquette, if we start systematically raising the issue with everyone who sends us Word files. To make this effort efficient, you will probably want to develop a canned reply that you can quickly send each time it is necessary. I've included two examples: the version I have been using recently, followed by a new version that teaches a Word user how to convert to other useful formats. They are followed by several suggestions sent by other people. You can use these replies verbatim if you like, or you can personalize them or write your own. By all means construct a reply that fits your ideas and your personality--if the replies are personal and not all alike, that will make the campaign more effective. These replies are meant for individuals who send Word files. When you encounter an organization that imposes use of Word format, that calls for a different sort of reply; Amazingly, some recruiters do this even when looking for someone for a free software job. Anyone hunting for a Word version of the resume will probably read this page. With our numbers, simply by asking, we can make a difference. You sent the attachment in Microsoft Word format, a secret proprietary format, so I cannot read it. If you send me the plain text, HTML, or PDF, then I could read it. Sending people documents in Word format has bad effects, because that practice puts pressure on them to use Microsoft software. In effect, you become a buttress of the Microsoft monopoly. This specific problem is a major obstacle to the broader adoption of GNU/Linux. Would you please reconsider the use of Word format for communication with other people? You sent the attachment in Microsoft Word format, a secret proprietary format, so it is hard for me to read. If you send me plain text, HTML, or PDF, then I will read it. Distributing documents in Word format is bad for you and for others. You can't be sure what they will look like if someone views them with a different version of Word; Sending Word attachments is bad for you, because a Word document normally includes hidden information about the author, enabling those in the know to pry into the author's activities (maybe yours). Text that you think you deleted may still be embarrassingly present. But above all, sending people Word documents puts pressure on them to use Microsoft software and helps to deny them any other choice. In effect, you become a buttress of the Microsoft monopoly. This pressure is a major obstacle to the broader adoption of free software. Would you please reconsider the use of Word format for communication with other people? Open the document, click on File, then Save As, and in the Save As Type strip box at the bottom of the box, choose HTML Document or Web Page. You can then attach the new HTML document instead of your Word document. Note that Word changes in inconsistent ways--if you see slightly different menu item names, please try them. To convert to plain text is almost the same--instead of HTML Document, choose Text Only or Text Document as the Save As Type. Your computer may also have a program to convert to pdf format. Scroll through available printers and select the pdf converter. Click on the Print button and enter a name for the pdf file when requested. It requires that you edit it for the specific example, and it presumes you have a way to extract the contents and see how long they are. Why did you choose to send me 876,377 bytes in your recent message when the content is only 27,133 bytes? Microsoft can (and did recently in Kenya and Brazil) have local police enforce laws that prohibit students from studying the code, prohibit entrepeneurs starting new companies, and prohibit professionals offering their services.
Cache (70 bytes)
www.versiontracker.com/dyn/moreinfo/macos/126
E-mail a Friend about Adobe PDF Printer Driver Plug-in 10 Broken Link?