ok, so the LPK calls uniscribe. Do you feel we should implement the LPK
style of interface to gdi32? It seems needlessly cumbersome to me. The
LPK.dll interfaces seem to be undocumented but based on names should not
be to difficult to figure out.
-aric
Dmitry Timoshkov wrote:
Aric Stewart <a...@codeweavers.com> wrote:
I know this is not official MSDN documentation but this appears to
disagree with you. http://www.catch22.net/tuts/neatpad/11
It also makes sense to have all the complex script processing logic in
one place instead of spreading it out and duplicating it.
Bidi and reordering were supported by gdi32 before Uniscribe has been
introduced.
Accridong to http://msdn.microsoft.com/en-us/goglobal/bb688137.aspx
uniscribe is used by lpk.dll (language packs): "ExtTextOut can be used
to lay out multilingual Unicode text including complex scripts. There is
no need for you to do anything other than call ExtTextOut; it handles
everything for you."
Why do you say that Windows gdi32 does not use usp10? I do not see a
direct dependency but I have not traced inside to see if it is doing
LoadProcAddress or the like.
Inspecting strings in gdi32.dll should be enough.
