Tina wrote:
If I take out
the now disappeared long footnote (by deleting the footnote reference in the
text), all the other footnotes go back where they belong
Are you sure about this? If there are lots of long notes in the doc
it's very likely that FM has pushed some of them in their entirety
On 17 Oct 2007 at 12:59, Tina Ricks wrote:
Has anyone seen this? Any ideas about how to deal with long footnotes in
Frame other than go back to the author and tell him to rewrite?
Well, I think the author will insist... So I would try a quirk, because the
whole text seems to be a quirk
Hi,
We have a comment condition which should be hidden in the
final document and other conditions which should be shown.
However, here I ran into problems, when I have text which
has comment and another condition applied, and text with
comment should be hidden. I tried this:
o
My walnut is telling me that a footnote is a footnote and things that
do not fit within the majority of a page as allowed in FrameMaker must
be something else, like an end note or just as an insert (not in the
FM way) that is just shown indented and/or in smaller type in direct
continuation of the
Hi,
Sorry, 2 more issues:
o I noticed that boolean expressions set in one file of a book
are not overridden when I set Show All for the whole book.
In this file still Show as per Expression is set.
o When I want to set boolean expressions for the whole book, not
all available conditions
Hi all,
Have any of you created .chm files for applications built using the .NET
studio?
The problem that interests me is the lack of a ui.h file for the context
mapping. .NET no longer uses this MFC convention. For the same reason,
Microsoft help studio cannot trap HTML help messages for these
On Oct 11, 2007, at 10:23 AM, Technical Writer wrote:
The trend has been in that direction since the dotcom bust, when a
number of (formerly) highly paid developers found a comfortable job
writing help files more appealing than unemployment or stocking the
shelves at Wal-Mart.
If
A pithy and very well-written message, Ron. Bravo!
Yours truly,
John Hedtke
Author/Consultant/Contract Writer
www.hedtke.com -- website
541-685-5000 (office landline)
541-554-2189 (cell)
[EMAIL PROTECTED] (primary email)
[EMAIL PROTECTED] (secondary email)
Van Boening, Tammy wrote:
I have been trying in vain to unsubscribe from the framers
list and tech-whirl list for several days now as I am leaving
this gig and will soon have a new email address; however, no
luck. No matter what I do, whenever I log in, I either get
timed out or when I
Agreed. I'm surprised this isn't a more common practice.
On 10/18/07, Chris Borokowski [EMAIL PROTECTED] wrote:
What makes more sense in my mind is for technical writers to expand
their role to the life-cycle of the product, from conception to
maintenance, by investing in understanding
What makes more sense in my mind is for technical writers to expand
their role to the life-cycle of the product, from conception to
maintenance, by investing in understanding interaction design/interface
design, quality control and user advocacy positions.
--- Ron Miller [EMAIL PROTECTED] wrote:
The movement toward Extreme Programming and Agile Development is a
case in point; documentation is considered a waste of valuable
developer time, and only needs to be slapped together in minimalist
form at the last minute. That is at odds with the TW perspective
of involvement during the
Bodvar Bjorgvinsson wrote:
My walnut is telling me that a footnote is a footnote and things that
do not fit within the majority of a page as allowed in FrameMaker must
be something else, like an end note or just as an insert (not in the
FM way) that is just shown indented and/or in smaller type
XP and Agile are excuses for bad behavior. We're manly men who code
brilliantly; we don't need documentation because our code is perfect
and if the users don't understand our godlike design, that's their
problem. XP and Agile will get code out the door and it may even be
good code
Technical writing, specifically end-user documentation of software
applications, is perceived by the majority of producers as less than useful
and, in general, a waste of money, time, and effort. Similarly, the TW's view
that they are adding value to a product may be just as impoverished.
There's other problems with Linux, and this article says it all:
http://www.pcmag.com/article2/0,2704,2197786,00.asp
I am agnostic about Linux. It does some things well. It's not ready for
the desktop because installation of the OS, and then software, is often
a massive PITA. With Windows, it
I would maintain, that it's impossible to facilitate knowledge
transfer without good style, form and consistency, but I would agree
that without clear writing, it hardly matters how good it looks.
You will never achieve the perfect interface. It's not going to
happen. Your grandmother is
I've seen XP happening in a number of companies that are now
dead. Think of it as evolution in action.
I've also seen companies that do not use Agile go out of business, so
maybe Agile is not what drove them out of business.
XP and Agile are excuses for bad behavior. We're manly
men who
Lots to digest here:
Technical Writer [EMAIL PROTECTED] wrote:
Technical writing, specifically end-user documentation of software
applications, is perceived by the majority of producers as less than useful
and, in general, a waste of money, time, and effort.
This is observable.
I agree with Gordon. Infact, there is requirement for more and more
documentation. I see that every new user interface comes with its own set of
tutorials.
Smile makes you more close; try it
Thanks and Regards,
N. Jain
Writer
91-9810676241
http://www.neerajjain8.com |
Human engineering, customer research prior to design concept, GUI concept and
progression testing, usability testing, quality control, user advocacy, basic
GUI verification and operability (short of rigorous software design testing)...
the list goes on. There are a lot of areas where TWs could
HA! Quite true! TW's usually also bring an approach that is closer to green
field than the developers, engineers, etc., can provide. Because they
understand how THEY INTEND for it to function and be used, they can be a bit
myopic about how what they have CREATED actually plays out.
Rene
Bill
Tina wrote:
"If I take out
the now disappeared long footnote (by deleting the footnote reference in the
text), all the other footnotes go back where they belong"
Are you sure about this? If there are lots of long notes in the doc
it's very likely that FM has pushed some of them in their
On 17 Oct 2007 at 12:59, Tina Ricks wrote:
> Has anyone seen this? Any ideas about how to deal with long footnotes in
> Frame other than go back to the author and tell him to rewrite?
Well, I think the author will insist... So I would try a quirk, because the
whole text seems to be a quirk
My walnut is telling me that a footnote is a footnote and things that
do not fit within the majority of a page as allowed in FrameMaker must
be something else, like an end note or just as an "insert" (not in the
FM way) that is just shown indented and/or in smaller type in direct
continuation of
Hi,
Sorry, 2 more issues:
o I noticed that boolean expressions set in one file of a book
are not overridden when I set "Show All" for the whole book.
In this file still "Show as per Expression" is set.
o When I want to set boolean expressions for the whole book, not
all available
Hi all,
Have any of you created .chm files for applications built using the .NET
studio?
The problem that interests me is the lack of a ui.h file for the context
mapping. .NET no longer uses this MFC convention. For the same reason,
Microsoft help studio cannot trap HTML help messages for these
On Oct 11, 2007, at 10:23 AM, Technical Writer wrote:
>
> The trend has been in that direction since the dotcom bust, when a
> number of (formerly) highly paid developers found a comfortable job
> writing help files more appealing than unemployment or stocking the
> shelves at Wal-Mart.
What makes more sense in my mind is for technical writers to expand
their role to the life-cycle of the product, from conception to
maintenance, by investing in understanding interaction design/interface
design, quality control and user advocacy positions.
--- Ron Miller wrote:
>
>
>
>
> On
A pithy and very well-written message, Ron. Bravo!
Yours truly,
John Hedtke
Author/Consultant/Contract Writer
www.hedtke.com <-- website
541-685-5000 (office landline)
541-554-2189 (cell)
john at hedtke.com (primary email)
johnhedtke at aol.com (secondary email)
Van Boening, Tammy wrote:
> I have been trying in vain to unsubscribe from the framers
> list and tech-whirl list for several days now as I am leaving
> this gig and will soon have a new email address; however, no
> luck. No matter what I do, whenever I log in, I either get
> timed out or
Agreed. I'm surprised this isn't a more common practice.
On 10/18/07, Chris Borokowski wrote:
> What makes more sense in my mind is for technical writers to expand
> their role to the life-cycle of the product, from conception to
> maintenance, by investing in understanding interaction
>
> The movement toward Extreme Programming and Agile Development is a
> case in point; documentation is considered a waste of valuable
> developer time, and only needs to be slapped together in minimalist
> form at the last minute. That is at odds with the "TW perspective"
> of involvement
Bodvar Bjorgvinsson wrote:
> My walnut is telling me that a footnote is a footnote and things that
> do not fit within the majority of a page as allowed in FrameMaker must
> be something else, like an end note or just as an "insert" (not in the
> FM way) that is just shown indented and/or in
XP and Agile are excuses for bad behavior. "We're manly men who code
brilliantly; we don't need documentation because our code is perfect
and if the users don't understand our godlike design, that's their
problem." XP and Agile will get code out the door and it may even be
good code
Technical writing, specifically end-user documentation of software
applications, is perceived by the majority of producers as "less than useful"
and, in general, a waste of money, time, and effort. Similarly, the TW's view
that they are "adding value" to a product may be just as impoverished.
There's other problems with Linux, and this article says it all:
http://www.pcmag.com/article2/0,2704,2197786,00.asp
I am agnostic about Linux. It does some things well. It's not ready for
the desktop because installation of the OS, and then software, is often
a massive PITA. With Windows, it
I would maintain, that it's impossible to facilitate knowledge
transfer without good style, form and consistency, but I would agree
that without clear writing, it hardly matters how good it looks.
You will never achieve the perfect interface. It's not going to
happen. Your grandmother is
> I've seen XP happening in a number of companies that are now
> dead. Think of it as evolution in action.
I've also seen companies that do not use Agile go out of business, so
maybe Agile is not what drove them out of business.
> XP and Agile are excuses for bad behavior. "We're manly
> men
Lots to digest here:
Technical Writer wrote:
Technical writing, specifically end-user documentation of software
applications, is perceived by the majority of producers as "less than useful"
and, in general, a waste of money, time, and effort.
This is observable.
Similarly, the TW's
I agree with Gordon. Infact, there is requirement for more and more
documentation. I see that every new user interface comes with its own set of
tutorials.
Smile makes you more close; try it
Thanks and Regards,
N. Jain
Writer
91-9810676241
http://www.neerajjain8.com |
Human engineering, customer research prior to design concept, GUI concept and
progression testing, usability testing, quality control, user advocacy, basic
GUI verification and operability (short of rigorous software design testing)...
the list goes on. There are a lot of areas where TWs could
I'd say that those are additional skills. What I took Chris' remark to
mean is that writers should be there through the entire process,
involved with design, so not only do they influence the product design
along with the other stakeholders, but also have a means of thoroughly
planning the entire
HA! Quite true! TW's usually also bring an approach that is closer to "green
field" than the developers, engineers, etc., can provide. Because they
understand how THEY INTEND for it to function and be used, they can be a bit
myopic about how what they have CREATED actually plays out.
Rene
Can't you just use Acrobat Professional 8? It translates the PDF to Word as
text insets, which you then change to pure text. It works for me.
Joel
On 10/17/07 11:59 AM, "O'Laoghaire Micheal"
wrote:
> Try using Nuance's PDFConverter4 ( http://www.nuance.com/pdfconverter/) for
> converting PDF
Hi, everyone-
I am using unstructured FM 7.2 (Windows) to maintain the documentation set for
a suite of software products. We have several different customers who each
receive a different subset of modules, depending on their business needs. Each
module can be customized for each client, so
46 matches
Mail list logo
