Skip to main content
A
Anonymous
January 5, 2015
Question

FrameMaker10: Cause of difference between actual display and element setting

  • January 5, 2015
  • 1 reply
  • 683 views


Hello, everyone

In using FM10 in Windows7, I've experienced the problems below.

1) A black square(■) is displayed while an ASTARISK element is set in the structure view. ("*1" is displayed on another computer )

2) Different BODY elements are used but no return is inserted between the sentences.

Acutually, I already know the solution to the problems: import an element definition to the file.

If you know the (possible) "cause" of the problem, please let me know.

[Message moved to FM Structured Forum by moderator]

This topic has been closed for replies.

1 reply

R
Russ Ward
Legend
January 6, 2015

darkhourse,

I am responding because I don't like to see a post go without any response. This is especially true because I think there is an answer to your question; however, I can't understand exactly what your questions are. Can you provide more information? In particular, where are you seeing the black square? And what do you mean by an ASTERISK element?

Also, for problem number 2, I have no idea what you are trying to say.

Russ

A
Anonymous
January 7, 2015

Hello, Russ

Thank you for your response and sorry for my elliptical explanations.

I'll rewrite the problems I have experienced below.

Problem1: An ASTERISK element is a note style (supplementary explanation) in manuals, defined to be displayed as "*1".

ex)  (Placed below a table, referring to "Description*1" in the table header, )

      *1: The descriptions do not apply if PC2025 is used.

What I meant in the question was that "■" was displayed instead of *1 although an ASTERISK element was used.

Problem2: A BODY element is used for sentences.

For "*1: The descriptions do not apply if PC2025 is used", you need to place a BODY element below the ASTERISK element in the hierarchical structure in order to write "The descriptions do not apply if PC2025 is used.".

If you want to start a new line in writing multiple sentences, you need to use another BODY element.

What I meant in the question was that although I used two BODY elements, the sentences were displayed without a line break as if just one BODY element was used.

I'm happy to provide further information if required.

Darkhourse


G
Gorly
Inspiring
January 8, 2015

Hello, Russ

Thank you for your perfect understanding.

●binary *.fm file

I asked some of my colloegues but they didn't know such a file format. We usually use files with extensions of ".fm" and ".xml".
Please tell me when we use "binary *.fm files" if necessary.

●XML file
I'm not importing XML files.
I'll introduce you to a bit of our task, just in case, although it may be irrelevant to the problem.
We usually use XML files when our task includes translations.
The work flow is:Translation work with Trados (translation software)→Export XML files→Import XML files to FM files.
My desktop has Trados installed on my computer but the files with the problem are manuals in our mother tongue.　So I needed neither XML nor Trados.

I doubt my answer will satisfy you but still look forwad to receiving your reply.

Darkhourse


I'm starting to grasp, where your problem might come from.

You're saying, that when you create a new document and use those elements you mentioned, you are getting those weird results?

And, after you import the element definitions, everything is as it should be again?

Then all you need to do, is to get your system administrator or whoever is responsible for your FM setup to update the standard templates you are using to include the latest element definition file (EDD), as it seems you are using an outdated or incorrect version of it.

The issue, that you are receiving a square bullet instead of "*1" means, that the ASTERISK element is mapped to some other text brick (the square bullet) than in the current version of your EDD (which is embedded in your template file).

The BODY element seems to be mapped to a character style instead of a paragraph style in this outdated version - meaning you will have no line breaks, as it is treated as an inline element.

So, in short terms: get in contact with the guy that did set up your structure definitions/ templates. He should be able to fix your problems in no time.

If the guy isn't in the company anymore or if those structures were created by some 3rd party company, you are going to need to do some more research on how to change templates and their respective element definitions.

It is most important for your work, that at least one person in your company has the knowledge how to fiddle with those things, or you might be facing more serious issues in the future.

On a side note: binary FM files are the ones using *.fm as an extension. Those files include everything the document consists of: your document, the template, the element definitions and everything else.

As a counterpart, XML files only contain your document and the structure markup. Templates, element definitions and almost everything else is applied to those files upon import in Framemaker, or excluded upon export.

-Alex

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices