Hello Wim,
Instead of translating MIF7, I strongly recommend to
translate MIF9 files. Until Trados does not support MIF9,
you can workaround this limitation by changing MIFFile 9.00
to MIFFile 8.00 in the first line of the MIF files
before translation. As far as I can see, the new FM9 features
Hello Klaus,
Unfortunately retranslating with FM9 files is not an option now. But apart
from that, I had the same problem with translated FM9 files for another
project. Somehow Trados doesn't create Unicode MIF output. May be that's the
drawback of using MIFFile 8.00, Trados did not update the
Classification: NOT PROTECTIVELY MARKED
Does the same in XP/FM9p250 unstructured, although I found that ending
one of the FM processes in Task Manager zapped the second instance as
well, and CPU usage died down immediately.
However, one has to ask why one would want to import formats from
Hello Wim,
There's no difference between FM8 and FM9 regarding
the encoding - both versions are using Unicode for the
internal character encoding.
Whether Trados uses Unicode or FrameRoman encoding
for the MIF output depends on the source MIF version
(7 - FrameRoman, 8 - Unicode).
Would
Hello Klaus,
So you say that when I save from FM9 as FM9 MIF (or FM8 MIF) the translated
files should be Unicode, including the marker texts. No extra settings
needed for Trados? In my last project this was not the case, may be the
files were saved as FM7 MIF then (they were saved using an old
Hi,
Additional to my other query, here' another one, for those who work with WWP
2003.
I'm not a frequent WWP user, so not very familiar with that tool.
I'm compiling a help project based on Russian FrameMaker files (FM 7.2, WWWP
2003 version 8.6.6587). We're creating a .chm file.
All text goes
One reason to import into the current document is to reset overrides. For
example, if writers are known to open the para designer
and create an override, then click Apply To Selection, this is a way to reset
the formats. Another reason might be that content from
an older template (but with
Hi Tim,
there is a very nice feature in SQUIDDS TOOLBOX for FrameMaker 7, 8 and
9: Server 'Analysis'
Feature 'Server Analysis' makes a list over all referenced files of a
directory of a server.
Then you know what and how many files are repeatedly referenced.
See more information in the manual
Hello Wim,
So you say that when I save from FM9 as FM9 MIF (or
FM8 MIF) the translated files should be Unicode, including
the marker texts. No extra settings needed for Trados?
Exactly, this is my experience.
may be the files were saved as FM7 MIF then (they were
saved using an old
Using (DITA) FrameMaker 8's Automatic Save - Every X minutes feature, one
user on my team reports that her .auto files are not deleted when she manually
saves the file. Frame docs say:
To create an autosave file at regular intervals, select Automatic Save and
enter an interval (in minutes)
Hello to the fonts of All Wisdom Framemaker,
;)
Seriously, Id like some advice. My company has three different software
packages, and the three share two common sub-packages. Up to this point, the
common bits were part of the Details chapter of each individual manual. Id
like to break
Hi Steve,
For shared text, I had planned to place the shared-text *.fm in each
PackageN.book, referring to the *.fm in each SUBPACKAGE folder. Would you
mind explaining the benefits of using text insets instead?
Thank you,
Lea
-Original Message-
From: Steve Johnson
Hi Steve,
My apologies for being unclear. If I understand you correctly, my strategy
and yours accomplish the same thing. Please let me try again.
Again, the folder structure is
*MANUALS*
PACKAGEFOLDER1 unique *.fm files and images for Package1
PACKAGEFOLDER2 same for Package2
Post it here:
http://tech.groups.yahoo.com/group/wwp-users/join
On Thu, May 20, 2010 at 6:11 AM, Wim Hooghwinkel - idtp w...@idtp.eu wrote:
Hi,
Additional to my other query, here' another one, for those who work with WWP
2003.
I'm not a frequent WWP user, so not very familiar with that
The folder structure should be taken into consideration only WRT
source control. In other words, when you branch from version 2.0 to
version 3.0, you want all like files to move together so things like
cross-references, figure references, and text insets move together in
the same relative
I'm not sure if the lck files are the source of your crash. It's possible that
there is a conflict in the conditions themselves.
I agree with Syed that you should start by opening each book file and adjusting
the conditional text settings individually. If there are any breaks in the
structure
That looks like it would work. I would advise trying it on a small scale first.
However, there would be no difference in having one directory with all
package files in it as long as they are used as text insets. They're
exactly the same as images in that respect. It depends on what makes
sense to
Am 20.05.2010 um 13:11 schrieb Wim Hooghwinkel - idtp:
Hi,
Additional to my other query, here' another one, for those who work with WWP
2003.
I'm not a frequent WWP user, so not very familiar with that tool.
I'm compiling a help project based on Russian FrameMaker files (FM 7.2, WWWP
On Thu, 20 May 2010 13:11:28 +0200, Wim Hooghwinkel - idtp w...@idtp.eu
wrote:
Additional to my other query, here' another one, for those who work with WWP
2003.
I'm not a frequent WWP user, so not very familiar with that tool.
I'm compiling a help project based on Russian FrameMaker files (FM
Hello Wim,
Instead of translating MIF7, I strongly recommend to
translate MIF9 files. Until Trados does not support MIF9,
you can workaround this limitation by changing
to in the first line of the MIF files
before translation. As far as I can see, the new FM9 features
won't be altered by
Hello Klaus,
Unfortunately retranslating with FM9 files is not an option now. But apart
from that, I had the same problem with translated FM9 files for another
project. Somehow Trados doesn't create Unicode MIF output. May be that's the
drawback of using , Trados did not update the tools to the
Classification: NOT PROTECTIVELY MARKED
Does the same in XP/FM9p250 unstructured, although I found that ending
one of the FM processes in Task Manager zapped the second instance as
well, and CPU usage died down immediately.
However, one has to ask why one would want to import formats from
Hello Wim,
There's no difference between FM8 and FM9 regarding
the encoding - both versions are using Unicode for the
internal character encoding.
Whether Trados uses Unicode or FrameRoman encoding
for the MIF output depends on the source MIF version
(7 -> FrameRoman, 8 -> Unicode).
> Would
Hello Klaus,
So you say that when I save from FM9 as FM9 MIF (or FM8 MIF) the translated
files should be Unicode, including the marker texts. No extra settings
needed for Trados? In my last project this was not the case, may be the
files were saved as FM7 MIF then (they were saved using an old
Hi,
Additional to my other query, here' another one, for those who work with WWP
2003.
I'm not a frequent WWP user, so not very familiar with that tool.
I'm compiling a help project based on Russian FrameMaker files (FM 7.2, WWWP
2003 version 8.6.6587). We're creating a .chm file.
All text goes
One reason to import into the current document is to reset overrides. For
example, if writers are known to open the para designer
and create an override, then click Apply To Selection, this is a way to reset
the formats. Another reason might be that content from
an older template (but with
Hi Tim,
there is a very nice feature in SQUIDDS TOOLBOX for FrameMaker 7, 8 and
9: Server 'Analysis'
Feature 'Server Analysis' makes a list over all referenced files of a
directory of a server.
Then you know what and how many files are repeatedly referenced.
See more information in the manual
Hello Wim,
> So you say that when I save from FM9 as FM9 MIF (or
> FM8 MIF) the translated files should be Unicode, including
> the marker texts. No extra settings needed for Trados?
Exactly, this is my experience.
> may be the files were saved as FM7 MIF then (they were
> saved using an
Using (DITA) FrameMaker 8's "Automatic Save - Every X minutes" feature, one
user on my team reports that her .auto files are not deleted when she manually
saves the file. Frame docs say:
"To create an autosave file at regular intervals, select Automatic Save and
enter an interval (in
Hello to the fonts of All Wisdom Framemaker,
;)
Seriously, I?d like some advice. My company has three different software
packages, and the three share two common sub-packages. Up to this point, the
common bits were part of the Details chapter of each individual manual. I?d
like to break out
Hi Steve,
For shared text, I had planned to place the shared-text *.fm in each
PackageN.book, referring to the *.fm in each SUBPACKAGE folder. Would you
mind explaining the benefits of using text insets instead?
Thank you,
Lea
> -Original Message-
> From: Steve Johnson
Hi Steve,
My apologies for being unclear. If I understand you correctly, my strategy
and yours accomplish the same thing. Please let me try again.
Again, the folder structure is
*MANUALS*
PACKAGEFOLDER1 ? unique *.fm files and images for Package1
PACKAGEFOLDER2 ? same for Package2
Post it here:
http://tech.groups.yahoo.com/group/wwp-users/join
On Thu, May 20, 2010 at 6:11 AM, Wim Hooghwinkel - idtp wrote:
> Hi,
>
> Additional to my other query, here' another one, for those who work with WWP
> 2003.
>
> I'm not a frequent WWP user, so not very familiar with that tool.
>
The folder structure should be taken into consideration only WRT
source control. In other words, when you branch from version 2.0 to
version 3.0, you want all like files to move together so things like
cross-references, figure references, and text insets move together in
the same relative
I'm not sure if the lck files are the source of your crash. It's possible that
there is a conflict in the conditions themselves.
I agree with Syed that you should start by opening each book file and adjusting
the conditional text settings individually. If there are any breaks in the
structure
That looks like it would work. I would advise trying it on a small scale first.
However, there would be no difference in having one directory with all
package files in it as long as they are used as text insets. They're
exactly the same as images in that respect. It depends on what makes
sense to
Am 20.05.2010 um 13:11 schrieb Wim Hooghwinkel - idtp:
> Hi,
>
> Additional to my other query, here' another one, for those who work with WWP
> 2003.
>
> I'm not a frequent WWP user, so not very familiar with that tool.
> I'm compiling a help project based on Russian FrameMaker files (FM 7.2,
On Thu, 20 May 2010 13:11:28 +0200, "Wim Hooghwinkel - idtp"
wrote:
>Additional to my other query, here' another one, for those who work with WWP
>2003.
>
>I'm not a frequent WWP user, so not very familiar with that tool.
>I'm compiling a help project based on Russian FrameMaker files (FM 7.2,
Hi!
Does anyone know how I add fonts to FrameMaker 7.2? There's not much in the
help on it.
Any help on this topic is greatly appreciated. I know I'm missing something,
probably something elemental.
Cheers,
Deb
39 matches
Mail list logo
