Categories: technology, work
Current music: Groove Salad
Just before I took off for lunch today, the contractor who picked up the projects I was working on before the reorg motioned me over and asked me, “how did you do it? You put together the whole shell of this project, and I’m just hanging stuff on it. Especially the command-line stuff... how did you get so much of it done with nothing to work with?” Pulling miracles out of my, er, back pocket has been a lot of what I’ve done at the office for the last few years. I got deadlines, limited access (at best) to equipment, a little help from my boss when he’s not swamped with other stuff, very little in the way of specifications, and somehow I managed to maintain documentation for three entire product lines.
My secret is: I’m lazy.
Look, I sit in front of a computer all day. If I can get the computer to do something for me, especially if it’s something that needs to be done more than once, I’ll do it. For example, our original (now “legacy”) product line came with about 4000 pages of documentation scattered over about 20 different manuals. We provided a master index, a 110-page book of its own, as a way to let customers zero in on which manual(s) covered a particular topic. The first time I did the master index, it took two solid weeks of nothing else. This is one of those prime examples for automation: I had to build a book in FrameMaker of all the other books, tag each chapter in each manual, run the index, convert the tags to document references (for example, change “EG” to Engineering Guidelines), remove all but the first reference to any chapter, blah blah blah. To make a long story shorter, I wrote a handful of AppleScripts that eliminated literally 80% of the grunt work: instead of two weeks, I could build the master index in two days. Yesterday, I wrote a script that created index entries from headings (which is OK for a first pass at indexing commands) that saved me a day’s worth of work.
I told you all that to tell you this.
A couple of weeks ago, I wrote about Massachusetts adopting Open Document Format (ODF) for state government documents. Between than and now, OpenOffice 2.0 went into beta test; yesterday, OASIS (Organization for the Advancement of Structured Information Standards) submitted ODF to the International Standards Organization (ISO) for consideration as an international standard for office document interchange.
The neat thing about all this is that the ODF format is easy to pick apart and fiddle with. Internally, content, graphics, and style information are separated and the whole thing is rolled up in a ZIP file. Content and style files use an XML format, which is important for two reasons: XML is plain text, and there are lots of utilities to work with it. So what does that mean? There are several Free programs that support ODF already (OpenOffice and AbiWord run on most computers, while Koffice also runs on Linux systems). But the really fun part is, given a document format both open and relatively easy to parse, you don’t need an office application to do things with ODF files.
In the computing world, when a group like OASIS sets out to nail down a standard, they form a Technical Committee (TC) of interested parties. In the case of the ODF TC, some of the interested parties include companies that make content management systems (or CMS... the alphabet soup is sloshing around quite a bit tonight!) — suffice it to say that a CMS allows you to store, retrieve, and process documents to make something new (kind of like putting basil leaves in a food processor and making pesto). Given the job of a CMS, it usually doesn’t just store a document as-is. In the case of an ODF file, the CMS would probably unzip it and extract just the content and metadata (data about the data) components. The graphics are already stored in the CMS. Let’s say I send a document to the CMS and come back for it a couple of months later. During that time, some of the artwork has been changed. The CMS grabs the original content and metadata, rolls in the updated graphics, and hands me an ODF file. Oh cool, I didn’t have to update the graphics myself!
Another handy utility might be nightly publishing runs. Sometimes, I’m working on a manual that’s getting change requests and bug reports coming in fast & furious. Some of the manuals I deal with have a lot of bitmap graphics, and can take nearly an hour to generate a PDF. Remember, I’m lazy... I don’t want to sit at work an hour overtime just to watch the computer make a PDF. In my theoretical ODF-based system, I simply send in the stuff I worked on during the day, and the CMS builds a new document and emails it (with a summary of what changed) to all the reviewers. The reviewers get fresh hot documentation every morning; I get to go home, sit on the porch, and write haiku before it gets dark.
With the manual finished, I have to send it to the translators. Currently, this involves gathering all the various files together and archiving them (and sending missing pieces or assuring them that the extraneous files aren’t important). In my dream system, I tell the CMS to give me an ODF document of the book. Boom, all the pieces get wrapped together, nothing gets dropped, nothing extra gets added, and I send one file to the translators.
I’m willing to put some effort into making this a reality. After all, I want the computer to do the work for me.
Showing posts with label computers. Show all posts
Showing posts with label computers. Show all posts
Friday, October 14, 2005 2 comments
Wednesday, September 07, 2005 No comments
More FrameMaker 7.2 Leakage
A post on the FrameUsers mailing list (thanks Thomas!) suggests doing a Google search on “FrameMaker new multiple undo” and then reading the cached page from Adobe UK (the first link when I tried it). Doing this turns up some more new features:
A sidebar had links for Solaris and Microsoft updates, suggesting that MacOS users are still left out. Figures.
- multiple undo (one of those long-standing malfeatures I griped about yesterday)
- some support for XML Schema (probably conversion to EDD)
- support for native Photoshop (PSD) files
A sidebar had links for Solaris and Microsoft updates, suggesting that MacOS users are still left out. Figures.
Tuesday, September 06, 2005 1 comment
Adobe Leaks FrameMaker 7.2 Info
In which I take a break from chronicling my personal life and talk about work stuff.
Over the Labor Day weekend, various pages on Adobe’s website mentioned the unreleased version 7.2 of FrameMaker, the preferred tool of the trade for most technical writers (who often affectionately call it “Frame”). Adobe (usually one to hold its cards close to the vest) has since revised the pages, although the old ones lived another day in Google’s caches before those too were updated.
But haste often leads to things getting skipped over, and that was the case with a migration guide white paper on Adobe Germany’s site. I grabbed an unrevised copy of the PDF Tuesday afternoon; the good people at Adobe.de have certainly gone home for the day but I expect the white paper to be sanitized first thing tomorrow morning (by about 2 a.m. EDT).
If you download too late, here’s what searching the PDF for “7.2” turned up in the way of new features:
All this is structure-related, which doesn’t do you much good if you aren’t interested in moving to structured Frame. I’m sure that there will be the usual bug replacements (i.e. removing some known bugs and introducing new bugs) as well.
A group of vendors and trainers have been constantly flogging their “FrameMaker Chautauqua” conference on various mailing lists where FrameMaker is either the main or a common topic. The conference includes presentations by Adobe and will be held in early November, so I expect that Adobe will officially announce version 7.2 either at the conference or shortly before. If I’m right, it’s safe to assume that 7.2 is in beta testing right now.
FrameMaker has languished in a near-limbo pretty much since Adobe bought up Frame Technologies some years back. Frame has benefitted from minor updates from time to time, but long-standing bugs and malfeatures have persisted. That, and an abortive foray into porting the Unix version to Linux, have lead many to believe that Adobe is less than enthusiastic about supporting the program. The final straw for some of us was in January 2004, when Adobe dropped support for MacOS citing lack of sales (largely brought on by Adobe’s reluctance to modernize the MacOS version to run natively on MacOS X, leaving FrameMaker one of the last reasons to ever use the “Classic” environment).
Pretty much all summer, the “Chautauqua” people have been hyping Adobe’s presence at their upcoming conference, promising Frame users that they won’t be disappointed by what Adobe has to say about Frame’s life expectancy. Unfortunately, there’s no word on re-introducing MacOS support, preferably for MacOS X. That’s a show-stopper for me and many others: if the rest of the tool chain works well, why change the underlying platform if one tool is no longer supported?
Personally, even if Adobe repents of Windows-centricity, I’m not convinced that page-oriented WYSIWYG tools like Frame are the way forward for technical writing — in a world where our final output is more likely to be PDF and HTML than paper, it doesn’t make much sense to work on the electronic equivalent of a printed page. It makes more sense nowadays to work with markup, either directly (ooo, icky tags, say my less-technical brethren and sistren) or indirectly through an interface that provides formatting hints but no fixed margins or other page-centric details. LyX is a good example of the latter kind of program.
In the end, I expect little or no surprises come November. I’m certainly not going to ask my boss for $695 + hotel to attend a conference for a tool I’m currently planning to abandon, even if the conference is close enough to drive to.
Over the Labor Day weekend, various pages on Adobe’s website mentioned the unreleased version 7.2 of FrameMaker, the preferred tool of the trade for most technical writers (who often affectionately call it “Frame”). Adobe (usually one to hold its cards close to the vest) has since revised the pages, although the old ones lived another day in Google’s caches before those too were updated.
But haste often leads to things getting skipped over, and that was the case with a migration guide white paper on Adobe Germany’s site. I grabbed an unrevised copy of the PDF Tuesday afternoon; the good people at Adobe.de have certainly gone home for the day but I expect the white paper to be sanitized first thing tomorrow morning (by about 2 a.m. EDT).
If you download too late, here’s what searching the PDF for “7.2” turned up in the way of new features:
- XSL processing at XML import and export (alongside existing read/write rules) — this is a feature I’ve wished for, but (see below) probably won’t get.
- Conversion tables, which add structure to unstructured files, can create a “first draft” EDD (a combination of DTD and style sheet).
- Conversion tables also support a “root element” to be applied to the converted document.
All this is structure-related, which doesn’t do you much good if you aren’t interested in moving to structured Frame. I’m sure that there will be the usual bug replacements (i.e. removing some known bugs and introducing new bugs) as well.
A group of vendors and trainers have been constantly flogging their “FrameMaker Chautauqua” conference on various mailing lists where FrameMaker is either the main or a common topic. The conference includes presentations by Adobe and will be held in early November, so I expect that Adobe will officially announce version 7.2 either at the conference or shortly before. If I’m right, it’s safe to assume that 7.2 is in beta testing right now.
FrameMaker has languished in a near-limbo pretty much since Adobe bought up Frame Technologies some years back. Frame has benefitted from minor updates from time to time, but long-standing bugs and malfeatures have persisted. That, and an abortive foray into porting the Unix version to Linux, have lead many to believe that Adobe is less than enthusiastic about supporting the program. The final straw for some of us was in January 2004, when Adobe dropped support for MacOS citing lack of sales (largely brought on by Adobe’s reluctance to modernize the MacOS version to run natively on MacOS X, leaving FrameMaker one of the last reasons to ever use the “Classic” environment).
Pretty much all summer, the “Chautauqua” people have been hyping Adobe’s presence at their upcoming conference, promising Frame users that they won’t be disappointed by what Adobe has to say about Frame’s life expectancy. Unfortunately, there’s no word on re-introducing MacOS support, preferably for MacOS X. That’s a show-stopper for me and many others: if the rest of the tool chain works well, why change the underlying platform if one tool is no longer supported?
Personally, even if Adobe repents of Windows-centricity, I’m not convinced that page-oriented WYSIWYG tools like Frame are the way forward for technical writing — in a world where our final output is more likely to be PDF and HTML than paper, it doesn’t make much sense to work on the electronic equivalent of a printed page. It makes more sense nowadays to work with markup, either directly (ooo, icky tags, say my less-technical brethren and sistren) or indirectly through an interface that provides formatting hints but no fixed margins or other page-centric details. LyX is a good example of the latter kind of program.
In the end, I expect little or no surprises come November. I’m certainly not going to ask my boss for $695 + hotel to attend a conference for a tool I’m currently planning to abandon, even if the conference is close enough to drive to.
Monday, August 22, 2005 No comments
A Boy and his computer
Current Music: BeatBlender
After a rather unpleasant episode Friday, The Boy and his aunt (whom we shall call “Big V” here on the blog) sort of patched things up between them. They have made a pact to help each other track their glucose levels (she's Type II, he's Type I), and today he had his act sufficiently together that he was pretty civil for a change (I've noticed he really gets whacked out when his glucose goes about 220 or so). So Friday, he was probably riding a serious sugar jag; he wrote this rambling letter about how much he hates us for trying to separate him & his girlfriend (we aren't trying, but would be overjoyed if it happened) and made a not-so-veiled threat to kill himself if he succeeded. That was enough to get me to call the local mental health agency and talk to a counselor there. We agreed that he needed to get in there, although there just wasn't any way to force him to go.
So today, he asked me to call him. Turns out he wanted to use the iMac that was still in his old bedroom to write papers and so forth. I didn't have any problem with that — when you need a computer you need a computer — so I tossed it and a smallish desk in the van and drove it down to Big V's place.
The interesting part was when I asked him what his paper was about. “Psychology,” he said. “I have to interview a psychologist.” Welllll, I was right there with a name and contact info on that one. On the way out, Big V stopped me and told me she was booting the girlfriend tomorrow because she was giving The Boy cigarettes. Perhaps our prayers are being answered!
After a rather unpleasant episode Friday, The Boy and his aunt (whom we shall call “Big V” here on the blog) sort of patched things up between them. They have made a pact to help each other track their glucose levels (she's Type II, he's Type I), and today he had his act sufficiently together that he was pretty civil for a change (I've noticed he really gets whacked out when his glucose goes about 220 or so). So Friday, he was probably riding a serious sugar jag; he wrote this rambling letter about how much he hates us for trying to separate him & his girlfriend (we aren't trying, but would be overjoyed if it happened) and made a not-so-veiled threat to kill himself if he succeeded. That was enough to get me to call the local mental health agency and talk to a counselor there. We agreed that he needed to get in there, although there just wasn't any way to force him to go.
So today, he asked me to call him. Turns out he wanted to use the iMac that was still in his old bedroom to write papers and so forth. I didn't have any problem with that — when you need a computer you need a computer — so I tossed it and a smallish desk in the van and drove it down to Big V's place.
The interesting part was when I asked him what his paper was about. “Psychology,” he said. “I have to interview a psychologist.” Welllll, I was right there with a name and contact info on that one. On the way out, Big V stopped me and told me she was booting the girlfriend tomorrow because she was giving The Boy cigarettes. Perhaps our prayers are being answered!
Wednesday, August 17, 2005 No comments
Computer-related items
Current music: BassDrive
A few more or less related news items and personal notes about today's and tomorrow's computers....
Well, that didn't take long: hackers got the development version of OSX86 running on standard PCs. Personally, I don't see much to get excited about. I (erroneously) expected Mac sales to crater in response to the announcement that Apple is moving to Intel CPUs over the next two years; it hasn't happened yet. My guess that the Intel-based Macs will use a 64-bit CPU and the OS won't run on the current (32-bit) Pentiums. Given I'm 0-1 on this topic so far, though, take that with a grain of salt. If the plan is to use Pentiums for the newer Macs, I doubt that Apple will put that much effort into locking it down — they'll do enough to make it non-trivial, and those people who buy OSX86 and install it on their white boxes will be on their own, support-wise. The way I see it, if Apple sells ten times more OSX86 boxes than their current Mac sales figures, they'll break even on sales and win big on margins.
On my own iBook, I've switched back to Apple's Safari browser. It's tons faster than what I was using (Camino) and it's built-in RSS aggregator works very well. If you were using Safari to read Tales from FAR Manor, you would see a little “RSS” button in the address bar. Click on that, and you'd get the RSS feed for my blog. You can bookmark the RSS feed and it will count the number of unread posts you have in that directory. It's really nice. Dashboard and Automator are everything they're cracked up to be as well. I'm using an older version of OSX (10.2.8) at work, and I already miss having these functions.
Speaking of iBooks, you had to have heard about the stampede in Richmond VA. Wazoo! I think I'd have eBay'ed the whole shebang myself; they could have easily raised $300,000 that way. But you can't expect intelligent thought from a school system that dumps computers that work and replace them with Smelly Dells. Unfortunately, when you use low-bidder purchasing, you get what you pay for.
I sure hope that school district isn't running W2K on their new computers. The Zotob worm hosed up bigger and much better-funded entities than a school district. Another report said ABC News had to use typewriters to get the news out. Wow... I'm surprised they even had any typewriters available, let alone enough to go around.
I'm being a good boy and not blogging from work. More tomorrow, if time allows. The Evil Twins are visiting, but fortunately they're already in bed. I should be in my bed as well. 'Night!
A few more or less related news items and personal notes about today's and tomorrow's computers....
Well, that didn't take long: hackers got the development version of OSX86 running on standard PCs. Personally, I don't see much to get excited about. I (erroneously) expected Mac sales to crater in response to the announcement that Apple is moving to Intel CPUs over the next two years; it hasn't happened yet. My guess that the Intel-based Macs will use a 64-bit CPU and the OS won't run on the current (32-bit) Pentiums. Given I'm 0-1 on this topic so far, though, take that with a grain of salt. If the plan is to use Pentiums for the newer Macs, I doubt that Apple will put that much effort into locking it down — they'll do enough to make it non-trivial, and those people who buy OSX86 and install it on their white boxes will be on their own, support-wise. The way I see it, if Apple sells ten times more OSX86 boxes than their current Mac sales figures, they'll break even on sales and win big on margins.
On my own iBook, I've switched back to Apple's Safari browser. It's tons faster than what I was using (Camino) and it's built-in RSS aggregator works very well. If you were using Safari to read Tales from FAR Manor, you would see a little “RSS” button in the address bar. Click on that, and you'd get the RSS feed for my blog. You can bookmark the RSS feed and it will count the number of unread posts you have in that directory. It's really nice. Dashboard and Automator are everything they're cracked up to be as well. I'm using an older version of OSX (10.2.8) at work, and I already miss having these functions.
Speaking of iBooks, you had to have heard about the stampede in Richmond VA. Wazoo! I think I'd have eBay'ed the whole shebang myself; they could have easily raised $300,000 that way. But you can't expect intelligent thought from a school system that dumps computers that work and replace them with Smelly Dells. Unfortunately, when you use low-bidder purchasing, you get what you pay for.
I sure hope that school district isn't running W2K on their new computers. The Zotob worm hosed up bigger and much better-funded entities than a school district. Another report said ABC News had to use typewriters to get the news out. Wow... I'm surprised they even had any typewriters available, let alone enough to go around.
I'm being a good boy and not blogging from work. More tomorrow, if time allows. The Evil Twins are visiting, but fortunately they're already in bed. I should be in my bed as well. 'Night!
Sunday, August 14, 2005 No comments
Cuddling up with Tiger
Current music: Groove Salad
They (who's they? You know, “them”!) say to never upgrade your computer when you have a deadline. Hey, I use Macs, I've never gotten bit before... until last night.
A while back, I wrote about cashing in some stock options. The check finally arrived, and after paying some bills there was about $250 left for “discretionary” items. Our Macs have been languishing on Jaguar (OSX 10.2) for some time now, more and more software requires something later nowadays, and frankly it's been chafing me. So we made a trip down to the mall to get a Tiger (OSX 10.4) “family pack” (5 licenses for less than 2 single licenses) and I got around to installing it yesterday. I figured I'd have it together in plenty of time to finish the church bulletin.
WRONG! Actually, it turned out that the only apps that flaked out were those I use to do the church bulletin: Vim, groff, and X11 (I use a PostScript viewer to check things before printing). I ended up switching over to NeoOffice and finishing up about 1:30 a.m.
It took a little poking and prodding, but all is well with my iBook again. I had to load X11 and Xcode (the development system) from the software DVD, download a Tiger-specific version of Vim, and recompile groff. I'm slowly poking at the new features, starting with Automater. Dashboard looks really nice too.
Vacation's pretty much over... I'll probably be back to updating two or three times a week after today.
They (who's they? You know, “them”!) say to never upgrade your computer when you have a deadline. Hey, I use Macs, I've never gotten bit before... until last night.
A while back, I wrote about cashing in some stock options. The check finally arrived, and after paying some bills there was about $250 left for “discretionary” items. Our Macs have been languishing on Jaguar (OSX 10.2) for some time now, more and more software requires something later nowadays, and frankly it's been chafing me. So we made a trip down to the mall to get a Tiger (OSX 10.4) “family pack” (5 licenses for less than 2 single licenses) and I got around to installing it yesterday. I figured I'd have it together in plenty of time to finish the church bulletin.
WRONG! Actually, it turned out that the only apps that flaked out were those I use to do the church bulletin: Vim, groff, and X11 (I use a PostScript viewer to check things before printing). I ended up switching over to NeoOffice and finishing up about 1:30 a.m.
It took a little poking and prodding, but all is well with my iBook again. I had to load X11 and Xcode (the development system) from the software DVD, download a Tiger-specific version of Vim, and recompile groff. I'm slowly poking at the new features, starting with Automater. Dashboard looks really nice too.
Vacation's pretty much over... I'll probably be back to updating two or three times a week after today.
Subscribe to:
Posts (Atom)
LinkWithin
