Sun, 6/28/09, Lynne A. Price wrote:
> From: Lynne A. Price
> Subject: RE: Logging FrameMaker book errors in a text file
> To: "Gordon Furbush" , framers@lists.frameusers.com,
> "Rick Quatro"
> Date: Sunday, June 28, 2009, 4:00 PM
> At 02:57 PM 6/22/2
At 08:16 AM 7/1/2009, Les Smalley wrote:
>I can't test it at this machine, but I'm 99% sure that shift-return is \n
> (as in a "new line") in the find dialog. Les
Les,
You are correct. Either \n or \r can be used.
--Lynne
Lynne A. Price
Text Structure Consulting, Inc.
Specializ
Chris,
Wow, I was being terse! Of course, a global find/change would work. I
was thinking (but certainly did not describe) a client or script that would
make a backup copy, do the global find/change you mention, generate the
XML, and delete the backup copy.
By the way, \r can be used to en
I can't test it at this machine, but I'm 99% sure that shift-return is \n (as
in a "new line") in the find dialog.
– Les
--- On Wed, 7/1/09, Chris Despopoulos wrote:I
don't think you need scripts or FDK clients. Can't you just find/change on the
book? Of course, I forget the find char seq
I don't think you need scripts or FDK clients. Can't you just find/change on
the book? Of course, I forget the find char sequence for a Shift-Return, but
I'm fairly sure it exists... (I always like to advocate the low-tech solution
if at all possible.)
cud
Lynne Price says...
Gordon,
S
On Tue, 30 Jun 2009 16:18:35 -0700, "Lynne A. Price"
wrote:
>At 01:44 PM 6/29/2009, Gordon Furbush wrote:
>
>>We're using unstructured FrameMaker and run the XML output
>>through a MarkLogic content processing pipeline to render
>>the HTML. If you have any work-arounds for unstructured
>>Fram
At 01:44 PM 6/29/2009, Gordon Furbush wrote:
>Hi Lynne, Looks like your work-arounds apply to structured
>FrameMaker. We're using unstructured FrameMaker and run the XML output
>through a MarkLogic content processing pipeline to render the HTML. If you
>have any work-arounds for unstructured F
Gordon,
You are correct that by default FM exports a forced return as a regular
return. There are other special characters that FM converts to more usual
characters. For example, it exports a discretionary hyphen as a regular hyphen.
There are a couple of read/write rules that may help in y
At 02:57 PM 6/22/2009, Gordon Furbush wrote:
>Due to a bug in FrameMaker 8 that improperly generates XML, our book build
>generates MIF files for all of the FM files.
Gordon,
What is the XML export bug? Could XSLT provide a workaround?
--Lynne
Lynne A. Price
Text Structure Consulti
, Rick Quatro wrote:
> From: Rick Quatro
> Subject: RE: Logging FrameMaker book errors in a text file
> To: "'Gordon Furbush'" , framers@lists.frameusers.com
> Date: Saturday, June 20, 2009, 7:06 AM
> FrameMaker Console window messages
> are stored in a file c
FrameMaker Console window messages are stored in a file called consfile.txt
in the FrameMaker folder. So, for any message written there, you can look at
this file after the build process completes.
For more complete reporting and scripting abilities, take a look at
FrameScript (http://www.framescr
11 matches
Mail list logo
