> time and overwrite the "Proprietary Footer" variable as needed.
>
> Alison
>
>
> -Original Message-
> From: Framers [mailto:framers-bounces+acraig=
> bkultrasound@lists.frameusers.com] On Behalf Of Lin Sims
> Sent: Tuesday, May 10, 2016 10:08 PM
>
ot; variable as needed.
Alison
-Original Message-
From: Framers
[mailto:framers-bounces+acraig=bkultrasound@lists.frameusers.com] On Behalf
Of Lin Sims
Sent: Tuesday, May 10, 2016 10:08 PM
To: Robert Lauriston
Cc: Frame Users
Subject: Re: [Framers] Conditional Expression bui
The company has standardized on Frame, so Flare is not an option.
We really need to be in DITA. We were doing that before we were acquired
and the centralized technical communications department got siloed to
individual business units, and my new boss decided that he wanted me to use
unstructured
I found FrameMaker's conditions became hard to use and maintain with
even three overlapping deliverables: in one case, for students,
teachers, and system administrators, in another customers, managers,
and sysadmins.
Flare's reuse features are much more manageable and transparent for
more complex
I wanted to thank you again for the help with this. I was looking at a
nightmare, and it's now just a bad memory. :-)
While it already seems to be working fine, I wanted to double-check
something. The expressions are set up as you suggested, to NOT the
conditions I don't want visible in a particul
I'd probably name that TrustedCustomerOnly (or NDACustomerOnly?)
instead of External.
On Tue, May 10, 2016 at 10:07 PM, Lin Sims wrote:
> Most of the text is unconditional. And sadly, I actually need the External
> tag.
>
> Not because of any of the actual TEXT, but because of the proprietary
> l
x27;s a way to save
conditional expressions as 'menu items' now, then obviously do that).
Original Message ----
Subject: Re: [Framers] Conditional Expression build crashing FrameMaker
with Internal Errors
From: Lin Sims <[1]ljsims...@gmail.com>
Date: Tue, May
Most of the text is unconditional. And sadly, I actually need the External
tag.
Not because of any of the actual TEXT, but because of the proprietary
language in the footers. We have one sentence for internal, do not show to
customers on pain of feeding the dragons, and another of you're our
custo
Exactly. In your situation, I'd maybe have AOnly, ACustOnly,
AInternalOnly, BOnly, BCustOnly, BInternalOnly, and Internal. Then the
conditional expressions would be:
for A regular version: not (ACustOnly or AInternalOnly or BOnly or
BCustOnly or BInternalOnly or Internal)
for A Cust version: not (
Interesting. If I understand you correctly, you're suggesting that the text
that needs to appear in a certain version be tagged with a condition for
that version, and then in all the other versions (where it doesn't appear),
you NOT it.
I tell you what, after today I am definitely going to remembe
If you have much content that is used in all versions, defining
conditional text to be excluded with NOT is simpler and less work.
On Tue, May 10, 2016 at 3:02 PM, Lin Sims wrote:
> One of the "rules" I learned somewhere was to either have all your
> conditions say what the text is IN, or have th
Internal is (sometimes) being combined with tags that specify the IP. For
example, in the Only We Get to Look At It version of the book for IP A,
there will be information that is specific to IP A that is not supposed to
be visible to external customers, and we don't want to provide any IP B
inform
quot;IP A +
Internal" condition.
-FR
From: Framers on
behalf of Robert Lauriston
Sent: Tuesday, May 10, 2016 5:02 PM
To: Lin Sims; framers@lists.frameusers.com
Subject: Re: [Framers] Conditional Expression build crashing FrameMaker with
Interna
Generally speaking, when defining a set of conditions, you want to (1)
minimize the amount of text that has to be tagged, (2) minimize
multiple tagging, (3) maximize unconditional text, and (4) define the
minimum number of conditions to achieve that.
Sometimes that means defining conditions for te
Yours is a more elegant solution. As I said before, this is my first
go-around with Conditional expressions. It didn't help at all that the
standard I was told to apply here was to tag text with the condition for
the book I want to produce. That produced some odd results I can no longer
recall (mos
This is my first time working with conditional expressions, as opposed to
simple on/off conditions, and it's entirely possible I'm overthinking it.
I've spent some time with grids and a coworker, and I think I've
(hopefully) worked it out. Now to write it up so I don't forget.
The basic issue is t
("A" or "External" or ("A" and "External")) could be simplified to
("A" or "External")
not (("A" and "Internal") or "B" or ("B" and "External") or "TBP or
"WriterNote")
could be simplified to
not ("A" and "Internal") or "B" or "TBP or "WriterNote")
But it's not clear why you can't just use
n
> Message: 2
> Date: Tue, 10 May 2016 09:43:10 -0400
> From: Lin Sims <>
> To: Frame Users <>
> Subject: [Framers] Conditional Expression build crashing FrameMaker
> with Internal Errors
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
>
The standard approach is to have tags InternalOnly and ExternalOnly.
If you want something to appear in both, you use neither tag.
On Tue, May 10, 2016 at 8:10 AM, Lin Sims wrote:
> Whoops. I take back that last. If I have something tagged as
>
> A + Internal + External
>
> and I want it to show
Whoops. I take back that last. If I have something tagged as
A + Internal + External
and I want it to show in the A+External book, the expression
"A" and not ("B" or "Internal")
hides it.
Running more experiments.
On Tue, May 10, 2016 at 10:54 AM, Lin Sims wrote:
> I only just found i
I only just found it, so no. I have a bad habit of finding things like
this, though. When I was documenting software, the coders alternately loved
me and hated me. :)
And it looks as if I may be overthinking this in a BIG way. Apparently, I
was trying to be over-explicit.
For example, the express
At 09:43 -0400 10/5/16, Lin Sims wrote:
>...but as soon as I try to enclose the entire "and not" clause in parens,
>Frame crashes. The same thing happens if I enclose the second clause first
>(it saves fine) and then try to enclose the first clause.
>
>I tried editing in the MIF, but the entire ex
FM12, latest patch
Win 7 Pro, 64-bit (not sure if it has the latest patches, that's IT's issue)
I'm trying to build some moderately complex conditional expressions. At the
moment I'm trying to account for 6 separate conditions, with a probable 7th
in the offing, but every time I try to build an ex
23 matches
Mail list logo
