Does the interpreter named 'AutoHotkey.exe' now have unicode support? Topic is solved

[Gary-Atlan82]

I have installed V2, the following executables are now on available:

Code: Select all

C:\Program Files\AutoHotkey\v2\AutoHotkey.exe
C:\Program Files\AutoHotkey\v2\AutoHotkey64_UIA.exe
C:\Program Files\AutoHotkey\v2\AutoHotkey32_UIA.exe
C:\Program Files\AutoHotkey\v2\AutoHotkey.chm
C:\Program Files\AutoHotkey\v2\AutoHotkey32.exe
C:\Program Files\AutoHotkey\v2\AutoHotkey64.exe

coming from V1, I had to use the interpreter named AutoHotkeyU64.exe for unicode support rather than the one named AutoHotkey.exe. Is this still the case with V2?

I could try to test this myself but I am not sure how reliable my results may be, I also was no able to find anything mentioning this in the documentation.

I would appreciate any help on this.

[just me]

AHK v2 is Unicode-only!

[Gary-Atlan82]

@just me
I see, well that is a relief. Thanks!

But then I am wondering what are the other executables for? Isnt the "U" in "AutoHotkey64_UIA.exe" for "Unicode"?

[neogna2]

But then I am wondering what are the other executables for? Isnt the "U" in "AutoHotkey64_UIA.exe" for "Unicode"?

https://www.autohotkey.com/docs/v2/Program.htm#Installer_uiAccess

[gregster]

coming from V1, I had to use the interpreter named AutoHotkeyU64.exe for unicode support rather than the one named AutoHotkey.exe. Is this still the case with V2?

Afaik, the file AutoHotkey.exe was never a specific version but a copy of one of the other available exe-files. It all depended on what you chose when you installed AHK. If you chose the 32 bit ANSI version as default at installation, it was that one; if you chose 64 bit Unicode, it was a copy of AutoHotkeyU64.exe.
Now, with the new Launcher, autohotkey.exe is no longer an actual exe-file, but a symlink to one.

symlink.png (8.99 KiB) Viewed 197 times