• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

FM2017 & FM2019 Object properties dialog for images does not respect xml attribute

Explorer ,
Sep 16, 2020 Sep 16, 2020

Copy link to clipboard

Copied

Hi everybody,

 

I've found a few posts claiming that FM2017 and FM2019 have images issues that FM2015 did not have.

My collegues and I are facing the issues likewise.

 

Opening an XML file with images defined either by "scale" or e.g. by "width", some images will be "mis-sized".

Consider this <fig> node:

<fig><figspace/><image href="../PathToImage/Image.png" placement="break"  scale="24.00" />
<title>Title of the Image</title></fig>

The image may be scaled by 24%, but not always.

I tried to pinpoint the issue by inserting this node several time a row.

<fig><figspace/><image href="../PathToImage/Image.png" placement="break"  scale="24.00" />
<title>First Insertion</title></fig>
<fig><figspace/><image href="../PathToImage/Image.png" placement="break"  scale="24.00" />
<title>Second Insertion</title></fig>

 No difference between the two nodes, yet, the value for scale in the object properties dialog in FM are different between the two images. (and the scale value in the dialog ist different from the value the scale attribute)sBugFM_Images.png

 

Changing the scale in the oject properties helps until closing the file. When opened again, the same wrong values are there again.

Any suggestions?

 

TOPICS
Error , Formatting and numbering , Structured , XML author

Views

426

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 17, 2020 Sep 17, 2020

Copy link to clipboard

Copied

Can you please share the file set once so we can look at why this difference. This is an area we do plan to address and improve over the upcoming Summer Release of 2020 updates. 

 

Thanks

Amitoj Singh

E: amisingh@adobe.com

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 18, 2020 Sep 18, 2020

Copy link to clipboard

Copied

Thank you Amitoj, I wrote you an email.

 

For the rest of the community:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "technicalContent/dtd/task.dtd" [
]>

<task id="id19AVA0AB0UL"
 xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/">
 <title>Some Title</title>
 <taskbody><context><p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua:</p></context>
  <steps><step id="id199G80D60DH"><cmd>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</cmd>
    <stepresult><p>At lectus urna duis convallis convallis tellus id.</p></stepresult></step>
   <step><cmd>Sem fringilla ut morbi tincidunt augue interdum velit euismod in.</cmd>
    <fig><figspace/><image href="../../../../CommonGraphics/Screenshots/Image1.png" placement="break"  scale="40.00" />
     <title>Title for the First Figure</title></fig>
    <fig><figspace/><image href="../../../../CommonGraphics/Screenshots/Image1.png" placement="break"  scale="40.00" />
     <title>Here is Copy of the First Figure</title></fig></step>
   <note type="tip"><notesymbol/><p>Tellus in metus vulputate eu scelerisque felis imperdiet proin fermentum. Et pharetra pharetra massa massa. Lacus suspendisse faucibus interdum posuere lorem ipsum dolor sit. A lacus vestibulum sed arcu.</p></note></steps>
  <postreq><p>Mauris augue neque gravida in fermentum et sollicitudin ac. Ac auctor augue mauris augue neque. Adipiscing enim eu turpis egestas pretium aenean pharetra magna ac.</p></postreq></taskbody></task>

Information about the image:

1010 x 999 Pixels (1.01 MPixels) (1.01)
35.6 x 35.2 cm; 14.03 x 13.88 inches

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 14, 2020 Dec 14, 2020

Copy link to clipboard

Copied

Hi FabianK007,

 

FM fits an object to the frame size when it is inserted. Is the image bigger than the frame in this case?

Also, reagarding the different scaling on the image, Can you specify if the frame where image is inserted is different?

 

Thanks & Regards,

Namita

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 09, 2021 Apr 09, 2021

Copy link to clipboard

Copied

LATEST

Hi Namita,

The file is created with FM2015 then opened and saved with FM2019. I assume the frames are the same.

Furthermore, the effect would not occur for the first occurrence of the image in the document. Copying the first image (thus having two) we'll have the first image being good but not the second one (although it's just a copy).

Unfortunately, we don't have FM2019 for the moment, so I cannot test anything for the moment.

Regards
Fabian

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines