Creating a COM server will fail if path contains non-Latin letters
Original Reporter info from Mantis: Wallaby
-
Reporter name:
Original Reporter info from Mantis: Wallaby
- Reporter name:
Description:
In unit ComServ when a global TComServer object is initialised, it will fail if the current module's path contains non-Latin letters (and Windows default code page is set to English).
This would be because the ANSI version of GetModuleFileName is used. I suggest to replace that with GetModuleFileNameW for which I have attached a patch. This way an application that contains COM automation will fully support foreign characters in paths.
Mantis conversion info:
- Mantis ID: 38382
- Build: trunk
- Platform: Windows
- Version: 3.3.1
- Fixed in revision: 49245 (#f0cc698a)