Exporting to Framemaker

Is there a technique that minimizes the work when exporting
content for use in Framemaker? The export process to Word is so
error filled that it makes me crazy.

You could try checking your version of ntdll.dll (a Windows protected system file) for corruption using the "sfc /scannow" command. This replaces corrupted protected system files with the correct MS ones. Also, you could then check if there are any issues with the DirectX graphics (the drivers could be affecting the FM behaviourr) on your system using the DXDIAG utility.
However, as it seems to happen on two systems, the corruption doesn't seem that likely of a culprit. Are you using FM with the structure or unstructured interface, i.e. is your workflow creating the XML using the Save As XML from unstrucured files or are you exporting the XML from a structured application?

Similar Messages

Cannot export the framemaker graphic element

Hi you,
I need some help for exporting graphics on translation to XML. In general FM exports a changed graphic into a new *.cgm file. This works. Now I'd like to change the format to eps and wrote the read/write rules:
element "Grafik" { is fm graphic element;
writer anchored frame export to file "$(entity).eps" as "EPSI";}
When I save the FM document to XML, the message occurs: cannot export the FrameMaker graphic element () into the specified graphic format.
The XML will be created an also the entity for the graphic, but not the needed graphic file. What is wrong?
Thanks,
Stucki78

Hi Maike,
the EPS is referenced in FM. In unstructured documents sometimes we added a text frame to the anchored frame, because it was easier for translation and we need only one graphic instead a graphic for each language. Now we want change to structured working in FM to give only one XML to the translator. The text frame then will cause a new graphic, but we still want translate the text inside the graphic. That is why we need EPS or something like this.
Do you have a better idea for the problem? We discussed the problem and think about leaving the text frame away and using a graphic for each language.
Stucki78

How do I preserve cross reference text when exporting to XML?

I am exporting my Framemaker documents to XML. However, when I open the raw XML, the reference formatting is obviously gone. So instead of seeing, say, see Figure 6. I now see, see .
Is there some way to preserve this on export?
Help would be much appreceated!

Josh,
The normal behavior is to have an empty element with the ID/IDRef markup that allows the xref element to be resolved again afterwards, by whatever post-processing step you put the XML through. The text of a cross-reference is a FrameMaker formatting artifact (not unlike a paragraph format, etc.) and is intentionally discarded during export. If you reimport the XML with the empty element, FM will re-resolve the xref, and then will restore the text using whatever format it originally had (the format name is also stored as markup).
If you want to preserve the element tag of the xref, I don't think there is any way to preserve the text, unless you write an import/export API client. You could possibly use an XSLT stylesheet to repopulate the text in some cases, but this seems like a process fraught with many complications.
If you do not care about the element tag, the manual says that you can just unwrap it, then you'll get the xref text. Here is a (rough) snip from the Structure Developers Guide:
Translating FrameMaker cross-reference elements to text in markup
You may not want your FrameMaker cross-reference elements to remain elements in the
markup representation—you can choose to translate them to text instead. To do so, use
this rule:
fm element "fmtag" unwrap;
where fmtag is the FrameMaker element tag for a cross-reference element.
All of this does beg the following question, though... why do you want to do this, especially if the text is referencing figure numbers, page numbers, etc. that have no relevance in the markup? Normally, it is expected that preservation of the markup is the essential thing, allowing the text to be regenerated later by whatever process uses the XML (perhaps including FM). If you drop the element tag, the actual link will be permanently lost.
Russ

Fonts Not Embedding Consistently with PDF Export - Inconsistent Fix and Unknown Cause

I have had ongoing problems with PDF export from FrameMaker. Sometimes the correct fonts do not embed in the PDF and Times New Roman is substituted. The problem appears and disappears and is causing me a lot of lost time and frustration.
I am running FrameMaker 9.0 fully patched on Windows 7 Ultimate 64-bit. I have seen people complain about this issue and am familiar with the suggested fixes. However, the exact cause and solution eludes me because the problem continues to recur and I am only able to recover with guesswork and workarounds.
Initially I did the following:
ACROBAT PDF SETTINGS
- In the printer properties for Adobe PDF settings I turned off the option "Rely on system fonts only; do not use documents fonts."
ACROBAT DISTILLER SETTING
Under "Font" Settings I changed the following:
- Under "Settings/Font Locations" I added the font folder for Technical Communication Suite 2.0 and made sure all the fonts existed there and in the Windows default font directory.
- Under "Settings/Edit Adobe PDF Setting/Fonts" I changed the following options:
- Selected "Embed all fonts"
- Under "Embedding" chose "Always Embed" for the target fonts.
I tweaked these settings for hours and got no results. Then I rebooted and the problem had magically disappeared. I fixed the issue in the same way on another machine and the results were permanent and I was just happy to finally have it fixed, But this time it didn't last.
I should note that upon reboot, when I used the stock "PDF Job Options," the correct fonts still embedded, leading me to believe that the fix had nothing to do with the changes I made to Distiller settings.
After reboot I generated PDFs with the correct fonts embedded. Then I shut down FM, but left the system running. The next morning I opened FM again and the same problem occurred.
So I rebooted again -- and the problem disappeared again. I therefore thought maybe the issue fixes on reboot but recurs when you shut down FM and reopen. So I shut down FM again and reopened, but it is still working fine for the moment.
I verified that the Adobe PDF settings under "Printers & Devices" that I turned off (Rely on system fonts only; do not use documents fonts) remained correctly unchecked through all these changes.
I would really like to know why this happens so I can resolve it permanently and avoid more lost time.
Thanks in advance,
Douglas

The common theme I'm seeing here is that the setting edits you make in
Distiller through the FM "Save As PDF" option don't seem to take effect.
Do you know if that is true or could you elaborate on the notorious nature
of this method for me?
>
There are too many potential and transient problems to list. The only thing
I can say is that I've been an active member of the FrameUsers listserv
(http://lists.frameusers.com/mailman/listinfo/framers) since FM version 6.0,
circa 2001, and probably 95% of the PDF problems reported there have been
fixed simply by using print to Adobe PDF (or to Acrobat Distiller in older
PDF versions), instead of using Save as PDF. Common advice there has always
been to avoid Save as PDF and even some Adobe employees have recommended
against using it. It doesn't matter which FM version.
The once-busy FrameUsers listserve has been fading away, recently, as this
new Adobe forum software allows reading via e-mail, and attachment of
screenshots. Even if you look around on this forum now, you'll probably
find that there are two main fixes for issues with PDF. One is NOT using
Save as PDF, which seems to fix a whole bunch of issues. The other is the
use of a Windows hotfix to squash a Windows OS bug that causes dropped
characters in PDFs.
In the rare instances that someone has issues with printing to PDF, they are
almost always related to errors in settings. Or occasionally someone can't
embed fonts because they are trying to the embed the virtual fonts that come
with their printer driver instead of fonts that have actually been installed
on their computer. (The fonts are hard-wired on their printer, so the system
can use them but not embed them.)

Error in XSL transformation

I am having trouble importing a XML file that I have previously exported. when I import the XML I get "Expected end of tag 'para'. I tried to edit the XML to add the end tag but am having trouble locating it. Any suggestion?

An XML document exported from FrameMaker should not be missing an end-tag. Are you having trouble locating the erroneous "para" element or the XML file?
If the former, I suggest paring down your document to the shortest possible test case. If the latter, I gather from your subject line that your application uses XSLT. Is XSLT run when you export the document, when you import the result or both? In any case, you may need to compare pre- and post- versions of the XML document because the XSLT transform may have introduced the error.
--Lynne

Forced return, non-breaking hyphens & spaces, suppress hyphenation + XML

Forced return (linefeed), non-breaking hyphens and spaces, suppress hyphenation.
None of these are preserved when exporting from FrameMaker to XML, since they do not seem to be represented by a Unicode code point. My question to you is: How do you deal with those things in XML?
The last issues (non-breaking and suppress hyphen) have recently been brought up in:
http://forums.adobe.com/thread/450363
http://forums.adobe.com/thread/459503
Forced return is a common thing in many FrameMaker documents to improve readability of certain phrases.
For export of FM to XML, there have been proposals to use a special element with a prefix just to capture the special FrameMaker symbol. It works, and may be a valid useful path in certain cases, but I think that it is a questionable way of dealing with it for several reasons:
It is only relevant for roundtrip, since these special elements will hardly be interpreted by other XML tools, which of course limits the value of XML export.
It is unwieldy, to say the least, to require the user to insert special elements for saying simple things that otherwise are just natural key strokes in the regular text flow, and which are not perceived as structural elements of information. Most users would think of these symbols/charactes as control characters, and there is no validation warning that says you may not use these characters/symbols.
An element is used for formatting purposes only, whereas all other elements are used for content or structure.
There is no automatic way of transforming an existing text that has these "symbols" into some special element when a document is structured with a conversion table.
There is no automatic way of transforming a structured FM document to XML such that these special "symbols" get translated to some suitable XML construct.
If the last point could be solved, i.e if all those control characters or markers could automatically be translated to a suitable XML representation, then I would consider the whole issue as solved, otherwise not.
Even without FrameMaker, how do people deal with these things in "pure xml". For instance, when XML is used for publishing (which I know Arnis Gubins is doing), there will guaranteed be a need to control both hyphenation and line breaks. So how do you (they) do that?
How do other vendors cope with these issues, e.g XPP?

Lynne,
As anyone can see, entity declarations have not really been in the domain of my expertise (understatement), but I might just learn bits and pieces...
Thanks! I have now done some more reading in various pdfs, such as scructapps etc, but also the w3c xml spec, all of which I have "read" before, but reading is not always the same as understanding...
I now have used the "entity approach" to make both discretionary hyphen and suppress hyphen work, so that it is represented in the XML export and round-trips just fine.
Forced return still puzzles me somewhat though: I have a working solution for that using the same entity approach, but it will not work for text ranges (although it is a bit odd to have forced returns in text range elements). Moreover, I am not certain that it really is the best way. In reading other posts on this issue, I have seen that some people want forced returns to really be linefeeds in the xml output, with no other linefeeds, and conversely, when importing xml that are "formatted" in lines, such as code, they want to preserve that.
One way to achieve that is to use:
     reader line break is forced return;
     writer line break is 1000 characters; (or more characters)
Then it is completely symmetric (i.e works also if some other app has generated the xml with intentional line breaks. And this method is global for all elements, and it works for me.
Another way to achieve this is to use the following, but it is only valid inside an element:
     preserve line breaks;
     writer line break is 1000 characters;
Then it is also completely symmetric (in the above sense), and it works for me.
The latter method has the drawback that it only works for text in the element; it is not inherited to its children.
But if we look at only one element, what is the difference between the two methods?
As far as I have been able to see, the results are identical! Why two methods? The first one seems more powerful and general(?)
Scrutinizing the documentation though, it says that 'preserve line breaks' will add an attribute 'xml:space', but I can't see that in my output?
Also, concerning the documentation for line break, it says that FM would ignore line breaks when exporting, but it does NOT do that (fortunately). Forced returns always result in linefeeds, no matter what.
I would be thankful if these issues could be explained, or elaborated.
Also, would you recommend against any of these methods?
With my preferred method of using the global 'reader line break is forced return' instead of a local (or many local) 'preserve line breaks', there is of course the danger that when importing xml, it is absolutely necessary that the xml really only has line breaks where they are intended, and not generated every 80 characters or so!
Is there anything that says it is "ugly" or "bad style" to honor line breaks, and generate long lines?
Finally, why do we need to limit the number of characters written in one line these days? Why 80, why 1000, why not an unlimited number of characters!?
Will software these days really crash if given a very long line (assuming that it doesn't exceed total ram memory of course)?
Sorry about so many questions, but I can't find any answers to them in the docs I have read and searched.

RH7: PDF generation of help project bypassing Word

All,
I have a user who is trying out the trial of RoboHelp 7 and
wants to know when generating PDF output, is there a way to bypass
creating a Word document and go straight to the PDF. Is Word still
utilized this way for Printed Documentation no matter if a PDF is
made or not?
Any info would be much appreciated.
Thanks,
Greg

It would seem logical that Adobe will have export to
Framemaker on their plans for future releases but that doesn't help
right now.
If the content is in FrameMaker, or could be, then perhaps
the Technical Communication Suite holds an alternative solution.
That can output to the version of RH7 that comes with it. When
FrameMaker is later updated, I understand it is a simple click to
update the RH7 project.
The only other possibility, and it seems unlikely, is to
hammer the customer a bit more on their objections to Word. They
say "because in our experience, Word becomes unstable after a
certain size is reached (sometimes even <100 pages if there are
a lot of graphics and screenshots). Word pagination is one of the
first to go. I'm afraid that it would be difficult or impossible to
PDF long documents"
Word really should not be unstable at that level and it is
not my experience, even with many screenshots. Whenever I see
comments like that, I do wonder if some more investigation would
solve the problem. I always want to get my hands on the project at
that point and try to make it fall over. Sometimes the cause can be
found. Often it is just the template used.

XML read errors--failure to open dtd (DITA)

Hi all,
I've run out of ideas and places to look on this one, I hope someone can help.
The specs: WinXP Pro, Frame 8.0p277. Built-in DITA. Not using DITA Open Toolkit. No major issues except for previously discussed conref problems which, many thanks to Scott, seem to be under control.
The context: I'm a freelancer, on contract to a financial institution. I work part-time in my own office (up-to-date, preferred set-up) and part-time onsite. I can't go into detail, but the set-up is less than ideal. I have to do much back-and-forth portaging of project and template files, and they are often corrupted when I reopen them.
Specs onsite I'm not sure about, but it's definitely Frame 8 with the first patch. I'm pretty sure they haven't installed any others, so the 8.03 patch shouldn't be an issue. (I'll check and report back, if that info is needed.)
The error: Came out of the blue last week, my first day back in my office after three days onsite. Now, every time I open or create any xml file, using any template, I get an XML Read Report Log error that reports a failure to open the DTD, and a parse error in the document prolog. I don't know where it's coming from, and I don't know why it started happening. I modified structapps once, many months ago, but hadn't touched it since, and I've never touched the r/w rules files in either location.
(I realize I should test this scenario onsite, but I daren't risk importing trouble, if it started here.)
Specifically, the error reads: Could not open DTD file: C:\Documents and Settings\path-to-project-files-folder\ditabase.dtd Parse error at line 9, char 1: Error procssing external entity reference.
I don't understand why it's looking for the dtd file in the same folder as the project files when I've never stored it there, and I have the following in the structapps, and r/w rules files.
DTD: $STRUCTDIR\xml\dita\default-app\dtd\ditabase.dtd
Read/write rules: $STRUCTDIR\xml\dita\default-app\DITA-Topic-FM\topic.rules.txt
The R/W Rules statement reads: writer external dtd is public "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd";
I can go completely cross-eyed after a few hours trying to parse these docs myself. The answer may well be right in front of me, but for the life of me I can't see it. I hope someone else can.
Karen

Hello Karen,
Have you been able to resolve this issue? I'm encountering a similar issue while going through the FrameMaker 8 Help topics: Processing XML > Migration from Unstructured FrameMaker to XML > Getting started with structure.
I have followed along with all the examples all the way down to the "Testing XML round-tripping" topic. When I go to the step: Export the FrameMaker file to XML, and select my XML application, I get a parsing error similar to what you had mentioned above.
The Help topics have you first build an EDD for a simple document (proposal) - successful.
They then have you open a new document and import the EDD - successful.
They then have you add formatting to the EDD and then reimport into your document to test it. - successful
They then have you build the structured app by saving the EDD to DTD. You are then supposed to create a template by removing all the content from your original file that they had you open and save it as a template. Then you are supposed to edit the application definition file. Finally you copy the template and the DTD to the Adobe FrameMaker 8 folder. - successful
I've done this process twice and each time I get the same Save to XML Log error message when trying to export my document to XML.
The first things that are displayed are the path the source and destination folders.
Next is the XML parser error messages (Document Prolog).
There are basically 2 parsing errors, line 3 and 9.
line 3, "Could not open DTD file" C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\$STRUCTDIR\XML\Preface\Preface.dtd
Error in processing external entity reference"
line 9, "Could not open DTD file" C:/Documents%20and%20Settings/michael_randall/My%20Documents/FrameEDDTemplatePractice/$ST RUCTDIR/XML/Preface/Preface.dtd
Error in processing external entity reference"
Please let me know if have any new information.
Thanks,
Michael Randall

Any changes in MIF specification between FM8 and FM9?

MIF files exported from FrameMaker 9 are tagged with <MIFFile 9.00>, MIFs from FrameMaker 8 are tagged <MIFFile 8.00>
Chapter 10 of the The FrameMaker 9 MIF reference lists the MIF syntax changes in FrameMaker 8; and lists all the changes that were in earlier versions, but does not list any changes for FrameMaker (version?) 9.
Two questions.
1. Are there any changes in the MIF specification between FrameMaker 8 and FrameMaker 9?
2. If so does anyone know where we could get a list of these changes?
Thanks in advance for the help.

SMB202 wrote:
MIF files exported from FrameMaker 9 are tagged with <MIFFile 9.00>, MIFs from FrameMaker 8 are tagged <MIFFile 8.00>
Chapter 10 of the The FrameMaker 9 MIF reference lists the MIF syntax changes in FrameMaker 8; and lists all the changes that were in earlier versions, but does not list any changes for FrameMaker (version?) 9.
Two questions.
1. Are there any changes in the MIF specification between FrameMaker 8 and FrameMaker 9?
2. If so does anyone know where we could get a list of these changes?
Thanks in advance for the help.
Until a real doc set materializes, you can try saving a FrameMaker 9.x doc as MIF and opening it in FM 8, then see the console messages that begin with "skipping."
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Is there a way to export data from Framemaker 7.0 to InDesign CS3 for the MAC

I am asking this question for our Advertising department so I am not too close to the situation. Another company that is part of oujr platform designed their catalogs in Framermaker 7.0. We have Framemaker 6.0. The only reason we have it is to work with this other version of Framemaker 7.0. Our advertising people use InDesign CS3 for the Mac. Right now Advertising gives the person with Framermaker 7.0 changes to be made to their catalog. He exports the file as an IMF file and she pulls it into Framermaker 6.0.
We tried to upgrade from Framemaker 6.0 to 9.0, but that wasn't possible.
Ideally we would like to take a 600 page catalog created with Framemaker and convert it to InDesign.
We would also like to take the files created with Framemaker 7.0 and import them into InDesign.
Is there a way to do this?
Thanks in advance.
dh

You can convert FrameMaker MIF (interchange) files to InDesign with the dtptools.com MIF Filter plug-in for InDesign. The plug-in is free, because you have to pay for the pages you convert. The bigger bundle of pages you buy, the lower cost per page.
dtptools.com also has a really free plug-in for FrameMaker that converts .fm files to .mif, whole directories at a time.
The converted InDesign files usually look very close to the original FM files, but it's possible to create things in FM that fools the converter, so you'll need to look the conversions over carefully.
I reviewed MIF Filter in some detail in InDesign Magazine in a late 2007 issue.
You should be aware that InDesign CS3 is no longer sold, so you can't buy more copies for all your users to be working in the same release. While it's possible to exchange files between ID CS3 and CS4 there are some things that don't convert perfectly, so you'll still have to inspect closely. I believe the most-common issue is text reflow.
It's not clear if you intend never to go back to using FrameMaker for any of the catalog work, except perhaps for creating original text.
Without seeing an example of the catalog pages, it's impossible to recommend any useful strategies. You can post a screen shot to this forum by clicking the camera icon in the button bar above the reply entry area. Inserting with the camera puts the picture on the forum very quickly, vs. attaching the picture as a file (it takes hours or days.)
There may be other strategies for creating your catalog.
HTH
Regards,
Peter Gold
KnowHow ProServices

Framemaker 9 PDF exports with red boxes around text areas

I have a doc, made in FM 7, using version 9
When I make a PDF i get boxes around some of the text. It wasn't there during FM design.
example
(see red)
Please help

AxialInfo wrote:
you might consider saving the FM file as MIF and then looking at the MIF using the wonderful freebie MIFBrowser, from Graham Wideman, from here:
Wideman Adobe FrameMaker Topics
to find the problem area do a search for the string that is in the title
"Downblast Centrifugal
Exhaust Ventilator
Roof Mounted
Belt Drive"
although just pasting it here it looks like you might have soft carriage returns in it which will make it necessary to just search for the two-word segments.
After you find the phrase, use the left navigation area to walk "up" the MIF file, looking for the specific structure that those words are in (is it a text box, or rather a graphic frame inside a text box, correct?) Is this an anchored frame, or is it just floating? If it's anchored, where is it anchored?
In the MIF, see if you can identify any odd sounding properties of the text box or graphic frame. The MIF reference manual is a PDF found in the FM documentation folder.
Also, one other possibility is that there's something funky with the red swash that goes across the page that's somehow "contaminating" the text frame. What kind of graphic type is the red swash? Could you take a copy of the FM file and remove the swash and then make a PDF, to see if that solves the red outline.
edit: additional questions: are the swash and the text frame on the body page or on the master page? When Arnis suggested checking for graphics behind the text frame, did you also check the master page(s) as well as the body pages?
Sheila
I tried the program:
<TextFlow
<Notes
> # end of Notes
<Para
<Unique 1291794>
<Pgf
   <PgfTag `Body'>
   <PgfUseNextTag No>
   <PgfNextTag `'>
   <PgfAlignment Right>
   <PgfFIndent 0.0">
   <PgfLIndent 0.0">
   <PgfRIndent 0.0">
   <PgfFIndentRelative No>
   <PgfFIndentOffset 0.0">
   <PgfTopSeparator `'>
   <PgfTopSepAtIndent No>
   <PgfTopSepOffset 0.0">
   <PgfBotSeparator `'>
   <PgfBotSepAtIndent No>
   <PgfBotSepOffset 0.0">
   <PgfPlacement Anywhere>
   <PgfPlacementStyle Normal>
   <PgfRunInDefaultPunct `. '>
   <PgfSpBefore 0.0 pt>
   <PgfSpAfter 0.0 pt>
   <PgfWithPrev No>
   <PgfWithNext No>
   <PgfBlockSize 1>
   <PgfFont
    <FTag `'>
    <FPlatformName `W.Arial.R.700'>
    <FFamily `Arial'>
    <FVar `Regular'>
    <FWeight `Bold'>
    <FAngle `Regular'>
    <FEncoding `FrameRoman'>
    <FSize 14.0 pt>
    <FUnderlining FNoUnderlining>
    <FOverline No>
    <FStrike No>
    <FChangeBar No>
    <FOutline No>
    <FShadow No>
    <FPairKern Yes>
    <FTsume No>
    <FCase FAsTyped>
    <FPosition FNormal>
    <FDX 0.0%>
    <FDY 0.0%>
    <FDW 0.0%>
    <FStretch 100.0%>
    <FLanguage USEnglish>
    <FLocked No>
    <FSeparation 0>
    <FColor `Black'>
   > # end of PgfFont
   <PgfLineSpacing Fixed>
   <PgfLeading 3.0 pt>
   <PgfAutoNum No>
   <PgfNumTabs 0>
   <PgfHyphenate Yes>
   <HyphenMaxLines 2>
   <HyphenMinPrefix 3>
   <HyphenMinSuffix 3>
   <HyphenMinWord 5>
   <PgfLetterSpace No>
   <PgfMinWordSpace 90>
   <PgfOptWordSpace 100>
   <PgfMaxWordSpace 110>
   <PgfMinJRomanLetterSpace 0>
   <PgfOptJRomanLetterSpace 25>
   <PgfMaxJRomanLetterSpace 50>
   <PgfMinJLetterSpace 0>
   <PgfOptJLetterSpace 0>
   <PgfMaxJLetterSpace 10>
   <PgfYakumonoType Floating>
   <PgfAcrobatLevel 0>
   <PgfPDFStructureLevel 5>
   <PgfLanguage USEnglish>
   <PgfCellAlignment Top>
   <PgfCellMargins 0.0 pt 0.0 pt 0.0 pt 0.0 pt>
   <PgfCellLMarginFixed No>
   <PgfCellTMarginFixed No>
   <PgfCellRMarginFixed No>
   <PgfCellBMarginFixed No>
   <PgfLocked No>
> # end of Pgf
<ParaLine
   <TextRectID 119>
   <String `Downblast Centrifugal'>
> # end of ParaLine
> # end of Para
<Para
<Unique 1291795>
<PgfTag `Body'>
<Pgf
   <PgfAlignment Right>
   <PgfFont
    <FTag `'>
    <FPlatformName `W.Arial.R.700'>
    <FFamily `Arial'>
    <FVar `Regular'>
    <FWeight `Bold'>
    <FAngle `Regular'>
    <FEncoding `FrameRoman'>
    <FSize 14.0 pt>
    <FUnderlining FNoUnderlining>
    <FOverline No>
    <FStrike No>
    <FChangeBar No>
    <FOutline No>
    <FShadow No>
    <FPairKern Yes>
    <FTsume No>
    <FCase FAsTyped>
    <FPosition FNormal>
    <FDX 0.0%>
    <FDY 0.0%>
    <FDW 0.0%>
    <FStretch 100.0%>
    <FLanguage USEnglish>
    <FLocked No>
    <FSeparation 0>
    <FColor `Black'>
   > # end of PgfFont
   <PgfLeading 3.0 pt>
> # end of Pgf
<ParaLine
   <String `Exhaust Ventilator'>
> # end of ParaLine
> # end of Para
<Para
<Unique 1291796>
<PgfTag `Body'>
<Pgf
   <PgfAlignment Right>
   <PgfFont
    <FTag `'>
    <FPlatformName `W.Arial.R.700'>
    <FFamily `Arial'>
    <FVar `Regular'>
    <FWeight `Bold'>
    <FAngle `Regular'>
    <FEncoding `FrameRoman'>
    <FSize 14.0 pt>
    <FUnderlining FNoUnderlining>
    <FOverline No>
    <FStrike No>
    <FChangeBar No>
    <FOutline No>
    <FShadow No>
    <FPairKern Yes>
    <FTsume No>
    <FCase FAsTyped>
    <FPosition FNormal>
    <FDX 0.0%>
    <FDY 0.0%>
    <FDW 0.0%>
    <FStretch 100.0%>
    <FLanguage USEnglish>
    <FLocked No>
    <FSeparation 0>
    <FColor `Black'>
   > # end of PgfFont
   <PgfLeading 3.0 pt>
> # end of Pgf
<ParaLine
   <String `Roof Mounted'>
> # end of ParaLine
> # end of Para
<Para
<Unique 1291797>
<PgfTag `Body'>
<Pgf
   <PgfAlignment Right>
   <PgfFont
    <FTag `'>
    <FPlatformName `W.Arial.R.700'>
    <FFamily `Arial'>
    <FVar `Regular'>
    <FWeight `Bold'>
    <FAngle `Regular'>
    <FEncoding `FrameRoman'>
    <FSize 14.0 pt>
    <FUnderlining FNoUnderlining>
    <FOverline No>
    <FStrike No>
    <FChangeBar No>
    <FOutline No>
    <FShadow No>
    <FPairKern Yes>
    <FTsume No>
    <FCase FAsTyped>
    <FPosition FNormal>
    <FDX 0.0%>
    <FDY 0.0%>
    <FDW 0.0%>
    <FStretch 100.0%>
    <FLanguage USEnglish>
    <FLocked No>
    <FSeparation 0>
    <FColor `Black'>
   > # end of PgfFont
   <PgfLeading 3.0 pt>
> # end of Pgf
<ParaLine
   <String `Belt Drive'>
> # end of ParaLine
> # end of Para
> # end of TextFlow
I don't see the red in there
I made another pdf, after deleting the red bar (it's a eps.) and the reb boxes are still there
        I'm not using any master.
Thanks for the advice anyhow
-Matt

Framemaker 9.0p196 crashes while exporting to xml

Hello,
This occurs both with XP Pro SP3 and Win7 iSP 1 . On a XP Pro SP3 without domain connection the crash does not occur. According to the event log caused ntdll.dll the crash.
Addendum: The XML is created correctly. this happens to all book projects, new and old. Does anyone have an idea?

You could try checking your version of ntdll.dll (a Windows protected system file) for corruption using the "sfc /scannow" command. This replaces corrupted protected system files with the correct MS ones. Also, you could then check if there are any issues with the DirectX graphics (the drivers could be affecting the FM behaviourr) on your system using the DXDIAG utility.
However, as it seems to happen on two systems, the corruption doesn't seem that likely of a culprit. Are you using FM with the structure or unstructured interface, i.e. is your workflow creating the XML using the Save As XML from unstrucured files or are you exporting the XML from a structured application?

Losing Word italics when exporting FrameMaker 11 file

When I import a Word file into Frame - the italics and bold characters are maintained. But if I save the file as HTML or XML - they disappear. If I retag them with the character tags they are maintained, but working in a science document the italics are everywhere. Is it possible to search for the original italics and replace with character tag?
I am using FrameMaker 11.

Another possible approach is, once you've opened the Word document in FrameMaker, to use the File > Utilities > Create and Apply Formats command. This command creates new formats (in particular, paragraph and character formats) as necessary, storing them in the associated catalog and applying them to objects in the current document, so that there are no format overrides. For example, suppose your Word document has 24pt bold red text within titles, 12 point bold text within regular paragraphs, and 10 point bold text within list items, Create and Apply Formats might create new formats called CHARFMT1, CHARFMT2, and CHARFMT3 for these three cases. You can then use these tags in Find/Change to make a global change to a more meaningful format name or in a conversion table, to map content with the specified tags to the appropriate element types.
Be warned, though, that often Create and Apply Formats can produce a large number of formats from one Word tag. For example, there may be numerous variations in the formatting of paragraphs tagged Normal. Create and Apply Formats retains the name Normal for the first one, and appends sequence numbers to the others. You may find yourself with paragraph formats tagged Normal1, Normal2, and so forth with the sequence number going to 20 or more.
Furthermore, since it is unlikely that all variations of a format used in one document appear and appear in the same order in a different document, it is likely that different sequence numbers and hence different tags will be used for a particular variation in two different documents.
Nevertheless, in many projects this command can be extremely useful.
--Lynne

Some CGM graphics do not appear when FrameMaker files are converted to PDF

CGM files are exported from ISO (Arbortext Isodraw 7.0 CadProcess) files. Then they are imported into Adobe FrameMaker 7.2, where all elements of the illustration are visible and can be printed. The FrameMaker FM file is converted to a PDF file using the Adobe PDF converter function of Frame. When the PDF file is opened by Adobe Acrobat 8,0 Professional, some, but not all of the illustrations in the file exhibit this problem (The callouts and other text may appear, but the lines, curves, etc. do not). The illustration prints the same way it appears on the screen. When exporting the ISO file as a CGM, the following selections are made.
When importing file into Frame, "Import by Reference" is selected.
When creating PDF in Frame, the following selections are made.
Any Suggestions would be greatly appreciated. Thanks very much.

Thanks, Michael.
I will give it a try.
Avox Systems Web Site: http://www.avoxsys.com
AVOX SYSTEMS
AIRCRAFT SYSTEMS
Rick Barusic
Senior Technical Writer
225 Erie Street - Lancaster, NY 14086 - USA
Tel: 716-686-1706
[email protected]
http://www.zodiacaerospace.com
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination, or other use of or
taking any action in reliance upon this information by persons or entities
other than the intended recipient is prohibited. If you received this in
error, please contact the sender and delete the material from any
computer.
From:   MichaelKazlow <[email protected]>
To:     rick barusic <[email protected]>
Date:   11/24/2010 10:32 PM
Subject:        Some CGM graphics do not appear when
FrameMakerfiles are converted to PDF
First you should update to the latest version of Acrobat 8, since you say
you are running Acrobat 8, you should update to 8.2.5. Update your
FrameMaker to 7.2p158. Those two steps might do the trick. If that fails
try using a different settings file. Perhaps High Quality or Press
Quality. I would never use Standard for anything where fidelity is
important.

How to export to text file without ruin the format

Hi guys,
I need some help here. My company recently come with the decision to print the mainframe report file that usually come as a text file, to a virtual printer. This virtual printer is printing the report as Adobe PDF format. The problem is, my Line of Business have a macros on Excell file that will grab the information from the text file to be processed in the Excell format. I tried to use Adobe Professional 8 to re-convert the PDF file to be text file, but the result is, most of the blank space is gone, and it is align to left, thus make it unusable to the Excell file.
Unfortunately, I can't provide you the sample of the document, because it contain classified customer info.
But appreciate if you can give me some advice.
Thanks and Regards.

It sounds as if you are dealing with untagged PDF.
Tagged output PDFs, with a well-formed structure, provide (amoung other things) the ability to Save As/Export
content to some other applications with all or most of the layout/format intact.
I suspect that the output PDFs you have are untagged.
As there is, currently, a rather limited number of applications that support adequate tag management
(FrameMaker, InDesign, MS Word (via Adobe's PDFMaker & to a much lesser extent with Office Save As to PDF - XPS)
I suspect the mechanism used to provide your PDFs won't cut it with regards to providing a tagged output PDF having a
well-fomed structure (which would include dictionaries containing format/layout data).
As alluded to by Bernd, there may be third party plug-ins that might help.
The more reliable/functional ones tend to not be inexpensive.
Be well...

Exporting to Framemaker

Similar Messages

Maybe you are looking for