Fonts via fontstand.com: wrong characters & wrong formatting when importing *.idml)´

[CarlosK]

Hi,

some weeks ago I wanted to edit an *.idml file in Publisher which included a font I don't have.

I used fontstand.com to burrow the font in 3 different version for three hours ("Haylard" Display, Text, book if I'm not wrong).

First of all there was a wrong character for the "F".
Moreover the importing of the *.idml didn't look like it was foratted correctly. I. e. the line breaks and placement seemd a bit out of place.

I'd be happy if anyone has a clue, how to maybe fix it. Because actually it would be a fine workflow.

 

Regards

[Wosven]

Hi @CarlosK,

It would be helpful if you could add screen shots.

I suppose most of the time it's APub that get the space between characters wrong, or because the font version is different from the original.

Selecting the text and setting the tracking to 0 is a possible solution.

[stokerg]

Hi @CarlosK,

Further to what @Wosven has said, If you could attach the IDML file or a sample that shows the same issue, that would be a big help in finding out whats happening  

[MikeW]

1 hour ago, Wosven said:

...

I suppose most of the time it's APub that get the space between characters wrong, or because the font version is different from the original.

Selecting the text and setting the tracking to 0 is a possible solution.

Much of the time, spacing issues with .idml files is due to the difference in how ID sets letter spacing--i.e., composing a run of text. If one has ID set to one of the paragraph composers (versus the single line composers) and how font metrics/kerning are handled (i.e., metrics versus optical), even different versions of ID will/may compose the text differently than the version that was used to create the .idml.

Affinity applications only use a single line composer and only use a font's metrics. Changing either of those settings in ID from how Affinity applications compose text and lines will/may break in different places.

[walt.farrell]

3 hours ago, CarlosK said:

First of all there was a wrong character for the "F".

I don't think anyone has discussed this yet, but again it's a case where a sample document and a screenshot would be very helpful. It could be due to using a different version of the font, or to something else.

[kenmcd]

59 minutes ago, walt.farrell said:

I don't think anyone has discussed this yet, but again it's a case where a sample document and a screenshot would be very helpful. It could be due to using a different version of the font, or to something else.

We are going to need the IDML file to see what is happening.
I do not see any OpenType substitutions for F in the Halyard fonts.
So we need to see what characters are being imported from the IDML file.

[CarlosK]

Hello everybody,

thank you very much for the lively discussion and all of your answers. ❤️

Right now I'm on the road, but will try to deal with this ASAP. Please check back in as soon as I worked out a reply