IDML document - wrong DPI and change does not rescale font sizes

[Walter B]

Hello everyone,

I need some assistance with Affinity Publisher and IDML files I have to deal with.

Our design department works with Adobe InDesign and saves the documents as INDD files. For me they store is as IDML files additionaly.
This worked flawless so far, but I didn't need to handle the idml files for over half of a year now and when I tried to view a new idml file today, I had some trouble with the size of, in the end, the whole document (not the document size, but the size of the elements within the document).

I needed to check which font and font size to use and got font size vales of "108,3px", which was very unlikly to be correct.
After some investigation I figured out, that the DPI of the document was set to "600", which is not correct, cause the original file was created with 72 DPI (for web).

So I tried to change the document DPI to 72 (also stated as the resolution to this problem in this forum post), but nothing happend/changed at all.
The document is at it was before (everything to large) and also the font sizes did not change.

So my questions are:

• Is there something, that has to be done different, when the file is saved in idml format with InDesign? (what my colleagurs have to do)
• Is there something, that I have to do different, when handling with idml files?
• Why does changing the DPI of the document have no effect on anything?
• Is this maybe a bug of the current version or does it work as designed, but I have to deal with it in another way?

As a workaround I just mathematically "scaled down" the font sizes. 600/72 = 108,3/x -> x is calculatable
But of course this can only be a temporary workaround and not the solution.

I'd be thankful for any advice and all your help. Thank you!

Best regards,
Walter

P.S.: Is this a completely community driven forum or is the Serif support also reading and answering here?

[Lee D]

Hi @Walter B Welcome to the forums.

We do have some reports logged that relate to IDML files, DPI and fonts, these are with the developers to investigate further. Apart from the workaround you've already used there isn't much that can be done as the importing of the file is done automatically.

If it's possible to provide an example .IDML file that this occurs with I can test to confirm the issues and add it to the existing reports.