File: ex_ttf.ini

package info (click to toggle)
allegro5 2%3A5.2.10.1%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 10,820 kB
  • sloc: ansic: 109,795; cpp: 12,976; objc: 4,592; java: 2,845; python: 2,595; javascript: 1,238; sh: 1,008; makefile: 40; xml: 27; pascal: 24
file content (19 lines) | stat: -rw-r--r-- 957 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
# There are problems with UTF-8 string literals under MSVC.
# There appear to be two cases:
# 1. It thinks our source file use the local file encoding.  This mostly
#    works okay: the UTF-8 strings look like strings in an 8-bit charset and
#    will be passed through directly.  But in other locales (e.g. East Asian)
#    it won't work.
# 2. If we add a UTF-8 byte order mark (signature) then MSVC will recognise
#    the source file as UTF-8, but will then try to re-encode the strings
#    into the local charset.
# So, unfortunately, for portability to MSVC, we have to externalise UTF-8
# strings or write them out using escape codes.

symbols1=■□▢▣▤▥▦▧▨▩▪▫▬▭▮▯▰▱
symbols2=▲△▴▵▶▷▸▹►▻▼▽▾▿◀◁◂◃◄◅◆◇◈◉◊
symbols3=○◌◍◎●◐◑◒◓◔◕◖◗◘◙
substr1=«Thís»|you
substr2=should|‘ìş’
substr3=not|“cøünt”|see
substr4=réstrïçteđ…|this.