|
From: Mihai N. on 15 May 2008 03:36 > As I mentioned to OP, we've found that MS Sans Serif is missing some > characters (Japanese specifically) on Win2K. We used to use MS Gothic UI, > but I don't really like that font. I find it difficult to find a font that > works for all cases. MS Gothic UI is the right font for Japanese. We don't have to like it, it is a native Japanese who can judge. -- Mihai Nita [Microsoft MVP, Visual C++] http://www.mihai-nita.net ------------------------------------------ Replace _year_ with _ to get the real email
From: Mihai N. on 15 May 2008 03:47 > The font specified is "MS Sans Serif", and when I pasted the 7/8 in > (copied from Character Map), all I got was a blot. I sugested "Microsoft Sans Serif", an OpenType font that is a completely different beast than "MS Sans Serif", a bitmap font. > But from what > you suggested, I should have seen the 7/8 symbol displayed, which I didn't. 7/8 shows ok in Vista with "Microsoft Sans Serif" and even "MS Sans Serif" (and probably XP, I need a reboot). The "magic" things makeing fonts work (mapping, substitution, linking, etc.) improved a lot from NT to 2000 to XP to Vista. What you say is probably true for 2000 or older. > However, the nature of the app is that whatever font the user has selected > is the font I want to use, so if the user is using wingdings, I will > display in wingdings, if the user > has selected Lucida Sans Console I will display in that font, etc. For dialogs? Looks a bit weird. In fact, on Vista the original application messes up the font in some dialogs and I end up with a bitmap font ("MS Sans Serif" ?) Give a try to my CharMapEx on your system. It shows in black the characters that are really in the font, and in red all the magic characters that Windows finds somewhere else. -- Mihai Nita [Microsoft MVP, Visual C++] http://www.mihai-nita.net ------------------------------------------ Replace _year_ with _ to get the real email
From: Mihai N. on 15 May 2008 03:54 > The sources for the Font Explorer can be downloaded from my site as part of > the Win32 book CD download. Got it. Tried to compile it and got 1 error (VS 2008) (some notification where MFC changed the handler signature). Commented the ON_WM_NCHITTEST line out and got a running application. The tried to compile it as Unicode and got 20 errors (VS 2008) After running it thru my tool I had 0 compilation errors. Fixed the use of sizeof in 2 places, and got a running Unicode application in 5 minutes. Not a thorrow job, definitely some more cleaning is required, but not bad. Not judging you application here, but my tool. I am currios to see how usefull it is to cut the big conversion work. If you ever get to try it, I would be greatfull for any feedback. -- Mihai Nita [Microsoft MVP, Visual C++] http://www.mihai-nita.net ------------------------------------------ Replace _year_ with _ to get the real email
From: Tom Serface on 15 May 2008 09:28 Yes, you're right of course. I may actually go back to that one since I have so many problems with the Microsoft Sans Serif font. I just hate to use a different font in one set of resources than in the others. It's more difficult to maintain that way. Tom "Mihai N." <nmihai_year_2000(a)yahoo.com> wrote in message news:Xns9AA0620F42FBMihaiN(a)207.46.248.16... >> As I mentioned to OP, we've found that MS Sans Serif is missing some >> characters (Japanese specifically) on Win2K. We used to use MS Gothic >> UI, >> but I don't really like that font. I find it difficult to find a font >> that >> works for all cases. > MS Gothic UI is the right font for Japanese. > We don't have to like it, it is a native Japanese who can judge. > > > -- > Mihai Nita [Microsoft MVP, Visual C++] > http://www.mihai-nita.net > ------------------------------------------ > Replace _year_ with _ to get the real email
From: Joseph M. Newcomer on 15 May 2008 12:03 See below... On Thu, 15 May 2008 00:47:16 -0700, "Mihai N." <nmihai_year_2000(a)yahoo.com> wrote: >> The font specified is "MS Sans Serif", and when I pasted the 7/8 in >> (copied from Character Map), all I got was a blot. > >I sugested "Microsoft Sans Serif", an OpenType font that is a completely >different beast than "MS Sans Serif", a bitmap font. *** Oops. Noted. *** > > >> But from what >> you suggested, I should have seen the 7/8 symbol displayed, which I didn't. > >7/8 shows ok in Vista with "Microsoft Sans Serif" and even "MS Sans Serif" >(and probably XP, I need a reboot). >The "magic" things makeing fonts work (mapping, substitution, linking, etc.) >improved a lot from NT to 2000 to XP to Vista. >What you say is probably true for 2000 or older. **** I was running XP SP2 two weeks ago when I discovered this. But since I had MS Sans Serif, that probably explains it all **** > > >> However, the nature of the app is that whatever font the user has selected >> is the font I want to use, so if the user is using wingdings, I will >> display in wingdings, if the user >> has selected Lucida Sans Console I will display in that font, etc. > >For dialogs? Looks a bit weird. In fact, on Vista the original application >messes up the font in some dialogs and I end up with a bitmap font >("MS Sans Serif" ?) **** No, only for specific edit controls in the dialog. **** > >Give a try to my CharMapEx on your system. >It shows in black the characters that are really in the font, and in red >all the magic characters that Windows finds somewhere else. **** Cool. Where can I find this? Also, I'd be interested in adding the code for this detection to my Font Explorer, so if it is available, and you give permission, I'd like to use it (I'll even add a credit line to you!) When I finish my current research paper (which is probably going to become a book, as it is now close to 200 pages!) I'm going to finish the port of the Font Explorer from VS4.2 and fix a lot of the klunkier aspects of the interface because I'd only been programming in MFC for a year when I wrote it. joe Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: Found: a really odd bug Next: Make button on the dialog currently selected programmatically |