AutoHotkey Community

[JoeSchmoe]

Hi all,

In a script that I've been working on forever, I need a pair of characters that aren't typically used in strings, to use as delimeters and for marking special substrings. These characters would be used internally by the script to encode various things

My first thought is to use the ASCII BEL, BS, or EOT characters. For example, I might want to do

[[VxE]]

Yes, you can use characters like ñ and Ö as delimiters. AHK apparently uses the ansi code page internally, so any ansi character between 1 and 255 is ok with AHK.
_________________
Ternary (a ? b : c) guide     TSV Table Manipulation Library
Post code inside [code][/code] tags!

[JoeSchmoe]

Thanks!

I think I've settled on using ¬, «, », and § in my script for now.

So are ANSI encodings deep in AHK in such a way that I can be confident that commands will be pretty robust? Is anyone aware of any limitations involved with using the full set of ANSI characters in AHK? I'd hate to get pretty far into a project only to discover a key limitation that renders the basic design strategy impractical.

[YMP]

I am constantly using the full set, since cyrillic letters are mapped to the upper half of the ANSI codes. One problem with the upper codes is that they may denote different characters in different locales. In my locale, the default codepage is Windows-1251, not 1252, so my ANSI charset does not include, for example, German letters with umlauts because their codes are used for cyrillic characters. However, this is only a representation problem; AutoHotkey actually works not with characters as we see them on the screen but with character codes.

[JoeSchmoe]

Thanks, YMP. That's very helpful to know.