Lars Nooden [mailto:[email protected]] > > On 4/7/10 5:30 PM, McLauchlan, Kevin wrote: > > > My crystal ball ... > > Save the speculation for the stock market and the sob story > for someone who cares.
Hee hee. :-) > Having a metric buttload of legacy documents and a great wish > to be able > to recover them in editable form, won't make them editable. > Even needing the documents to be editable won't make them so > unless they > already are in a source format, like ODF. I think my point, later on, was that more-recent flavors from Adobe might be turning that around. I know all about what PDF is _supposed_ to be for. I've been making that same argument to ignorant folk (often with budgetary and decision-making power) for years. I used to refer them to the Adobe web site, where Adobe said a lot of the same thing. But... I think even Adobe is beginning to bow to the inevitable. > > PDF it is then. Dozens of them. No source text. No source > > drawings or screen-caps or photos. > > If you have to change them, then you are looking at rekeying. That's > similar as when businesses started to scan in their old paper records. > > > By the way, aren't there signs - in recent versions of ... > There are signs that OpenOffice.org is being adopted more in > the public > sector to fulfill the requirements to use ODF. As ODF includes more > complete SVG support, then it will be easier to work with Scribus and > other DTP tools. Spoken like a true politician. My primary reason for choosing OOo is its non-MS-ness. Next is that the price is right. I've owned MS-Office before, personally, at roughly a thousand bucks (circa 1997) - won't do that again. Next is that OOo is cross-platform - though that's become less strictly important as I use my MacBook Pro more and my Linux boxes less-and-less. After that, there are a few things that Word 2003 does nasty that OOo doesn't break as badly. However, for some things that OOo breaks, or makes difficult for me, I now have InDesign at work. That's WAY overkill for the small handful of small docs that I'll be using it to produce, but hey... they were willing to buy it for me. The majority of my big work is now WebHelp, created in MadCap Flare. That leaves OOo for some lengthy reference guides and toolkit docs that I would formerly have done in FrameMaker. I could probably use OOo for a wider selection of my stuff (except the WebHelp), but there's no pressing incentive. At least I've been able to minimize any use of Word. That counts for a lot in my book. :-) The next time we get a clump of PDFs with no source, I'll be trying every tool at my disposal to avoid having to re-type 'em. Haven't seen a way to fit Scribus into my workflow. Not yet, anyway. - KThe information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
