[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.1.pod

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.135 by ayin, Wed Aug 1 01:45:06 2007 UTC vs.
Revision 1.140 by sasha, Fri Oct 26 18:27:29 2007 UTC

 Unlike the original rxvt, B<rxvt-unicode> stores all text in Unicode
 internally. That means it can store and display most scripts in the
 world. Being a terminal emulator, however, some things are very difficult,
 especially cursive scripts such as arabic, vertically written scripts
 like mongolian or scripts requiring extremely complex combining rules,
-like tibetan or devenagari. Don't expect pretty output when using these
+like tibetan or devanagari. Don't expect pretty output when using these
 scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
 fine, though. A somewhat difficult case are right-to-left scripts, such
 as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms
 belong into the application, not the terminal emulator (too many things --
 such as cursor-movement while editing -- break otherwise), but that might
 =item B<-ss>|B<+ss>
 Turn on/off skip scrolling (allow multiple screens per refresh); resource B<skipScroll>.
-=item B<-ip>|B<+ip> | B<-tr>|B<+tr>
+=item B<-tr>|B<+tr>
-Turn on/off inheriting parent window's pixmap. Alternative form is
+Turn on/off illusion of a transparent window background. Obsolete form of it is
-B<-tr>; resource B<inheritPixmap>.
+B<-ip> and it should not be used anymore; resource B<transparent>.
-I<Please note that transparency of any kind if completely unsupported by
+I<Please note that old resource name of B<inheritPixmap> is obsolete and should be
-the author. Don't bug him with installation questions! Read the FAQ (man 7
+changed to B<transparent>. Backwards compatibility support for B<inheritPixmap> will
-@@RXVT_NAME@@)!>
+be phased out in future versions of rxvt!>
+I<Please address all transparency related issues to Sasha Vasko at
+sasha@aftercode.net. Read the FAQ (man 7 @@RXVT_NAME@@)!>
 =item B<-fade> I<number>
 Fade the text by the given percentage when focus is lost. Small values
 fade a little only, 100 completely replaces all colours by the fade
 is opaque black. resource B<fadeColor>.
 =item B<-tint> I<colour>
 Tint the transparent background pixmap with the given colour when
-transparency is enabled with B<-tr> or B<-ip>. This only works for
+transparency is enabled with B<-tr>. This only works for
 non-tiled backgrounds, currently. See also the B<-sh> option that can be
 used to brighten or darken the image in addition to tinting it.
 Please note that certain tint colours can be applied on the server-side,
 thus yielding performance gain of two orders of magnitude. These colours are:
 blue, red, green, cyan, magenta, yellow, and those close to them; resource
 at the same time as transparency - such pixmap will be blended over
 transparency image, using method specified. Supported values are :
 B<add>, B<alphablend>, B<allanon> - color values averaging, B<colorize>,
 B<darken>, B<diff>, B<dissipate>, B<hue>, B<lighten>, B<overlay>,
 B<saturate>, B<screen>, B<sub>, B<tint>, B<value>. The default is
-alpha-blending; resource I<blendType>.
+alpha-blending. Compile I<afterimage>; resource I<blendType>.
 =item B<-blr> I<HxV>
 Apply Gaussian Blur with the specified radii to the transparent
 background image. If single number is specified - both vertical and
 horizontal radii are considered to be the same. Setting one of the
 radii to 1 and another to a large number creates interesting effects
-on some backgrounds. Maximum radius value is 128; resource I<blurRadius>.
+on some backgrounds. Maximum radius value is 128. Compile I<afterimage>;
+resource I<blurRadius>.
 =item B<-bg> I<colour>
 Window background colour; resource B<background>.
 =item B<-lsp> I<number>
 Compile I<frills>: Lines (pixel height) to insert between each row of
 the display. Useful to work around font rendering problems; resource
-B<linespace>.
+B<lineSpace>.
 =item B<-tn> I<termname>
 This option specifies the name of the terminal type to be set in the
 B<TERM> environment variable. This terminal type must exist in the
 other blending type, specified with B<-blt "type"> option.
 [default 0x0+50+50]
 =item B<path:> I<path>
-Specify the colon-delimited search path for finding XPM files.
+Specify the colon-delimited search path for finding background image files.
 =item B<font:> I<fontlist>
 Select the fonts to be used. This is a comma separated list of font names
 that are checked in order when trying to find glyphs for characters. The
 =item B<termName:> I<termname>
 Specifies the terminal type name to be set in the B<TERM> environment
 variable; option B<-tn>.
-=item B<linespace:> I<number>
+=item B<lineSpace:> I<number>
 Specifies number of lines (pixel height) to insert between each row of
 the display [default 0]; option B<-lsp>.
 =item B<meta8:> I<boolean>
 searching keysym macros from B</usr/X11R6/include/X11/keysymdef.h> and
 omitting the prefix B<XK_>. Alternatively you can specify I<key> by its hex
 keysym value (B<0x0000 - 0xFFFF>). Note that the lookup of I<sym>s is not
 performed in an exact manner; however, the closest match is assured.
-I<string> may contain escape values (C<\a>: bell, C<\b>: backspace,
+I<string> may contain escape values (C<\n>: newline, C<\000>: octal
-C<\e>, C<\E>: escape, C<\n>: newline, C<\r>: carriage return, C<\t>: tab,
+number), see RESOURCES in C<man 7 X> for futher details.
-C<\000>: octal number) or verbatim control characters (C<^?>: delete,
-C<^@>: null, C<^A> ...) and may be enclosed with double quotes so that it
-can start or end with whitespace. B<This feature is deprecated and will
-be removed>.
-Please note that you need to double the C<\> in resource files, as
-Xlib itself does its own de-escaping (you can use C<\033> instead of
-C<\e> (and so on), which will work with both Xt and @@RXVT_NAME@@'s own
-processing).
 You can define a range of keysyms in one shot by providing a I<string>
 with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimiter `/'
 should be a character not used by the strings.
 resources or on the command line.
 =item B<COLORTERM>
 Either C<rxvt>, C<rxvt-xpm>, depending on whether @@RXVT_NAME@@ was
-compiled with XPM support, and optionally with the added extension
+compiled with background image support, and optionally with the added
-C<-mono> to indicate that rxvt-unicode runs on a monochrome screen.
+extension C<-mono> to indicate that rxvt-unicode runs on a monochrome
+screen.
 =item B<COLORFGBG>
 Set to a string of the form C<fg;bg> or C<fg;xpm;bg>, where C<fg> is
 the colour code used as default foreground/text colour (or the string
 C<default> to indicate that the default-colour escape sequence is to be
 used), C<bg> is the colour code used as default background colour (or the
 string C<default>), and C<xpm> is the string C<default> if @@RXVT_NAME@@
-was compiled with XPM support. Libraries like C<ncurses> and C<slang> can
+was compiled with background image support. Libraries like C<ncurses>
-(and do) use this information to optimize screen output.
+and C<slang> can (and do) use this information to optimize screen output.
 =item B<WINDOWID>
 Set to the (decimal) X Window ID of the @@RXVT_NAME@@ window (the toplevel
 window, which usually has subwindows for the scrollbar, the terminal

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.135 by ayin, Wed Aug 1 01:45:06 2007 UTC vs. Revision 1.140 by sasha, Fri Oct 26 18:27:29 2007 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.135 by ayin, Wed Aug 1 01:45:06 2007 UTC vs.
Revision 1.140 by sasha, Fri Oct 26 18:27:29 2007 UTC