Pffeww!!!
I was in panic mode there for a while this morning, thanks for the fix guys!
Marc
Printable View
Pffeww!!!
I was in panic mode there for a while this morning, thanks for the fix guys!
Marc
lets not rush to blame Microsoft - they are not able to test their patches against every conceivable possibility...
According to Corel, the issue is:
Adobe products seem to work fine, so either they are going about obtaining this information differently or ... something.Quote:
The problem is with a windows API called GetGlyphOutline(). (http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx). For certain fonts like those mentionned here, it fails to return us the memory size we need to extract a character's glyph's curves.
I suspect application vendors are going to have to issue update patches.
And I was incorrect about previous XDP versions.
Take care, Mike
fair enough Mike - thanks for that - now is that an API issue, a font issue, an app vendor issue.... or just one of those things....... or what..... hey....
From what I found from searching, this update affected many graphics programs I found complaints about this issue in Xara, Corel, Inkscape, Quark, and even Adobe forums. And so far there only seems to be one solution, Don't install the update.
As Barbara pointed out this is an important security update, each of us will have to decide what to do. As a designer I need my fonts intact, especially for the next few days as I near the end of my Christmas rush. So far I still am unable to find anything from Microsoft that would indicate that they are going to fix the updates.
Does the update need fixing is the first question - or is it just one of those times when a vendor makes a change the rest of us all have to live with.... could be either
No idea if the vendors or MS will have a joint or individual fix.
I pity software vendors if it is left to them. How exactly would they then handle previous versions? Make everyone upgrade?
Take care, Mike
No idea if the vendors or MS will have a joint or individual fix.
I pity software vendors if it is left to them. How exactly would they then handle previous versions? Make everyone upgrade?
From Microsoft. Initial response on the Microsoft Connect web site for reporting bugs:
Take care, MikeQuote:
Thank you for contacting Microsoft community. This update would require an update from the program developers to cope with the changes made, however you can hide the update.
Follow these steps to hide Windows update:
a. Open Windows Update by clicking the Start button . In the search box, type Update, and then, in the list of results, click Windows Update.
b. Do one of the following:
· Click the link that tells you important updates are available if you have important updates to hide.
· Click the link that tells you optional updates are available if you have optional updates to hide.
c. Select any update that you want to hide, right-click it, and then click Hide update. Do this for each update you want to hide.
d. Click OK.
Hope this information helps. If you need further assistance with Windows, please reply we will be happy to help you.
I'd just like to toss this thought out on the subject of finger-pointing:
Before Windows 95 came out, Microsoft gave every developer plenty of time to let them know that a program will not/should not write directly to screen. I had a modeling program that was lighting-fast on a Pentium 3 I recall, and it was because it usurped the video calls to Windows to write directly to screen under Win 3.1.
After Windows 95 came out, the engineers at MacroMedia had to do some big-time rewriting of the program because Win 95 wouldn't allow direct to screen writes.
+++++++++++++++++++Now++++++++++++++++
Isn't it conceivable that vendors, and not Microsoft, will have to patch this font thing, because they've been doing something with fetching glyph outlines that they were advised long ago not to do? And Adobe was one of the few vendors who listened?
I'm not judging anyone, not the Xara Group, not anyone.
I'm just throwing out a possibility.
-g