Great overview, John! Just one thing I'd like to comment on:
> every place that I say you need "a OneSign profile" they need to say
"an Applesandoranges" profile - the a/an is not part of your
variable and must be caught with a search-replace.
Seems to me that if you're doing a
A few quick comments related to the two most specific points you make.
* For company name (and product names, if it becomes necessary), we'll create a
user variable.
Try to avoid the entire "a" versus "an" issue by planning the writing. That
means if you write for the Apple market and for the
In Framers Digest, Vol 3, Issue 14 Deb Hardy wrote, in part, "I'm pretty
sure that images and anchored frames can't have user variables attached to
them, . . ."
The way I get around this limitation is to place images/anchored frames in
separate paragraphs (named figure, for example), select
I think your variable/standard_file_name strategy will work fine so
long as all the versions for all the vendors are the same. As soon as
somebody adds or drops a feature, you'll probably have to go to
conditional text to control the differeing content in the chapter.
Art
On 1/17/06, Deb Hardy
At 11:22 am -0800 17/1/06, Deb Hardy wrote:
Do both of these approaches seem reasonable and optimal? I'm particularly
concerned about the logo-replacement issue.
Deb - what you suggest sounds sensible: others might be able to suggest extra
tricks. One thing you'll need to watch on the
To: framers@lists.frameusers.com
Subject: Rebranding/OEM'ing Frame files
I originally posted this question on Friday, but it didn't go through.
(Switching to plain text now!) Thanks in advance for any feedback.
Deb Hardy [EMAIL PROTECTED] wrote:
For those of you who distribute your source files to OEM
PROTECTED] On
Behalf Of Deb Hardy
Sent: Tuesday, January 17, 2006 2:23 PM
To: framers@lists.frameusers.com
Subject: Rebranding/OEM'ing Frame files
I originally posted this question on Friday, but it
didn't go through. (Switching to plain text now!)
Thanks in advance for any feedback.
Deb Hardy [EMAIL
I originally posted this question on Friday, but it
didn't go through. (Switching to plain text now!)
Thanks in advance for any feedback.
Deb Hardy wrote:
For those of you who distribute your source files to
OEM partners, would you be willing to share the basics
of how you prepare your Frame
I think your variable/standard_file_name strategy will work fine so
long as all the versions for all the vendors are the same. As soon as
somebody adds or drops a feature, you'll probably have to go to
conditional text to control the differeing content in the chapter.
Art
On 1/17/06, Deb Hardy
At 11:22 am -0800 17/1/06, Deb Hardy wrote:
>Do both of these approaches seem reasonable and optimal? I'm particularly
>concerned about the logo-replacement issue.
Deb - what you suggest sounds sensible: others might be able to suggest extra
tricks. One thing you'll need to watch on the
rs.com
[mailto:framers-bounces+grant.hogarth=reuters.com at lists.frameusers.com]
On Behalf Of Deb Hardy
Sent: Tuesday, January 17, 2006 12:23 PM
To: framers at lists.frameusers.com
Subject: Rebranding/OEM'ing Frame files
I originally posted this question on Friday, but it didn't go through.
(Swi
rom: framers-bounces+jsgammato=imprivata@lists.frameusers.com
[mailto:framers-bounces+jsgammato=imprivata.com at lists.frameusers.com] On
Behalf Of Deb Hardy
Sent: Tuesday, January 17, 2006 2:23 PM
To: framers at lists.frameusers.com
Subject: Rebranding/OEM'ing Frame files
I originally posted this que
12 matches
Mail list logo
