Hi Rick,
Similarly to Linda I moved from FM 8 to FM 10 on Windows 7 early this year.
I use the Track Text Edits feature for all documents.
My experience:
o Mandatory for me to see exact changes:
What exactly has changed.
Which change do I have to communicate to others.
Which file must be
Jang, I think we're in agreement. I wasn't suggesting format rules over
formats stored in catalogs. I was only saying that the formatting *triggers*
have to be stored in the EDD. Maybe I didn't make the point clearly, but that
was what I meant to say. I personally prefer to use formats
Just my two cents on this.
There is no right answer. Depends where you want the control to be and
maybe your philosophical approach - as in no formatting in the EDD.
When I went structured, it was an opportunity to reduce paragraph format
bloat. I analyzed what I needed, pared down the
I like Fred's arguments here. I have mainly advocated the
Paragraph/Character format approach in EDDs for two main reasons:
1) It is generally easier to have a single EDD work with multiple templates,
which is advantageous for some document sets.
2) It allows the client a bit of flexibility in
Hi Rick,
I'll just split this up into a pro and con list. :) Bottom line up front:
its a decent solution if you are using it for a small team with three
writers or less but it does not scale well at all in terms of content OR
the number of users making edits. You'd be better off just using the
Hi guys
If you're planning to roundtrip through XML, with different authors
using different XML editors, you'd need to have all the formatting in
the EDD, right?
Or am I on completely the wrong track in my ignorance?
Thanks
Rebecca
Rick Quatro r...@rickquatro.com 14/09/12 10:02
I like
You don't need to use structured FM for that. My paragraph tags map to
different formats / tags depending on whether the output is PDF, Web
help, Confluence XHTML, or 7-bit ASCII with layout.
On Thu, Sep 13, 2012 at 10:29 AM, Fred Wersan fwer...@mak.com wrote:
A previous respondent said:
The
Goal: Upon generating a PDF, checkboxes appear next to each paragraph of
a particular type, aligned right against the page margin. Can not use
autonumbering, because the paragraph tag already has numbers. Can not
manually create them in the PDF post-distillation, because we're talking
about
Hi Rick,
Similarly to Linda I moved from FM 8 to FM 10 on Windows 7 early this year.
I use the Track Text Edits feature for all documents.
My experience:
o Mandatory for me to see exact changes:
What exactly has changed.
Which change do I have to communicate to others.
Which file must be
ith
Scott that going via true XML might be a good solution, but only if the
authors are not pulled out of their comfort zone too much.
Ciao
Jang
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.frameusers.com/pipermail/framers/attachments/2012
Just my two cents on this.
There is no right answer. Depends where you want the control to be and
maybe your philosophical approach - as in "no formatting in the EDD".
When I went structured, it was an opportunity to reduce paragraph format
bloat. I analyzed what I needed, pared down the
I like Fred's arguments here. I have mainly advocated the
Paragraph/Character format approach in EDDs for two main reasons:
1) It is generally easier to have a single EDD work with multiple templates,
which is advantageous for some document sets.
2) It allows the client a bit of flexibility in
You don't need to use structured FM for that. My paragraph tags map to
different formats / tags depending on whether the output is PDF, Web
help, Confluence XHTML, or 7-bit ASCII with layout.
On Thu, Sep 13, 2012 at 10:29 AM, Fred Wersan wrote:
> A previous respondent said: "
>
> The idea with
Goal: Upon generating a PDF, checkboxes appear next to each paragraph of
a particular type, aligned right against the page margin. Can not use
autonumbering, because the paragraph tag already has numbers. Can not
manually create them in the PDF post-distillation, because we're talking
about
14 matches
Mail list logo
