Quantcast
Channel: Adobe Community : Popular Discussions - FrameMaker Structured
Viewing all 66580 articles
Browse latest View live
↧

OTF Fonts Thai

September 7, 2009, 9:27 am
$
0
0

Hello,

 

we are working with structured FM 8 and do translate in pretty much all languages except for Arabic. So far, there were no complaints for the Asian languages. But now, we receive the feedback that the characters for Thai (Arial Unicode) are correct but that there are spaces between some characters making it difficult to read the text. We have done various tests and recognized that all True-Type fonts are causing these problems. Now, I installed an OTF-Font for Thai and the problems stay the same. Therefor, my question if the Thai font is upported at all?

 

Thank you very much in advance,

Sandra Ullrich

↧
Search

Absolute path in Doctype DTD makes DTD unavailable on other machines

September 29, 2010, 1:19 pm
$
0
0

Hi all,

 

When saving to XML, I understand that Frame takes the relative path to the DTD as described in structapps.fm (in our case, $STRUCTDIR\xml\xdocbook\app\docbookx.dtd) and generates an absolute path in the XML it writes, like this:

 

DOCTYPE chapter SYSTEM "file:///C:/Program%20Files/Adobe/FrameMaker9/structure/xml/xdocbook/app/docbookx.dtd"...

 

This, of course, makes the files impossible to open on a machine that has Frame installed in something other than "Program Files".  Any way to get around this?  Have Frame generate a relative path in some way?  I've researched this in the ref and dev guides and don't see any way to control this.  I did try adding something to the rules, like this...

 

writer external dtd is system "docbookx.dtd";

 

but then Frame just looks directly in the folder that contains the document you're trying to open.

 

Thanks for any suggestions.

 

- Shelley

↧
↧

"page wide" table attribute, where is it set?

November 11, 2010, 9:23 am
$
0
0

The standard (example) dita topic r/w rules for table elements include:

 

attribute "pgwide" is fm property page wide;

 

Does FM have such a property for tables?  It's certainly documented in the struct dev guide and ref, but I don't know what it correlates to.

 

I would like to use this to set the pgwide attribute in my dita sources.  The only work-around I've found is to change the rule to:

 

attribute "pgwide" is fm attribute;

 

add the pgwide attribute to table in the edd, and set it.  It's a no-op as far as FM is concerned, but is at least preserved on reading and writing.  Without changing the r/w rule, FM appears to throw my value away.

 

I'd like to think there's a better way, and it at least looks like there's intent.

 

Thanks

Bruce

↧

Making display options sticky

October 25, 2011, 8:00 pm
$
0
0

In FM 10, whenever I open a DITA topic, the Structure View and Element Catalog display options revert to defaults that look cluttered and annoying to me. The Structure View displays all the attributes, and the Element Catalog shows all the element descriptive tags. In the Structure View, I right-click, select Attribute Display Options, and set the display option to No Attributes. In the Element Catalog, I click the Options button and unset the option Show Element Descriptive Tags. Then both windows are simple and uncluttered. When I finish editing my DITA topic, save it, and close it and then open another DITA topic, the Structure View and Element Catalog revert to the cluttered view again. This gets annoying. I looked for preferences to making my preferred views permanent, but I could not find anything in the interface, in the DITA options, in the user manual, or in the maker.ini file. I tried saving the settings as part of my DITA workspace configuration, but the preferences weren't saved with the workspace, either. I don't mind having these more elaborate views available, but I do mind not being able to control them as a preference. Does anyone have a solution for this?

 

Susan

↧

converting Framemaker files into PDF progaramatically using publishing server

December 20, 2012, 11:22 pm
$
0
0

Hi All

 

Background:
We are going for upgrade of  Frame maker 8 which is on unix system  to FM 10 or 11. We are using Framemaker mainly for renditions, i.e to convert the fm documents to PDF. To convert fm document to PDF we are using the below mentioned command line utility available in FM 8.(on unix). /opt/app/frame8.0/bin/fmprint -i -p Sample.fm.fmtpl Sample.fm Currently the the fm file which need to converted to PDF and the FM 8(installed) are available on the same unix system ,so we were able to initiate/use the command line utility of FM 8. The rendition of the FM to PDF is On -Demand.( We are not running any batch activities/ bulk renditions).We are rendering the document as soon as the document  is available.

Requirement:
As we are going to  upgrade the FM to newer versions which would be installed on the Windows machine as Frame maker 10 or 11 will not support unix plat form, so can you please let us know which option is better to use i.e we want to convert fm file to PDF using java program without any manual intevention using publishing server/client version.
can any one help us as it is very urgent for us.
please let us know the ways to do and links for helpful documents .

thank you very much for your help in advance!!\

 

Best reagrds

Ramesh babu

↧
↧

How to modify the color of an "xref" element existing as a cross-reference?

May 6, 2014, 11:00 pm
$
0
0

How to modify the color of an "xref" element existing as a cross-reference? It's color now is black, but I want it blue. Excerpts from the EDD file are as follows. Can someone help? Thanks in advance. You can also give me your skype if you have the answer.

 

 

Element (CrossReference): xref

Attribute list

Name: show Choice Optional

Choices: new, replace, automatic

Default: automatic

Name: ref-text String Optional

Name: ref-external-id String Optional

Name: ref-file String Optional

Name: ref-id String Optional

Name: window-number Choice Optional

Choices: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

Default: 1

Name: condition String Optional

Name: condition-model String Optional

Name: property String Optional

Name: revision Choice Optional

Choices: changed, added, deleted, off

Name: anchor-id String Optional

Name: msg-info String Optional

Initial cross-reference format

If context is: * < (list-steps | block)

Use cross-reference format: number

Else

Use cross-reference format: number-and-text

↧

FrameMaker Server 8 in a cluster server

June 6, 2008, 12:30 am
$
0
0
Does anyone have any experience with FrameMaker Server 8 (or previous versions) running in a cluster server?

Also, if anybody has implemented FrameMaker Server 8 running unattended in any kind of server --be it a High Performance, High Availability or any other configuration-- please feel free to comment.

Thanks
Juan Souza
↧

"Unwrap" CDATA with XSLT

June 12, 2008, 1:41 pm
$
0
0
Hi,

I know this isn't necessarily a FrameMaker question, but it is a place where I know people. So forgive me for asking it here.

I have some CDATA sections in an XML file that contain markup that I want to be parsed eventually, and I want to be able to extract it with the markup intact. Can I do this with XSLT, or does the nature of CDATA negate the use of retrieving the markup with an XML-parser-dependent technology?

Here's a sample element (element tags replaced with curly braces)

{documentation}{![CDATA[{p}Some text{/p}]]}{/documentation}

Is there any way I can get that p element out of there with XSLT, without excaping any of the characters, so it is parsable markup in the output?

[{p}Some text{/p}

Thanks,
Russ
↧
Search

topics from third-tier maps are missing in final DITA-built FM doc

March 7, 2009, 8:48 am
$
0
0
I'm using FM 8.0p277 on XP
No third-party tools.
All my dita files are broken down to the topic, concept, task, reference element level.
I'm now building an FM chapter from nested maps.

Problem
When I build an fm document from a DITA map (DITA / Build FM Document from Dita File),
the third-tier topic elements and their concept and task sub-elements (built from sub-sub maps) do not appear in my final FM document.
An error message briefly appears: "FM document generated from DITA Map, but with errors. Please refer to console for errors."
(I can't find this console.)
The FM document is built, but with missing elements.

For instance:
I build a mini map C: with topicrefs to one concept, and one task element wrapped in a topicref to a topic element (Turning off the machine).
(This becomes a sub-section of my chapter.)

Then I build an intermediate map B: with topicrefs to several concept elements and task elements, plus a topicref to mini map C, all wrapped in a topicref to a topic element (Safety Features).
(This maps a heading 2 level section of my chapter.)

Then I build the top map A: with topicrefs to four intermediate maps, including map B (linked to map c), these are all wrapped in a topicref to a topic (Saftety Topics).
(This becomes my Chapter fm document.)

Problem:
Everything comes in at the right order, except that the information from map C is missing.
FrameMaker 8.0 does not seem to be able to pull in the third-tier map's topics. (Three nests of mapped topics.)

Is that right?
Do I need to give up the idea of breaking info down to the lowest topic, concept, task, reference, and making these third-tier little mini-maps?

Note: each mini and intermediate map build into FM documents just fine.
↧
↧

DITA programming, software, user interface elements

April 3, 2009, 7:32 am
$
0
0
I'm evaluating the DITA capabilities in FrameMaker 9. As far as I can tell, the programming, software, and user interface element domains are not enabled by default. Can these domains be enabled? If so, how?
↧

Variable Conversion to XML

April 30, 2009, 6:45 pm
$
0
0

Using: FM 8.0

I am exporting a structured fm file as XML and trying to setup my read/right (rw) rules to eliminate the characters that are placed around each variable when exported.

 

When I export a fm file as XML the words that were set as a variable within Framemaker are export with a preceding & and a trailing ;

 

For example if the word Cardboard is set as a fm variable, it appears like this when exported as XML:

&Cardboard;

 

Is there a r/w rule that would strip the “&” and the “;” away from these words during the export process?

 

Thanks in advance for everyone’s help.

 

↧

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

July 20, 2009, 1:31 pm
$
0
0

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:

  1. 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.
  2. 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.
  3. An element is used for formatting purposes only, whereas all other elements are used for content or structure.
  4. 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.
  5. 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?

↧

Importing MathML in to FrameMaker 7.1

December 30, 2009, 4:05 am
$
0
0

Hai All

 

Is there any plugin available to import MathML in to FrameMaker 7.1(Structure).

 

 

Thanks in Advance

 

Mathew.cj

↧
↧

Generated PDF file...TOC Items Not Linked

January 12, 2010, 11:24 am
$
0
0

Been racking my brain all day trying to figure out how the heck I created a PDF document TOC with hot links to the document pages from FM 9...and now all of a sudden when I save as a PDF from FM 9 my PDF document TOC is not linked to the document.  Help in FM 9 is not very helpful.  I'm using FM 9, Structured.  Help please.

 

Thank you,

 

Eric G.

↧

Unable to print to PDF Oversize pages from FrameMaker 9.0 and 7.2

June 7, 2010, 10:14 pm
$
0
0

Hi All,

 

I am trying to print to PDF a publication that is full of oversize wiring diagrams. The pages are all images ranging in size from standard A3 and A4 siz sheets through to a foldout being 1470 mm W X 297 mm H. We have no problem printing A3, A4 and 630 mm W X 297 H. These are all Portrait images. When we set up our custom print size to accomodate the 1470 mm W X 297 mm H we get the pages without the content, and even some of the oversize pages are not the correct size on print.

 

The page sizes we are using are:

  • A4
  • A3
  • 630 x 297 mm
  • 840 x 297 mm
  • 1050 x 297 mm
  • 1260 x 297 mm
  • 1470 x 297 mm

The procedures we are using to set up the printing are:

 

1.      Print to PDF (Do not Save to PDF, you do not have control over paper sizes)

Under Print Setup make sure you select PDF Driver and select the Paper size as largest that is in your book.  Example: If A4 and A3 pages, print to A3

2.      Select Generate Acrobat Data and select

 

 

Note: Back in FM Print dialogue; make sure Print to File is turned OFF, before you click Print

Any assistance would be greatly appreciated.

 

Regards

 

AJ Wilkinson

 

 

 

↧
Search

Error: Cannot make any changes. This document is view only. FM 10 and TCS 3

August 10, 2011, 8:49 am
$
0
0
  • I created a DITA file of type "topic" and saved it with a specific name.
  • Then I tried to add a body tag under the pre-entered title tag.
  • Immediately the error message is displayed:  "Cannot make any changes.  This document is view only."

My FrameMaker 10 is part of the Technical Communication Suite 3 (TCS 3).  I tested this on another computer in FM 10 trial version only, and it works OK.  Is there a problem with FM 10 and TCS 3?

↧

How do I create page breaks in the structure itself?

September 6, 2011, 4:10 am
$
0
0

Hello,

 

I'm switching from word to structured FM and DITA. I know that I could use the lines element to create page breaks where I need them, and also insert manual page breaks at the top of the next available page.

 

But there must be a better way in the structure somehow, conditional on certain conditions - for example, new topics always on a new page or no separation of images from its immediately preceding reference. Please could somebody expain how I can create such page breaks in the structure.

↧
↧

Framemaker 10 EDD syntax for automatically set attribute values

February 22, 2012, 2:52 am
$
0
0

Hi all,

 

it is necessary to set one or more attribute values of a parent element automatically only by exist or not exist conditions of an spezified child element!

 

Please help!

↧

Why aren't my DITA elements nesting?

March 28, 2012, 3:40 pm
$
0
0

FrameMaker 10 and patched || Windows 7 64-bit

 

Our company is migrating from unstructured to structured DITA XML.  We had not encountered any "showstoppers" that would keep us from proceeding...until we tried producing FM Book files for our print offerings.  It's my understanding that to take advantage of FrameMaker's numbering and pagination features using DITA source content, one must create a DITA map and save it out as a FM Book file, first.  However, when we do this—and subsequently try to print it like a "normal" book—all of our DITA <title> elements remain at the highest heading level.  In other words, each topic, which lives in a hierarchical structure inside any one of the DITA sub-maps, will always take on the paragraph style of .  My topic titles don't nest; everything is at a "flat" level!   Interestingly enough, they nest correctly if I print directly from a DITA map and not from a hybrid DITA+FM book file.  But if I take that route, I forfeit FrameMaker's ability to create a table of contents, index, etc.—features I can't live without.

 

I've tried fixing this behavior over the course of an entire week, but I have not had any success.  I cannot find any resources that address this issue, nor can I find anyone with the same issue.  Left to my own devices, I've experimented with re-building the maps numerous times; I've built the maps as plain maps and as bookmaps; I've even tried strange things like conref-ing everything.

 

What am I missing?  Does anyone know what is going on here?  How can I get my <title> elements to nest?

 

Some background information:

We place chapters in submaps (one per).

We place those submaps in one, big map.

 

Any help would be greatly appreciated,

Sean

↧

problems importing XHTML

May 25, 2012, 1:06 pm
$
0
0

I followed the instructions in this video to import an XHTML file generated by RoboHelp:

 

http://tv.adobe.com/watch/adobe-evangelist-technical-communication/bring-indesign-content- into-framemaker-10

 

First I had to switch to structured mode, unstructured FrameMaker doesn't know what to do with the file.

 

When I open it in structured mode, I get the error "Validation of XML file failed. Continue?"

 

XML Read Report Log ...

XML Parser Messages (Document Instance)

Error at file ...

line 75, char 78, Message: Attribute 'title' is not declared for element 'script'

Error at line 83, char 82, Message: Attribute 'title' is not declared for element 'script'

 

The import completes, but a bunch of code (see below) gets pulled in without being interpreted. Is there some way to suppress that? I could post-process the files but this seems like something FrameMaker ought to be able to handle.

 

/**/ body { background-color: #ffffff; } A:visited { color: #006699; } A:active { color: #FFCC00; } A:link { color: #006699; } /**/

/**/ table.whs1 { width: 500px; } tr.whs2 { vertical-align: top; text-align: left; } th.whs3 { vertical-align: top; text-align: left; width: 30%; padding-left: 1px; padding-top: 1px; padding-right: 1px; padding-bottom: 1px; } th.whs4 { width: 70%; padding-left: 1px; padding-top: 1px; padding-right: 1px; padding-bottom: 1px; } td.whs5 { padding-left: 1px; padding-top: 1px; padding-right: 1px; padding-bottom: 1px; } /**/

/**/ div.WebHelpPopupMenu { position: absolute; left: 0px; top: 0px; z-index: 4; visibility: hidden; } /**/

// <!-- if (navigator.appName !="Netscape") { document.write("<link rel='stylesheet' href='SentrionStyle.css'>");} //--> //

// <!-- function reDo() { if (innerWidth != origWidth || innerHeight != origHeight) location.reload(); } if ((parseInt(navigator.appVersion) == 4) && (navigator.appName == "Netscape")) { origWidth = innerWidth; origHeight = innerHeight; onresize = reDo; } onerror = null; //--> //

 

Here's what that looks like in the XHTML file:

 

<style type="text/css">

/*<![CDATA[*/

body {

        background-color: #ffffff;

}

A:visited {

        color: #006699;

}

A:active {

        color: #FFCC00;

}

A:link {

        color: #006699;

}

/*]]>*/

</style>

 

<style type="text/css">

/*<![CDATA[*/

table.whs1 {

        width: 500px;

}

tr.whs2 {

        vertical-align: top;

        text-align: left;

}

th.whs3 {

        vertical-align: top;

        text-align: left;

        width: 30%;

        padding-left: 1px;

        padding-top: 1px;

        padding-right: 1px;

        padding-bottom: 1px;

}

th.whs4 {

        width: 70%;

        padding-left: 1px;

        padding-top: 1px;

        padding-right: 1px;

        padding-bottom: 1px;

}

td.whs5 {

        padding-left: 1px;

        padding-top: 1px;

        padding-right: 1px;

        padding-bottom: 1px;

}

/*]]>*/

</style>

 

<style type="text/css">

/*<![CDATA[*/

div.WebHelpPopupMenu {

        position: absolute;

        left: 0px;

        top: 0px;

        z-index: 4;

        visibility: hidden;

}

/*]]>*/

</style>

 

<script type="text/javascript" language="JavaScript" title="WebHelpSplitCss">

//<![CDATA[

<!--

if (navigator.appName !="Netscape")

{   document.write("<link rel='stylesheet' href='SentrionStyle.css'>");}

//-->

//]]>

</script>

<script type="text/javascript" language="JavaScript" title="WebHelpInlineScript">

//<![CDATA[

<!--

function reDo() {

  if (innerWidth != origWidth || innerHeight != origHeight)

     location.reload();

}

if ((parseInt(navigator.appVersion) == 4) && (navigator.appName == "Netscape")) {

        origWidth = innerWidth;

        origHeight = innerHeight;

        onresize = reDo;

}

onerror = null;

//-->

//]]>

</script>

↧
Viewing all 66580 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>