I don't know of such an option. You could run it through HTML Tidy or
some other utility.
On Tue, Jan 6, 2015 at 11:29 AM, Celine Deguire wrote:
> Hello
>
> From Framemaker 11 on Windows 7, for conversion to HTML then later to XHTML
> (for use with MS Helpviewer), the img src definitions are brok
I am curious ... does the MS Helpviewer render this content any
differently, with or without the line break after "perspective of an HTML parser, this break is insignificant and should
have no effect on the HTML tree.
-Alan
---
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technica
Celine Deguire wrote on 1/6/2015 11:29 AM:
Hello
From Framemaker 11 on Windows 7, for conversion to HTML then later to XHTML
(for use with MS Helpviewer), the img src definitions are broken onto two
lines where images are embedded in sentences. Does anyone know how to force
the img src definit
FrameMaker just ignores any MIF tags it doesn't recognize, so there
should be no problem opening MIF 12 in FM8. I've gone between many
different FM versions and never had a problem.
As Rick notes FM 12 > MIF 12 > FM 8 is a better choice than FM 12 >
MIF 7 > FM 8.
__
Hi Michael,
The reason you don't want to do this is because the save to MIF 7.0 will
change the text encoding to the old FrameRoman character set. Then when you
open the MIF with FrameMaker 12 (or any version 8 or higher), the text
encoding will get changed back to Unicode. There is an outside
Hello
>From Framemaker 11 on Windows 7, for conversion to HTML then later to XHTML
(for use with MS Helpviewer), the img src definitions are broken onto two
lines where images are embedded in sentences. Does anyone know how to force
the img src definition to stay on one line? The following example
Hi Lise,
In FrameMaker v12, there are two options for saving in MIF format:
MIF 12.0 (*.mif)
MIF 7.0 (*.mif)
I don't have FrameMaker v8 installed, but I would think you would want files
saved in MIF 7.0 format. I do go between FMv10 and FMv12 fairly often and that
is the format I use.
Hope th
Hi Lise,
In later versions of FrameMaker, there are two MIF versions you can choose:
MIF #.#, where #.# is the current FrameMaker version you are saving from and
MIF 7.0, which is the pre-unicode version of MIF. You don't want MIF 7.0,
you want the current version. So, if they are using FrameMa
My experience with Language Service Providers is that you simply tell them what
version of Frame they have to use on your files. This is part of your contract
and they should include it in their quote.
Also, I send .fm files and receive .fm in return. I've never exchanged MIF
files with the var
Thanks, Barbara!
And yes, I got to that link from a google search of "framemaker 12 save as
framemaker 8" so I just copied and pasted that address, but when I click on
the link from my e-mail below, I can't get to it either. Weird.
Here it is the long way, via google:
https://www.google.com/url?sa=
Framers,
A little googling did not clarify anything for me, so I thought I'd ask
here.
I'm on Frame 8; none of the added features in subsequent releases seemed
relevant enough to me to justify upgrading (and it works fine for me on
Windows 7).
The issue I have is that I need to send some manuals ou
11 matches
Mail list logo