| … | |
… | |
| 65 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
65 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
| 66 | :am:bw:eo:km:mi:ms:xn:xo:\ |
66 | :am:bw:eo:km:mi:ms:xn:xo:\ |
| 67 | :co#80:it#8:li#24:lm#0:\ |
67 | :co#80:it#8:li#24:lm#0:\ |
| 68 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
68 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
| 69 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
69 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
| 70 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ |
70 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
| 71 | :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ |
71 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
| 72 | :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ |
72 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
| 73 | :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ |
73 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
74 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
| 74 | :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
75 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
| 75 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
76 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
| 76 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
77 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
| 77 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
78 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
| 78 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
79 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
| 79 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
80 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
| … | |
… | |
| 225 | 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. |
| 226 | |
227 | |
| 227 | 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 |
| 228 | bounding box data is correct. |
229 | bounding box data is correct. |
| 229 | |
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 | |
| 230 | My Compose (Multi_key) key is no longer working. |
238 | My Compose (Multi_key) key is no longer working. |
| 231 | 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 |
| 232 | set correctly, or you specified a preeditStyle that is not supported |
240 | set correctly, or you specified a preeditStyle that is not supported |
| 233 | by your input method. For example, if you specified OverTheSpot and |
241 | by your input method. For example, if you specified OverTheSpot and |
| 234 | your input method (e.g. the default input method handling Compose |
242 | your input method (e.g. the default input method handling Compose |
| … | |
… | |
| 278 | As you might have guessed, FreeBSD does neither define this symobl |
286 | As you might have guessed, FreeBSD does neither define this symobl |
| 279 | 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 |
| 280 | representation of wchar_t. This is, of course, completely fine with |
288 | representation of wchar_t. This is, of course, completely fine with |
| 281 | respect to standards. |
289 | respect to standards. |
| 282 | |
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 | |
| 283 | However, "__STDC_ISO_10646__" is the only sane way to support |
294 | "__STDC_ISO_10646__" is the only sane way to support multi-language |
| 284 | 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) |
| 285 | non-standardized) representation of wchar_t makes it impossible to |
296 | representation of wchar_t makes it impossible to convert between |
| 286 | 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 |
| 287 | any other encoding without implementing OS-specific-wrappers for |
298 | encoding without implementing OS-specific-wrappers for each and |
| 288 | 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 |
| 289 | into anything except the current locale encoding. |
300 | anything except the current locale encoding. |
| 290 | |
301 | |
| 291 | Some applications (such as the formidable mlterm) work around this |
302 | Some applications (such as the formidable mlterm) work around this |
| 292 | by carrying their own replacement functions for character set |
303 | by carrying their own replacement functions for character set |
| 293 | handling with them, and either implementing OS-dependent hacks or |
304 | handling with them, and either implementing OS-dependent hacks or |
| 294 | doing multiple conversions (which is slow and unreliable in case the |
305 | doing multiple conversions (which is slow and unreliable in case the |
| … | |
… | |
| 296 | emulator). |
307 | emulator). |
| 297 | |
308 | |
| 298 | 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 |
| 299 | 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 |
| 300 | 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. |
| 301 | |
316 | |
| 302 | How does rxvt-unicode determine the encoding to use? |
317 | How does rxvt-unicode determine the encoding to use? |
| 303 | Is there an option to switch encodings? |
318 | Is there an option to switch encodings? |
| 304 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
319 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
| 305 | 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 |
