Skip to main content
S
sebdea
Inspiring
June 10, 2015
Question

Running headers do not work, automatic numbering cannot be changed

  • June 10, 2015
  • 2 replies
  • 888 views

Hi there,

I have received a FM 10 document from a translating agency. They claim it is the only file they received from their client. Here are few things I am fighting to solve:

A. The document is supposed to have running headers.They are defined as Variables (<$elemtextonly[Heading(GraphicsPage),Heading(Intro),Heading(Chapter),Heading(Index),Heading(Appendix),Heading(Notes),Heading(Glossary)]>)

The only problem is that when I look at the paragraph designer or catalog there are no styles such as Heading(Intro), heading(Chapter) etc. etc. etc.

Despite the fact that I've created those styles the running headers do not update. Any idea? In fact, entire document is set to use a single paragraph style: Body. In different font sizes and Cases, but all document it is set to use Body, except for TOC.

This fact brings me to my second question. Is there a way to Find/Replace a variable (an autonumbering variable) all over the document so I do not have to do it manually? That's why. Since all text is set as Body, Image caption is also a Body style with autonumbering:

Now, I want to change BUILD to IMAGINE. I know where to look for it and how to change it:

The only problem is that when I click on Update All, the entire paragraphs, sections chapters etc. will have IMAGINE in front of them.

Any options?

I never encountered such an interesting document, to say the least.

The client sent the original document as well, but as  VIEW ONLY frame maker file. I do not have access to any of the menus except for navigation.

Thank you for your help.

Best regards,

Sebastian

This topic has been closed for replies.

2 replies

M
Mike-Hardy
Participating Frequently
June 11, 2015

This looks like it is a structured document (the variable is asking for $elemtextonly). Choose Edit > Preferences, set the Product Interface to Structured FrameMaker, and restart FrameMaker. You'll then have the tools you need to look at the document.

A document called an EDD (Element Definition Document) defines both what markup is allowed in the sturctured document (similar to a DTD), and what formatting to apply in different contexts (similar to a stylesheet such as CSS). There are two common ways an EDD does the formatting:

  • the EDD selects a paragraph format appropriate to the context, and the paragraph format sets the formatting
  • the initial formatting is set by a paragraph format such as Body, and the EDD than modifies this formatting as appropriate to the context.

The latter method keeps all formatting in the EDD, and is a perfectly valid way to do things. I've used it myself. And it looks like this is exactly what you have.

If you haven't been given a copy of the EDD, there is a copy of it within every structured document. You can export it by choosing File > Structure Tools > Export Element Catalog as EDD.

S
sebdeaAuthor
Inspiring
June 11, 2015

I did not receive an EDD file. I tried to export it as you said. No chance.

It looks like a structured FM10 document.

The last solution is to simply format translated document and leave the rest (TOC, Index and headers) on client's end to solve them.

Thank you for help. And for your time.

Regards,

Sebastian

G
Gorly
Inspiring
June 12, 2015

When you say that there's no element catalog to be exported, you almost certainly did save the file already in unstructured FM, which destroys the structure altogether (or maybe they did that already - wouldn't surprise me, to be honest).

What you need to "rescue" the document, is to take the original document you received and check, if that one still has structure. If that is the case, work from there on.

If that document has also no structure, you have two options:

1. Ask for the untranslated original and copy&paste all the translated texts into the structure (that one is going to be tedious).

2. Ask the translators to get their job done and have them use a structured translation process in their TMS, which should preserve the original structure.

I've seen this far too often. We work with structured FM files a lot, and translators manage it on a regular basis to mess up with the structure in the documents.

Either they destroy the structure altogether, replace entities with some HTML junk or destroy inline elements.

Arnis Gubins
Arnis Gubins
Inspiring
June 10, 2015

Sebastien,

Is this a structured or unstructured document that you got back from the translation agency? Are you using the correct structured application/template for this document if structured? The variables are asking for elements, not paragraph styles.

If it is all set as Body with differing fonts and cases, then overrides are being ued - a very big no-no!

To unlock the original FM document, use the shortcut <esc> F l k  (that's captial F, lowercase "L", and lowercase "K").

[Also, if it is structured, this thread will be moved to the Structured FM forum]

S
sebdeaAuthor
Inspiring
June 11, 2015

Yes. The file is Structured document. Sorry to put it into a wrong section. Please move it where it supposed to be.

I can move it my own but please let me know how.

Thank you.

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