Facing challenges in ScriptShape(USP10.dll) Windows API in Windows 10

329 Views Asked by At
  1. Application under Test : Notepad
  2. Contents Typed in the Notepad : ABCD

Behavior observed in Windows environments :-

Windows 7/Windows 8.1 : In order to draw the text ABCD in notepad, the call gets into ScriptShape Windows API(USP10.dll) to generate Glpyhs, and then moves to ExtTextOut(GDI32.dll).

Windows 10 : In order to draw the text ABCD in notepad, calls enters into ExtTextOut(GDI32.dll) without going through ScriptShape Windows API(USP10.dll).

If we analyse the process dmp of notepad.exe then in case of Windows 7/Windows 8.1 USP10.dll is invoked whereas in case of Windows 10 the USP10.dll is never invoked, which implies that none of the ScriptShape related calls are getting triggered. So, my question is in case of Windows 10 where is it getting routed to ? Which dll is involved to generate the Glyph indices from Unicode character if USP10.dll is not involved ?

Any suggestion will help

0

There are 0 best solutions below