see issue 19186 for attachement

Something like this has only been seen as a resolution / zoom factor
issue.

Please check if all is visible when you change the zoom factor and if
you print the formula.

Also please state the OS type and version you use.

yes, everything is printed and can be seen in a "bigger" zoom factor, 
but the chosen resolution is high enough to allow the sign be drawn 
fully (you can also see the start of the missing bottom line so it 
would just have to be continued).

I see the problem in calculating the pixel positions when translating 
from one internal resolution to a display or whatever resolution as 
it simply gets calculated and if the pixel is not to be drawn, it is 
not to be drawn; but in this case (100% zoom), it could be drawn and 
this is also sth. I'd like to see in the special characters table 
where such symbols aren't identified immediately because they are 
incompletely drawn.

Win 98 SE on a Kyro II

TL->HDU: Looks similar to the problem with "=" sign some time ago.
Please check.

I could not reproduce this with the latest SRX645 m17 installation
using Windows 98 though.

OpenSymbol fonts look horrible in Special Characters dialogue


scaling problem ;  should look better nevertheless

HDU->IH: Similar problem to the Equal Sign Issue.
The tool used for Opensymbol does a bad job when addings hints. I
suggest to either use a better tool or redesign the affected symbols
for better readability in small sizes. Be careful not to destroy
metric compatibility to StarSymbol.

IH->Lars: Unfortunately I do not have enough time to give OpenSymbol
hand tuned hinting (that is a very longlasting work). I used the
automatic hinting function of Fontographer before I generated the
final font data in PfaEdit(due to many bugs in fonto). If there are
some problems with specific symbols (like we had prev. with "=") then
please tell me which symbols I should give an new design for small
resolutions. If you can find somebody who will do the complete hand
tuned hinting for OpenSymbol, I would be very pleased to put this data
into the font. In the meantime I will have a closer look at the font
data in OpenSymbol (perhaps some hinting data get lost?)

Created attachment 10043 [details]
test file

Hi,


I noticed that the OpenSymbol fonts render fine in Win XP if using
Standard Antialiasing which I'm doing now, so the previous problem is
no issue for me anymore. I attached a Writer file showing the
differences between the different Aliasing settings. I'd give all
those missing an "underbar" a new design like the =,:=, or the "is
subset", "is superset" sign.

Lars

IH: if it is ok for you now please close this issue.

it's ok for me now

so closing