Problem with result-document()

November 22, 2017, 3:43 am

≫ Next: Image getting cut off when converting the fm file to pdf

≪ Previous: FrameMaker 2017 display issues on 4k monitor

$

0

0

Some of our XML documents contain "included" subdocuments.

I have a pre-processor stylesheet which replaces every

<include href="relative-path-to-doc" />

with

<included href="relative-path-to-doc">

  ..content from included document..

</included>

 

Framemaker runs this correctly when loading the outer document and all the subcontent is included. The stylesheet calls

<xsl:apply-templates select="document(@href)/*"/>

to do this and the relative-path-to-doc is evaluated relative to the outer document which was passed to the pre-processor.

 

The problem I am having is when the full document is saved. There is a complementary post-processor stylesheet which is supposed to identify any

<included href="relative-path-to-doc">...content...</included>,

replace the included element with the include element in the output document, and process all the included content within

<xsl:result-document href="relative-path-to-doc"><xsl:apply-templates ... /></xsl:result-document>

 

When I run this stylesheet outside of Framemaker it correctly creates the result-document relative to the primary document, regardless of where I call the stylesheet from. Document() and xsl:result-document() are correctly complementary. But within Framemaker it fails with the error

Fatal Error at file C:\Program Files (x86)\Adobe\Adobe FrameMaker 2017\structure\xml\helpcenter\app\post.xsl, line 40, char -1, Message: java.io.FileNotFoundException: Access to the path 'C:\Program Files (x86)\Adobe\Adobe FrameMaker 2017\formats_sub.xml' is denied.

 

Is this a bug? How could I achieve what I am trying to do here?

 

Thanks

T

---

Image getting cut off when converting the fm file to pdf

November 22, 2017, 6:53 am

≫ Next: FM 2017: Possible to create new variable from existing?

≪ Previous: Problem with result-document()

$

0

0

If I rotate an image in FrameMaker and convert the fm file to pdf, then the image is cutted in the PDF. I use FrameMaker version 2015.

I found this problem already in this forum. There was the solution: "rotate the image before you import this file in FrameMaker". This solution doesn't fit to me. True - I can save the images with the necessary rotation, before I import them. My problem is, that I have images like the cutter, which I have to use in different rotations. It can't be the solution, that I save one image in 15 different rotations.

 

I already tryed other image-formats ond other images like png, pdf, eps. Every time it's the same result.

 

FrameMaker	PDF	Fileformat
		svg 1.0
		svg 1.0

 

I hope you can help me,

 

Julian

FM 2017: Possible to create new variable from existing?

November 22, 2017, 10:59 am

≫ Next: Images not displayed correctly in HTML5 Help

≪ Previous: Image getting cut off when converting the fm file to pdf

$

0

0

Prior to FM 2017, we could open the Edit Variable dialog box, and it had two options: could either edit the existing variable, or use the edit to create a new variable (~ make from).

 

That feature seems to have been removed. The only method I see for creating new ones is the Add button , Creating variables that have similar definitions is now quite TEDIOUS.

 

Did I miss something? Is it hiding somewhere? (Already poked around FM and Google searched, and did a brief search through the answer database here.)

Images not displayed correctly in HTML5 Help

November 23, 2017, 6:36 am

≫ Next: In FM 2017, where is the Resize Table Columns dialog?

≪ Previous: FM 2017: Possible to create new variable from existing?

$

0

0

Hello, I am having an issue when converting my FM 2017 documents to responsive HTML5. Pictures are displayed center-aligned in the middle of the topic, instaed of being left-aligned. I found out that this is associated with conditional text tags. If the text has some conditional text, it shows the issues for pictures that are in that paragraph.

I am using FM 2017. I see the issues in old documents (FM 12) and new documents as well. The common factor seems to be the conditional text.

Thanks in advance,

Fabrizio

In FM 2017, where is the Resize Table Columns dialog?

November 24, 2017, 2:27 am

≫ Next: Font format not applied to an inline element in FrameMaker 2017

≪ Previous: Images not displayed correctly in HTML5 Help

$

0

0

In FM 2017 (14.0.3.500), I can't find the new Resize Table Columns dialog? It's not in Table>Resize All Table Columns.

Font format not applied to an inline element in FrameMaker 2017

November 26, 2017, 6:58 pm

≫ Next: Calling XSLT with CallClient

≪ Previous: In FM 2017, where is the Resize Table Columns dialog?

$

0

0

With our custom structured application in FrameMaker 2017, insertion of an inline element, in this case a //defterm, followed by the entry of text, should result in the text being italicized.  However it does not.  If the //defterm element is selected, and then in the Element pod, changed to a //defterm, the text is italicized.  Alternatively if the text is entered, selected, and then //defterm chosen in the element pod, the text is italicized as expected. The italicization in the EDD is provided by a Font Properties element (PropertiesFont).  It looks to me like the EDD rules are being applied correctly if I look in the Show Element Context pod.  However FrameMaker is not applying the Angle for the PropertiesFont. This image () shows the text where the italicization should occur but does not, and this image () shows the correct italicization.

 

I have tried to recreate the problem using the sample Business structured application by using a PropertiesFont to change the //Labels element to be italicized when inserted.  This works every time.  I will try with a more complex application like DITA later.

 

In FrameMaker 11 this works as expected either way.

 

Has anyone come across this?

Calling XSLT with CallClient

November 27, 2017, 11:33 am

≫ Next: Voreinstellungen FM 2015 werden nicht übernommen

≪ Previous: Font format not applied to an inline element in FrameMaker 2017

$

0

0

What is the syntax for calling XSLT transformations with ExtendScript's CallClient method? An example would be helpful.

 

Also, are there any other undocumented methods or properties that have been recently added? I was disappointed about not knowing about this before. Adobe guys, please let us power users know when there are new features in ExtendScript. Thank you very much.

 

-Rick

Voreinstellungen FM 2015 werden nicht übernommen

November 27, 2017, 10:47 pm

≫ Next: Grafik an die Größe des verankerten Rahmen anpassen

≪ Previous: Calling XSLT with CallClient

$

0

0

Guten Tag,

habe meine FM 2015 auf Windows 10 installiert.

Nach dem ersten Start habe ich in den Voreinstellungen meine Auswahl getroffen (Mit / ohne Backup, Strukturiert etc.).

Hat aber nix genutzt, bei jedem Anstarten verhält sich FM wie beim ersten Anstarten.

Wie kann der Fehler beseitigt werden?

Schon jetzt besten Dank an alle für Eure Hilfestellung.

---

Grafik an die Größe des verankerten Rahmen anpassen

November 28, 2017, 1:28 am

≫ Next: Post script error

≪ Previous: Voreinstellungen FM 2015 werden nicht übernommen

$

0

0

Guten Tag,

 

mein Problem ist Folgendes:

Ich importiere eine Grafik in einen verankerten Rahmen. Wenn die Grafik kleiner ist, als der verankerte Rahmen, muss ich die Grafik immer manuell auf die richtige Größe ziehen.

Gibt es eine Einstellung oder einen Shortcut, der den Rahmeninhalt (also die Grafik) automatisch auf die Größe des verankerten Rahmens anpasst?

 

Vielen Dank für die Hilfe.

 

Viele Grüße,

Torsten

Post script error

October 20, 2017, 9:36 am

≫ Next: How to check current page type

≪ Previous: Grafik an die Größe des verankerten Rahmen anpassen

$

0

0

%[ Error: syntaxerror; OffendingCommand: ) ]%%

%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%

%%[ Warning: PostScript error. No PDF file produced. ]

How to check current page type

November 30, 2017, 1:52 am

≫ Next: old FrameMaker version won't run after trial evaluation

≪ Previous: Post script error

$

0

0

"Welcome back my friends to the show that never ends" - I'm trying to handle variables and need to know whether the  current page is a master page or body page. As You know, on a master page more system variables are valid (Running H/F xx, Current Page #). So to set up a list of valid system vars I need to know where I am.

I read in the doc: PageObject is any Page object i.e., BodyPage, MasterPage, ReferencePage, HiddenPage.

Experiments show that I get answers with this short pgm - but what kind of pages are 'hidden' in the values 0...4, > 7 ?

Is this the correct way to test for the page type?

// CheckPageType.jsx
var   oDoc = app.ActiveDoc;
var   oPage = oDoc.CurrentPage;
var pageType = oPage.type;
$.writeln ("page = " + pageType);
/* type reported   5   Constants.FO_BodyPage        6   Constants.FO_MasterPage   7   Constants.FO_RefPage
*/

Ah well, "don't check for an error situation you don't know how to handle".

Klaus

old FrameMaker version won't run after trial evaluation

November 30, 2017, 2:01 am

≫ Next: Expand and collapse lab steps?

≪ Previous: How to check current page type

$

0

0

Hi

 

I hope there is an easy fix to this because otherwise I am stuck. I have been using FrameMaker v8 for years and it has survived several changes of PC and several Windows upgrades. I understand that FM8 is not officially supported on Windows 10, nevertheless after upgrading my laptop to Windows 10 in 2016 Framemaker 8 continued to run without issues.

 

This month I installed the evaluation copy of Framemaker 2017 and used it for 30 days. When the trial period finished and I uninstalled FM2017 my copy of FM8 would not run. I have tried a repair install, and an uninstall followed by full reinstall, and it still will not run. Task Manager shows a FrameMaker v8 process running but it is using no resources and doing absolutely nothing.

 

Has anyone any ideas where I could look to fix this? Adobe support haven't (yet) refused to help completely but they have said that FM 8 is not supported on Win 10 so I should expect problems. But it was running on Win 10 perfectly happily for over a year, so I'd rather not be fobbed off.

 

Thanks in advance

T

Expand and collapse lab steps?

November 30, 2017, 10:53 am

≫ Next: Can we downgrade a Adobe FM 2017 licencse to FM 9?

≪ Previous: old FrameMaker version won't run after trial evaluation

$

0

0

Hi,

We are starting to work on a lab guide template.  I would like to be able to show the students the high level lab instructions that they should be able to do and give them the option of expanding the instructions to show the sub-steps if they need them.  I think this is possible, but am not sure how.

Any suggestions?

Thanks,

Cindy !

Can we downgrade a Adobe FM 2017 licencse to FM 9?

December 1, 2017, 3:03 am

≫ Next: How to fix a broken DITA cross-reference

≪ Previous: Expand and collapse lab steps?

$

0

0

Hi there!

 

Our software outputs files that can be imported into Adobe FrameMaker. Since some of our customers still run around with Adobe Framemaker 9 licences we have to test our software with FM 9.

 

Is it possible to downgrade an Adobe FrameMaker 2017 Abo to FrameMaker 9?

 

If not: Where can we get a copy of Adobe FrameMaker 9?

 

 

Thanks in advance,

Sebastian

 

How to fix a broken DITA cross-reference

December 1, 2017, 6:41 am

≫ Next: how to fix a broken DITA cross-reference

≪ Previous: Can we downgrade a Adobe FM 2017 licencse to FM 9?

$

0

0

Hello all,

I have what is hopefully a simple question. I'm using FrameMaker 2017 and authoring new DITA documents.

I have a ditamap with dita files in it. I have some cross-references between files.

I renamed one of my dita files, removed the old named file from the ditamap and added the new named file to the ditamap.

 

Obviously, cross-references to the old named file broke.

When I select the Edit > Update References command, I get the familiar "Update Unresolved Cross-references" dialog, and proceed to fix the cross-reference in the same way I used to with unstructured FrameMaker. And it seems to work because the top of the dialog box states "0 unresolved cross-references". However, when I then save the file that includes the cross-reference and then re-open it, the cross-reference is still broken. I see that the fm-xref's "href" is still pointing to the old file.

 

Is there a way to fix broken cross-references, other than manually?

 

Thanks!

---

how to fix a broken DITA cross-reference

December 1, 2017, 6:44 am

≫ Next: Why is my book file converting svg to jpg when generating HTML5?

≪ Previous: How to fix a broken DITA cross-reference

$

0

0

Sorry for the double post. I thought I posted my original question in the Structured FM area but I did not.

 

-------------

 

Hello all,

I have what is hopefully a simple question. I'm using FrameMaker 2017 and authoring new DITA documents.

I have a ditamap with dita files in it. I have some cross-references between files.

I renamed one of my dita files, removed the old named file from the ditamap and added the new named file to the ditamap.

 

Obviously, cross-references to the old named file broke.

When I select the Edit > Update References command, I get the familiar "Update Unresolved Cross-references" dialog, and proceed to fix the cross-reference in the same way I used to with unstructured FrameMaker. And it seems to work because the top of the dialog box states "0 unresolved cross-references". However, when I then save the file that includes the cross-reference and then re-open it, the cross-reference is still broken. I see that the fm-xref's "href" is still pointing to the old file.

 

Is there a way to fix broken cross-references, other than manually?

 

Thanks!

Why is my book file converting svg to jpg when generating HTML5?

December 1, 2017, 12:59 pm

≫ Next: TCS 2017 - Acrobat Distiller license issue

≪ Previous: how to fix a broken DITA cross-reference

$

0

0

When I generate HTML5 for a book file, it is converting my svg graphic into a jpg format. The strange thing is that this conversion only happens when I generate the entire book, not when I generate an individual file in the book.

TCS 2017 - Acrobat Distiller license issue

December 4, 2017, 3:40 am

≫ Next: Keep getting the correct cross-reference as un-resolved cross-reference...

≪ Previous: Why is my book file converting svg to jpg when generating HTML5?

$

0

0

I have a licensed version of Adobe Technical Communication Suite. When I try generating a PDF from FrameMaker 2017 source I get this message:

The FrameMaker version that I have is licensed.

 

Can you please suggest how to resolve this?

Keep getting the correct cross-reference as un-resolved cross-reference...

December 4, 2017, 11:55 am

≫ Next: Publish HTML5 NO TOC

≪ Previous: TCS 2017 - Acrobat Distiller license issue

$

0

0

I'm using FM 2017. Generating a book file and keeps bringing up an un-resolved x-ref. However, the x-reference is correct, it is not an un-resolved x-ref. Clicking on the x-ref takes me to the correct source. Also, generated a pdf and the link works fine. I tried using a different format for the x-ref but still shows up as an unresolved x-ref? Is something wrong with the source?

Publish HTML5 NO TOC

December 4, 2017, 6:53 pm

≫ Next: Can not add a relationship table

≪ Previous: Keep getting the correct cross-reference as un-resolved cross-reference...

$

0

0

Hi,

I am new to Framemaker.

I created a ditamap, and publish as a HTML5 output.

but there was no TOC in the navigation bar.

How to fix the problem?