This looks very much like the cause of the problem that Mike Ver Duin is having at http://community.coreldraw.com/forums/t/33943.aspx
Is anybody else finding their fontnav (64 bit or otherwise) is diagnosing italic fonts as duplicates?
My details:
X6 installed on newly delivered 64 bit win 7 professional (with all available windows updates).
Asked fontnav to find fonts from D:\Users\Public\Documents\Corel\Content X6\Fonts (as installed from X6 DVD).
The catalogue shows at most two fonts from each family of four:
Going to file > Settings > Duplicate Fonts shows the reason: the regular and italic versions of the font have been improperly detected as duplicates of each other.
It applies equally to the fonts on the Corel CD and those already installed in windows, including standard fonts such as Times New Roman.
OS Name Microsoft Windows 7 ProfessionalVersion 6.1.7601 Service Pack 1 Build 7601Other OS Description Not AvailableOS Manufacturer Microsoft CorporationSystem Name PCS2System Manufacturer System manufacturerSystem Model System Product NameSystem Type x64-based PCProcessor AMD A8-3870 APU with Radeon(tm) HD Graphics, 3000 Mhz, 4 Core(s), 4 Logical Processor(s)BIOS Version/Date American Megatrends Inc. 1901, 08/02/2012SMBIOS Version 2.6Windows Directory C:\WindowsSystem Directory C:\Windows\system32Boot Device \Device\HarddiskVolume2Locale United KingdomHardware Abstraction Layer Version = "6.1.7601.17514"User Name PcS2\HarryTime Zone GMT Daylight TimeInstalled Physical Memory (RAM) 16.0 GBTotal Physical Memory 15.5 GBAvailable Physical Memory 13.3 GBTotal Virtual Memory 31.0 GBAvailable Virtual Memory 28.6 GBPage File Space 15.5 GBPage File C:\pagefile.sys
- - -
I'm having the same problem, except that for me it seems to be working correctly on my 64 bit desktop (at least I haven't noticed any fonts misbehaving there yet), but not working on my 32 bit laptop where several fonts are showing only two of the four fonts on the group.
Does anyone know if Corel have acknowledged that this is actually a recognised problem and is going to get fixed.
harryLondon said:Perhaps as part of the fix you could add a "rebuild catalog" checkbox to the Find Fonts dialogue.
I think this is a good idea. I'll mention it but this is unlikely to happen because it require a lot more effort that you would think. (translation, quality assurance, ui design, etc...)
Just wondering if there was any news on this yet? I'm being driven nuts by constant font problems right now. I've tried Nexus but unfortunately we have an archive of about 60000 fonts and Nexus is painfully slow to start and to run as a result. If i could find another font management program that ran in a similar way to BFN (I.e., maintained a simple database of all fonts) with or without auto installation, i'd be buying it immediately.
I started a Corel Support case on this very soon after updating to X6. I got the runaround from their support - everything from uninstall and do a clean install through to 'it must be a problem with Windows - wipe it and start again'. Corel technicians knew about this problem, but the support staff had no idea. There is no fix yet, despite this being a problem with the previous version of Navigator and opentype fonts. Just a case of burying your head in the sand and hope it goes away. But hey, Corel now supports opentype ligatures - if you can get the font to show up!
I am currently using Nexus. It's not perfect and it is slow to start (especially with Illustrator). But at least it works. It is better than the paid alternatives as Suitcase is horrendous and Font Expert is so technical that it's impractical. It is a real pity as Font Navigator was an excellent program. It's origins go back to Font Minder - the original font management tool back in the days of Windows 3.11 and NT4. It didn't handle postscript fonts too well back then, but improved after it's reincarnation under Bitstream. Unfortunately it hasn't been updated since 2006 and now it has problems with opentype fonts and in some cases, truetype fonts. Postscript fonts work fine now.
My beef is why did Corel include it, knowing that there were problems with it? Just like the Barcode Generator which doesn't produce barcodes to GS1 (global standard) specifications. Then they include the web creator program, which is so far behind Dreamweaver that it is practically useless. The clipart supplied gets smaller with each version of CorelDraw and harder to find what you need. Perhaps the answer is for Corel to stick with what they were good at, get that right and then look at other areas.
As a user since version3, I am fairly familiar with Draw and am saddened at the decline in what was once a simple and usable program. Now they have tinkered with it - everything has to be 'interactive'. CorelTrace is now interactive trace and totally useless. Who wants a trace where you end up with art spread across 3000 layers? Extrude is almost unworkable and the emboss is in the dark ages. Corel was the leader in art creation, the best program for logo design. Now it comes a poor second to Illustrator.
unicorn said: it hasn't been updated since 2006
It hasn't been updated by bitstream since 2006, but that's not surprising as bitstream no longer exists as an entity. Its fonts now belong to Monotype but fontnav doesn't seem to be part of the transfer.
But the version distributed with CorelDraw has been updated (or, at the very least, recompiled) -- there are differences in file sizes in the versions distributed with X3 to X6. Those changes are obviously not yet enough to catch up with changes in windows and/or its libraries, but its good to see that Corel has recognised the problem and is working on it at last.
unicorn said:why did Corel include it, knowing that there were problems with it?
It actually works perfectly in XP 32 bit and probably in some other situations too. Corel may have known that some people had problems, but it seemed to be working for most others. It was not until Mike posted http://community.coreldraw.com/forums/t/33943.aspx and some of us were able to confirm that a problem existed. It was also total coincidence that I bought a new machine soon after which exhibited the same problem and hence this thread. But X6 had already been out several months then. Before that, it was not even certain that BFN was the cause. Certainly, Corel should have informed its hotline staff of the problem but I don't think there was enough known about the problem when X6 was released to consider excluding fontnav.
We did not. Sometimes, defects are only discovered once the app in in the field. I apologize for the inconveniences that it is causing you.