With a bit of duct-tape, Excel worksheets, and Python scripts, the
future is now. We use 'out-of-band' index entries to produce
back-of-the-book indexes.
The index is authored separately from the body text, using simple Excel
worksheets as the exchange format, and associated to the body text
With a bit of duct-tape, Excel worksheets, and Python scripts, the
future is now. We use 'out-of-band' index entries to produce
back-of-the-book indexes.
The index is authored separately from the body text, using simple Excel
worksheets as the exchange format, and associated to the body text
Eric Dunn wrote:
> Now what exactly is the difference between "hunt and peck" and "drill".
Drilling through a graphical user interface would involve pointing at hot
spots to get to the subsystem of interest, then working from a list of
commonly required process - Servicing, Repair Procedures,
Eric Dunn wrote:
Now what exactly is the difference between hunt and peck and drill.
Drilling through a graphical user interface would involve pointing at hot
spots to get to the subsystem of interest, then working from a list of
commonly required process - Servicing, Repair Procedures, etc.
Marcus Carr [EMAIL PROTECTED] on 02/22/2007 10:46:17 PM:
For our mechanically gifted friend, I'd be
inclined to provide a graphic interface and a touch screen that let him
drill to the warp drive than compel him to hunt and peck on a toughened
keyboard. An index may have its place, but it's
Hedley Finger wrote:
> The original discussion was, generally, about what Adobe needed to do
> to find out what functionality their customers would need in the
> future.
>
> I attempted to make the point that a study of the third-party plugins
> would indicate to Adobe the gaps in FrameMaker's
Marcus, Marcus, Marcus:
> > I attempted to make the point that a study of the third-party plugins
> > would indicate to Adobe the gaps in FrameMaker's functionality that
> > they need to address, and chose indexing plugins as an example where
> > there are many independent plugins to improve this
hedley.finger at myob.com wrote:
> Marcus, Marcus, Marcus:
Hedley, Hedley, Hedley... :-)
> I'm surprised that you of all people should associate functionality
> with presentation. It's a bit similar to separating format from
> content. 8^) And I'm surprised that you equate indexes only with
Marcus^3:
The example of the Turbo Tarburner was chosen with care. Even as we
bicker, a major automotive manufacturer is implementing an on-demand
customised workshop manual.
The mechanic will simply enter the car's body number or VIN or whatever,
and a custom manual for just the equipment
H4y^3,
hedley.finger at myob.com wrote:
> The example of the Turbo Tarburner was chosen with care. Even as we
> bicker, a major automotive manufacturer is implementing an on-demand
> customised workshop manual.
>
> The mechanic will simply enter the car's body number or VIN or
> whatever, and
Hedley Finger wrote:
The original discussion was, generally, about what Adobe needed to do
to find out what functionality their customers would need in the
future.
I attempted to make the point that a study of the third-party plugins
would indicate to Adobe the gaps in FrameMaker's
Marcus, Marcus, Marcus:
I attempted to make the point that a study of the third-party plugins
would indicate to Adobe the gaps in FrameMaker's functionality that
they need to address, and chose indexing plugins as an example where
there are many independent plugins to improve this
[EMAIL PROTECTED] wrote:
Marcus, Marcus, Marcus:
Hedley, Hedley, Hedley... :-)
I'm surprised that you of all people should associate functionality
with presentation. It's a bit similar to separating format from
content. 8^) And I'm surprised that you equate indexes only with
hardcopy.
Marcus^3:
The example of the Turbo Tarburner was chosen with care. Even as we
bicker, a major automotive manufacturer is implementing an on-demand
customised workshop manual.
The mechanic will simply enter the car's body number or VIN or whatever,
and a custom manual for just the equipment
H4y^3,
[EMAIL PROTECTED] wrote:
The example of the Turbo Tarburner was chosen with care. Even as we
bicker, a major automotive manufacturer is implementing an on-demand
customised workshop manual.
The mechanic will simply enter the car's body number or VIN or
whatever, and a custom manual
Since my post about plugins diverted this thread from its original topic
onto a discussion of the merits of plugins, may I amplify my remarks?
The original discussion was, generally, about what Adobe needed to do to
find out what functionality their customers would need in the future.
I
Since my post about plugins diverted this thread from its original topic
onto a discussion of the merits of plugins, may I amplify my remarks?
The original discussion was, generally, about what Adobe needed to do to
find out what functionality their customers would need in the future.
I
17 matches
Mail list logo
