In any case you should always finish a font-family declaration with 'serif' or 'sans-serif' in this situation. Then if none of the fonts you indicated are on the user's system, a font that they do have will be used.
Good point.
Lesson learned: I really shouldn't write heady stuff before sunrise and a fair serving of coffee.
What I had in mind was rather the case (admittedly rare, but happened to me) when a non-Unicode font has the same name as a Unicode one. The culprit in my case was Georgia with CE characters, back then when W2k was brand new. Made a website assuming every Georgia has the full set of Latin glyphs, while my customer had an Italian Win98 supplied with a Win-1252 Georgia... Still hate those empty squares.
Researching the user base is something I find iffy anyway. Every once in a while there is a thread trying to find a safe sequence of fonts usable both on Windows and MacOS, and it ends up with a boatload of different typefaces, plus assorted arguments about display details. Directly asking a vietnamese designer might be more straightforward.
Anyway, my suggestion should be more correctly amended to: 'use a generic font-family and let the browser help itself, rather than risk a miss trying to overdesign the appearance'.
djn
begin:vcard fn:Dejan Kozina n:Kozina;Dejan org:Dejan Kozina Web Design Studio adr:;;Dolina 346;Dolina;TS;I-34018;Italy email;internet:[EMAIL PROTECTED] tel;work:+39 348 7355 225 tel;fax:+39 040 228 436 tel;cell:+39 348 7355 225 x-mozilla-html:TRUE url:http://www.kozina.com/ version:2.1 end:vcard
