Cut off text/font in selection. Cannot access Open type/alternate features.

Hello,

I tried the fonts provided and the problem is not in CorelDRAW but in the fonts design. We have already a similar issue with other fonts. Unfortunately there is nothing we can do about it.

Fonts were tested with X6, X7, and X8 and all versions behave the same way.

Hope this helps,
Oumhani

Other applications that use the Windows font subsystem do not have the issue. CorelDraw should be able to handle the problematic fonts just as these other applications do.

oumhanib said:

there is nothing we can do about it.

If Adobe can do it and we can't there has to be a reason. I would assume  that reason is one of compliance. 

It is not just Adobe applications that can display these fonts properly.

As Oumhanib writes, they are made improperly in the technical sense. And Windows is sending the proper font metrics to applications that rely on Windows to report the font metrics. But there are some applications that still read the actual ascender/descender info from the characters.

Typical Windows applications cannot do what Adobe has done--Adobe bypasses the OS font system and reads the fonts directly. So without doing the same, all the benefits that Adobe has with their font technology cannot happen.

However, this problem use to be relegated to only artistic text in CD for various updates and paragraph text worked. There are threads around here where it was suggested and worked.

I haven't tried lately, but it also use to be that wireframe view showed the ascenders/decenders, as did adding an outline. Adding an outline worked as it forced CD into using a different rendering of a font (probably applies to wireframe view as well).

MikeWe said:

Typical Windows applications cannot do what Adobe has done--Adobe bypasses the OS font system and reads the fonts directly. So without doing the same, all the benefits that Adobe has with their font technology cannot happen.

I have multiple architect client having issues with fonts in their Adobe products, not sure what the issues are and I really don't have time to care. Some fonts work some don't so what is the price and really are there benefits?

So what is correct?

Is this MS saying do it this way or else?

Is this Microsofts way of weeding out bad font code for future enhancements?

We can do something about it but it is a complex problem with a complex solution that is beyond the scope of the next release at this moment. Some day, we will get to it.