Author: kwade
Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12145
Modified Files: package-notes.xml Log Message: Fixes for bz#159174, bz#159177, some whitespace cleanup came with the territory.
Index: package-notes.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- package-notes.xml 31 May 2005 01:09:54 -0000 1.13 +++ package-notes.xml 31 May 2005 23:17:45 -0000 1.14 @@ -551,90 +551,90 @@ version 12.2. </para> <variablelist> - <varlistentry> - <term>Filepath Changes</term> - <listitem> - <para> - The name and locations of some files in the - <filename>iiimf</filename> packages have changed. - </para> - <para> - The IIIMF server has been renamed from - <filename>/usr/sbin/htt</filename> to - <filename>/usr/bin/iiimd</filename>, and the XIM bridge - client renamed from <filename>httx</filename> to - <filename>iiimx</filename>. The - <filename>init.d</filename> script name has not changed: - it is still called <filename>iiim</filename>. All the - global system configuration files are now located under - <filename>/etc/iiim/</filename>. - </para> - <para> - Language Engine (LE) developers should note that LE - modules and their data now live under - <filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>, - while runtime data is stored under - <filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>. - </para> - <para> - For more information on the exact path and file location - changes, please refer to Fedora IIIMF FAQ: - </para> - <para> - <ulink - url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html%22%3Ehttp://www.fe...</ulink>. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Hotkeys</term> - <listitem> - <para> - Trigger keys, such as - <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> - used to activate Input Methods, are now configurable with - the command-line tool <command>iiimf-le-tools</command>. - This feature is only supported by GTK2 applications - currently. For other applications using XIM the trigger - key can be changed using an X resource. Refer to the - IIIMF FAQ at <ulink - url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html%22%3Ehttp://www.fe...</ulink> - for more details on how to change trigger hotkeys. - </para> - <para> - Note that the keyname refers to the X key symbol name. For - example, if you want to activate with - <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>, - you - need to specify '<Control>at' as the keyname not - '<Control>@'. - </para> - <para> - The per-user configuration of hotkeys does not work - currently with &SEL; in enforcing mode due to lack of - &SEL; policy. In this case, the hotkey can only be - changed in the system-wide configuration. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Qt Support</term> - <listitem> - <para> - A Qt immodule for <filename>iiimf</filename> is now - included. This immodule works but lacks a status - window and is considered experimental. Therefore, the default for Qt - applications is to continue using XIM for IIMF input. - </para> - <para> - If you wish to try the immodule in a Qt application, first - install the <filename>iiimf-qt</filename> package, start - the application, then click mouse button-3 in an input - area and select <guimenuitem>iiimqcf</guimenuitem> from - the <guisubmenu>Select Input Method</guisubmenu>' submenu. - </para> - </listitem> - </varlistentry> + <varlistentry> + <term>File Path Changes</term> + <listitem> + <para> + The names and locations of some files in the + <filename>iiimf</filename> packages have changed. + </para> + <para> + The IIIMF server has been renamed from + <filename>/usr/sbin/htt</filename> to + <filename>/usr/bin/iiimd</filename>, and the XIM bridge + client renamed from <filename>httx</filename> to + <filename>iiimx</filename>. The + <filename>init.d</filename> script name has not changed: + it is still called <filename>iiim</filename>. All the + global system configuration files are now located under + <filename>/etc/iiim/</filename>. + </para> + <para> + Language Engine (LE) developers should note that LE + modules and their data now live under + <filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>, + while runtime data is stored under + <filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>. + </para> + <para> + For more information on the exact path and file location + changes, please refer to Fedora IIIMF FAQ: + </para> + <para> + <ulink + url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html%22%3Ehttp://www.fe...</ulink>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Hotkeys</term> + <listitem> + <para> + Trigger keys, such as + <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> + used to activate Input Methods, are now configurable with + the command-line tool <command>iiimf-le-tools</command>. + This feature is only supported by GTK2 applications + currently. For other applications using XIM the trigger + key can be changed using an X resource. Refer to the + IIIMF FAQ at <ulink + url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html%22%3Ehttp://www.fe...</ulink> + for more details on how to change trigger hotkeys. + </para> + <para> + Note that the keyname refers to the X key symbol name. For + example, if you want to activate with + <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>, + you need to specify '<Control>at' as the keyname not + '<Control>@'. + </para> + <para> + The per-user configuration of hotkeys does not work + currently with &SEL; in enforcing mode due to lack of + &SEL; policy. In this case, the hotkey can only be + changed in the system-wide configuration. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Qt Support</term> + <listitem> + <para> + A Qt immodule for <filename>iiimf</filename> is now + included. This immodule works but lacks a status window + and is considered experimental. Therefore, the default + for Qt applications is to continue using XIM for IIMF + input. + </para> + <para> + If you wish to try the immodule in a Qt application, first + install the <filename>iiimf-qt</filename> package, start + the application, then click mouse button-3 in an input + area and select <guimenuitem>iiimqcf</guimenuitem> from + the <guisubmenu>Select Input Method</guisubmenu>' submenu. + </para> + </listitem> + </varlistentry> </variablelist> </section> </section>
docs-commits@lists.fedoraproject.org