| 1 |
# There are problems with UTF-8 string literals under MSVC. |
| 2 |
# There appear to be two cases: |
| 3 |
# 1. It thinks our source file use the local file encoding. This mostly |
| 4 |
# works okay: the UTF-8 strings look like strings in an 8-bit charset and |
| 5 |
# will be passed through directly. But in other locales (e.g. East Asian) |
| 6 |
# it won't work. |
| 7 |
# 2. If we add a UTF-8 byte order mark (signature) then MSVC will recognise |
| 8 |
# the source file as UTF-8, but will then try to re-encode the strings |
| 9 |
# into the local charset. |
| 10 |
# So, unfortunately, for portability to MSVC, we have to externalise UTF-8 |
| 11 |
# strings or write them out using escape codes. |
| 12 |
|
| 13 |
symbols1=■□▢▣▤▥▦▧▨▩▪▫▬▭▮▯▰▱ |
| 14 |
symbols2=▲△▴▵▶▷▸▹►▻▼▽▾▿◀◁◂◃◄◅◆◇◈◉◊ |
| 15 |
symbols3=○◌◍◎●◐◑◒◓◔◕◖◗◘◙ |
| 16 |
substr1=«Thís»|you |
| 17 |
substr2=should|‘ìş’ |
| 18 |
substr3=not|“cøünt”|see |
| 19 |
substr4=réstrïçteđ…|this. |