[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
>>>>> "G" == Gregory Leblanc <GLeblanc@cu-portland.edu> writes:
>> -----Original Message----- From: Gary Lawrence Murphy
>> ... and I'd be extremely grateful if you could just
>> outline the entire process and tool set you use to process
>> these files into print editions.
G> I'm assuming you're asking this of the LDP, and not someone
G> else, so I'll try to answer as best I can.
My post was in response to a post on DocBook XML, and that is the
process where I needed an outline; I can do the Jade thing in my sleep
now, but need to make the jump into the XML way of doing things.
Actually, as it turns out, I won't need it: MCP has backed down on
using DocBook for the publishing process. Authors can write in
DocBook and typesetting is all gung-ho for XML, but the files will
continue to be munged into MsWord because editorial review had a bird
over learning the DocBook tools.
In my experience, which I vow never to repeat, this conversion process
ruins all semantic structure of a document. The result is akin to
transforming a graphic image into ASCII and then expecting someone who
does not know the content to transform it back into a full-color
image; the process is so horribly lossy that it is virtually
impossible to create proper and correct technical documents. Do I
If anyone knows of a publisher who _will_ use DocBook end to end,
please let me know ;)
Gary Lawrence Murphy <email@example.com>: office voice/fax: 01 519 4222723
TCI - Business Innovations through Open Source : http://www.teledyn.com
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com