Re: GetGlyphOutline API

For example I stored all strings in my document files as UTF-16 before
going
to unicode, in order to achieve a more consistent file format across
different program versions. So it converts its strings to WCHAR before
saving, and from WCHAR after reading. Thus, while my current release
version is not Unicode (and supports win98), it will read the files from
my development version which is Unicode (and will drop win98 support).

Options:
- go Unicode all the way, and use MSLU for Win 9x
- take a look at T2W/W2T for conversions that MUST be done (ie MIDI)


[One problem is that some of my best documentation
came with "fontographer" a good font editor which is unfortunately so
ancient (and apparently no longer under development) that Unicode did not
figure highly.]
Yes, it is a pitty that practically Fontographer died.
You might take a look at FontForge (http://fontforge.sourceforge.net/)
I did not try it, but seems decent enough.
And since all you probably need is adding Unicode cmaps (no glyph changes, no
nothing), might be jsut fines.
And if you try it, please share the experience, good or bad :-)


--
Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email
.

Relevant Pages

  • Re: TCHAR and buffer overflows
    ... This would be a problem if you hadn't defined UNICODE in your build. ... unsigned char *_mbsncpy(unsigned char *strDest, ... >> macro WCHAR was introduced to switch between ascii and unicode chars as ... > I think you mean TCHAR. ...
    (comp.security.misc)
  • Re: TCHAR and buffer overflows
    ... This would be a problem if you hadn't defined UNICODE in your build. ... unsigned char *_mbsncpy(unsigned char *strDest, ... >> macro WCHAR was introduced to switch between ascii and unicode chars as ... > I think you mean TCHAR. ...
    (comp.os.ms-windows.nt.admin.security)
  • TCHAR and buffer overflows
    ... > strncpy, strncat, etc don't eliminate buffer overflows; ... > macro WCHAR was introduced to switch between ascii and unicode chars as ...
    (comp.security.misc)
  • TCHAR and buffer overflows
    ... > strncpy, strncat, etc don't eliminate buffer overflows; ... > macro WCHAR was introduced to switch between ascii and unicode chars as ...
    (comp.os.ms-windows.nt.admin.security)
  • Re: eVC3 to eVC4 Build Issues
    ... >I've recently upgraded from eMbedded VC 3 to VC 4, primarily to gain support ... TCHAR and WCHAR are the same only if UNICODE is defined during ... UNICODE is defined, then you can get away with mixing ... >"Can't build MFC OLE projects using static MFC libraries." ...
    (microsoft.public.pocketpc.developer)