diff options
| author | Alan Coopersmith <alan.coopersmith@sun.com> | 2009-10-22 23:21:07 -0700 |
|---|---|---|
| committer | Alan Coopersmith <alan.coopersmith@sun.com> | 2009-10-22 23:21:07 -0700 |
| commit | 7fb8d99c74fc122313323de177f20ed2601bbbd7 (patch) | |
| tree | f3cbd64f469226a1af84b09bde0ac3c6c04de37d | |
| parent | 2f53384c7b3f2bdde1be530ef213f413a9e87e02 (diff) | |
Move description of XFree86 4.4 compose changes to Compose man page in libX11
After 5 years, they no longer need to be called out as a new feature in
the release notes.
Signed-off-by: Alan Coopersmith <alan.coopersmith@sun.com>
| -rw-r--r-- | sgml/RELNOTES.sgml | 83 |
1 files changed, 0 insertions, 83 deletions
diff --git a/sgml/RELNOTES.sgml b/sgml/RELNOTES.sgml index 8da048d..7cad050 100644 --- a/sgml/RELNOTES.sgml +++ b/sgml/RELNOTES.sgml @@ -943,89 +943,6 @@ The next section describes what is new in the latest version </Para> </Sect2> - <Sect2 id="compose"> - <Title>Xlib Compose file support and extensions </Title> - - <Para> - A more flexible Compose file processing system was added to Xlib in - XFree86 4.4.0 and X11R6.7. The compose file is searched for in - the following order: - </Para> - - <Para> - <OrderedList> - <ListItem> - <Para> - If the environment variable <envar>$XCOMPOSEFILE</envar> - is set, its value is - used as the name of the Compose file. - </Para> - </ListItem> - <ListItem> - <Para> - If the user's home directory has a file named - "<filename>.XCompose</filename>", it is used as the Compose - file. - </Para> - </ListItem> - <ListItem> - <Para> - The old method is used, and the compose file is - "<<Emphasis remap="it">xlocaledir</Emphasis>><Literal - remap="tt">/</Literal><<Emphasis - remap="it">localename</Emphasis>><Literal - remap="tt">/Compose</Literal>". - </Para> - </ListItem> - </OrderedList> - </Para> - - <Para> - Compose files can now use an "include" instruction. This allows - local modifications to be made to existing compose files without - including all of the content directly. For example, the system's - iso8859-1 compose file can be included with a line like this: - - <Screen> - include "/usr/X11R6/lib/X11/locale/iso8859-1/Compose" - </Screen> - There are two substitutions that can be made in the file name of the - include instruction. <Emphasis remap="bf">%H</Emphasis> expands to the user's home directory - (the <Emphasis remap="bf">$HOME</Emphasis> environment variable), and <Emphasis remap="bf">%L</Emphasis> expands to the - name of the locale specific Compose file (i.e., - "<<Emphasis remap="it">xlocaledir</Emphasis>><Literal remap="tt">/</Literal><<Emphasis remap="it">localename</Emphasis>><Literal remap="tt">/Compose</Literal>"). - </Para> - - <Para> - For example, you can include in your compose file the default Compose file - by using: - - <Screen> - include "%L" - </Screen> - and then rewrite only the few rules that you need to change. New - compose rules can be added, and previous ones replaced. - </Para> - - <Para> - Finally, it is no longer necessary to specify in the right part of - a rule a locale encoded string in addition to the keysym name. If - the string is omitted, Xlib figures it out from the keysym - according to the current locale. I.e., if a rule looks like: - - <Screen> - <dead_grave> <A> : "\300" Agrave - </Screen> - the result of the composition is always the letter with the "\300" - code. But if the rule is: - - <Screen> - <dead_grave> <A> : Agrave - </Screen> - the result depends on how Agrave is mapped in the current locale. - </Para> - </Sect2> - <Sect2 id="luxi"> <Title>Luxi fonts from Bigelow and Holmes </Title> |