| … | |
… | |
| 1150 | As you might have guessed, FreeBSD does neither define this symbol nor |
1150 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1151 | does it support it. Instead, it uses its own internal representation of |
1151 | does it support it. Instead, it uses its own internal representation of |
| 1152 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
1152 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
| 1153 | |
1153 | |
| 1154 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
1154 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
| 1155 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. |
1155 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>). |
| 1156 | |
1156 | |
| 1157 | C<__STDC_ISO_10646__> is the only sane way to support multi-language |
1157 | C<__STDC_ISO_10646__> is the only sane way to support multi-language |
| 1158 | apps in an OS, as using a locale-dependent (and non-standardized) |
1158 | apps in an OS, as using a locale-dependent (and non-standardized) |
| 1159 | representation of B<wchar_t> makes it impossible to convert between |
1159 | representation of B<wchar_t> makes it impossible to convert between |
| 1160 | B<wchar_t> (as used by X11 and your applications) and any other encoding |
1160 | B<wchar_t> (as used by X11 and your applications) and any other encoding |
