Thank you, very helpfull.
Whe you say: translate Unicode characters to character entities (e.g.,
ccaron;)
I can't get the character entitie displayed correct in FrameMaker, it either
becomes a variable (with the unicode value or (when mapped in the rules file) a
wrong character?
Met
Has anyone compared Astoria to Vasont as a CMS system appropriate for
use with Structured FrameMaker?
Any showstoppers for either?
Any recommendations?
Thanks
Jim Light
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
At 08:30 AM 5/8/2006, Jim Light wrote:
I need to create a conversion table to convert a non-structured document
to SFM. ... How does the conversion mechanism deal with insets?
Jim,
Since text insets remain text insets when a document is structured, the
conversion table cannot change the
Follow up?
All my insets are currently unstructured FrameMaker files. The
conversion would leave them as structured FrameMaker files, I suppose.
If so, that means that when I export the container file as XML all the
insets would be included within the XML.
TO get separate XML files on export,
$paranum\t$paratext\t\t$pagenum
which now does what I want. If the TOC entry is one line, no impact.
If the TOC entry is two lines, the page number still right aligns.
This is what I want.
However...I'm interested in other ways of doing this. If anyone has a
more gracefull way of addressing it,
I have been watching this thread with not a little interest.
This sounds like the West Street Consulting plug-in InsetPlus would be
the tool of choice. Wouldn't hurt to take a look at it.
http://www.weststreetconsulting.com/WSC_PurchaseDownloads.htm
And the price is right, free.
-Original
$paranum\t$paratext\t\t$pagenum
which now does what I want.
I don't know if it's more graceful, but I use a run-in
paragraph for $chapnum and a separate in-column paragraph
for the rest. This
Thanks, The \t\t seems works OK for now. The only tweak I'd like to
make is to have the page
Is the whole purpose of this to create sidehead heading?
The documentation (such as it is :)) for WebWorks
Standard, which comes with FrameMaker 7.0, says it
can create a 2-frame page for a multi-doc set where
the titles of the docs remain listed in the left
pane while the contents
Hi, gang!
Anyone ever found a way to convert old Mac OS PageMaker files into FM?
~ Don S.
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL
Hi folks
This is just an annoyance, but I thought I'd ask in case I'm doing something
horribly wrong. I'm doing a lot of work in an FM document that includes a
75-page long table, landscape format. When I use the mouse wheel to scroll from
page to page, the response is mostly pretty jerky -
Thank you, very helpfull.
Whe you say: translate Unicode characters to character entities (e.g.,
)
I can't get the character entitie displayed correct in FrameMaker, it either
becomes a variable (with the unicode value or (when mapped in the rules file) a
wrong character?
Met vriendelijke
Thnak you.
one question:
if you say - does this mean that
the whole target XML will be in ASCII or only the 'changed' parts? What effect
would this have on other unicode characters that we don't want to convert? And:
can such a XSLT also be used on export of XML to transform the ASCII back
A couple of things: set the autonumber format in the Paragraph format to
<$chapnum> instead of . Frame uses the chapnum variable automatically,
set up the numbering from the Book file (you can do this in each file, but
I just find it easier to work from the book file).
To set up the
Oops! I forgot the version of Frame that he is using does not use chapnum.
Sorry!
Susan
- Forwarded by Susan Mcdonald/Bos/Teradyne on 05/08/2006 09:55 AM
-
Susan Mcdonald/Bos/Teradyne
05/08/2006 09:52 AM
To
framers at lists.frameusers.com
cc
Subject
Re: Framers Digest, Vol 7, Issue
At 05:55 AM 5/8/2006, Wim Hooghwinkel \(Scriptware\) wrote:
>I can't get the character entitie displayed correct in FrameMaker, it
>either becomes a variable (with the unicode value or (when mapped in the
>rules file) a wrong character?
Wim,
Make sure your r/w rules specify FrameMaker
Has anyone compared Astoria to Vasont as a CMS system appropriate for
use with Structured FrameMaker?
Any showstoppers for either?
Any recommendations?
Thanks
Jim Light
I need to create a conversion table to convert a non-structured document
to SFM. The files contain insets and I have not dealt with insets, yet,
so I have two questions:
I know that the spell checker and the Find/Change utility cannot search
insets, so I'm worried about how the conversion tool
At 08:30 AM 5/8/2006, Jim Light wrote:
>I need to create a conversion table to convert a non-structured document
>to SFM. ... How does the conversion mechanism deal with insets?
Jim,
Since text insets remain text insets when a document is structured, the
conversion table cannot change the
Follow up?
All my insets are currently unstructured FrameMaker files. The
conversion would leave them as structured FrameMaker files, I suppose.
If so, that means that when I export the container file as XML all the
insets would be included within the XML.
TO get separate XML files on export,
> <$paranum>\t<$paratext>\t\t<$pagenum>
>
> which now does what I want. If the TOC entry is one line, no impact.
> If the TOC entry is two lines, the page number still right aligns.
> This is what I want.
>
> However...I'm interested in other ways of doing this. If anyone has a
> more gracefull
I have been watching this thread with not a little interest.
This sounds like the West Street Consulting plug-in "InsetPlus" would be
the tool of choice. Wouldn't hurt to take a look at it.
http://www.weststreetconsulting.com/WSC_PurchaseDownloads.htm
And the price is right, free.
I have been watching this thread with not a little interest.
This sounds like the West Street Consulting plug-in "InsetPlus" would be
the tool of choice. Wouldn't hurt to take a look at it.
http://www.weststreetconsulting.com/WSC_PurchaseDownloads.htm
And the price is right, free.
> > <$paranum>\t<$paratext>\t\t<$pagenum>
> > which now does what I want.
>
> I don't know if it's more graceful, but I use a run-in
> paragraph for <$chapnum> and a separate in-column paragraph
> for the rest. This
Thanks, The \t\t seems works OK for now. The only tweak I'd like to
make is
The documentation (such as it is :)) for WebWorks Standard, which comes with
FrameMaker 7.0, says it can create a 2-frame page for a multi-doc set where
the titles of the docs remain listed in the left pane while the contents
display in the right pane.
I have not been able to get this to work in
I appreciate any guidance on this frustrating puzzle -
I am generating WW Help 5 from a 258pp, 21-chapter software manual done
in FrameMaker 7.2. I use pretty mundane indexing, with some help from
IXgen. There are some multiple entries in a single marker, a few
<$nopage> entries, but nothing
It sounds like you might want to use the frameset version of the Dynamic
HTML template. I have made this work when I configured it all in WWP Pro,
then ran the template in WWP Standard. I'm not sure where in WWP Standard
to find the settings that make this work.
In the frameset version of the
Hi, gang!
Anyone ever found a way to convert old Mac OS PageMaker files into FM?
~ Don S.
27 matches
Mail list logo