| … | |
… | |
| 226 | that doesn't work, you might be forced to use a different font. |
226 | that doesn't work, you might be forced to use a different font. |
| 227 | |
227 | |
| 228 | All of this is not a problem when using X11 core fonts, as their |
228 | All of this is not a problem when using X11 core fonts, as their |
| 229 | bounding box data is correct. |
229 | bounding box data is correct. |
| 230 | |
230 | |
|
|
231 | On Solaris 9, many line-drawing characters are too wide. |
|
|
232 | Seems to be a known bug, read |
|
|
233 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
234 | following ugly workaround to get non-double-wide-characters working: |
|
|
235 | |
|
|
236 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
|
|
237 | |
| 231 | My Compose (Multi_key) key is no longer working. |
238 | My Compose (Multi_key) key is no longer working. |
| 232 | The most common causes for this are that either your locale is not |
239 | The most common causes for this are that either your locale is not |
| 233 | set correctly, or you specified a preeditStyle that is not supported |
240 | set correctly, or you specified a preeditStyle that is not supported |
| 234 | by your input method. For example, if you specified OverTheSpot and |
241 | by your input method. For example, if you specified OverTheSpot and |
| 235 | your input method (e.g. the default input method handling Compose |
242 | your input method (e.g. the default input method handling Compose |
| … | |
… | |
| 279 | As you might have guessed, FreeBSD does neither define this symobl |
286 | As you might have guessed, FreeBSD does neither define this symobl |
| 280 | nor does it support it. Instead, it uses it's own internal |
287 | nor does it support it. Instead, it uses it's own internal |
| 281 | representation of wchar_t. This is, of course, completely fine with |
288 | representation of wchar_t. This is, of course, completely fine with |
| 282 | respect to standards. |
289 | respect to standards. |
| 283 | |
290 | |
|
|
291 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" |
|
|
292 | and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
|
|
293 | |
| 284 | However, "__STDC_ISO_10646__" is the only sane way to support |
294 | "__STDC_ISO_10646__" is the only sane way to support multi-language |
| 285 | multi-language apps in an OS, as using a locale-dependent (and |
295 | apps in an OS, as using a locale-dependent (and non-standardized) |
| 286 | non-standardized) representation of wchar_t makes it impossible to |
296 | representation of wchar_t makes it impossible to convert between |
| 287 | convert between wchar_t (as used by X11 and your applications) and |
297 | wchar_t (as used by X11 and your applications) and any other |
| 288 | any other encoding without implementing OS-specific-wrappers for |
298 | encoding without implementing OS-specific-wrappers for each and |
| 289 | each and every locale. There simply are no APIs to convert wchar_t |
299 | every locale. There simply are no APIs to convert wchar_t into |
| 290 | into anything except the current locale encoding. |
300 | anything except the current locale encoding. |
| 291 | |
301 | |
| 292 | Some applications (such as the formidable mlterm) work around this |
302 | Some applications (such as the formidable mlterm) work around this |
| 293 | by carrying their own replacement functions for character set |
303 | by carrying their own replacement functions for character set |
| 294 | handling with them, and either implementing OS-dependent hacks or |
304 | handling with them, and either implementing OS-dependent hacks or |
| 295 | doing multiple conversions (which is slow and unreliable in case the |
305 | doing multiple conversions (which is slow and unreliable in case the |
| … | |
… | |
| 297 | emulator). |
307 | emulator). |
| 298 | |
308 | |
| 299 | The rxvt-unicode author insists that the right way to fix this is in |
309 | The rxvt-unicode author insists that the right way to fix this is in |
| 300 | the system libraries once and for all, instead of forcing every app |
310 | the system libraries once and for all, instead of forcing every app |
| 301 | to carry complete replacements for them :) |
311 | to carry complete replacements for them :) |
|
|
312 | |
|
|
313 | I use Solaris 9 and it doesn't compile/work/etc. |
|
|
314 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
|
|
315 | problems with "wcwidth" and a compile problem. |
| 302 | |
316 | |
| 303 | How does rxvt-unicode determine the encoding to use? |
317 | How does rxvt-unicode determine the encoding to use? |
| 304 | Is there an option to switch encodings? |
318 | Is there an option to switch encodings? |
| 305 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
319 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
| 306 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
320 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
