Ridder, Fred wrote:
What's important in this mode of operation is to give the flows
useful, descriptive names (rather than the default A, B, etc.)
that uniquely identify each chunk. The challenge is to keep the
names short since the list box in the Import Flow... dialog
only displays about 20
> Hedley Finger wrote:
>
> > Problem: while you can Open All Files in a book, there
> > appears to be no global way of opening all the text insets in
> > all the components of a book.
Thanks to all who contributed to this one. Replies and clarifications in
no particular order: (1) The
Ridder, Fred wrote:
> What's important in this mode of operation is to give the flows
> useful, descriptive names (rather than the default A, B, etc.)
> that uniquely identify each chunk. The challenge is to keep the
> names short since the list box in the Import Flow... dialog
> only displays
Hello Hedley,
I create a new FrameMaker book (I call it a repository.book) in which I
collect all my text insets. I use this repository.book for spell-checking,
global changes etc.
Admitted, it's a workaround, but it works pretty well.
Best regards
--
Yves Barbion
Technical Writer
Hedley, Richard,
If, indeed, there are many hundreds, you may want
to use Framescript to create the books. :-)
Note that there's a free FrameScript available:
BookOfTextInsets.fsl v1.6
Creates a new temporary book with all (nested) text
insets of the current document or book. This
All:
Some time before IBM released DITA to a puzzled and unsuspecting world, a
colleague of mine solved the problem of repurposing/reusing small
fragments of content using text insets. Basically, the components of a
book consist of shell files that contain nothing but text insets. This
Hello Hedley,
I create a new FrameMaker book (I call it a "repository.book") in which I
collect all my text insets. I use this repository.book for spell-checking,
global changes etc.
Admitted, it's a workaround, but it works pretty well.
Best regards
--
Yves Barbion
Technical Writer
Hedley Finger wrote:
> Problem: while you can Open All Files in a book, there
> appears to be no global way of opening all the text insets in
> all the components of a book.
I've used Yves' solution of a book of text inset source files, and it
works nicely.
Do you create an individual FM
Hedley, Richard,
> > If, indeed, there are many hundreds, you may want
> > to use Framescript to create the books. :-)
Note that there's a free FrameScript available:
BookOfTextInsets.fsl v1.6
Creates a new temporary book with all (nested) text
insets of the current document or book.
l text insets in all components in a book ...
phew!
> Hedley Finger wrote:
>
> > Problem: while you can Open All Files in a book, there
> > appears to be no global way of opening all the text insets in
> > all the components of a book.
Thanks to all who con
All:
Some time before IBM released DITA to a puzzled and unsuspecting world, a
colleague of mine solved the problem of repurposing/reusing small
fragments of content using text insets. Basically, the components of a
book consist of shell files that contain nothing but text insets. This
11 matches
Mail list logo
