|
Post by George on Jul 30, 2017 12:21:01 GMT -5
Hmmm, Both the Help file and the Web site that I'm looking at appear correct. e.g. they show characters X'02' X'03' X'04' x'05' as box drawing characters, while both Courier and Courier New do NOT have these characters. Why do you think they are showing Courier?
George
|
|
|
Post by George on Jul 31, 2017 13:55:50 GMT -5
OK, I tried creating the sample font displays again, and they sure don't come out very well. I have no idea how I managed to create those previous previews. As to why - Windows substitution etc. I have no idea. The fonts are enumerated and displayed by a standard Windows API to perform Font selection, I have no real control over what Windows actually does inside that 'black box'. But this only seems to happen with the DejaVuSans Mono font which you sent me. The font selection dialog doesn't even properly create the DejaVuSans Mono Bold name correctly, you have to manually add the Bold on to it. So maybe there's something not quite right with the way the font was built. Your knowledge of fonts etc. is far superior to mine. As well, I have no idea just what the DejaVu Sans Mono Bold font fully looks like, so I have no way to check whether what's loaded is indeed even correct. Below is a font display of the full 256 character set in three fonts, as I see them displayed. Maybe you know what the DejaVu font really should look like and tell me what's right/wrong. The images are in Raster 14, Courier New and DejaVu Sans Mono Bold. These were all created from screen snapshots of the SPFLite character display tool. It looks to me like the DejaVu font has just 'picked up' the 1st 32 characters from whatever previous font was loaded (in this case Courier). Just an observation. George
|
|
|
Post by George on Jul 31, 2017 16:15:38 GMT -5
All I request are SCREENFONTS and FIXEDPITCHONLY. I have not selected the NOFACESEL, NOSTYLESEL or NOSIZESEL options.
I don't see any others in the following that I could add to make a difference, unless you do.
%CF_SCREENFONTS = &H00000001& %CF_PRINTERFONTS = &H00000002& %CF_BOTH = %CF_SCREENFONTS OR %CF_PRINTERFONTS %CF_SHOWHELP = &H00000004& %CF_ENABLEHOOK = &H00000008& %CF_ENABLETEMPLATE = &H00000010& %CF_ENABLETEMPLATEHANDLE = &H00000020& %CF_INITTOLOGFONTSTRUCT = &H00000040& %CF_USESTYLE = &H00000080& %CF_EFFECTS = &H00000100& %CF_APPLY = &H00000200& #IF %WINVER >= &H0400 %CF_ANSIONLY = &H00000400& #ENDIF %CF_SCRIPTSONLY = %CF_ANSIONLY %CF_NOVECTORFONTS = &H00000800& %CF_NOOEMFONTS = %CF_NOVECTORFONTS %CF_NOSIMULATIONS = &H00001000& %CF_LIMITSIZE = &H00002000& %CF_FIXEDPITCHONLY = &H00004000& %CF_WYSIWYG = &H00008000& ' must also have CF_SCREENFONTS & CF_PRINTERFONTS %CF_FORCEFONTEXIST = &H00010000& %CF_SCALABLEONLY = &H00020000& %CF_TTONLY = &H00040000& %CF_NOFACESEL = &H00080000& %CF_NOSTYLESEL = &H00100000& %CF_NOSIZESEL = &H00200000& #IF %WINVER > &H0400 %CF_SELECTSCRIPT = &H00400000& %CF_NOSCRIPTSEL = &H00800000& %CF_NOVERTFONTS = &H01000000& #ENDIF ' %WINVER >= &H0400 #IF (%WINVER >= &H0601) %CF_INACTIVEFONTS = &H02000000& #ENDIF ' %WINVER >= &H0601
|
|
|
Post by George on Aug 1, 2017 12:00:38 GMT -5
Here's the DejaVu Sans Mono Book sample
|
|
|
Post by George on Aug 12, 2017 14:37:13 GMT -5
Sorry Robert, I have been missing your answer here for a few days. This is odd then. It still seems something must be not quite right with the font when it doesn't add the BOLD name correctly. Haven't seen that with any of the other fonts.
George
|
|
|
Post by George on Aug 14, 2017 11:40:57 GMT -5
I tried the program out. First it was saying the Deja fonts contained invalid font data and also were missing Registry items. I tried using it's 'Repair' options, but it didn't seem to do anything, I didn't get any messages, good or bad.
So I did the procedure for rebuilding the font cache, and now it no longer complains about invalid font data, but still says there's a problem with the registry. It says to re-boot, but I've now done that about 4 times, still nothing is better. I tried repairing other fonts it complains about, but nothing seems to happen for any of them. I'm running it as an administrator, so its not that.
Basically, it seems its 'repair' functions have no effect. I'm just leaving it at this point. I always thought the whole font area was a big morass that I didn't understand and should just stay away from.
George
|
|
|
Post by George on Aug 14, 2017 15:02:45 GMT -5
I had uninstalled and reinstalled previously - no effect.
George
|
|
|
Post by George on Aug 16, 2017 10:37:32 GMT -5
I tried it with WordPad and it seems to have no problem. I'll follow the code I use in the font selection, although it is odd that this font seems singled out to misfire.
George
|
|
|
Post by George on Aug 16, 2017 15:38:40 GMT -5
OK, there were several inconsistencies in handling the font selection related to the style operand (bold, etc). So I cleaned that up so that style is now 'remembered' separately, along with the name and pitch. Some things are better, but frankly the whole font area sucks! Once you try displaying a file with all 256 characters, a whole bunch of the fonts simply fail miserably since they don't have glyphs (is that the right word?) for all characters. I don't understand why so called fixed pitch fonts can't simply insert a normal width blank if they don't choose to implement a proper glyph, leaving it as null or whatever simply destroys its usefulness and it should NOT be called a fixed pitch font.
If you'd like a test copy to play with I can put it in our shared Dropbox folder.
George
|
|
|
Post by George on Aug 19, 2017 15:37:48 GMT -5
Robert: OK I just released a new version, so I won't bother with Dropbox. If you want to provide me with some 'correct' images for the sample font section please go ahead and ass them over. I'll get them swapped into the Doc. somehow before the next release.
I'm trying to tidy this all up since we're off on our 50th anniversary cruise in a few weeks and will be gone for about 6 weeks.
As my desktop countdown gadget says - 32 days to go!.
George
|
|
|
Post by George on Sept 4, 2017 10:27:32 GMT -5
Robert: Sorry for not answering, I did get it and update stuff. Can you send a BOLD version as well?
George
|
|
|
Post by George on Sept 7, 2017 12:37:02 GMT -5
OK, thanks. I'll drop that one into the doc as well. George
[Done]
|
|