| Server IP : 182.53.201.61 / Your IP : 216.73.217.175 Web Server : Apache/2.2.15 (Fedora) System : Linux km10.dyndns.org 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov 7 21:25:57 EST 2009 i686 User : apache ( 48) PHP Version : 5.3.3 Disable Function : NONE MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/gnome/help/system-admin-guide/de/ |
Upload File : |
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
<!ENTITY gnomeversion "2.14">
<!ENTITY manrevision "2.4">
<!ENTITY date "March 2004">
<!ENTITY LEGAL SYSTEM "legal.xml">
<!ENTITY gconf SYSTEM "gconf.xml">
<!ENTITY menustructure SYSTEM "menustructure.xml">
<!ENTITY themes SYSTEM "themes.xml">
<!ENTITY fontconfig SYSTEM "fontconfig.xml">
<!ENTITY mimetypes SYSTEM "mimetypes.xml">
<!ENTITY screensavers SYSTEM "screensavers.xml">
<!ENTITY sessions SYSTEM "sessions.xml">
<!ENTITY help SYSTEM "help.xml">
<!ENTITY performance SYSTEM "performance.xml">
<!ENTITY lockdown SYSTEM "lockdown.xml">
<!ENTITY appendixa SYSTEM "appendixa.xml">
<!ENTITY appendixb SYSTEM "appendixb.xml">
<!ENTITY gloss SYSTEM "glossary.xml">
]>
<book id="index" lang="de">
<title>GNOME Desktop-Systemverwaltungshandbuch</title>
<bookinfo>
<abstract role="description">
<para>Das GNOME-Systemverwaltungshandbuch stellt Informationen für Systemverwalter bereit, die sich auf die Konfiguration und Verwaltung verschiedener Aspekte der Desktopumgebung für Benutzer beziehen.</para>
</abstract>
<copyright>
<year>2006</year>
<holder>Brent Smith</holder>
</copyright>
<copyright>
<year>2005</year>
<holder>Brent Smith</holder>
</copyright>
<copyright>
<year>2004</year>
<holder>Sun Microsystems</holder>
</copyright>
<copyright>
<year>2003</year>
<holder>Sun Microsystems</holder>
</copyright><copyright><year>2008, 2009</year><holder>Mario Blättermann (mariobl@gnome.org)</holder></copyright>
<!-- translators: uncomment this:
<copyright>
<year>2002</year>
<holder>ME-THE-TRANSLATOR (Latin translation)</holder>
</copyright>
-->
<publisher role="maintainer">
<publishername>GNOME-Dokumentationsprojekt</publishername>
</publisher> <legalnotice id="legalnotice">
<para>Das vorliegende Dokument kann gemäß den Bedingungen der GNU Free Documentation License (GFDL), Version 1.1 oder jeder späteren, von der Free Software Foundation veröffentlichten Version ohne unveränderbare Abschnitte sowie ohne Texte auf dem vorderen und hinteren Buchdeckel kopiert, verteilt und/oder modifiziert werden. Eine Kopie der GFDL finden Sie unter diesem <ulink type="help" url="ghelp:fdl">Link</ulink> oder in der mit diesem Handbuch gelieferten Datei COPYING-DOCS.</para>
<para>Dieses Handbuch ist Teil einer Sammlung von GNOME-Handbüchern, die unter der GFDL veröffentlicht werden. Wenn Sie dieses Handbuch getrennt von der Sammlung weiterverbreiten möchten, können Sie das tun, indem Sie eine Kopie der Lizenz zum Handbuch hinzufügen, wie es in Abschnitt 6 der Lizenz beschrieben ist.</para>
<para>Viele der Namen, die von Unternehmen verwendet werden, um ihre Produkte und Dienstleistungen von anderen zu unterscheiden, sind eingetragene Warenzeichen. An den Stellen, an denen diese Namen in einer GNOME-Dokumentation erscheinen, werden die Namen in Großbuchstaben oder mit einem großen Anfangsbuchstaben geschrieben, wenn das GNOME-Dokumentationsprojekt auf diese Warenzeichen hingewiesen wird.</para>
<para>DAS DOKUMENT UND VERÄNDERTE FASSUNGEN DES DOKUMENTS WERDEN UNTER DEN BEDINGUNGEN DER GNU FREE DOCUMENTATION LICENSE ZUR VERFÜGUNG GESTELLT MIT DEM WEITERGEHENDEN VERSTÄNDNIS, DASS: <orderedlist>
<listitem>
<para>DIESES DOKUMENT WIRD »WIE VORLIEGEND« GELIEFERT, OHNE GARANTIEN IRGENDEINER ART, SOWOHL AUSDRÜCKLICH GENANNTE ALS AUCH ANGEDEUTETE. DIES BEZIEHT SICH AUCH OHNE EINSCHRÄNKUNG AUF GARANTIEN, DASS DIESES DOKUMENT ODER VERÄNDERTE FASSUNGEN DIESES DOKUMENTS FREI VON HANDELSDEFEKTEN, FÜR EINEN BESTIMMTEN ZWECK GEEIGNET IST ODER DASS ES KEINE RECHTE DRITTER VERLETZT. DAS VOLLE RISIKO WAS QUALITÄT, GENAUIGKEIT UND LEISTUNG DES DOKUMENTS ODER VERÄNDERTE FASSUNGEN DES DOKUMENTS LIEGT BEI IHNEN. SOLLTE EIN DOKUMENT ODER EINE VERÄNDERTE FASSUNG DAVON FEHLER IRGENDEINER ART BEINHALTEN, TRAGEN SIE (NICHT DER URSPRUNGSAUTOR, DER AUTOR ODER EIN MITWIRKENDER) DIE KOSTEN FÜR NOTWENDIGE DIENSTLEISTUNGEN, REPARATUREN ODER FEHLERKORREKTUREN. DIESER HAFTUNGSAUSSCHLUSS IST EIN ESSENZIELLER TEIL DIESER LIZENZ. DIE VERWENDUNG EINES DOKUMENTS ODER EINER VERÄNDERTEN VERSION DES DOKUMENTS IST NICHT GESTATTET AUßER UNTER BEACHTUNG DIESES HAFTUNGSAUSSCHLUSSES UND</para>
</listitem>
<listitem>
<para>UNTER KEINEN UMSTÄNDEN UND AUF BASIS KEINER RECHTSGRUNDLAGE, EGAL OB DURCH UNERLAUBTEN HANDLUNGEN (EINSCHLIEßLICH FAHRLÄSSIGKEIT), VERTRAG ODER ANDERWEITIG KANN DER AUTOR, URSPRUNGSAUTOR, EIN MITWIRKENDER ODER EIN VERTRIEBSPARTNER DIESES DOKUMENTS ODER EINER VERÄNDERTEN FASSUNG DES DOKUMENTS ODER EIN ZULIEFERER EINER DIESER PARTEIEN, HAFTBAR GEMACHT WERDEN FÜR DIREKTE, INDIREKTE, SPEZIELLE, VERSEHENTLICHE ODER FOLGESCHÄDEN JEGLICHER ART, EINSCHLIEßLICH UND OHNE EINSCHRÄNKUNGEN SCHÄDEN DURCH VERLUST VON KULANZ, ARBEITSAUSFALL, COMPUTERVERSAGEN ODER COMPUTERFEHLFUNKTIONEN ODER ALLE ANDEREN SCHÄDEN ODER VERLUSTE, DIE SICH AUS ODER IN VERBINDUNG MIT DER VERWENDUNG DES DOKUMENTS UND VERÄNDERTER FASSUNGEN DES DOKUMENTS ERGEBEN, AUCH WENN DIE OBEN GENANNTEN PARTEIEN ÜBER DIE MÖGLICHKEIT SOLCHER SCHÄDEN INFORMIERT WAREN.</para>
</listitem>
</orderedlist></para>
</legalnotice>
<authorgroup>
<author>
<firstname>Brent</firstname>
<surname>Smith</surname>
<affiliation>
<orgname>GNOME-Dokumentationsprojekt</orgname>
</affiliation>
</author>
<author>
<firstname>Sun</firstname>
<surname>GNOME-Dokumentationsteam</surname>
<affiliation>
<orgname>Sun Microsystems</orgname>
</affiliation>
</author>
</authorgroup>
<revhistory>
<revision>
<revnumber>GNOME 2.14 Desktop-Systemverwaltungshandbuch V2.4</revnumber>
<date>März 2004</date>
<revdescription>
<para role="author">GNOME-Dokumentationsprojekt</para>
<para role="publisher">GNOME-Dokumentationsprojekt</para>
</revdescription>
</revision>
<revision>
<revnumber>GNOME 2.6 Desktop-Systemverwaltungshandbuch V2.3</revnumber>
<date>März 2004</date>
<revdescription>
<para role="author">Sun Microsystems</para>
<para role="publisher">GNOME-Dokumentationsprojekt</para>
</revdescription>
</revision>
<revision>
<revnumber>GNOME 2.4 Desktop-Systemverwaltungshandbuch V2.2</revnumber>
<date>September 2003</date>
<revdescription>
<para role="author">Sun Microsystems</para>
<para role="publisher">GNOME-Dokumentationsprojekt</para>
</revdescription>
</revision>
<revision>
<revnumber>GNOME 2.2 Desktop-Systemverwaltungshandbuch V2.4</revnumber>
<date>Januar 2003</date>
<revdescription>
<para role="author">Sun Microsystems</para>
<para role="publisher">GNOME-Dokumentationsprojekt</para>
</revdescription>
</revision>
<revision>
<revnumber>GNOME 2.0 Desktop-Systemverwaltungshandbuch V2.0</revnumber>
<date>Dezember 2002</date>
<revdescription>
<para role="author">Sun Microsystems</para>
<para role="publisher">GNOME-Dokumentationsprojekt</para>
</revdescription>
</revision>
</revhistory>
<releaseinfo>In diesem Handbuch wird die Version 2.14 des GNOME-Desktops beschrieben.</releaseinfo>
<legalnotice>
<title>Rückmeldungen</title>
<para>Wenn Sie Fehler finden oder Vorschläge zum GNOME-Desktop oder diesem Handbuch haben, folgen Sie den Anweisungen auf der <ulink url="ghelp:user-guide?feedback" type="help">GNOME-Seite für Rückmeldungen</ulink>.</para>
</legalnotice>
</bookinfo>
<chapter id="gconf-0">
<title>GConf verwenden</title>
<highlights>
<para>In diesem Kapitel wird beschrieben, wie Sie <application>GConf</application> zur Verwaltung der Benutzereinstellungen verwenden können.</para>
</highlights>
<sect1 id="gconf-1">
<title>Einführung in GConf</title>
<indexterm>
<primary>GConf</primary>
<secondary>Einführung</secondary>
</indexterm>
<para><application>GConf</application> vereinfacht die Verwaltung der Einstellungen der GNOME-Dsktopbenutzer. <application>GConf</application> ermöglicht den Systemverwaltern die Ausführung folgender Aufgaben:</para>
<itemizedlist>
<listitem>
<para>Setzen von obligatorischen Werten für bestimmte Einstellungen für alle Benutzer. Auf diese Weise können Systemverwalter festlegen, ob Benutzer bestimmte Einstellungen verändern dürfen.</para>
</listitem>
<listitem>
<para>Das Setzen von Standardwerten bestimmter Einstellungen für alle Benutzer.</para>
</listitem>
<listitem>
<para>Verwenden empfohlener Einstellungswerte, die in den Definitionsdateien der Einstellungen angegeben sind.</para>
</listitem>
<listitem>
<para>Lesen von Dokumentation für jede Einstellung.</para>
</listitem>
</itemizedlist>
<para><application>GConf</application> stellt auch Änderungen von Einstellungswerten fest, sowohl lokal als auch im Netzwerk. Auf diese Weise werden bei einer Änderung eines Einstellungswertes alle Anwendungen unmittelbar aktualisiert, die diese Einstellung verwenden.</para>
<para><application>GConf</application> umfasst die folgenden Komponenten:</para>
<itemizedlist>
<listitem>
<para>Eine Datenbank der Benutzereinstellungen</para>
</listitem>
<listitem>
<para>Ein Dienst, <command>gconfd-2</command>.</para>
</listitem>
<listitem>
<para>Ein Befehlszeilenwerkzeug, <command>gconftool-2</command>.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="gconf-24">
<title>GConf-Datenbank</title>
<indexterm>
<primary>GConf</primary>
<secondary>Datenbank</secondary>
</indexterm>
<para>Each preference in the <application>GConf</application> repository is
expressed as a key-value pair. A <firstterm>GConf preference key</firstterm>
is an element in the repository that corresponds to an application preference.
For example, the <systemitem>/apps/gnome-session/options/show_splash_screen</systemitem>
preference key corresponds to the <guilabel>Show splash screen on login</guilabel>
option in the <application>Sessions</application> preference tool. The GNOME
Desktop user interface does not contain all of the preference keys in the <application>GConf</application> repository. For example, the <application>Panel</application>
preference tool does not contain an option that corresponds to the <systemitem>/apps/panel/global/tooltips_enabled</systemitem> key.</para>
<para>Die Datenbank ist wie ein simples hierarchisches Dateisystem aufgebaut. Die Datenbank enthält Folgendes:</para>
<itemizedlist>
<listitem>
<para>Directories that correspond to applications that use the <application>GConf</application> repository. For example, the file system contains the
directory <systemitem>/apps/metacity</systemitem>. </para>
</listitem>
<listitem>
<para>Unterordner, die sich auf Einstellungskategorien beziehen. Beispielsweise enthält das Dateisystem den Ordner <systemitem>/apps/metacity/general</systemitem>.</para>
</listitem>
<listitem>
<para>Spezielle Dateien, die eine Liste der Einstellungsschlüssel im jeweiligen Ordner sowie Informationen über diese Schlüssel enthalten. Beispielsweise enthält eine solche Datei Informationen über die Schlüssel, die sich auf die HTTP-Proxy-Einstellungen im Ordner <systemitem>/system/http_proxy</systemitem> beziehen.</para>
</listitem>
<listitem>
<para>A <systemitem>/schemas</systemitem> directory that contains files
that describe all of the preference keys.</para>
</listitem>
</itemizedlist>
<para>Preference keys typically have simple values such as strings, integers,
or lists of strings and integers. The format of the preference key in the
repository depends on the backend module that is used to read the repository.
The following is an example of the <systemitem>/desktop/gnome/interface/font_name</systemitem> preference key when an Extensible Markup Language (XML) backend
module is used to read the repository:</para>
<programlisting><![CDATA[<entry name="font_name" mtime="1038323555" muser="user123" type="string">
<stringvalue>Sans 10</stringvalue></entry>]]></programlisting>
<note>
<para>When this guide refers to a preference key, the path to the key
is added to the name of the key. For example, the <systemitem>font_name</systemitem>
preference key in the <systemitem>/desktop/gnome/interface</systemitem> subdirectory
is referred to as <systemitem>/desktop/gnome/interface/font_name</systemitem>.</para>
</note>
<sect2 id="gconf-26">
<title>GConf-Konfigurationsquellen</title>
<indexterm>
<primary>GConf</primary>
<secondary>Konfigurationsquellen</secondary>
</indexterm>
<para>The <application>GConf</application> repository contains
a series of storage locations that are called <firstterm>configuration sources</firstterm>. The configuration sources are listed in the <firstterm>GConf
path file</firstterm>. The location of the <application>GConf</application>
path file is <systemitem>/etc/gconf/<replaceable>gconf-version-number</replaceable>/path</systemitem>. Each user has a path file. The path file specifies the following
information for each configuration source:</para>
<itemizedlist>
<listitem>
<para>Das Backend-Modul zum Lesen der Datenbank.</para>
</listitem>
<listitem>
<para>Die Zugriffsrechte der Datenbank.</para>
</listitem>
<listitem>
<para>Der Speicherort der Datenbank.</para>
</listitem>
</itemizedlist>
<para>Die <application>GConf</application>-Pfaddatei enthält auch <systemitem>include</systemitem>-Anweisungen. Per Vorgabe sieht der Inhalt der <application>GConf</application>-Pfaddatei wie folgt aus:</para>
<programlisting>xml:readonly:/etc/gconf/gconf.xml.mandatory
include /etc/gconf/2/local-mandatory.path
include "$(HOME)/.gconf.path"
include /etc/gconf/2/local-defaults.path
xml:readwrite:$(HOME)/.gconf
xml:readonly:/etc/gconf/gconf.xml.defaults</programlisting>
<para>Wenn <application>GConf</application> nach einem Einstellungswert sucht, dann liest <application>GConf</application> die Konfigurationsquellen anhand der in der Pfaddatei vorgegebenen Reihenfolge aus. Die folgende Tabelle beschreibt die Konfigurationsquellen der Pfaddatei:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="31.29*"/>
<colspec colwidth="68.71*"/>
<thead>
<row rowsep="1">
<entry>
<para>Konfigurationsquelle</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>Obligatorisch</para>
</entry>
<entry valign="top">
<para>Die Zugriffsrechte dieser Konfigurationsquelle sind auf »Nur lesen« gesetzt. Benutzer können die Werte in dieser Quelle nicht überschreiben, so dass die Einstellungen in dieser Quelle obligatorisch sind.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>Benutzer</para>
</entry>
<entry valign="top">
<para>Die Konfigurationsquelle wird im Ordner <filename>.gconf</filename> im persönlichen Ordner des Benutzers gespeichert. Wenn der Benutzer Einstellungen ändert, dann wird die neue Einstellungsinformation zu diesem Ort hinzugefügt.</para>
<para>Sie können den <application>Konfigurationseditor</application> zum Anpassen der Konfigurationsquelle des Benutzers verwenden.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>Standard</para>
</entry>
<entry valign="top">
<para>Diese Konfigurationsquelle enthält die vorgegebenen Einstellungen.</para>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>Die Anordnung der Konfigurationsquellen in der Pfaddatei stellt sicher, dass obligatorische Einstellungen die benutzerdefinierten Einstellungen überschreiben. Außerdem wird sichergestellt, dass benutzerdefinierte Einstellungen die vorgegebenen Einstellungen überschreiben. Daher wendet <application>GConf</application> die Einstellungen in folgender Reihenfolge der Priorität an:</para>
<orderedlist>
<listitem>
<para>Obligatorische Einstellungen</para>
</listitem>
<listitem>
<para>Benutzerdefinierte Einstellungen</para>
</listitem>
<listitem>
<para>Standardeinstellungen</para>
</listitem>
</orderedlist>
<para>Die <systemitem>include</systemitem>-Anweisungen in der <application>GConf</application>-Pfaddatei ermöglichen Systemverwaltern, weitere Konfigurationsquellen anzugeben.</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="50*"/>
<colspec colwidth="50*"/>
<thead>
<row rowsep="1">
<entry>
<para>Included Configuration Source</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>
<filename>/etc/gconf/2/local-mandatory.path</filename>
</para>
</entry>
<entry valign="top">
<para>Verwenden Sie diese Konfigurationsquelle zum Speichern obligatorischer Einstellungswerte für ein bestimmtes System.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>$(HOME)/.gconf.path</filename>
</para>
</entry>
<entry valign="top">
<para>The user specifies the location of the configuration
source in the home directory, in a file that is called <filename>.gconf.path</filename>.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>/etc/gconf/2/local-defaults.path</filename>
</para>
</entry>
<entry valign="top">
<para>Verwenden Sie diese Konfigurationsquelle zum Speichern vorgegebener Einstellungswerte für ein bestimmtes System.</para>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect2>
<sect2 id="gconf-27">
<title>GConf-Schemas</title>
<indexterm>
<primary>GConf</primary>
<secondary>schemas</secondary>
</indexterm>
<indexterm>
<primary>GConf</primary>
<secondary>Schema-Schlüssel</secondary>
</indexterm>
<indexterm>
<primary>GConf</primary>
<secondary>Schema-Objekte</secondary>
</indexterm>
<indexterm>
<primary>schemas</primary>
<secondary>Beschreibung</secondary>
</indexterm>
<indexterm>
<primary>schemas</primary>
<secondary>Schema-Schlüssel</secondary>
</indexterm>
<indexterm>
<primary>schemas</primary>
<secondary>Schema-Objekte</secondary>
</indexterm>
<para>Ein <firstterm>GConf-Schema</firstterm> ist ein Sammelbegriff für einen <firstterm>GConf-Schema-Schlüssel</firstterm> und ein <firstterm>GConf-Schema-Objekt</firstterm>. Die folgende Tabelle beschreibt Schema-Schlüssel und Schema-Objekte und stellt diese zu den Einstellungschlüsseln in Beziehung:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec0" colwidth="24.31*"/>
<colspec colname="colspec1" colwidth="75.69*"/>
<thead>
<row rowsep="1">
<entry>
<para>Eintrag</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry colname="colspec0" valign="top">
<para>Einstellungsschlüssel</para>
</entry>
<entry colname="colspec1" valign="top">
<para>An element in the <application>GConf</application> repository that corresponds to an application preference.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>Schema-Schlüssel</para>
</entry>
<entry valign="top">
<para>A key that stores a schema object for a preference key. </para>
</entry>
</row>
<row>
<entry valign="top">
<para>Schema-Objekt</para>
</entry>
<entry valign="top">
<para>Ein Element einer Konfigurationsquelle, welches Informationen über einen Einstellungsschlüssel enthält, wie die folgenden:</para>
<itemizedlist>
<listitem>
<para>Der Name der Anwendung, welche den Einstellungsschlüssel verwendet.</para>
</listitem>
<listitem>
<para>Der Typ des für den Einstellungsschlüssel erforderlichen Wertes, z. B. Integer, Boolean, usw.</para>
</listitem>
<listitem>
<para>Ein Vorgabewert für den Einstellungsschlüssel.</para>
</listitem>
<listitem>
<para>Kurze Dokumentation des Einstellungsschlüssels.</para>
</listitem>
</itemizedlist>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>In der folgenden Tabelle finden Sie Beispiele für einen Einstellungsschlüssel, einen Schema-Schlüssel und ein Schema-Objekt:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec0" colwidth="24.31*"/>
<colspec colname="colspec1" colwidth="75.69*"/>
<thead>
<row rowsep="1">
<entry>
<para>Eintrag</para>
</entry>
<entry>
<para>Beispiel</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry colname="colspec0" valign="top">
<para>Einstellungsschlüssel</para>
</entry>
<entry colname="colspec1" valign="top">
<para>
<systemitem>/desktop/gnome/interface/font_name</systemitem>
</para>
</entry>
</row>
<row>
<entry colname="colspec0" valign="top">
<para>Schema-Schlüssel</para>
</entry>
<entry colname="colspec1" valign="top">
<para>
<systemitem>/schemas/desktop/gnome/interface/font_name</systemitem>
</para>
</entry>
</row>
<row>
<entry valign="top">
<para>Schema-Objekt</para>
</entry>
<entry valign="top">
<programlisting><![CDATA[<schema>
<applyto>/desktop/gnome/interface/font_name</applyto>
<key>/schemas/desktop/gnome/interface/font_name</key>
<owner>gnome</owner>
<type>string</type>
<default>Sans 10</default>
<locale name="C">
<short>Default font</short>
<long>Name of the default font used by gtk+.</long>
</locale>
</schema>]]></programlisting>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>You can associate a schema key with a preference key. For example, the
following <systemitem>/desktop/gnome/interface/font_name</systemitem> key includes
a schema key:</para>
<programlisting><![CDATA[<entry name="font_name" mtime="1034873859"
schema="/schemas/desktop/gnome/interface/font_name"/>]]></programlisting>
<para>When you associate a schema key with a preference key, the preference
uses the suggested value that is specified in the schema object of the schema
key. The suggested value is contained in the <sgmltag><default></sgmltag>
element in the schema object. By default, all the preference keys in the default
configuration source are associated with schema keys.</para>
<para>Typischerweise werden Schemata in der vorgegebenen Konfigurationsquelle gespeichert.</para>
</sect2>
<sect2 id="gconf-2">
<title>GConf-Schema-Definitionsdateien</title>
<indexterm>
<primary>GConf</primary>
<secondary>Schema-Definitionsdateien</secondary>
<tertiary>Einführung</tertiary>
</indexterm>
<indexterm>
<primary>schemas</primary>
<secondary>Schema-Definitionsdateien</secondary>
<tertiary>Einführung</tertiary>
</indexterm>
<para>Schemas are generated from <firstterm>schema definition
files</firstterm>. A schema definition file defines the characteristics of
all of the keys in a particular application. Schema definition files have
a <filename>.schemas</filename> extension.</para>
<para>The schema definition files are included in the <filename>/etc/gconf/schemas</filename> directory. You can use the schema definition files to create a
new configuration source.</para>
<para>Some schema definition files correspond closely to a part of the GNOME
Desktop user interface. For example, <filename>system_http_proxy.schemas</filename>
corresponds to the <application>Network Proxy</application> preference tool. Other schema definition files contain
preference keys that are not present in the GNOME Desktop user interface.
For example, the <systemitem>/apps/panel/global/tooltips_enabled</systemitem> key
is not present in the user interface. </para>
<para>Some parts of the GNOME Desktop user interface contain preferences that
represent preference keys from more than one schema definition file. For example,
the <application>Keyboard Shortcuts</application> preference tool contains preferences that represent
keys from the <filename>panel-global-config.schemas</filename> and <filename>metacity.schemas</filename> files.</para>
</sect2>
</sect1>
<sect1 id="gconf-25">
<title>GConf-Dienst</title>
<indexterm>
<primary>gconfd</primary>
<see>GConf-Dienst</see>
</indexterm>
<indexterm>
<primary>GConf</primary>
<secondary>Dienst</secondary>
</indexterm>
<para>The <application>GConf</application> daemon is called <command>gconfd-2</command>. The <application>GConf</application> daemon notifies applications when a preference value changes.
For example, you might select to show only icons in toolbars in the <application>Menus & Toolbars</application> preference tool. When you select this option
in the preference tool, the toolbars on all open applications are updated
instantly. The <application>GConf</application> daemon can operate locally,
or across a network.</para>
<para>An instance of the <application>GConf</application> daemon is started
for each user. The <application>GConf</application> daemon does not have to
deal with complex problems such as authentication and data security. When
the <application>GConf</application> daemon starts, the daemon loads the <application>GConf</application> path file. The <application>GConf</application> daemon
manages all access between applications and the configuration sources.</para>
<para>Wenn eine Anwendung den Wert eines Einstellungsschlüssels erfragt, dann durchsucht der Dienst die Konfigurationsquellen wie folgt:</para>
<orderedlist>
<listitem>
<para>Search for the value of the preference key in each configuration
source, in the order specified in the path file. If the value is found, return
the value.</para>
</listitem>
<listitem>
<para>If a value is not found, search for the schema key that corresponds
to the preference key in each configuration source, in the order specified
in the path file.</para>
</listitem>
<listitem>
<para>If the schema key is found, check the value of the schema
key.</para>
</listitem>
<listitem>
<para>If the value of the schema key is a schema object, return
the suggested value in the <sgmltag><default></sgmltag> element of the
schema object.</para>
</listitem>
</orderedlist>
<para>The <application>GConf</application> daemon also caches preference key
values. All applications use this cache, so applications only need to access
the configuration sources once.</para>
<para>Um den <application>GConf</application>-Dienst zu beenden, führen Sie den folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 --shutdown</userinput></screen>
</sect1>
<sect1 id="gconf-6">
<title>GConf-Befehlszeilenwerkzeug</title>
<anchor id="gconf-TBL-7"/>
<indexterm>
<primary>gconftool-2</primary>
<see>GConf-Befehlszeilenwerkzeug</see>
</indexterm>
<indexterm>
<primary>GConf</primary>
<secondary>Befehlszeilenwerkzeug</secondary>
</indexterm>
<para><application>GConf</application> enthält ein Befehlszeilenwerkzeug namens <command>gconftool-2</command>. Sie können den Befehl <command>gconftool-2</command> zur Erledigung folgender Aufgaben verwenden:</para>
<itemizedlist>
<listitem>
<para>Legt den Wert des Schlüssels fest.</para>
</listitem>
<listitem>
<para>Display the values of keys.</para>
</listitem>
<listitem>
<para>Install schemas from schema definition files when you install
an application.</para>
</listitem>
</itemizedlist>
<para>Beispielsweise verwenden Sie folgenden Befehl, um die Werte aller Schlüssel im Ordner <systemitem>/desktop/gnome</systemitem> und dessen Unterordnern anzuzeigen.</para>
<screen><userinput>gconftool-2 --recursive-list /desktop/gnome</userinput></screen>
<para>Below are listed some of the options that you can
use with the <command>gconftool-2</command> command. For detailed command line options,
please see <ulink url="man:gconftool-2(1)">man:gconftool-2(1)</ulink>.</para>
<variablelist>
<title>Befehlszeilenoptionen für gconftool-2</title>
<varlistentry>
<term>
<option>--all-dirs</option>
</term>
<listitem>
<para>Listet alle in einem von Ihnen angegebenen Ordner enthaltenen Unterordner auf.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--all-entries</option>
</term>
<listitem>
<para>Zeigt die Werte aller in einem von Ihnen angegebenen Ordner enthaltenen Schlüssel an.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--config-source=<replaceable>configuration-source</replaceable></option>
</term>
<listitem>
<para>Use this option with the <option>--direct</option> option
to specify a configuration source to use. If you do not specify a configuration
source with this option, the command runs on all configuration sources in
the path file.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--direct</option>
</term>
<listitem>
<para>Use this option with the <option>--config-source</option> option to access a configuration source directly.
When you use this option, <application>GConf</application> bypasses the server.
Ensure that the <application>GConf</application> daemon, <command>gconfd-2</command>, is not running before you use this option.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--dump</option>
</term>
<listitem>
<para>Generates a list that contains all preference
keys in a <application>GConf</application> repository directory that you specify.
The list contains XML descriptions of all the keys. The list is contained
in a <sgmltag><gconfentryfile></sgmltag> element. </para>
<para>For example,
you can redirect the output from this option to generate a file that lists
all keys that are related to your panel configuration. You can use the <option>--load</option> option with this file.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--get</option>
</term>
<listitem>
<para>Displays the value of a preference key that you specify.
Also displays the values of the elements in the schema object for a schema
key that you specify.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--help</option>
</term>
<listitem>
<para>Displays a help message about the <command>gconftool-2</command> command, and the options that you can use with the <command>gconftool-2</command> command.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--load=<replaceable>Dateiname</replaceable></option>
</term>
<listitem>
<para>Use this option to sets the values of preference keys in the current directory
in a configuration source to the values in the file that you specify. The
file that you specify must contain XML descriptions of the keys, in a <literal><gconfentryfile></literal> element.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--long-desc=<replaceable>Beschreibung</replaceable></option>
</term>
<listitem>
<para>Use this option with the <option>--set-schema</option>
option to specify a long description for a schema key. </para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--makefile-install-rule</option>
</term>
<listitem>
<para>Installs schema definition files to applications.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--owner=<replaceable>Eigentümer</replaceable></option>
</term>
<listitem>
<para>Use this option with the <option>--set-schema</option> option to specify
an owner for a schema key. </para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--recursive-list</option>
</term>
<listitem>
<para>Displays the values of all preference keys in all
subdirectories in a directory that you specify.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--recursive-unset</option>
</term>
<listitem>
<para>Resets
the values of all preference keys, in all subdirectories in a directory, from
the user setting to the setting in the default configuration source.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--set</option>
</term>
<listitem>
<para>Sets the value of a preference key, and writes the value
to the user configuration source. Use the <option>--type</option> option
with the <option>--set</option> option to specify the data type of the value
that you want to set. For example, the following command sets the value of
the <systemitem>/apps/gnome-terminal/profiles/Default/background_color</systemitem>
key in the user configuration source:</para>
<screen><userinput>gconftool-2 \
--set "/apps/gnome-terminal/profiles/Default/background_color" \
--type string "#000000"</userinput></screen>
<para>You can also use the <option>--direct</option> option and the <option>--config-source</option> option
with the <option>--set</option> option to write a value to another configuration
source.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--set-schema</option>
</term>
<listitem>
<para>Sets the value of an attribute
in a schema key, and writes the value to the default configuration source.</para>
<para>Use the following options with the <option>--set-schema</option>
option to specify the attribute that you want to update:</para>
<itemizedlist>
<listitem>
<para>
<option>--type</option>
</para>
</listitem>
<listitem>
<para>
<option>--short-desc</option>
</para>
</listitem>
<listitem>
<para>
<option>--long-desc</option>
</para>
</listitem>
<listitem>
<para>
<option>--owner</option>
</para>
</listitem>
</itemizedlist>
<para>For example, the following command sets the short description
in the schema key for the <systemitem>/apps/gnome-terminal/profiles/Default/background_color</systemitem> key:</para>
<screen><userinput>gconftool-2 \
--set-schema "/schemas/apps/gnome-terminal/profiles/Default/background_color" \
--short-desc "Default background color of terminal"</userinput></screen>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--short-desc=<replaceable>Beschreibung</replaceable></option>
</term>
<listitem>
<para>Use this option with the <option>--set-schema</option>
option to specify a short description for a schema key. </para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--shutdown</option>
</term>
<listitem>
<para>Beendet den <application>GConf</application>-Dienst.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--type=<replaceable>Datentyp</replaceable></option>
</term>
<listitem>
<para>Use this option to specify the data type when you set a
value of a preference key. You can also use this option when you set the value
of an attribute in a schema key. The following is a list of valid data types:</para>
<itemizedlist>
<listitem>
<para>
<type>bool</type>
</para>
</listitem>
<listitem>
<para>
<type>float</type>
</para>
</listitem>
<listitem>
<para>
<type>int</type>
</para>
</listitem>
<listitem>
<para>
<type>list</type>
</para>
</listitem>
<listitem>
<para>
<type>pair</type>
</para>
</listitem>
<listitem>
<para>
<type>string</type>
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--unset</option>
</term>
<listitem>
<para>Resets the value of a preference
key from the user setting to the setting in the default configuration source.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--usage</option>
</term>
<listitem>
<para>Displays a brief help message
about the <command>gconftool-2</command> command, and the options that you
can use with the <command>gconftool-2</command> command.</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="gconf-7">
<title>Festlegen von Einstellungswerten</title>
<indexterm>
<primary>GConf</primary>
<secondary>Einstellungswerte setzen</secondary>
</indexterm>
<indexterm>
<primary>Einstellungswerte</primary>
<secondary>Einstellungen mit GConf</secondary>
</indexterm>
<para>You can set a mandatory value or a
default value for a preference key. Before you change mandatory preference
values or default preference values for users, you must ensure that the <application>GConf</application> daemon is not running for any user. Ensure that all users
are logged out before you change preference values for users.</para>
<para>To set a mandatory value or a default value for a preference key, use
the <command>gconftool-2</command> command, as follows:</para>
<screen><userinput>gconftool-2 --direct \
--config-source <replaceable>configuration-source</replaceable> \
--type <replaceable>Datentyp</replaceable> \
--set <replaceable>Einstellungsschlüssel</replaceable> <replaceable>Wert</replaceable></userinput></screen>
<para>For example, to set <literal>wwwproxy.xyz.com</literal> as the mandatory
HTTP proxy host, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type string \
--set /system/http_proxy/host wwwproxy.xyz.com</userinput></screen>
<para>Der Benutzer kann diesen Einstellungswert nicht überschreiben.</para>
<para>Zum Setzen der Standardwerte können Sie auch den Befehl <command>gconftool-2</command> verwenden. Wenn Sie beispielsweise die Anzahl der Arbeitsflächen auf 5 setzen wollen, führen Sie den folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type int \
--set /apps/metacity/general/num_workspaces 5</userinput></screen>
<para>Der Benutzer kann diesen Einstellungswert überschreiben.</para>
<caution>
<para>Before you change mandatory preference values or default preference
values for users, you must ensure that all users are logged out.</para>
</caution>
</sect1>
<sect1 id="gconf-8">
<title>Konfigurieren allgemeiner Einstellungen</title>
<para>Der folgende Abschnitt beschreibt, wie obligatorische oder vorgegebenen Werte den allgemeinen Einstellungen zugeordnet werden können.</para>
<sect2 id="gconf-10">
<title>HTTP-Proxy-Einstellungen</title>
<indexterm>
<primary>GConf</primary>
<secondary>HTTP-Proxy-Einstellungen</secondary>
</indexterm>
<indexterm>
<primary>HTTP-Proxy</primary>
<secondary>Einstellungen mit GConf</secondary>
</indexterm>
<para>To set HTTP proxy preferences, you modify
the values of the preference keys in the <systemitem>/system/http_proxy/</systemitem>
location. For example, to set a mandatory value for the HTTP proxy host, run
the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type string \
--set /system/http_proxy/host <replaceable>proxy-name</replaceable></userinput></screen>
<para>To set a default value for the HTTP proxy host, run the following command: </para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type string \
--set /system/http_proxy/host <replaceable>proxy-name</replaceable></userinput></screen>
<para>You can also set other HTTP proxy-related preferences. For information
on the other HTTP proxy preferences, see the <filename>system_http_proxy.schemas</filename> schema definition file.</para>
</sect2>
<sect2 id="gconf-11">
<title>Einstellungen zur Druckverwaltung</title>
<para>To set print manager preferences, you modify the values of the preference
keys in the <systemitem>/apps/gnome-print-manager</systemitem> location. For example,
if you do not want users to view the print jobs of other users, set a mandatory
value as follows: </para>
<indexterm>
<primary>GConf</primary>
<secondary>Druckerverwaltung</secondary>
</indexterm>
<indexterm>
<primary>Druckerverwaltung</primary>
<secondary>Einstellungen mit GConf</secondary>
</indexterm>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type bool \
--set /apps/gnome-print-manager/show_all_jobs false</userinput></screen>
<para>To set a default value for this preference, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type bool \
--set /apps/gnome-print-manager/show_all_jobs false</userinput></screen>
<para>You can also set other print manager preferences. For information on
the other print manager preferences, see the <filename>gnome-print-manager.schemas</filename> schema definition file.</para>
<!--gnome-print-manager isn't in Mercury. Is there a replacement?-->
</sect2>
<sect2 id="gconf-12">
<title>Anzahl der Arbeitsflächen einstellen</title>
<indexterm>
<primary>GConf</primary>
<secondary>Festlegen der Anzahl der Arbeitsflächen</secondary>
</indexterm>
<indexterm>
<primary>Arbeitsflächen</primary>
<secondary>Anzahl festlegen mit GConf</secondary>
</indexterm>
<para>To set a mandatory
number of workspaces, use the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type int \
--set /apps/metacity/general/num_workspaces <replaceable>integer</replaceable></userinput></screen>
<para>To set a default number of workspaces, use the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type int \
--set /apps/metacity/general/num_workspaces <replaceable>integer</replaceable></userinput></screen>
<para>You can also set other window manager preferences. For information on
the other window manager preferences, see the <filename>metacity.schemas</filename>
schema definition file.</para>
</sect2>
<sect2 id="gconf-16">
<title>Festlegen von Einstellungen zur Tastatur-Barrierefreiheit</title>
<indexterm>
<primary>GConf</primary>
<secondary>Tastatur-Barrierefreiheit einstellen</secondary>
</indexterm>
<indexterm>
<primary>Tastatur</primary>
<secondary>Barrierefreiheits-Einstellungen mit GConf</secondary>
</indexterm>
<para>To set keyboard accessibility preferences, you modify the values of the preference
keys in the <systemitem>/desktop/gnome/accessibility/keyboard</systemitem> location.
For example, if you want to set a mandatory value so that keyboard accessibility
features are enabled, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type bool \
--set /desktop/gnome/accessibility/keyboard/enable true</userinput></screen>
<para>To set a default value for this preference, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type bool \
--set /desktop/gnome/accessibility/keyboard/enable false</userinput></screen>
<para>You can also set other keyboard accessibility preferences. For information
on the other keyboard accessibility preferences, see the <filename>desktop_gnome_accessibility_keyboard.schemas</filename> schema definition file.</para>
</sect2>
<sect2 id="gconf-18">
<title>To Set Keyboard Shortcut Preferences</title>
<indexterm>
<primary>GConf</primary>
<secondary>keyboard shortcuts, setting</secondary>
</indexterm>
<indexterm>
<primary>Tastatur</primary>
<secondary>Setzen von Tastenkürzeln mit GConf</secondary>
</indexterm>
<para>To set
keyboard shortcut preferences, you modify the values of preference keys in <systemitem>/apps/metacity/global_keybindings</systemitem> location. For example, you might
want users to use only the <keycombo><keycap>Alt</keycap><keycap>F3</keycap></keycombo> keyboard
shortcut to open the <guilabel>Run Application</guilabel> dialog. To set this
mandatory value, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type string \
--set /apps/metacity/global_keybindings/panel_run_dialog '<Alt>F3'</userinput></screen>
<para>You can also set other keyboard shortcut preferences. For information
on the other keyboard shortcut preferences, see the <filename>metacity.schemas</filename> schema definition file.</para>
</sect2>
<sect2 id="gconf-14">
<title>Einstellungen für Panels und Panel-Objekte</title>
<indexterm>
<primary>GConf</primary>
<secondary>panel object preferences, setting</secondary>
</indexterm>
<indexterm>
<primary>GConf</primary>
<secondary>Benutzerdefinierte Panel-Einstellungen</secondary>
</indexterm>
<indexterm>
<primary>Panels</primary>
<secondary>individuelle Einstellungen mit GConf</secondary>
</indexterm>
<para>Die Datei <filename>panel-default-setup.entries</filename> legt die folgenden Details für die Panels des GNOME-Desktops fest:</para>
<itemizedlist>
<listitem>
<para>Anzahl der Panels.</para>
</listitem>
<listitem>
<para>Typen der Panels.</para>
</listitem>
<listitem>
<para>Eigenschaften der Panels.</para>
</listitem>
<listitem>
<para>Inhalt der Panels.</para>
</listitem>
</itemizedlist>
<para>Die Konfiguration individueller Panels und Panel-Objekte ist eine komplexe Aufgabe. Dafür sollten Sie zunächst den Aufbau der Datei <filename>panel-default-setup.entries</filename> verstehen. Weitere Informationen über diese Datei finden Sie im nächsten Abschnitt.</para>
<para>Zur individuellen Einstellung der Panels und Panel-Objekte müssen Sie zahlreiche Einstellungen in der Konfigurationsquelle verändern. Der einfachste Weg ist die Verwendung des Befehls <command>gconftool-2</command> mit den Optionen <option>--dump</option> und <option>--load</option>. Weitere Informationen über die Einstellungen für Panels und Panel-Objekte finden Sie in <xref linkend="gconf-3"/>.</para>
<sect3 id="gconf-23">
<title>Individuelle Panels und Panel-Objekte</title>
<indexterm>
<primary>GConf</primary>
<secondary>Schema-Definitionsdateien</secondary>
<tertiary>Panel und Panelobjekt</tertiary>
</indexterm>
<indexterm>
<primary>schemas</primary>
<secondary>Schema-Definitionsdateien</secondary>
<tertiary>Panel und Panelobjekt</tertiary>
</indexterm>
<para>The file <filename>panel-default-setup.entries</filename> contains sections that specify panels and panel contents. The <filename>panel-default-setup.entries</filename> file specifies values for schema keys.
The <filename>panel-default-setup.entries</filename> file resides in the <filename>/etc/gconf/schemas</filename> directory. </para>
<para>Die Datei <filename>panel-default-setup.entries</filename> ist wie folgt aufgebaut:</para>
<orderedlist>
<listitem>
<para>Schlüssel, die den allgemeinen Aufbau von Panels, Applets und anderen Panel-Objekten auf dem GNOME-Desktop festlegen. Die folgenden Schlüssel geben die anzahl der Panels, Panel-Objekte und angezeigten Applets auf dem GNOME-Desktop an:</para>
<itemizedlist>
<listitem>
<para>
<systemitem>/apps/panel/default_setup/general/toplevel_id_list</systemitem>
</para>
</listitem>
<listitem>
<para>
<systemitem>/apps/panel/default_setup/general/object_id_list</systemitem>
</para>
</listitem>
<listitem>
<para>
<systemitem>/apps/panel/default_setup/general/applet_id_list</systemitem>
</para>
</listitem>
</itemizedlist>
<para>Die Schlüssel ordnen auch Bezeichner jedem Panel, Panel-Objekt und Applet zu. Als Beispiel zeigt folgender Ausschnitt aus der Datei <filename>panel-default-setup.entries</filename>, dass ein Panel auf dem GNOME-Desktop erscheint:</para>
<programlisting><![CDATA[<entry>
<key>toplevel_id_list</key>
<schema_key>/schemas/apps/panel/general/toplevel_id_list</schema_key>
<value>
<list type="string">
<value>
<string>bottom_panel</string>
</value>
</list>
</value>
</entry>]]></programlisting>
<para>In der Datei <filename>panel-default-setup.entries</filename> bezieht sich der Bezeichner <systemitem>bottom_panel</systemitem> auf das Panel am unteren Bildschirmrand.</para>
</listitem>
<listitem>
<para>Schlüssel, die die Eigenschaften eines Panels festlegen. Die Eigenschaftsschlüssel eines Panels sind wie folgt strukturiert:</para>
<programlisting>/apps/panel/default_setup/toplevels/<replaceable>panel-name</replaceable>/<replaceable>panel-property-key</replaceable></programlisting>
<para>For example, the key <systemitem>/apps/panel/default_setup/toplevels/bottom_panel/size</systemitem> specifies the size of the bottom panel. </para>
</listitem>
<listitem>
<para>Keys that specify the panel objects, the panel object properties,
and the panels in which the objects reside. For example, the following sample
from <filename>panel-default-setup.entries</filename> specifies a <guimenu>Main Menu</guimenu> object at the left side of the bottom panel:</para>
<programlisting><![CDATA[<entrylist base="/apps/panel/default_setup/objects/main_menu">
<entry>
<key>object_type</key>
<schema_key>/schemas/apps/panel/objects/object_type</schema_key>
<value>
<string>menu-object</string>
</value>
</entry>
<entry>
<key>toplevel_id</key>
<schema_key>/schemas/apps/panel/objects/toplevel_id</schema_key>
<value>
<string>bottom_panel</string>
</value>
</entry>
<entry>
<key>position</key>
<schema_key>/schemas/apps/panel/objects/position</schema_key>
<value>
<int>0</int>
</value>
</entry>
<!-- Possibly more entry elements -->
</entrylist>]]></programlisting>
</listitem>
<listitem>
<para>Keys that specify the applets, the applet preferences, and
the panels in which the applets reside. For example, the following sample
from <filename>panel-default-setup.entries</filename> specifies the <application>Window List</application> applet, in the bottom panel:</para>
<programlisting><![CDATA[<entrylist base="/apps/panel/default_setup/applets/window_list">
<entry>
<key>object_type</key>
<schema_key>/schemas/apps/panel/objects/object_type</schema_key>
<value>
<string>bonobo-applet</string>
</value>
</entry>
<entry>
<key>toplevel_id</key>
<schema_key>/schemas/apps/panel/objects/toplevel_id</schema_key>
<value>
<string>bottom_panel</string>
</value>
</entry>
<entry>
<key>position</key>
<schema_key>/schemas/apps/panel/objects/position</schema_key>
<value>
<int>2</int>
</value>
</entry>
<!-- Possibly more entry elements -->
<entry>
<key>bonobo_iid</key>
<schema_key>/schemas/apps/panel/objects/bonobo_iid_type</schema_key>
<value>
<string>OAFIID:GNOME_WindowListApplet</string>
</value>
</entry>
</entrylist>]]></programlisting>
<para>The OAFIID is a unique identifier for an applet. To find the OAFIID
for a particular applet, see the <filename>.server</filename> file for the
applet in the <filename>/usr/lib/bonobo/servers</filename> directory. For
example, the following excerpt from <filename>GNOME_Wncklet_Factory.server</filename> shows the OAFIID for the <application>Window List</application>
applet:</para>
<programlisting><![CDATA[<oaf_server iid="OAFIID:GNOME_WindowListApplet"
type="factory" location="OAFIID:GNOME_Wncklet_Factory">]]></programlisting>
</listitem>
</orderedlist>
</sect3>
<sect3 id="gconf-3">
<title>To Set Preferences for Individual Panels and Panel Objects</title>
<para>To set the preferences for a panel and the objects on a panel perform
the following steps:</para>
<orderedlist>
<listitem>
<para>Log in to a GNOME session, and configure the panels as required.</para>
</listitem>
<listitem>
<para>Use the <option>--dump</option> option with the <command>gconftool-2</command> command line tool to generate a file that contains an
XML description of your panel configuration. The <option>--dump</option>
option generates a list that contains all preference keys in a <application>GConf</application> repository directory that you specify. </para>
<para>For example, the following command creates an XML description of the
default panel configuration in a file called <filename>my-panel-setup.entries</filename>:</para>
<screen><userinput>gconftool-2 --dump /apps/panel > my-panel-setup.entries</userinput></screen>
</listitem>
<listitem>
<para>Open the <filename>my-panel-setup.entries</filename> file
in a text editor, and modify the file as required.</para>
<para>For example, you might want to change the location of the desktop entry
files. The following is an excerpt from a file generated with the <option>--dump</option> option:</para>
<programlisting><![CDATA[<entry>
<key>objects/object_16/launcher_location</key>
<schema_key>/schemas/apps/panel/objects/launcher_location</schema_key>
<value>
<string>hadjaha-00adce02f7.desktop</string>
</value>
</entry>]]></programlisting>
<para>In the sample above, you might want to change the reference to <filename>hadjaha-00adce02f7.desktop</filename> to another desktop entry file that is
available globally.</para>
<para>When you generate a panel configuration with the <option>--dump</option>
option, the positions of the panel objects are absolute positions. You might
want to change the positions of panel objects from absolute positions to relative
positions. The object at the extreme left of a panel has a <systemitem>position</systemitem> value of <literal>0</literal>. The next object has a <systemitem>position</systemitem> value of <literal>1</literal>, and so on. If you want object
positions to be relative to the right side of the panel, set the value of
the <systemitem>right_stick</systemitem> key to <literal>true</literal>. </para>
<!--Give full key name for position.-->
</listitem>
<listitem>
<para>Use the <option>--load</option> option with the <command>gconftool-2</command> command line tool to set the values of the default configuration
source to the values in the <filename>my-panel-setup.entries</filename> file.
For example, the following command sets the values of the keys in the default
configuration source to the values of the corresponding keys in <filename>my-panel-setup.entries</filename>:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--load my-panel-setup.entries</userinput></screen>
</listitem>
</orderedlist>
</sect3>
</sect2>
</sect1>
<sect1 id="gconf-9">
<title>Setting Look-and-Feel Preferences</title>
<para>Die folgenden Abschnitte beschreiben, wie Sie obligatorische oder vorgegebene Werte den Einstellungen für das Erscheinungsbild zuordnen.</para>
<sect2 id="gconf-19">
<title>Festlegen von Schrifteinstellungen </title>
<indexterm>
<primary>GConf</primary>
<secondary>Schriften einstellen</secondary>
</indexterm>
<indexterm>
<primary>Schriften</primary>
<secondary>Einstellungen mit GConf</secondary>
</indexterm>
<para>To set font preferences, you modify the values of two preference
keys. The following table shows the keys to modify, and the part of the user
interface to which the keys correspond:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="50*"/>
<colspec colwidth="50*"/>
<thead>
<row rowsep="1">
<entry>
<para>GConf-Ort</para>
</entry>
<entry>
<para>Komponente der Benutzerschnittstelle</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>/desktop/gnome/interface/font_name</para>
</entry>
<entry valign="top">
<para><application>Font</application> preference tool, <guilabel>Application font</guilabel> option</para>
</entry>
</row>
<row>
<entry valign="top">
<para>/apps/nautilus/preferences/desktop_font</para>
</entry>
<entry valign="top">
<para><application>Font</application> preference tool, <guilabel>Desktop font</guilabel> option</para>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>For example, to set <literal>Sans 12</literal> as the mandatory application
font, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type string \
--set /desktop/gnome/interface/font_name "Sans 12"</userinput></screen>
<para><indexterm><primary>desktop</primary><secondary>font preferences, setting
with GConf</secondary></indexterm>To set <literal>palatino 12</literal> as
the default desktop object font, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type string \
--set /apps/nautilus/preferences/desktop_font "palatino 12"</userinput></screen>
</sect2>
<sect2 id="gconf-20">
<title>Einstellungen für den Hintergrund</title>
<indexterm>
<primary>GConf</primary>
<secondary>Hintergrund, einstellen</secondary>
</indexterm>
<indexterm>
<primary>Hintergrund</primary>
<secondary>Einstellungen, ändern mit GConf</secondary>
</indexterm>
<para>To set preferences for the
desktop background, you modify the values of the preference keys in the <systemitem>/desktop/gnome/background</systemitem> location. For example, to set a mandatory
image for the background, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type string \
--set /desktop/gnome/background/picture_filename <replaceable>filename.png</replaceable></userinput></screen>
<para>To set a default value for this preference, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type string \
--set /desktop/gnome/background/picture_filename <replaceable>filename.png</replaceable></userinput></screen>
<para>You can also set other background preferences. For information on the
other background preferences, see the <filename>desktop_gnome_background.schemas</filename> schema definition file.</para>
</sect2>
<sect2 id="gconf-21">
<title>Einstellungen für den Begrüßungsbildschirm</title>
<indexterm>
<primary>GConf</primary>
<secondary>Begrüßungsbildschirm, einstellen</secondary>
</indexterm>
<indexterm>
<primary>Begrüßungsbildschirm</primary>
<secondary>Bild, Einstellen mit GConf</secondary>
</indexterm>
<para>To set splash image preferences, you
modify the value of the preference keys in the <systemitem>/apps/gnome-session/options/</systemitem> location. For example, if you do not want users ever to see a
splash image, set a mandatory value as follows:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type bool \
--set /apps/gnome-session/options/show_splash_screen false</userinput></screen>
<para>To set a default value for this preference, run the following command:</para>
<screen><userinput>gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.defaults \
--type bool \
--set /apps/gnome-session/options/show_splash_screen false</userinput></screen>
<para>Sie können noch weitere Einstellungen für den Begrüßungsbildschirm ändern. Nähere Informationen hierzu finden Sie in der Schema-Definitionsdatei <filename>gnome-session.schemas</filename>.</para>
</sect2>
</sect1>
<sect1 id="gconf-28">
<title>Wiederherstellung der vorgegebenen Einstellungswerte</title>
<indexterm>
<primary>GConf</primary>
<secondary>restoring default preference
values</secondary>
</indexterm>
<indexterm>
<primary>Einstellungswerte</primary>
<secondary>Standardwerte wiederherstellen mit GConf</secondary>
</indexterm>
<para>Um die vorgegebenen Einstellungswerte für einen Benutzer wiederherzustellen, führen Sie den folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 --direct \
--config-source <replaceable>Benutzer-Konfigurationsquelle</replaceable> \
--recursive-unset</userinput></screen>
<para>Ersetzen Sie <replaceable>user-configuration-source</replaceable> durch die Konfigurationsquelle im Ordner <filename>.gconf</filename> im persönlichen Ordner des Benutzers.</para>
<para>This command resets the values of all preference keys, in all subdirectories,
from the user setting to the setting in the default configuration source.</para>
</sect1>
</chapter>
<chapter id="menustructure-0">
<title>Menüs bearbeiten</title>
<anchor id="menustructure-22"/>
<anchor id="menustructure-TBL-12"/>
<anchor id="menustructure-TBL-17"/>
<highlights>
<para>Dieser Abschnitt beschreibt, wie der GNOME-Desktop Menüs verarbeitet und wie Sie diese Menüs anpassen können.</para>
</highlights>
<sect1 id="menustructure-1">
<title>Einführung in Menüs</title>
<indexterm>
<primary>Menüs</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>The GNOME Desktop implements menus according to the <ulink url="http://www.freedesktop.org/wiki/Standards/menu-spec">XDG menu
specification</ulink>. By supporting this specification, GNOME allows you
to:</para>
<itemizedlist>
<listitem>
<para>Customize the menu hierarchy easily. You can edit a small number
of files to customize the menu hierarchy. You do not need to modify
your applications or move files.</para>
</listitem>
<listitem>
<para>Install applications easily. You do not need to provide
information about the menu hierarchy to applications when you install
the applications.</para>
</listitem>
<listitem>
<para>Configure menus so that users cannot modify the menus.</para>
</listitem>
</itemizedlist>
<para>Die Menüs auf dem GNOME-Desktop verwenden die folgenden Komponenten:</para>
<itemizedlist>
<listitem>
<para>Menu definition files</para>
</listitem>
<listitem>
<para>Desktop entry files</para>
</listitem>
<listitem>
<para>Directory entry files</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="menustructure-13">
<title>Menu Definition Files</title>
<indexterm>
<primary>menu definition files</primary>
</indexterm>
<indexterm>
<primary>.menu-Dateien</primary>
<see>menu definition files</see>
</indexterm>
<para>Menu files define the hierarchy of menus that are used in the GNOME
menu bar. By modifying these files, you can customize menus for all users,
or for a single user depending on the location of the
<filename>applications.menu</filename> file that you modify.</para>
<para>Menu files must reside at
<filename>$XDG_CONFIG_DIRS/menus/applications.menu</filename>. If
<envar>$XDG_CONFIG_DIRS</envar><footnote>
<para>$XDG_CONFIG_DIRS ist die in der <ulink url="http://www.freedesktop.org/Standards/basedir-spec">XDG base directory specification</ulink> definierte Umgebungsvariable.</para>
</footnote> is not set, then the default path
<filename>/etc/xdg</filename> is used. This also implies that a user
specific version may be located at
<filename>$XDG_CONFIG_HOME/menus/applications.menu</filename>
which is searched first. If <envar>$XDG_CONFIG_HOME</envar> is not set,
then the default path <filename>~/.config</filename> is used. Directories
which appear first in <envar>$XDG_CONFIG_DIRS</envar> are given precedence
when there are several <filename>applications.menu</filename> files. The
first file found is used and subsequent files are ignored.</para>
<para>If you are confused about the order in which paths are searched,
here is a simple list for resolving the location of
<filename>applications.menu</filename>:</para>
<orderedlist>
<listitem>
<para>Search each directory in <envar>$XDG_CONFIG_HOME</envar> in
order to find <filename>menus/applications.menu</filename>. If
<envar>$XDG_CONFIG_HOME</envar> is not set, it defaults to the
<filename>~/.config/</filename> directory.</para>
</listitem>
<listitem>
<para>Search each directory in <envar>$XDG_CONFIG_DIRS</envar> in
order to find <filename>menus/applications.menu</filename>. If
<filename>$XDG_CONFIG_DIRS</filename> is not set, it defaults to the
<filename>/etc/xdg/</filename> directory.</para>
</listitem>
<listitem>
<para>Use the first <filename>applications.menu</filename> file
found.</para>
</listitem>
</orderedlist>
<para>You can see an example of a <filename>.menu</filename> file in <xref linkend="example-menu"/>. In this example, the top level menu is named
<literal>Applications</literal>, which is specified using the
<literal><Name></literal> element. The
<literal>Applications</literal> menu contains a single submenu, but
several submenus are allowed. Each submenu may also have an
<literal><Include></literal> element. The purpose of the
<literal><Include></literal> element is to perform a filter on the
set of available desktop entries using matching rules.</para>
<para>For example, the <literal><Category></literal> element is a
basic matching rule that selects a <link linkend="menustructure-desktopentry"><emphasis>desktop
entry</emphasis></link> only if the <link linkend="category-key"><literal>Categories</literal> key</link> contains
the content of the <literal><Category></literal> element. In the
example, the <literal>Accessories</literal> menu will include a
<emphasis>desktop entry</emphasis> only if it contains
<quote>Utility</quote> but not <quote>System</quote> in the Categories
key. For more information on the Categories key, see <xref linkend="menustructure-desktopentry"/>.</para>
<example id="example-menu">
<title>Beispiel für eine <filename>.menu</filename>-Datei</title>
<para><programlisting><!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<Menu>
<Name>Applications</Name>
<Directory>Applications.directory</Directory>
<!-- Read standard .directory and .desktop file locations -->
<DefaultAppDirs/>
<DefaultDirectoryDirs/>
<!-- Accessories submenu -->
<Menu>
<Name>Accessories</Name>
<Directory>Accessories.directory</Directory>
<Include>
<And>
<Category>Utility</Category>
<Not>
<Category>System</Category>
</Not>
</And>
</Include>
</Menu> <!-- End Accessories -->
<!-- possibly more submenus -->
</Menu> <!-- End Applications -->
</programlisting></para>
</example>
<para><xref linkend="menustructure-xmlmenu"/> beschreibt einige der Elemente in den <filename>.menu</filename>-Dateien. Eine detailliertere Beschreibung finden Sie in der <ulink url="http://www.freedesktop.org/wiki/Standards/menu-spec">XDG-Menüspezifikation</ulink>.</para>
<table frame="topbot" id="menustructure-xmlmenu">
<title>Menu Definition File Elements</title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec2" colwidth="33.83*"/>
<colspec colname="colspec3" colwidth="80.00*"/>
<thead>
<row rowsep="1">
<entry><para>Element</para></entry>
<entry><para>Beschreibung</para></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="colspec2" valign="top"><para><literal><Menu></literal> </para></entry>
<entry colname="colspec3" valign="top"><para>The root element
which may contain nested <literal><Menu></literal> elements
that define submenus. How these elements are nested determines the
menu structure.</para></entry>
</row>
<row>
<entry colname="colspec2" valign="top"><para><literal><Name></literal> </para></entry>
<entry colname="colspec3" valign="top"><para>Specifies the name of
the menu. Every <literal><Menu></literal> element must
contain a <literal><Name></literal> element.</para></entry>
</row>
<row>
<entry colname="colspec2" valign="top"><para><literal><Directory></literal>
</para></entry>
<entry colname="colspec3" valign="top"><para>Specifies the name of
the directory entry file that specifies the name, comment, and
icon for the menu. If this element is not specified, then the
<literal><Name></literal> element is to be used to display
the menu name.</para><para>By default,
<filename>.directory</filename> files are searched for in the
location
<filename>$XDG_DATA_DIRS/desktop-directories/</filename>
as set forth in the <citetitle>XDG menu
specification.</citetitle></para></entry>
</row>
<row>
<entry colname="colspec2"><literal><DefaultAppDirs></literal></entry>
<entry colname="colspec3">This is an instruction which indicates
that all the available desktop entries from
<filename>$XDG_DATA_DIRS/applications/</filename>
should be scanned. If this instruction is not included, then these
locations are not scanned for desktop entries.</entry>
</row>
<row>
<entry colname="colspec2"><literal><DefaultDirectoryDirs></literal></entry>
<entry colname="colspec3">This is an instruction which indicates
that all the available directory entries from
<filename>$XDG_DATA_DIRS/desktop-directories/</filename>
should be scanned. If the instruction is not included, then these
locations are not scanned for directory entries.</entry>
</row>
<row>
<entry colname="colspec2" valign="top"><para><literal><Include></literal></para></entry>
<entry colname="colspec3">Contains a list of matching rules by
which the contents of a menu are generated. May include the
<literal><Filename></literal>,
<literal><Category></literal>,
<literal><And></literal>, <literal><Or></literal>,
<literal><Not></literal>, or <literal><All></literal>
matching rules. If more than one rule is present, the rules are
logically ORed so that <emphasis>desktop entries</emphasis> that
match any rule are included.</entry>
</row>
<row>
<entry colname="colspec2"><literal><Exclude></literal></entry>
<entry colname="colspec3">The opposite of
<literal><Include></literal> since any <emphasis>desktop
entries</emphasis> that are matched in this element are excluded
from the previous set of included elements. For this reason, this
element must appear after the <literal><Include></literal>
element.</entry>
</row>
<row>
<entry colsep="colspec2"><literal><Filename></literal></entry>
<entry colname="colspec3">A matching rule that selects a
<emphasis>desktop entry</emphasis> when the Desktop File-Id
matches the contents of the <literal><Filename></literal>
element.</entry>
</row>
<row>
<entry colname="colspec2"><literal><Category></literal></entry>
<entry colname="colspec3">A matching rule that selects a
<emphasis>desktop entry</emphasis> when the Categories key matches
the contents of the <literal><Category></literal>
element.</entry>
</row>
<row>
<entry colname="colspec2"><literal><And></literal></entry>
<entry colname="colspec3">A matching rule that selects a
<emphasis>desktop entry</emphasis> when it is selected by
<emphasis>all</emphasis> the nested matching rules in the
<literal><And></literal> element.</entry>
</row>
<row>
<entry colname="colspec2"><literal><Or></literal></entry>
<entry colname="colspec3">A matching rule that selects a
<emphasis>desktop entry</emphasis> when it is selected by
<emphasis>any</emphasis> of the nested matching rules in the
<literal><Or></literal> element.</entry>
</row>
<row>
<entry colname="colspec2"><literal><Not></literal></entry>
<entry colname="colspec3">A matching rule that does not select a
<emphasis>desktop entry</emphasis> when it is selected by
<emphasis>any</emphasis> of the nested matching rules in the
<literal><Not></literal> element.</entry>
</row>
<row>
<entry colname="colspec2"><literal><All></literal></entry>
<entry colname="colspec3">A matching rule which selects all
<emphasis>desktop entries</emphasis>.</entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="menustructure-desktopentry">
<title>Desktop Entry Files</title>
<anchor id="menustructure-6"/>
<indexterm>
<primary>desktop entry files</primary>
</indexterm>
<indexterm>
<primary>.desktop-Dateien</primary>
<see>desktop entry files</see>
</indexterm>
<para>A <firstterm>desktop entry file</firstterm> is a data file that
provides information about an item in a menu. The desktop entry file
specifies the details for the item such as a name, a command to run, an
icon, and so on. It also contains keywords which determine the location of
the item in the menu hierarchy.</para>
<para>Desktop entry files must reside in the
<filename>$XDG_DATA_DIRS/applications</filename> directory and must have a
<filename>.desktop</filename> file extension. If
<envar>$XDG_DATA_DIRS</envar><footnote>
<para>$XDG_DATA_DIRS ist die in der <ulink url="http://www.freedesktop.org/Standards/basedir-spec">XDG base directory specification</ulink> definierte Umgebungsvariable.</para>
</footnote> is not set, then the default path is
<filename>/usr/share</filename> is used. This also implies that user
specific desktop entries may be located at
<filename>$XDG_DATA_HOME/applications</filename> which is
searched first. If <envar>$XDG_DATA_HOME</envar> is not set, then the
default path <filename>~/.local/share</filename> is used. Desktop entries
are collected from all directories in the <envar>$XDG_DATA_DIRS</envar>
environment variable. Directories which appear first in
<envar>$XDG_DATA_DIRS</envar> are given precedence when there are
several <filename>.desktop</filename> files with the same name.</para>
<para>Es folgt ein Beispiel für eine Desktop-Datei:</para>
<programlisting>[Desktop Entry]
Encoding=UTF-8
Name=Calculator
Name[fr]=Calculatrice
...
Comment=Perform calculations
Comment[fr]=Effectue des calculs compliqués
...
Exec=gcalctool
Icon=accessories-calculator
Terminal=false
Type=Application
StartupNotify=true
Categories=GNOME;GTK;Utility;Calculator</programlisting>
<para><xref linkend="menustructure-TBL-7"/> describes the most important
keys in desktop entry files. To get more information about desktop entry
files, see the <ulink url="http://www.freedesktop.org/Standards/desktop-entry-spec">XDG Desktop
Entry Specification</ulink>.</para>
<table frame="topbot" id="menustructure-TBL-7">
<title>Desktop Entry Keys</title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec0" colwidth="25.25*"/>
<colspec colname="colspec1" colwidth="74.75*"/>
<thead>
<row rowsep="1">
<entry><para>Desktop Entry Key</para></entry>
<entry><para>Beschreibung</para></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="colspec0" id="category-key" valign="top"><para>
<literal>Categories</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Specifies the
keywords that describe the item. The keywords are separated with
semicolons (;). To see a list of the standard category keywords,
see the desktop menu specification at
<ulink url="http://www.freedesktop.org/Standards/menu-spec">
http://www.freedesktop.org/Standards/menu-spec</ulink>
</para><para><link linkend="menustructure-13">Menu
Definition Files</link> map desktop entries to menus by using
matching rules against the Categories key.</para></entry>
</row>
<row>
<entry valign="top"><para> <literal>Comment</literal>
</para></entry>
<entry valign="top"><para>Specifies a short description of the
item. The comment is displayed as a tooltip when you point to the
item in the menu. </para></entry>
</row>
<row>
<entry valign="top"><para> <literal>Encoding</literal>
</para></entry>
<entry valign="top"><para>Legt die Zeichenkodierung der Desktop-Datei fest.</para></entry>
</row>
<row>
<entry valign="top"><para> <literal>Exec</literal> </para></entry>
<entry valign="top"><para>Specifies a command to execute when you
choose the item from the menu. </para></entry>
</row>
<row>
<entry colname="colspec0" valign="top"><para>
<literal>Icon</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Specifies the
filename of an icon that represents the item. Does not specify the
path to the filename, or the file extension. </para></entry>
</row>
<row>
<entry><literal>MimeType</literal></entry>
<entry>Legt die Mime-Typen fest, mit denen eine anwendung umgehen kann.</entry>
</row>
<row>
<entry valign="top"><para> <literal>Name</literal> </para></entry>
<entry valign="top"><para>Specifies the name of the item. This
name is displayed on the item in the menu. </para></entry>
</row>
<row>
<entry valign="top"><para> <literal>NoDisplay</literal> </para></entry>
<entry valign="top"><para>Diese Option bedeutet »Diese Anwendung existiert, soll aber nicht in den Menüs angezeigt werden«.</para></entry>
</row>
<row>
<entry colname="colspec0" valign="top"><para>
<literal>Terminal</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Specifies whether the
command in the <literal>Exec</literal> key runs in a terminal
window. If the value is <literal>true</literal> the command runs
in a terminal window. </para><para>If the command does not create
a window in which to run, the value of this key must be
<literal>true</literal>.</para></entry>
</row>
<row>
<entry colname="colspec0" valign="top"><para>
<literal>Type</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Specifies the type of
item. This value is one of the following: </para><itemizedlist>
<listitem>
<para><literal>Application</literal>: Ein Eintrag, der eine Anwendung startet.</para>
</listitem>
<listitem>
<para><literal>Link</literal>: Ein Eintrag, der auf eine Datei, einen Ordner oder eine entfernte Ressource verweist (z.B. eine FTP-Seite, eine Webseite, eine Windows-Freigabe...)</para>
</listitem>
<listitem>
<para><literal>FSDevice</literal>: Ein Eintrag, der ein Dateisystem darstellt.</para>
</listitem>
<listitem>
<para><literal>Directory</literal>: Ein Eintrag, der einen Ordner bezeichnet.</para>
</listitem>
</itemizedlist></entry>
</row>
</tbody>
</tgroup>
</table>
<para>For more information on the keys in desktop entry files, see the
desktop entry specification at the following URL:</para>
<literallayout>
<ulink url="http://www.freedesktop.org/Standards/desktop-entry-spec">http://www.freedesktop.org/Standards/desktop-entry-spec</ulink>
</literallayout>
<note>
<para>Panel launchers and desktop objects also use desktop entry files.
The desktop entry files for launchers and desktop objects provide the
same information as for items in a menu. For example, the desktop entry
files provide the command to run when a user chooses the launcher or
object.</para>
</note>
</sect1>
<sect1 id="menustructure-14">
<title>Directory Entry Files</title>
<indexterm>
<primary>directory entry files</primary>
</indexterm>
<indexterm>
<primary>.directory-Dateien</primary>
<see>directory entry files</see>
</indexterm>
<para>A <firstterm>directory entry file</firstterm> is a data file that
provides information about a menu. The directory entry file specifies the
details for the menu such as a name, a tooltip, and an icon. Directory
entry files have a <filename>.directory</filename> file extension.</para>
<para>Directory entry files must reside in the
<filename>$XDG_DATA_DIRS/desktop-directories</filename> directory. If
<envar>$XDG_DATA_DIRS</envar> is not set, then the default path is
<filename>/usr/share</filename> is used. This also implies that user
specific directory entries may be located at
<filename>$XDG_DATA_HOME/desktop-directories</filename>
which is searched first. If <envar>$XDG_DATA_HOME</envar> is not set, then
the default path <filename>~/.local/share</filename> is used. Directory
entries are collected from all directories in the
<envar>$XDG_DATA_DIRS</envar> environment variable. Directories which
appear first in <envar>$XDG_DATA_DIRS</envar> are given precedence when
there are several <filename>.directory</filename> files with the same
name.</para>
<para>The following is a sample directory entry file:</para>
<programlisting>[Desktop Entry]
Name=Graphics
Name[fr]=Graphisme
...
Comment=Graphics applications
Comment[fr]=Applications graphiques
...
Icon=gnome-graphics
Type=Directory
Encoding=UTF-8</programlisting>
<para><xref linkend="menustructure-TBL-15"/> describes the most important
keys in directory entry files.</para>
<table frame="topbot" id="menustructure-TBL-15">
<title>Directory Entry Keys</title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec0" colwidth="27.07*"/>
<colspec colname="colspec1" colwidth="72.93*"/>
<thead>
<row rowsep="1">
<entry><para>Directory Entry Key</para></entry>
<entry><para>Beschreibung</para></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="colspec0" valign="top"><para>
<literal>Name</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Legt den Namen des Menüs fest. Dieser Name wird im Menü angezeigt.</para></entry>
</row>
<row>
<entry colname="colspec0" valign="top"><para>
<literal>Comment</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Eine kurze Beschreibung des Menüs. Dieser Kommentar wird als Minihilfe angezeigt, wenn sich der Mauszeiger über dem Menü befindet.</para></entry>
</row>
<row>
<entry colname="colspec0" valign="top"><para>
<literal>Icon</literal> </para></entry>
<entry colname="colspec1" valign="top"><para>Specifies the
filename of an icon that represents the menu. Does not specify the
path to the filename, or the file extension. </para></entry>
</row>
<row>
<entry valign="top"><para> <literal>Type</literal> </para></entry>
<entry valign="top"><para>Specifies the type of menu. The value of
this key is always <literal>Directory</literal>.</para></entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="menustructure-2">
<title>Bearbeitung der Systemmenüs</title>
<anchor id="menustructure-23"/>
<indexterm>
<primary>Menüs</primary>
<secondary>bearbeiten</secondary>
</indexterm>
<para>You can edit menu configuration files and menu data files manually
to customize menus.</para>
<sect2 id="menustructure-3">
<title>Menüs hinzufügen</title>
<anchor id="menustructure-19"/>
<anchor id="menustructure-20"/>
<indexterm>
<primary>Menüs</primary>
<secondary>hinzufügen</secondary>
</indexterm>
<para>Um ein Menü für alle Benutzer hinzuzufügen, führen Sie die folgenden Schritte aus:</para>
<orderedlist>
<listitem>
<para>Create a directory entry file for the item that you want to
add. Place the directory entry file in the
<filename>$XDG_DATA_DIRS/desktop-directories</filename>
directory. For more information on directory entry files, see <xref linkend="menustructure-14"/>.</para>
</listitem>
<listitem>
<para>Locate the
<filename>$XDG_CONFIG_DIRS/menus/applications.menu</filename>
file.</para>
</listitem>
<listitem>
<para>In the <filename>.menu</filename> file, add a
<literal><Menu></literal> element for the new menu. For more
information on <filename>.menu</filename> files, see <xref linkend="menustructure-13"/>.</para>
</listitem>
<listitem>
<para>Create a <literal><Name></literal> element below
<literal><Menu></literal>. The content of the element should
contain the name for the menu.</para>
</listitem>
<listitem>
<para>Create a <literal><Directory></literal> element below
<literal><Menu></literal>. The content of the element should
contain the name of the directory entry file.</para>
</listitem>
<listitem>
<para>Wie Sie einen Eintrag zu einem Menü hinzufügen können, lesen Sie in <xref linkend="menustructure-4"/>.</para>
</listitem>
</orderedlist>
<para>Beim nächsten Anmelden eines Benutzers sollte das Menü in der Menüleiste erscheinen.</para>
<note>
<title>Fehlendes Menü?</title>
<para>If you did not specify any matching rules in the
<literal><Include></literal> element, or if the rule did not
match any desktop entries, then you may not see the menu in the menu
bar.</para>
</note>
</sect2>
<sect2 id="menustructure-4">
<title>Hinzufügen eines Eintrags zu einem Menü</title>
<indexterm>
<primary>Menüs</primary>
<secondary>adding items to</secondary>
</indexterm>
<para>Um einen Menüeintrag für alle Benutzer hinzuzufügen, führen Sie die folgenden Schritte aus:</para>
<orderedlist>
<listitem>
<para>Create a desktop entry file for the item that you want to add.
For more information on desktop entry files, see <xref linkend="menustructure-desktopentry"/>.</para>
</listitem>
<listitem>
<para>Place the desktop entry file in the
<filename>$XDG_DATA_DIRS/applications</filename> folder.</para>
</listitem>
<listitem>
<para>Locate the
<filename>$XDG_CONFIG_DIRS/menus/applications.menu</filename>
file.</para>
</listitem>
<listitem>
<para>Verify that a <literal><Menu></literal> element contains
an <literal><Include></literal> element with a matching rule
that selects the desktop entry file made in step 1.</para>
</listitem>
</orderedlist>
<para>The next time that users log in, the menu item is in the assigned
location.</para>
</sect2>
<sect2 id="menustructure-9">
<title>Bearbeiten der Eigenschaften eines Menüs</title>
<indexterm>
<primary>Menüs</primary>
<secondary>editing properties of</secondary>
</indexterm>
<para>Um die Eigenschaften eines Menüs für alle Benutzer zu bearbeiten, führen Sie die folgenden Schritte aus:</para>
<orderedlist>
<listitem>
<para>Locate the
<filename>$XDG_CONFIG_DIRS/menus/applications.menu</filename>
file.</para>
</listitem>
<listitem>
<para>Find the <literal><Menu></literal> entry in this file
that corresponds to the menu you want to modify. Note the filename
of the directory entry in the <literal><Directory></literal>
element.</para>
</listitem>
<listitem>
<para>Locate the directory entry for this menu. Modify the contents
to change the properties of the menu. For more information on
<filename>.directory</filename> files, see <xref linkend="menustructure-14"/>.</para>
</listitem>
</orderedlist>
</sect2>
<sect2 id="menustructure-10">
<title>Bearbeiten eines Menüeintrages</title>
<indexterm>
<primary>Menüs</primary>
<secondary>Menüeinträge bearbeiten</secondary>
</indexterm>
<para>Um einen Menüeintrag zu bearbeiten, führen Sie die folgenden Schritte aus:</para>
<orderedlist>
<listitem>
<para>Locate the desktop entry in the
<filename>$XDG_DATA_DIRS/applications</filename>
directory that corresponds to the menu item.</para>
</listitem>
<listitem>
<para>Edit the desktop entry to change the properties of the menu
item. For more information on desktop entry files, see <xref linkend="menustructure-desktopentry"/>.</para>
</listitem>
</orderedlist>
</sect2>
<sect2 id="menustructure-11">
<title>Entfernen eines Eintrags aus einem Menü</title>
<indexterm>
<primary>Menüs</primary>
<secondary>Menüeinträge entfernen</secondary>
</indexterm>
<para>So entfernen Sie einen Menüeintrag für alle Benutzer:</para>
<orderedlist>
<listitem>
<para>Locate the
<filename>$XDG_CONFIG_DIRS/menus/applications.menu</filename>
file.</para>
</listitem>
<listitem>
<para>Find the <literal><Menu></literal> element in this file
that contains the desktop entry you want to delete.</para>
</listitem>
<listitem>
<para>Insert an <literal><Exclude></literal> element after the
closing tag for the <literal><Include></literal> element. Make
sure this is in the <literal><Menu></literal> element
determined in step 2.</para>
</listitem>
<listitem>
<para>Insert the <literal><Filename></literal> matching rule
as a subelement of <literal><Exclude></literal> to
specifically exclude a desktop entry.</para>
</listitem>
</orderedlist>
<para>The next time that users log in, the menu item is not displayed in
the menu. <xref linkend="menustructure-deleteitem"/> shows how this
done in the <filename>applications.menu</filename> file. The desktop
entry for <filename>dasher.desktop</filename> is explicitly excluded
from showing up in the accessibility menu.</para>
<example id="menustructure-deleteitem">
<title>Entfernen eines Eintrags aus einem Menü</title>
<programlisting><!-- ... -->
<Menu>
<Name>Accessibility</Name>
<Directory>Accessibility.directory</Directory>
<Include>
<And>
<Category>Accessibility</Category>
<Not><Category>Settings</Category></Not>
</And>
</Include>
<Exclude>
<Filename>dasher.desktop</Filename>
</Exclude>
</Menu>
<!-- ... -->
</programlisting>
</example>
</sect2>
</sect1>
<sect1 id="menustructure-usermenus">
<title>Bearbeiten von Benutzermenüs und Zusammenführen von Menüs</title>
<indexterm>
<primary>Menüs</primary>
<secondary>Benutzermenüs bearbeiten</secondary>
</indexterm>
<para>Sie können die folgenden GNOME-Desktopanwendungen für die Bearbeitung von Benutzermenüs verwenden:</para>
<itemizedlist>
<listitem>
<para>GNOME-Menüeditor</para>
</listitem>
</itemizedlist>
<para>Ein einfacher Menüeditor steht für die Benutzer zum Bearbeiten Ihrer Menüs zur Verfügung. Weitere Informationen hierzu finden Sie im Abschnitt <ulink url="ghelp:user-guide?goseditmainmenu-1">Arbeiten mit Menüs</ulink> des <ulink url="ghelp:user-guide">GNOME Desktop-Benutzerhandbuchs</ulink>.</para>
<para>To manually create a custom menu for a user, the
<filename>$XDG_CONFIG_HOME/menus/applications.menu</filename>
must exist. In the case that <envar>$XDG_CONFIG_HOME</envar> is not set,
the default <filename>~/.config</filename> directory is used. Since this is the
first location that is searched for the
<filename>applications.menu</filename> file, it takes precedence over all
other menu files.</para>
<para>User menus can contain all the elements described in <xref linkend="menustructure-13"/>. For a complete list of the elements
allowed, see the <ulink url="http://www.freedesktop.org/wiki/Standards/menu-spec">XDG menu
specification</ulink>.</para>
<para>Since user menu files take precedence over the system menu file, it
will completely replace the system menu unless it explicitly
<emphasis>merges</emphasis> the system menu. Information on menu merging
is available in the following subsections.</para>
<sect2>
<title>Zusammenführen des Systemmenüs</title>
<indexterm>
<primary>Menüs</primary>
<secondary>Systemmenü zusammenführen</secondary>
</indexterm>
<para>Often, a user only wants to add or delete menu items in addition
to the standard system menu. To support single changes like these, it is
recommended that you use the <literal><MergeFile></literal>
element with the attribute <literal>type="parent"</literal> within the
user's <filename>applications.menu</filename> file.</para>
<para>The <literal><MergeFile></literal> element allows a menu to
be merged with the contents of the user's menu file. When you specify
the attribute <literal>type="parent"</literal>, then the contents of the
<literal><MergeFile></literal> element are ignored and the next
<filename>applications.menu</filename> file in the
<filename>$XDG_CONFIG_DIRS/menus</filename> directory is used for
merging.</para>
<note>
<title>Ältere Spezifikationen</title>
<para>Older specifications did not include the <literal>type</literal>
attribute and simply required the location of the menu file to be
merged as the content of the <literal><MergeFile></literal>
element. As a result, you may still see a location specified in the
contents of <literal><MergeFile></literal>, even when
<literal>type="parent"</literal>.</para>
</note>
<para>Das Zusammenführen wird wie folgt ausgeführt:</para>
<itemizedlist>
<listitem>
<para>The children of the root <literal><Menu></literal>
element in the merged menu file<footnote>
<para>Merged menu file refers to the next
<filename>applications.menu</filename> in the
<filename>$XDG_CONFIG_DIRS/menus</filename> directory.</para>
</footnote> are substituted for the
<literal><MergeFile></literal> element in the base menu
file.</para>
</listitem>
<listitem>
<para>All child <literal><Menu></literal> elements with the
same name are consolidated into a single
<literal><Menu></literal> element. This is by done appending
all child elements of each <literal><Menu></literal> element
with the same name into the <emphasis>last</emphasis> occurrence of
the menu element.</para>
</listitem>
</itemizedlist>
<para><xref linkend="menustructure-systemmerge"/> zeigt ein Beispiel eines Benutzermenüs, das ein Systemmenü explizit einbindet.</para>
<example id="menustructure-systemmerge">
<title>Zusammenführen des Systemmenüs</title>
<programlisting><!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/menu-1.0.dtd">
<Menu>
<Name>Applications</Name>
<MergeFile type="parent">/etc/xdg/menus/applications.menu</MergeFile>
<Menu>
<Name>Accessibility</Name>
<Exclude>
<Filename>dasher.desktop</Filename>
</Exclude>
</Menu>
</Menu>
</programlisting>
</example>
</sect2>
<sect2>
<title>Merging Arbitrary Menus</title>
<indexterm>
<primary>Menüs</primary>
<secondary>merging arbitrary menus</secondary>
</indexterm>
<para>Arbitrary menu files can be merged in much the same way as system
menus. The difference is that the <literal>type</literal> attribute must
be set to <literal>path</literal> or must be excluded from the
<literal><MergeFile></literal> element in order to do this type of
merge.</para>
<para>The merge is performed in the same way except that the location of
the <emphasis>merged menu file</emphasis> is specified in the contents
of the <literal><MergeFile></literal> element.</para>
</sect2>
</sect1>
</chapter>
<chapter id="themes-0">
<title>Themen installieren</title>
<highlights>
<para>Dieser Abschnitt beschreibt Themen, die in GNOME verfügbaren Themeneinstellungen. die Installation von Optionen für die Themeneinstellung sowie die Erstellung eigener Optionen.</para>
</highlights>
<sect1 id="themes-1">
<title>Einführung in Themen</title>
<indexterm>
<primary>Themen</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>A theme is a group of coordinated settings that specifies the visual
appearance of a part of the GNOME Desktop. Users can choose themes to change
the appearance of the GNOME Desktop.</para>
<para>A theme contains settings that affect different parts of the GNOME Desktop,
as follows:</para>
<variablelist>
<varlistentry>
<term>Fensterinhalt</term>
<listitem>
<para><indexterm><primary>themes</primary><secondary>controls options</secondary><tertiary>introduction</tertiary></indexterm><indexterm><primary>GTK+ themes</primary><see>themes, controls
options</see></indexterm>The controls setting for a theme determines the visual
appearance of windows, panels, and applets. The controls setting also determines
the visual appearance of the GNOME-compliant interface items that appear on
windows, panels, and applets, such as menus, icons, and buttons. Some of the
controls setting options that are available are designed for special accessibility
needs. Users can choose an option for the controls setting from the <guilabel>Controls</guilabel> tabbed section in the <application>Theme</application>
preference tool.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Fensterrahmen</term>
<listitem>
<para><indexterm><primary>themes</primary><secondary>window frame options</secondary><tertiary>introduction</tertiary></indexterm><indexterm><primary>Metacity themes</primary><see>themes, window frame options</see></indexterm>The window frame setting for
a theme determines the appearance of the frames around windows only. Users
can choose an option for the window frame setting from the <guilabel>Window
Border</guilabel> tabbed section in the <application>Theme</application> preference
tool.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Icon</term>
<listitem>
<para><indexterm><primary>themes</primary><secondary>icons options</secondary><tertiary>introduction</tertiary></indexterm><indexterm><primary>icon themes</primary><see>themes, icons options</see></indexterm>The icon setting for a theme determines the appearance of
the icons on panels and the desktop background. Users can choose an option
for the icon setting from the <guilabel>Icons</guilabel> tabbed section in
the <application>Theme</application> preference tool.</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="themes-17">
<title>Themenindex-Datei</title>
<para>Jedes Thema verfügt über eine Indexdatei, die das Thema charakterisiert. Der Name der Indexdatei ist <filename>/usr/share/themes/<replaceable>Name-des-Themas</replaceable>/index.theme</filename>.</para>
<para>Nachfolgend ein Beispiel für eine Themenindex-Datei:</para>
<programlisting>[Desktop Entry]
Type=X-GNOME-Metatheme
Name=High Contrast Large
Name[es]=Alto contraste grande
Comment=Large black-on-white text and icons
Comment[es]=Textos e iconos grandes en negro sobre blanco
Encoding=UTF-8
[X-GNOME-Metatheme]
GtkTheme=HighContrastLargePrint
IconTheme=HighContrast
MetacityTheme=Atlanta
ApplicationFont=sans 18
</programlisting>
<para>Die folgende Tabelle beschreibt die Schlüssel in Themen-Indexdateien:</para>
<table frame="topbot" id="themes-TBL-18">
<title>Schlüssel in Themen-Indexdateien</title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec0" colwidth="33*"/>
<colspec colname="colspec1" colwidth="67*"/>
<thead>
<row rowsep="1">
<entry>
<para>Index File Key</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry colname="colspec0" valign="top">
<para>
<literal>Type</literal>
</para>
</entry>
<entry colname="colspec1" valign="top">
<para>Specifies that this theme determines
the appearance of several theme options, such as controls, window frames,
and icons.</para>
</entry>
</row>
<row>
<entry colname="colspec0" valign="top">
<para>
<literal>Name</literal>
</para>
</entry>
<entry colname="colspec1" valign="top">
<para>The name of the theme. This is
the name of the theme that is displayed in the <application>Theme</application>
preference tool.</para>
</entry>
</row>
<row>
<entry colname="colspec0" valign="top">
<para>
<literal>Comment</literal>
</para>
</entry>
<entry colname="colspec1" valign="top">
<para>Eine Kurzbeschreibung des Themas. Dieser Text wird unter dem Namen des Themas im Einstellungswerkzeug <application>Erscheinungsbild</application> angezeigt.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>GtkTheme</literal>
</para>
</entry>
<entry valign="top">
<para>Corresponds to the controls setting in the <application>Theme</application> preference tool. Specifies which controls setting option
to apply to windows, panels, and applets.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>IconTheme</literal>
</para>
</entry>
<entry valign="top">
<para>Corresponds to the icons setting in the <application>Theme</application> preference tool. Specifies which icons setting option
to apply to panels and the desktop background.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>MetacityTheme</literal>
</para>
</entry>
<entry valign="top">
<para>Corresponds to the window frame setting in the <application>Theme</application> preference tool. Specifies which window frame setting
option to apply to windows.</para>
</entry>
</row>
<row>
<entry colname="colspec0" valign="top">
<para>
<literal>ApplicationFont</literal>
</para>
</entry>
<entry colname="colspec1" valign="top">
<para>Corresponds to the application font setting in the <application>Font</application>
preference tool.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="themes-3">
<title>To Install a New Controls Option</title>
<indexterm>
<primary>Themen</primary>
<secondary>Steuerungsoptionen</secondary>
<tertiary>installieren</tertiary>
</indexterm>
<para>You can add a new option
for the controls setting in the <application>Theme</application> preference
tool. Controls options reside in the <filename>/usr/share/themes</filename>
directory. The typical structure of a controls option in the file system is
as follows:</para>
<variablelist>
<varlistentry>
<term>Optionsdatei</term>
<listitem>
<para>
<filename>/usr/share/themes/<replaceable>option-name</replaceable>/gtk-2.0/gtkrc</filename>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Bilddateien</term>
<listitem>
<para>
<filename>/usr/share/themes/<replaceable>option-name</replaceable>/pixmaps/*.*</filename>
</para>
</listitem>
</varlistentry>
</variablelist>
<para>Typically, a new option for the controls setting is supplied
as a <filename>.tar.gz</filename> file. To install the new controls option,
unzip the <filename>.tar.gz</filename> file, then untar the <filename>.tar</filename> file into the <filename>/usr/share/themes</filename> directory.</para>
<para>Users can install their own options for the controls setting. If a user
installs an option for the controls setting, the option is stored in the <filename>$HOME/.themes</filename> directory.</para>
</sect1>
<sect1 id="themes-5">
<title>Installieren einer neuen Option für den Fensterrahmen</title>
<indexterm>
<primary>Themen</primary>
<secondary>window frame options</secondary>
<tertiary>installieren</tertiary>
</indexterm>
<para>You can add a new option
for the window frame setting in the <application>Theme</application> preference
tool. Window frame options reside in the <filename>/usr/share/themes/<replaceable>option-name</replaceable>/metacity-1</filename> directory. The typical structure
of a window frame option in the file system is as follows:</para>
<variablelist>
<varlistentry>
<term>Optionsdatei</term>
<listitem>
<para>
<filename>/usr/share/themes/<replaceable>option-name</replaceable>/metacity-1/metacity-theme-1.xml</filename>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Bilddateien</term>
<listitem>
<para>
<filename>/usr/share/themes/<replaceable>option-name</replaceable>/metacity-1/*.*</filename>
</para>
</listitem>
</varlistentry>
</variablelist>
<para>Typically, a new option for the window frame setting
is supplied as a <filename>.tar.gz</filename> file. To install the new window
frame option, unzip the <filename>.tar.gz</filename> file, then untar the <filename>.tar</filename> file into the <filename>/usr/share/themes</filename> directory.</para>
<para>Users can install their own options for the window frame setting. If
a user installs an option for the window frame setting, the option is stored
in the <filename>$HOME/.themes</filename> directory.</para>
</sect1>
<sect1 id="themes-16">
<title>Installieren einer neuen Option für Symbole</title>
<indexterm>
<primary>Themen</primary>
<secondary>icons options</secondary>
<tertiary>installieren</tertiary>
</indexterm>
<para>You can add a new option for the icons
setting in the <application>Theme</application> preference tool. Icons options
reside in the <filename>/usr/share/icons/<replaceable>option-name</replaceable></filename>
directory. The typical structure of an icons option in the file system is
as follows:</para>
<variablelist>
<varlistentry>
<term>Optionsdatei</term>
<listitem>
<para>
<filename>/usr/share/icons/<replaceable>option-name</replaceable></filename>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Bilddateien</term>
<listitem>
<para>
<filename>/usr/share/icons/<replaceable>option-name</replaceable>/icons/*.*</filename>
</para>
</listitem>
</varlistentry>
</variablelist>
<para>Typically, a new option for the icons setting is supplied
as a <filename>.tar.gz</filename> file. To install the new icons option, unzip
the <filename>.tar.gz</filename> file, then untar the <filename>.tar</filename>
file into the <filename>/usr/share/icons</filename> directory.</para>
<para>Users can install their own options for the icons setting. If a user
installs an option for the icons setting, the option is stored in the <filename>$HOME/.icons/<replaceable>option-name</replaceable></filename> directory.</para>
</sect1>
<sect1 id="themes-11">
<title>Installieren von Symbolen für Themen</title>
<indexterm>
<primary>Themen</primary>
<secondary>Symbole installieren</secondary>
</indexterm>
<para>The GNOME Desktop provides several themes that are designed
for users with special visual needs. For example, some of the themes are designed
for users with low vision. Several versions of icons might be required so
that the icon can be displayed properly in each theme.</para>
<para>You might need to install a new icon for an application. When you install
a new icon, you must create several versions of the icon, so that the icon
displays correctly in the themes. You must create several versions of the
following types of icon:</para>
<itemizedlist>
<listitem>
<para>Symbole, die in Anwendungen auf dem GNOME-Desktop verwendet werden.</para>
</listitem>
<listitem>
<para>Icons that are used internally by GTK+ applications, or GTK+
stock icons.</para>
</listitem>
</itemizedlist>
<para>When you install a new icon, you must create several versions of the
icon, so that the icon displays correctly in the themes. You can create the
icons in several formats, for example Portable Network Graphic (PNG) format.
The suggested size of icons for the desktop environment is 48 pixels by 48
pixels. At this size, most themes can rescale the icons.</para>
<para>When you install a new icon, create the following 48 pixel by 48 pixel
versions of the icon:</para>
<itemizedlist>
<listitem>
<para>Regular icon</para>
</listitem>
<listitem>
<para>Low contrast icon</para>
</listitem>
<listitem>
<para>High contrast icon</para>
</listitem>
<listitem>
<para>Inverse high contrast icon</para>
</listitem>
</itemizedlist>
<para>If possible, create 16 pixel by 16 pixel versions of the each of the
icons above also, for themes that do not require large print.</para>
<para>Install the icons to the image files location that is specified for
the theme in <xref linkend="themes-3"/> or <xref linkend="themes-5"/>. For example,
to add icons to the HighContrastLargePrint theme, add the icons to the <filename>/usr/share/themes/HighContrastLargePrint/pixmaps</filename> directory. Add
references to the icons to the relevant theme files. For example, to add icons
to the HighContrastLargePrint theme, add references to the icons to the <filename>/usr/share/themes/HighContrastLargePrint/gtk-2.0/gtkrc</filename> file. Modify
the <filename>gtkrc</filename> file for the theme to associate the icon with
a GTK stock icon identifier.</para>
<para>Weitere Informationen über die Erstellung von Symbolen für Anwendungsstarter und Panels finden Sie hier: <ulink url="http://www.freedesktop.org/Standards/icon-theme-spec">http://www.freedesktop.org/Standards/icon-theme-spec</ulink>.</para>
</sect1>
<sect1 id="themes-15">
<title>To Create a Custom Controls Option</title>
<indexterm>
<primary>Themen</primary>
<secondary>Steuerungsoptionen</secondary>
<tertiary>creating custom</tertiary>
</indexterm>
<para>If the options for the
controls setting are not suitable for the needs of your users, you can create
a custom controls option. To create a custom controls option, perform the
following steps:</para>
<orderedlist>
<listitem>
<para>Create a directory structure for the option in the <filename>/usr/share/themes</filename> directory. Use the same directory structure that
other options use. For example, to create an option that is called SmallPrint,
create the following directories:</para>
<itemizedlist>
<listitem>
<para>
<filename>/usr/share/themes/SmallPrint</filename>
</para>
</listitem>
<listitem>
<para>
<filename>/usr/share/themes/SmallPrint/gtk-2.0</filename>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Locate the <filename>gtkrc</filename> file that is closest
to meeting the needs of your users. Copy the file to the <filename>gtk-2.0</filename> directory of your new option.</para>
</listitem>
<listitem>
<para>Open the <filename>gtkrc</filename> file in a text editor,
and modify the attributes of the interface elements as required. </para>
</listitem>
<listitem>
<para>If the new option includes images, install the images for
the new option in the <filename>pixmaps</filename> directory of your new option.
If the new option uses images from another option, you do not need to create
copies of the images for the new option. Instead, ensure that the reference
to the images in the <literal>pixmap_path</literal> entry in the <filename>gtkrc</filename> file is correct.</para>
</listitem>
</orderedlist>
<para>Users can now choose the new option for the controls setting.</para>
<para>Weitere Informationen über <filename>gtkrc</filename>-Dateien finden Sie hier: <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/index.html">http://developer.gnome.org/doc/API/2.0/gtk/index.html</ulink>.</para>
</sect1>
</chapter>
<chapter id="fontconfig-0">
<title>Schriften einstellen</title>
<highlights>
<para>Dieser Abschnitt beschreibt, wie Sie Schriften für den GNOME-Desktop einstellen.</para>
</highlights>
<sect1 id="fontconfig-1">
<title>Einführung in die Schrifteinstellungen</title>
<indexterm>
<primary>configuring fonts</primary>
<see>Schriften</see>
</indexterm>
<indexterm>
<primary>fontconfig</primary>
<see>Schriften</see>
</indexterm>
<indexterm>
<primary>Schriften</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>GNOME Desktop uses the <literal>fontconfig</literal> font configuration and
customization library. The <literal>fontconfig</literal> library can use all
kinds of fonts, including PostScript Type 1 fonts and TrueType fonts.</para>
<para>The <literal>fontconfig</literal> library provides a list of all the
fonts available on a GNOME Desktop system. To compile this list, <literal>fontconfig</literal> searches the directories listed in the <filename>/etc/fonts/fonts.conf</filename> file. To view all the fonts available on a system, access the <literal>fonts:///</literal> location in the file manager on the system.</para>
<para>Weitere Informationen über die Bibliothek <literal>fontconfig</literal> finden sie unter folgender Adresse:</para>
<literallayout>
<ulink url="http://freedesktop.org/software/fontconfig">http://freedesktop.org/software/fontconfig</ulink>
</literallayout>
</sect1>
<sect1 id="fontconfig-4">
<title>Schriftersetzung</title>
<indexterm>
<primary>Schriften</primary>
<secondary>substitution</secondary>
</indexterm>
<para>The <literal>fontconfig</literal> library performs font substitution
when either entire fonts, or individual characters, are not present. If the
system needs to display a font that is not available, <literal>fontconfig</literal> attempts to display another, similar font. For example, if a web
page requests to display the Verdana font, and that font is not installed
on the system, <literal>fontconfig</literal> displays a similar font, such
as Helvetica. The list of similar fonts is defined in the <filename>/etc/fonts/fonts.conf</filename> file. </para>
<para>If the system needs to display a character that is not present in the
selected font, <literal>fontconfig</literal> attempts to display the character
in another, similar font. For example, you might select Bitstream Vera Sans
as the font for the Text Editor application. The Bitstream Vera font family
does not include Cyrillic characters. If you open a document which contains
a Cyrillic character, Text Editor uses a similar font that includes Cyrillic
characters to display the character.</para>
<para>The <literal>fontconfig</literal> library also defines aliases for fonts,
for example, <literal>serif</literal>, <literal>sans-serif</literal>, and <literal>monospace</literal>. When you select one of the aliases for a font, the system
uses the first font that is defined for that alias in the <filename>/etc/fonts/fonts.conf</filename>. </para>
</sect1>
<sect1 id="fontconfig-2">
<title>Hinzufügen einer Schrift für alle Benutzer</title>
<indexterm>
<primary>Schriften</primary>
<secondary>adding for all users</secondary>
</indexterm>
<para>Um eine Schrift für alle Benutzer hinzuzufügen, gehen Sie wie folgt vor:</para>
<orderedlist>
<listitem>
<para>Copy the font file to one of the directories in the <filename>/etc/fonts/fonts.conf</filename> file. Typically, fonts are stored in the <filename>/usr/share/fonts/</filename> directory.</para>
</listitem>
<listitem>
<para>The <literal>fontconfig</literal> library updates the list
of fonts automatically. If the list of fonts is not updated, run the following
command:</para>
<screen><userinput>fc-cache <replaceable>directory-name</replaceable></userinput></screen>
</listitem>
</orderedlist>
</sect1>
<sect1 id="fontconfig-3">
<title>Hinzufügen einer Schrift für einen individuellen Benutzer</title>
<indexterm>
<primary>Schriften</primary>
<secondary>adding for individual users</secondary>
</indexterm>
<para>Um eine Schrift für einen individuellen Benutzer hinzuzufügen, gehen Sie wie folgt vor:</para>
<orderedlist>
<listitem>
<para>Copy the font file to the <filename>$HOME/.fonts</filename>
directory of the user. If you drag the font file to the <literal>fonts:///</literal> location in the file manager, the font file is copied to the <filename>$HOME/.fonts</filename> directory.</para>
</listitem>
<listitem>
<para>The <literal>fontconfig</literal> library updates the list
of fonts automatically. If the list of fonts is not updated, run the following
command:</para>
<screen><userinput>fc-cache <replaceable>directory-name</replaceable></userinput></screen>
</listitem>
</orderedlist>
</sect1>
</chapter>
<chapter id="mimetypes-0">
<title>MIME-Typen</title>
<anchor id="mimetypes-TBL-3"/>
<anchor id="mimetypes-TBL-6"/>
<anchor id="mimetypes-TBL-8"/>
<highlights>
<para>Dieser Abschnitt beschreibt, wie Anwendungen MIME-Typen erkennen, wie MIME-Typen registriert werden und wie Anwendungen zum GNOME-Desktop hinzugefügt werden können.</para>
</highlights>
<para>The purpose of this chapter is to make it easy for an administrator to
understand how to configure different parts of the MIME database and give an
general overview of the MIME system. Therefore we will
<emphasis>not</emphasis> attempt to go into details where it is not
necessary. For the gory details, it is recommended that you refer to the
<ulink url="http://www.freedesktop.org/Standards/shared-mime-info-spec">XDG
shared mime info specification</ulink>.</para>
<sect1 id="mimetypes-intro">
<title>Einführung in MIME-Typen</title>
<anchor id="mimetypes-1"/>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>A <firstterm>Multipurpose Internet Mail Extension</firstterm>
[<acronym>MIME</acronym>] type identifies the format of a file.
Applications such as Internet browsers and email applications use the MIME
type of a file to decide which actions to perform on it. For example, an
email application can use the MIME type to detect the format of an
attachment and choose an appropriate viewer for the file, such as opening
a text document with <application>gedit</application>.</para>
<para>Ein weiteres Beispiel: Der <application>Nautilus</application>-Dateimanager benötigt Informationen über den MIME-Typ einer Datei zur Ausführung folgender Aufgaben:</para>
<itemizedlist>
<listitem>
<para>Open the file in an appropriate application.</para>
</listitem>
<listitem>
<para>Anzeigen einer Zeichenkette, die den Dateityp beschreibt.</para>
</listitem>
<listitem>
<para>Anzeigen eines passenden Symbols, welches die Datei repräsentiert.</para>
</listitem>
<listitem>
<para>Anzeigen einer Liste weiterer Anwendungen, welche die Datei öffnen können.</para>
</listitem>
</itemizedlist>
<para>MIME types were originally proposed as a standard for identifying
the message body of an e-mail message. Now, many systems use MIME types to
identify the format of arbitrary files on the file system. MIME types are
composed of a top-level <emphasis>media type</emphasis> followed by a
<emphasis>subtype identifier</emphasis>, separated by a forward slash
character, <quote><literal>/</literal></quote>. One example of a MIME type
is <literal>image/jpeg</literal>. The media type in this example is
<quote><literal>image</literal></quote> and the subtype identifier is
<quote><literal>jpeg</literal></quote>. The top-level media type is meant
to be a general categorization about the content of the file, while the
subtype identifer is meant to specifically identify the format of the
file.</para>
<para>There are eight media types currently blessed by the
<acronym>IANA</acronym> [Internet Assigned Naming Authority]. These eight
media types are <simplelist type="inline">
<member>Anwendung</member>
<member>Audio</member>
<member>Bild</member>
<member>Meldung</member>
<member>Modell</member>
<member>multipart</member>
<member>Text</member>
<member>Video</member>
</simplelist>. Many subtypes exist for each media type; for more
information, see <ulink url="http://www.iana.org/assignments/media-types/">MIME Media
Types</ulink> at the <ulink url="http://www.iana.org/">IANA</ulink> web
site.</para>
<para>Implementation of MIME types in GNOME follows the <ulink url="http://www.freedesktop.org/Standards/shared-mime-info-spec">XDG
shared mime info specification</ulink>. This specification provides the
following advantages:</para>
<itemizedlist>
<listitem>
<para>Standard-Speicherorte für alle MIME-bezogenen Dateien.</para>
</listitem>
<listitem>
<para>A standard way for applications to register information about a
new MIME type.</para>
</listitem>
<listitem>
<para>A standard way to retrieve the MIME type for a file.</para>
</listitem>
<listitem>
<para>A standard way to retrieve information about a MIME type.</para>
</listitem>
</itemizedlist>
<para>The rest of the chapter describes the files and directories that
make up the MIME database, details about source XML files, how to create
or modify MIME types, how to register applications as handlers for certain
MIME types and finally, how to add an application to the GNOME
desktop.</para>
</sect1>
<sect1 id="mimetypes-database">
<title>Die MIME-Datenbank</title>
<anchor id="mimetypes-4"/>
<anchor id="mimetypes-5"/>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>Datenbank</secondary>
</indexterm>
<para>The MIME database is a collection of files that make up:</para>
<itemizedlist>
<listitem>
<para>The set of known MIME types</para>
</listitem>
<listitem>
<para>Die Methode zur Bestimmung des MIME-Typs einer Datei</para>
</listitem>
<listitem>
<para>Meta information regarding a MIME type, such as a human readable
description to use when displaying files of this type.</para>
</listitem>
</itemizedlist>
<sect2 id="mimetypes-location">
<title>Ort</title>
<para>As an administrator, the most important and basic step to
understanding the MIME system is learning the locations where these
files are stored. Since the <ulink url="http://www.freedesktop.org/Standards/shared-mime-info-spec">XDG
shared mime info specification</ulink> was drafted by the X Desktop
Group, it also makes use of the <ulink url="http://www.freedesktop.org/wiki/Standards/basedir-spec">XDG base
directory specification</ulink>. It is highly recommended that you
familiarize yourself with this specification, as it is also important
for other system administration tasks such as editing menus. A brief
summary of the directory locations as pertaining to the MIME
specification is given below.</para>
<para>The MIME database is created from the set of files located in the
<filename>$XDG_DATA_HOME/mime</filename> and
<filename>$XDG_DATA_DIRS/mime</filename> directories. If
these environment variables are unset, then they default to the values
<filename>~/.local/share</filename> and
<filename>/usr/local/share:/usr/share</filename> respectively. As can be
seen from the default value for <envar>$XDG_DATA_DIRS</envar> , each
environment variable is actually a colon separated list of directories.
The user's database at
<filename>$XDG_DATA_HOME/mime</filename> has precedence
over the system database at
<filename>$XDG_DATA_DIRS/mime</filename> when conflicting
definitions are encountered. Similar to the <citetitle>XDG shared mime
specification</citetitle>, we will refer to this set of directories as
<literal><MIME></literal> in the rest of this document.</para>
<para>For example, assuming default paths for the environment variables,
<quote>Load
<filename><MIME>/text/plain.xml</filename></quote>
means to load the following files:</para>
<itemizedlist>
<listitem>
<para><filename>~/.local/share/mime/text/plain.xml</filename></para>
</listitem>
<listitem>
<para><filename>/usr/local/share/mime/text/plain.xml</filename></para>
</listitem>
<listitem>
<para><filename>/usr/share/mime/text/plain.xml</filename></para>
</listitem>
</itemizedlist>
</sect2>
<sect2 id="mimetypes-contents">
<title>Inhalte</title>
<para>The following is a list of directories and files that are found
inside the MIME database along with brief descriptions:</para>
<variablelist>
<varlistentry>
<term><filename><MIME>/packages/</filename></term>
<listitem>
<para>This directory contains any number of XML files, each of
which describe a collection of MIME types. By default, the
<filename>freedesktop.org.xml</filename> file is installed in the
<filename>/usr/share/mime/packages</filename> directory. This file
contains all the default MIME types that are widely used and
recognized.</para>
<para>Applications which provide information about new MIME types
are to install a <emphasis>single</emphasis> new XML file here.
Depending on the prefix where the application is installed, it
will create the file in the <filename>/mime/package</filename>
subdirectory of one of the directories in
<envar>$XDG_DATA_HOME:$XDG_DATA_DIRS</envar>. For example, an
application installed to <filename>/usr/bin</filename> should
install a new source XML file to the
<filename>/usr/share/mime/packages</filename> directory. For more
information about the XML files in the
<filename>packages</filename> directory, please see <xref linkend="mimetypes-source-xml"/>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename><MIME>/<replaceable>MEDIA</replaceable>/<replaceable>SUBTYPE</replaceable>.xml</filename></term>
<listitem>
<para>These directories and files are automatically generated from
the collection of source XML files in the
<filename><MIME>/packages/</filename> subdirectory by the
<application>update-mime-database</application> application. For
example, for each <literal>mime-type</literal> element in the
<filename>/usr/share/mime/packages/freedesktop.org.xml</filename>
file, a directory is created at
<filename>/usr/share/mime/</filename> with the <emphasis>media
type</emphasis> of the MIME type. An XML file is created in that
directory with the <emphasis>subtype identifier</emphasis> of that
MIME type as well. The contents of the created XML file include
comments (and translations for them), subclasses designations and
aliases.</para>
<example>
<title>Beispiel: Datei <filename>/usr/share/mime/text/plain.xml</filename></title>
<para><programlisting><?xml version='1.0' encoding='utf-8'?>
<mime-type xmlns="http://www.freedesktop.org/standards/shared-mime-info" type="text/plain">
<!--Created automatically by update-mime-database. DO NOT EDIT!-->
<comment>plain text document</comment>
<!-- possibly more translations -->
<comment xml:lang="es">documento de texto sencillo</comment>
<comment xml:lang="eu">testu soileko dokumentua</comment>
<comment xml:lang="fi">perustekstiasiakirja</comment>
<comment xml:lang="fr">document plein texte</comment>
<!-- possibly more translations -->
</mime-type>
</programlisting>This file is generated by the
<application>update-mime-database</application> application,
using the default source XML file
<filename>freedesktop.org.xml</filename>.</para>
</example>
</listitem>
</varlistentry>
<varlistentry>
<term><filename><MIME>/globs</filename></term>
<listitem>
<para>Contains one line with a MIME type and a glob pattern,
separated by a colon. Files which match the glob pattern are
resolved to the MIME type specified before the colon. There are
special rules about how filenames are matched by the glob pattern;
for more details see the <citetitle>XDG shared mime
specification</citetitle>.</para>
<para>This file is also generated by the
<application>update-mime-database</application> application, using
the default source XML file
<filename>freedesktop.org.xml</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename><MIME>/magic</filename></term>
<listitem>
<para>A binary file which contains information on how to resolve
MIME types by <quote>sniffing</quote> the content of the file.
This is generally a set of one or more rules such as <quote>check
for the string <literal>%PDF- </literal>at byte offset 0 in the
file; if found, assign it the MIME type
<literal>application/pdf</literal></quote>.</para>
<para>Diese Datei wird auch durch den Befehl <application>update-mime-database</application> erzeugt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename><MIME>/XMLnamespaces</filename></term>
<listitem>
<para>Contains a mapping of XML namespaces to MIME types. Each
line contains three fields, the namespace, the localName and the
MIME type. Each field is separated by a space. If the localName is
empty, then there are two spaces between the namespace and the
MIME type.</para>
<para>Diese Datei wird auch durch den Befehl <application>update-mime-database</application> erzeugt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename><MIME>/aliases</filename></term>
<listitem>
<para>Contains a list of aliases for each MIME type. An alias is
simply a MIME type that is sometimes known as another type. For
each line in this file there are two fields: the first field is
the alias name, and the second field is the MIME type. The fields
are separated by a space.</para>
<para>Diese Datei wird auch durch den Befehl <application>update-mime-database</application> erzeugt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename><MIME>/subclasses</filename></term>
<listitem>
<para>Contains a list of subclassed MIME types and their
<quote>parent</quote> MIME type. From the <citetitle>XDG shared
mime specification:</citetitle><blockquote>
<para>A type is a subclass of another type if any instance of
the first type is also an instance of the second. For example,
all image/svg files are also text/xml, text/plain and
application/octet-stream files. Subclassing is about the
format, rather than the catagory of the data (for example,
there is no 'generic spreadsheet' class that all spreadsheets
inherit from).</para>
</blockquote>The format of this file is similar to the
<filename>aliases</filename> file. Each line contains two fields,
where the first field is the subclassed MIME type and the second
field is the parent MIME type. Each field is separated by a
space.</para>
<para>Diese Datei wird auch durch den Befehl <application>update-mime-database</application> erzeugt.</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2 id="mimetypes-refresh">
<title>Aktualisierung der MIME-Datenbank</title>
<para>Understanding how to refresh the MIME database is important for
administrators who wish to add new MIME types to the system, or
otherwise modify information about a MIME type. The application
<application>update-mime-database</application> is intended for this
purpose.</para>
<para>For example, if an application installs information about a new
MIME type to <filename>/usr/share/mime/packages/diff.xml</filename>,
then <application>update-mime-database</application> must be called with
the parameter <filename>/usr/share/mime</filename>.</para>
<screen><prompt>#</prompt> <userinput>update-mime-database /usr/share/mime</userinput>
<computeroutput>***
* Updating MIME database in /usr/share/mime...
***
</computeroutput></screen>
<para>The MIME database is refreshed by scanning all the source XML
files in the directory
<filename><MIME>/packages</filename>.</para>
</sect2>
</sect1>
<sect1 id="mimetypes-source-xml">
<title>The source XML files</title>
<anchor id="mimetypes-11"/>
<anchor id="mimetypes-12"/>
<anchor id="mimetypes-2"/>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>source XML files</secondary>
</indexterm>
<para>Located in the <filename><MIME>/packages</filename> directory,
these XML files provide all the information regarding MIME types that is
installed into the database by the
<application>update-mime-database</application> application. There are a
few rules about the XML file itself:</para>
<itemizedlist>
<listitem>
<para>It must specify the namespace as
<quote><literal>http://www.freedesktop.org/standards/shared-mime-info</literal></quote></para>
</listitem>
<listitem>
<para>The root element must be <literal>mime-info</literal></para>
</listitem>
<listitem>
<para>Zero or more <literal>mime-type</literal> elements can be
specified as children of the <literal>mime-info</literal> element. The
<literal>type</literal> attribute is used to specify the MIME type
that is being defined.</para>
</listitem>
</itemizedlist>
<para>By default, the <filename>freedesktop.org.xml</filename> file is
installed to the <filename>packages</filename> directory in one of the
<filename><MIME></filename> paths (usually
<filename>/usr/share/mime/packages</filename>).</para>
<para><xref linkend="mimetypes-mimeinfo-elements"/> gives a brief
description for each of the elements that can occur as children to the
<literal>mime-type</literal> element.</para>
<table frame="topbot" id="mimetypes-mimeinfo-elements">
<title>Child elements of <literal><mime-type></literal></title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="44.90*"/>
<colspec colwidth="59.10*"/>
<thead>
<row rowsep="1">
<entry>Element (and attributes)</entry>
<entry>Beschreibung</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal><glob pattern="<replaceable>*.xyz</replaceable>"></literal></entry>
<entry>This element specifies a glob pattern against filenames. If
the filename matches, then it is assigned the MIME type of the
parent <literal>mime-type</literal> element. The
<literal>pattern</literal> attribute is mandatory.</entry>
</row>
<row>
<entry><literal><magic priority="<replaceable>50</replaceable>"></literal></entry>
<entry>This element contains a list of <literal>match</literal>
elements as its children. The <literal>Priorität</literal>
attribute is optional, and specifies a priority between 0 and 100,
with 100 being the highest matching priority. Each child
<literal>match</literal> element has three required attributes:
<simplelist type="inline">
<member><literal>Typ</literal></member>
<member><literal>offset</literal></member>
<member><literal>Wert</literal></member>
</simplelist> and a fourth optional attribute,
<literal>mask</literal>. For details on these attributes, see the
<ulink url="http://www.freedesktop.org/Standards/shared-mime-info-spec">XDG
shared mime info specification</ulink>.</entry>
</row>
<row>
<entry><literal><alias type="<replaceable>media</replaceable>/<replaceable>subtype</replaceable>"></literal></entry>
<entry>This element defines an alias for the parent
<literal>mime-type</literal> element. An alias is simply a MIME
type that is sometimes known as another type. For example,
<literal>application/x-pdf</literal> is an alias for the MIME type
<literal>application/pdf</literal>.</entry>
</row>
<row>
<entry><literal><sub-class-of type="<replaceable>media</replaceable>/<replaceable>subtype</replaceable>"></literal></entry>
<entry>This element defines the parent
<literal>mime-type</literal> element as a subclass of the MIME
type specified in the <literal>Typ</literal> attribute. For
example, <literal>image/svg</literal> is a sub class of the MIME
type <literal>text/xml</literal>, <literal>text/plain</literal>,
and <literal>application/octet-stream</literal>.</entry>
</row>
<row>
<entry><literal><comment xml:lang="<replaceable>locale</replaceable>"></literal></entry>
<entry>This element provides a human readable description for the
MIME type. There can be zero or more occurrences of this element
as long as each one contains a unique value for the
<literal>xml:lang</literal> attribute.</entry>
</row>
<row>
<entry><literal><root-XML namespaceURI="<replaceable>Namensraum</replaceable>" localName=""></literal></entry>
<entry>If a file is determined to an XML file, then this element
helps to further classify it through the use of the
<literal>namespaceURI</literal> and <literal>localName</literal>
attributes, both of which are required. The attribute
<literal>namespaceURI</literal> is the namespace of the document,
and <literal>localName</literal> is the name of the root element
for the document. If <literal>localName</literal> is present but
its value is empty, then the root element may have any name, but
the namespace must still match.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>The easiest way to understand these files is to take a look at an
example. Borrowing from the <citetitle>XDG shared mime
specification</citetitle>, <xref linkend="mimetypes-source-xml-example"/>
displays the contents of a source XML file called
<filename>diff.xml</filename>. This example defines the MIME type
<literal>text/x-diff</literal>. There are multiple
<literal>comment</literal> elements which give a human readable name to
the MIME type in a number of different languages. This MIME type has both
rules for matching through glob patterns <emphasis>and</emphasis> through
the use of content <quote>sniffing</quote> (better known as
<filename>magic</filename> rules). Any file with the extension
<literal>.diff</literal> or <filename>.patch</filename> will resolve to
this MIME type. Additionally any file whose contents start with the
strings specified in the <literal>value</literal> attributes of the
<literal>match</literal> element, will resolve to the
<literal>text/x-diff</literal> MIME type.</para>
<para>The order in which glob patterns and magic rules apply is beyond the
scope of this document. For details on this, see the <ulink url="http://www.freedesktop.org/Standards/shared-mime-info-spec">XDG
shared mime info specification</ulink>.</para>
<example id="mimetypes-source-xml-example">
<title>Beispiel für eine XML-Quelldatei: <filename>diff.xml</filename></title>
<programlisting><?xml version='1.0'?>
<mime-info xmlns='http://www.freedesktop.org/standards/shared-mime-info'>
<mime-type type="text/x-diff">
<comment>Differences between files</comment>
<comment xml:lang="af">verskille tussen lêers</comment>
<!-- more translated comment elements -->
<magic priority="50">
<match type="string" offset="0" value="diff\t"/>
<match type="string" offset="0" value="***\t"/>
<match type="string" offset="0" value="Common subdirectories: "/>
</magic>
<glob pattern="*.diff"/>
<glob pattern="*.patch"/>
</mime-type>
</mime-info></programlisting>
</example>
</sect1>
<sect1 id="mimetypes-modifying">
<title>MIME-Typen bearbeiten …</title>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>verifying changes</secondary>
</indexterm>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>modifying</secondary>
</indexterm>
<para>You should never directly modify the source XML files that are
installed to the <filename><MIME>/packages</filename> directory by
applications. Instead, modify the <filename>Overrides.xml</filename> file.
This file has precedence over all other source XML files installed into
the same <filename>packages</filename> directory. If you are an
application author, then this rule does not apply. You should create a new
source XML file and place it in the proper
<filename><MIME>/packages</filename> directory (your
<filename>Makefile</filename> will take care of this, of course).</para>
<para>You can modify the MIME database for all users on the system or for
a particular user depending on the location of the file you change. To
modify the database for all users, make changes to the file
<filename>Overrides.xml</filename> in the
<filename>$XDG_DATA_DIRS/mime/packages</filename>
directory. To modify the database for a single user, make changes to the
file <filename>Overrides.xml</filename> in the
<filename>$XDG_DATA_HOME/mime/packages</filename>
directory.</para>
<para>After changes are made, you must always run the
<application>update-mime-database</application> application, with the
directory location of the MIME database as the first parameter.</para>
<sect2 id="mimetypes-addmodify">
<title>Hinzufügen oder Bearbeiten von MIME-Typen</title>
<para>So fügen Sie einen oder mehrere MIME-Typen für alle Benutzer hinzu:</para>
<orderedlist>
<listitem>
<para>Create or modify an existing
<filename>Overrides.xml</filename> source XML file, containing the
definitions for the MIME types. For more information, see <xref linkend="mimetypes-source-xml"/>.</para>
</listitem>
<listitem>
<para>Place the <filename>Overrides.xml</filename> file in the
<filename>/usr/share/mime/packages</filename> directory.</para>
</listitem>
<listitem>
<para>Update the MIME database by running
<application>update-mime-database</application> using the system
account.<screen><userinput>update-mime-database /usr/share/mime</userinput></screen></para>
</listitem>
</orderedlist>
<para>To add one or more MIME types for a single user, follow the same
steps, except place your <filename>Overrides.xml</filename> file in the
<filename>~/.local/share/mime/packages</filename> directory.
Additionally, call <application>update-mime-database</application> with
<filename>~/.local/share/mime/packages</filename> as the first
parameter.</para>
</sect2>
<sect2 id="mimetypes-verifying">
<title>Verifying Changes</title>
<anchor id="mimetypes-10"/>
<para>After you have made a change to the MIME database and refreshed
its contents, you can verify that the change has taken effect using the
<application>gnomevfs-info</application> application. This application
prints the MIME type and other useful information about a file.</para>
<para>Running <application>gnomevfs-info</application> on a SVG file
gives you the output shown below. You'll notice the default application
for this MIME type is <filename>eog.desktop</filename>; We will discuss
default applications in <xref linkend="mimetypes-registering"/>.</para>
<screen><prompt>$</prompt> <userinput>gnomevfs-info mime-diagram.svg</userinput>
<computeroutput>Name : mime-diagram.svg
Type : Regular
MIME type : image/svg+xml
Default app : eog.desktop
Size : 14869
Blocks : 32
I/O block size : 4096
Local : YES
SUID : NO
SGID : NO
Sticky : NO
Permissions : 600644
Link count : 1
UID : 1000
GID : 100
Access time : Wed Feb 22 18:24:47 2006
Modification time : Wed Feb 22 18:24:42 2006
Change time : Wed Feb 22 18:24:42 2006
Device # : 775
Inode # : 297252
Readable : YES
Writable : YES
Executable : NO</computeroutput>
<prompt>$</prompt>
</screen>
<para><xref linkend="mimetypes-newtype-example"/> walks through the steps of
creating a new MIME type and then verifying the changes using
<application>gnomevfs-info</application>.</para>
</sect2>
<sect2 id="mimetypes-newtype-example">
<title><literal>application/x-newtype</literal>-Beispiel</title>
<para>To create (or override) a MIME type and verify the changes:</para>
<orderedlist>
<listitem>
<para>Make a new, empty file in your home directory called
<filename>testing.xyz</filename>.</para>
</listitem>
<listitem>
<para>Use <application>gnomevfs-info</application> on the file to
find out the MIME type.The MIME type for this file should be
detected as <literal>text/plain</literal> because there are not any
glob patterns or magic rules that match it<footnote>
<para>When no glob patterns or magic rules match a file, then it
is resolved to the MIME type <literal>text/plain</literal> if it
contains textual data or
<literal>application/octet-stream</literal> for binary data. If
the file is empty, then it defaults to
<literal>text/plain</literal>.</para>
</footnote>.</para>
</listitem>
<listitem>
<para>Create (or modify) the <filename>Overrides.xml</filename> file
as described in <xref linkend="mimetypes-addmodify"/> with the
contents given in <xref linkend="mimetypes-overrides-xml"/>.</para>
</listitem>
<listitem>
<para>Refresh the database using
<application>update-mime-database</application>.</para>
</listitem>
<listitem>
<para>Use <application>gnomevfs-info</application> to verify that
your change has taken effect. You should see the MIME type for the
<filename>testing.xyz</filename> file resolved as
<literal>application/x-newtype</literal>.</para>
<screen><prompt>$</prompt> <userinput>gnomevfs-info testing.xyz | grep MIME
</userinput><computeroutput>MIME type : application/x-newtype
</computeroutput><prompt>$</prompt></screen>
</listitem>
</orderedlist>
<example id="mimetypes-overrides-xml">
<title>Die Datei <filename>Overrides.xml</filename></title>
<programlisting><?xml version='1.0' encoding='utf-8'?>
<mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info">
<mime-type type="application/x-newtype"><comment>new mime type</comment><glob pattern="*.xyz"/></mime-type>
</mime-info></programlisting>
</example>
</sect2>
</sect1>
<sect1 id="mimetypes-registering">
<title>Registrieren von Anwendungen für MIME-Typen</title>
<anchor id="mimetypes-7"/>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>registering applications for</secondary>
</indexterm>
<indexterm>
<primary>Anwendungen</primary>
<secondary>registry</secondary>
</indexterm>
<para>Registering applications to handle MIME types is fairly
straightforward. Applications are registered by creating a
<literal>MimeType</literal> key in their <filename>.desktop</filename>
entry file and listing each MIME type separated by a semicolon. The
<literal>MimeType</literal> key should only be used in
<filename>.desktop</filename> files whose <literal>Type</literal> key has
the value <quote><literal>Application</literal></quote>. For more
information on <filename>.desktop</filename> files, see <xref linkend="menustructure-desktopentry"/>.</para>
<para>After creating or modifying a <filename>.desktop</filename> entry
file, you must update the application database using the
<application>update-desktop-database</application> application (very
similar to <application>update-mime-database</application>, except it does not take a
parameter). This will create a
<filename>mimeinfo.cache</filename> file in the
<filename>applications</filename> subdirectory for each directory in
<filename>$XDG_DATA_HOME:$XDG_DATA_DIRS</filename>.
The cache file is necessary so that all the <filename>.desktop</filename>
files do not need to be scanned for just the <literal>MimeType</literal>
key, as this causes unnecessary disk I/O.</para>
<para>Default applications to use for specific MIME types should be
specified in a file called <filename>defaults.list</filename>. This file
is located in the <filename>applications</filename> subdirectory for each
directory in <envar>$XDG_DATA_HOME</envar> and
<envar>$XDG_DATA_DIRS</envar>. The format for this file consists of the
MIME type, the <literal>=</literal> symbol and the Desktop File ID (which
is the filename for the desktop entry file). <xref linkend="mimetypes-registering-example"/> is a short example of a
<filename>defaults.list</filename> file in a user's
<filename>~/.local/share/applications</filename> directory.</para>
<example id="mimetypes-registering-example">
<title>Die Datei <filename>defaults.list</filename> eines Benutzers</title>
<programlisting>[Default Applications]
application/pdf=evince.desktop
text/html=epiphany.desktop
text/plain=gedit.desktop
image/jpeg=eog.desktop
image/png=eog.desktop
text/xml=gedit.desktop
</programlisting>
</example>
<note>
<title>XDG Desktop Entry Specification</title>
<para>How to register MIME types for applications is part of the <ulink url="http://www.freedesktop.org/wiki/Standards/desktop-entry-spec">XDG desktop entry specification</ulink>, rather than the
<ulink url="http://www.freedesktop.org/Standards/shared-mime-info-spec">XDG
shared mime info specification</ulink>.</para>
</note>
</sect1>
<sect1 id="mimetypes-9">
<title>Hinzufügen einer Anwendung zum GNOME-Desktop</title>
<indexterm>
<primary>MIME-Typen</primary>
<secondary>Anwendungen hinzufügen</secondary>
</indexterm>
<indexterm>
<primary>Anwendungen</primary>
<secondary>hinzufügen</secondary>
</indexterm>
<para>Um eine neue Anwendung zum GNOME-Desktop hinzuzufügen, gehen Sie wie folgt vor:</para>
<orderedlist>
<listitem>
<para>Fügen Sie einen Menüeintrag für die Anwendung hinzu. Weitere Informationen über das Hinzufügen eines Eintargs zu einem Menü finden Sie in <xref linkend="menustructure-2"/>.</para>
</listitem>
<listitem>
<para>Add an icon for the application to
<filename>/usr/share/icons/<replaceable>theme-name</replaceable>/<replaceable>icon-size</replaceable>/apps</filename>.
For more information on icons and themes, see <xref linkend="themes-11"/>.</para>
</listitem>
<listitem>
<para>If the application uses a new MIME type, add a source XML file
to the MIME database. For more information, see <xref linkend="mimetypes-modifying"/>.</para>
</listitem>
<listitem>
<para>If the application uses a new MIME type, add an icon for the
MIME type to
<filename>/usr/share/icons/<replaceable>theme-name</replaceable>/<replaceable>icon-size</replaceable>/mimetypes</filename>.
For more information on icons and themes, see <xref linkend="themes-0"/>.</para>
</listitem>
<listitem>
<para>To associate the application with a MIME type, include a
<literal>MimeType</literal> key in your <filename>.desktop</filename>
file. For more information, see <xref linkend="mimetypes-registering"/>.</para>
</listitem>
</orderedlist>
</sect1>
</chapter>
<chapter id="screensavers-0">
<title>Setting Screensavers</title>
<highlights>
<para>This chapter describes how to set preferences for the screensaver.
This chapter also provides information on how to modify the displays that
are available for the screensaver.</para>
</highlights>
<sect1 id="screensavers-1">
<title>Einführung in Bildschirmschoner</title>
<indexterm>
<primary>Bildschirmschoner</primary>
<secondary>Einführung</secondary>
</indexterm>
<indexterm>
<primary>gnome-screensaver</primary>
<see>Bildschirmschoner</see>
</indexterm>
<para>A <firstterm>screensaver</firstterm> is an application that
replaces the image on a screen when the screen is not in use. The screensaver
application for the GNOME Desktop is <application>gnome-screensaver</application>.
The following sections describe how to set preferences for the <application>gnome-screensaver</application> application, and how to change the themes that
are available for the screensaver.</para>
</sect1>
<sect1 id="screensavers-2">
<title>Einstellungen des Bildschirmschoners ändern</title>
<indexterm>
<primary>Bildschirmschoner</primary>
<secondary>setting preferences</secondary>
</indexterm>
<para>All screensaver preferences and settings are stored in <application>GConf</application>.</para>
<para>To modify screensaver application preferences, users can use the <application>Screensaver</application> preference tool. For information on screensaver preferences, see <citetitle>GNOME Desktop User's Guide</citetitle>.</para>
<para>Sie können auch den Befehl <command>/usr/bin/gnome-screensaver-preferences</command> ausführen, um den Dialog <guilabel>Bildschirmschoner-Einstellungen</guilabel> zu öffnen.</para>
<para>To set default screensaver settings and policy for all users, modify the screensaver settings in the Default GConf Configuration Source.</para>
<para>To set mandatory screensaver settings and policy for all users, modify the screensaver settings in the Mandatory GConf Configuration Source.</para>
</sect1>
<sect1 id="screensavers-3">
<title>Ändern von Bildschirmschoner-Themen</title>
<indexterm>
<primary>Bildschirmschoner</primary>
<secondary>Ändern von Bildschirmschoner-Themen</secondary>
</indexterm>
<para>The screensaver application allows users
to choose one or more <firstterm>screensaver themes</firstterm>. A screensaver
theme is an application that displays images on the screen of the user when
the screen is not in use. The available screensaver themes are listed in the <application>Screensaver</application> preference tool.</para>
<para>To add a new screensaver theme, copy the executable file for the <firstterm>screensaver theme engine</firstterm> to somewhere in your PATH or into the
screensaver theme engine executable directory. The screensaver theme engine executable directory for your system can be determined using the following command:
<screen><userinput>pkg-config --variable=privlibexecdir gnome-screensaver</userinput></screen>
Next, add a <filename>.desktop</filename> file for the theme into the screensaver themes directory. The screensaver themes directory for your system
can be determined using the following command:
<screen><userinput>pkg-config --variable=themesdir gnome-screensaver</userinput></screen>
In the Exec field of the <filename>.desktop</filename> file include any arguments that are required to run the screensaver
theme on the whole screen, rather than in a window. For example, some legacy screensaver theme engines may require you
to include the <literal>-root</literal> option to display the screensaver
display on the whole screen.</para>
<para>The <application>Screensaver</application> infrastructure implements themes according to the <ulink url="http://www.freedesktop.org/wiki/Standards/menu-spec">XDG menu
specification</ulink>. By supporting this specification, GNOME allows you
to:</para>
<itemizedlist>
<listitem>
<para>Customize the themes easily. You can edit a small number
of files to customize the available themes. You do not need to modify
your applications or move files.</para>
</listitem>
<listitem>
<para>Install themes easily. You do not need to provide
information about the system when you install
the themes.</para>
</listitem>
<listitem>
<para>Configure the system so that users cannot modify the themes.</para>
</listitem>
</itemizedlist>
<para>Weitere Informationen finden Sie in <xref linkend="menustructure-0"/>.</para>
</sect1>
</chapter>
<chapter id="sessions-0">
<title>Sitzungsverwaltung</title>
<highlights>
<para>This chapter introduces session management, and describes
how to set session defaults. The chapter also contains information on sessions
and login scripts.</para>
</highlights>
<sect1 id="sessions-1">
<title>Einführung in Sitzungen</title>
<indexterm>
<primary>Sitzungen</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>A session occurs between the time that a user logs in to
the GNOME Desktop and the time that the user logs out. The session manager
starts after the <application>Login Manager</application> authenticates the
user. The session manager enables the user to manage the session. For example,
a user can save the state of a session and return to that session the next
time that the user logs in. </para>
<para>In einer Sitzung müssen mindestens die folgenden Anwendungen laufen:</para>
<itemizedlist>
<listitem>
<para>Der Sitzungsmanager, <command>gnome-session</command>.</para>
</listitem>
<listitem>
<para>The <application>GConf</application> X settings daemon, <command>gnome-settings-daemon</command>.</para>
</listitem>
<listitem>
<para>The <application>gnome-panel</application> application, which
runs the panels in the GNOME Desktop.</para>
</listitem>
<listitem>
<para>Der Fenstermanager <application>Metacity</application>.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="sessions-3">
<title>Festlegen von Sitzungs-Einstellungen</title>
<indexterm>
<primary>Sitzungen</primary>
<secondary>setting defaults</secondary>
</indexterm>
<para>Die folgende Tabelle listet die Dateien auf, die die vorgegebenen Sitzungsinformationen enthalten:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="51.80*"/>
<colspec colwidth="48.20*"/>
<thead>
<row rowsep="1">
<entry>
<para>Datei</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>
<filename>/usr/share/gnome/default.session</filename>
</para>
</entry>
<entry valign="top">
<para>Default session file.
Default session details are stored in this file.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>$HOME/.gnome2/session</filename>
</para>
</entry>
<entry valign="top">
<para>User session file. When a user modifies the session,
the details are stored in this file.</para>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<!--The last row does not appear to be true in Mercury - check.-->
<para>To set default session details for all users, modify the default session
file. </para>
<para>To restore the default session settings for a user, delete the session
file from the home directory of the user. If no user session file is present,
the default settings in <filename>/usr/share/gnome/default.session</filename>
are used. </para>
<para>To save the current session as the default session, users can run the <command>gnome-session-save</command> command. </para>
</sect1>
</chapter>
<chapter id="help-0">
<title>Hilfesystem</title>
<highlights>
<para>Dieser Abschnitt beschreibt das Hilfesystem des GNOME-Desktops.</para>
</highlights>
<sect1 id="help-1">
<title>Einführung in das Hilfesystem</title>
<indexterm>
<primary>Online-Hilfe</primary>
<see>Hilfe</see>
</indexterm>
<indexterm>
<primary>Hilfe</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>The GNOME Desktop displays help in the <application>Yelp</application> Help
browser. For more information, see <ulink url="ghelp:user-guide?yelp">Yelp Help Browser</ulink> in the
<ulink url="ghelp:user-guide">GNOME Desktop User Guide</ulink>.</para>
<para>The source documents for the help are XML files. The XML files are
written to the DocBook XML Version 4.1.2 document type definition (DTD). The
DocBook XML files are converted to HTML using stylesheets installed with <application>
gnome-doc-utils</application> and the HTML is displayed in the
help browser. For more information on DocBook XML, see the following URL:</para>
<literallayout>
<ulink url="http://www.oasis-open.org/docbook/xml/">http://www.oasis-open.org/docbook/xml</ulink>
</literallayout>
<para>The Help system uses <firstterm>Open Source Metadata Framework</firstterm>
(OMF) files, and a cataloging system. The next sections describe OMF files
and the cataloging system.</para>
</sect1>
<sect1 id="help-3">
<title>OMF-Dateien</title>
<indexterm>
<primary>.omf-Dateien</primary>
<see>OMF-Dateien</see>
</indexterm>
<indexterm>
<primary>Hilfe</primary>
<secondary>OMF-Dateien</secondary>
</indexterm>
<indexterm>
<primary>OMF-Dateien</primary>
</indexterm>
<para>The XML file for each manual
has an associated OMF file. The OMF file contains information about the manual
that is used by the Help browser. OMF files have a <filename>.omf</filename>
extension.</para>
<para>When you install an application, the installation process installs an
OMF file to a directory of OMF files. If a Help document has an associated
OMF file in an OMF file directory, the Help document is displayed in the Help
browser.</para>
<para>OMF-Dateien enthalten Informationen über Hilfedokumente wie folgt:</para>
<itemizedlist>
<listitem>
<para>Der Ort der XML-Datei für das Hilfedokument</para>
</listitem>
<listitem>
<para>Der Titel eines Hilfedokuments</para>
</listitem>
<listitem>
<para>A subject category to which the Help document belongs</para>
</listitem>
</itemizedlist>
<para>For more information on how to create OMF files, please see
<ulink url="ghelp:writing_scrollkeeper_omf_files">Writing Scrollkeeper
OMF Files</ulink>.</para>
</sect1>
<sect1 id="help-2">
<title>ScrollKeeper-Katalogisierungssystem</title>
<indexterm>
<primary>Hilfe</primary>
<secondary>ScrollKeeper-Katalogisierungssystem</secondary>
</indexterm>
<indexterm>
<primary>ScrollKeeper-Katalogisierungssystem</primary>
</indexterm>
<para><application>ScrollKeeper</application> is a cataloging
system for documentation. Its primary function is to manage the information in
OMF files for the help browser. When you install an application, the
OMF file is copied to the <filename>
<replaceable>$prefix</replaceable>/share/omf/<replaceable><application-name></replaceable>
</filename> directory.
</para>
<para><application>ScrollKeeper</application> builds a table of contents from the
collection of OMF files in the directories specified in
<filename><replaceable>$prefix</replaceable>/etc/scrollkeeper.conf</filename> file.
This file usually consists of a single line with the <varname>OMF_DIR</varname>
set to a comma separated list of directories to recursively search.</para>
<programlisting>OMF_DIR=/usr/share/omf:/usr/local/share/omf:/opt/gnome2/share/omf:/opt/kde/omf
</programlisting>
<para><application>ScrollKeeper</application> contains a hierarchy of subject
categories to which a help document can belong. The subject category of the document
in the OMF file determines the location of the document in the table of contents presented
by the help browser.</para>
<para>The hierarchy of subject categories is defined in the file
<filename>
<replaceable>$prefix</replaceable>/scrollkeeper/Templates/<replaceable><lang></replaceable>/scrollkeeper_cl.xml</filename>.
The subject category of a document must correspond to a category specified in this file.</para>
<para>For more information on the <application>Scrollkeeper</application> system,
visit the website at
<ulink url="http://scrollkeeper.sourceforge.net/">http://scrollkeeper.sourceforge.net/</ulink>.
</para>
<note>
<para>If the help document XML file is moved to a new location, then
the location in the OMF file needs to be updated.</para>
</note>
</sect1>
</chapter>
<chapter id="performance-0">
<title>Verbessern der Leistung</title>
<highlights>
<para>This chapter describes how to improve the performance of
the GNOME Desktop.</para>
</highlights>
<sect1 id="performance-1">
<title>Einführung in die Leistungsverbesserung</title>
<indexterm>
<primary>Leistung verbessern</primary>
<secondary>Einführung</secondary>
</indexterm>
<para>This chapter lists several preferences whose
settings you can change to improve the performance of the GNOME Desktop. You
can use the <command>gconftool-2</command> command to set values for preferences
for users. The example commands in this chapter show how to set values in
the user configuration source.</para>
<para>You can also use the <literal>--direct</literal> and <literal>--config-source</literal> options to set mandatory values or default values for preferences.
You can also use the <command>gconftool-2</command> command in a script to
set the values of many preferences. For more information on the <command>gconftool-2</command> command and the options that are available with the
command, see <xref linkend="gconf-0"/>.</para>
</sect1>
<sect1 id="performance-8">
<title>Reduzierung der Prozessorlast</title>
<indexterm>
<primary>Leistung verbessern</primary>
<secondary>reducing CPU
usage</secondary>
</indexterm>
<indexterm>
<primary>reducing</primary>
<secondary>Prozessorlast</secondary>
</indexterm>
<indexterm>
<primary>Prozessorlast</primary>
<secondary>reducing</secondary>
</indexterm>
<para>This section describes preferences that
you can set to reduce CPU usage by the GNOME Desktop. </para>
<sect2 id="performance-3">
<title>Verwendung von Themenoptionen mit geringeren Ansprüchen an die Prozessorleistung</title>
<indexterm>
<primary>Themen</primary>
<secondary>window frame options</secondary>
<tertiary>and CPU usage</tertiary>
</indexterm>
<indexterm>
<primary>Themen</primary>
<secondary>and CPU usage</secondary>
</indexterm>
<para>Some window frame theme
options load image files to draw the window frame. Other options use simpler
techniques to draw the window frame.</para>
<para>The Crux window frame option loads image files, and can be slow on systems
with limited CPU resources. To reduce CPU usage, use one of the following
window frame options: </para>
<itemizedlist>
<listitem>
<para>Atlanta</para>
</listitem>
<listitem>
<para>Esco</para>
</listitem>
</itemizedlist>
<para>The following window frame options also use less CPU resources than
Crux:</para>
<itemizedlist>
<listitem>
<para>AgingGorilla</para>
</listitem>
<listitem>
<para>Helligkeit</para>
</listitem>
<listitem>
<para>Metabox</para>
</listitem>
</itemizedlist>
<note>
<para>Metabox does not work well with inverse controls options such
as HighContrastInverse. Use Atlanta with inverse controls options.</para>
</note>
<para><indexterm><primary>themes</primary><secondary>window frame options</secondary><tertiary>changing</tertiary></indexterm>To change the window
frame theme option, run the following command: </para>
<screen><userinput>gconftool-2 \
--type string \
--set /apps/metacity/general/theme <replaceable>option-name</replaceable></userinput></screen>
<para>Um beispielsweise Atlanta zu verwenden, führen Sie folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 \
--type string \
--set /apps/metacity/general/theme Atlanta</userinput></screen>
<para>Alternatively, users can use the <application>Theme</application> preference
tool to select the appropriate option.</para>
<tip>
<para>You can use the <application>Metacity Theme Viewer</application>
to measure the performance of a window frame option, and to preview the option.
To start <application>Metacity Theme Viewer</application>, use the following
command:</para>
<screen><userinput>metacity-theme-viewer <replaceable>option-name</replaceable></userinput></screen>
<para>For example, to measure the performance of Atlanta and preview Atlanta,
run the following command: </para>
<screen><userinput>metacity-theme-viewer Atlanta</userinput></screen>
</tip>
</sect2>
<sect2 id="performance-2">
<title>Verminderung der Prozessorlast durch Abschalten der Symbolanzeige in Menüs</title>
<indexterm>
<primary>icons, in menus</primary>
<see>Menüsymbole</see>
</indexterm>
<indexterm>
<primary>Menüsymbole</primary>
<secondary>and CPU usage</secondary>
</indexterm>
<indexterm>
<primary>Menüsymbole</primary>
<secondary>turning off</secondary>
</indexterm>
<para>Einige Einträge zeigen Symbole neben dem Eintrag an. Um diese Funktion abzuschalten, führen sie den folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 \
--type bool \
--set /desktop/gnome/interface/menus_have_icons false</userinput></screen>
<para>Alternatively, users can use the <application>Menus & Toolbars</application>
preference tool to deselect the <guilabel>Show icons in menus</guilabel> option.</para>
</sect2>
<sect2 id="performance-6">
<title>So reduzieren Sie die Prozessorlast durch Abschalten des Begrüßungsbildschirms</title>
<indexterm>
<primary>Begrüßungsbildschirm</primary>
<secondary>and CPU usage</secondary>
</indexterm>
<para>By default, when users log in to the desktop environment,
a splash screen is displayed. Icons are displayed on the splash screen while
the user logs in. You can turn off the splash screen to reduce CPU usage during
login. </para>
<para><indexterm><primary>splash screen</primary><secondary>turning off</secondary></indexterm>To turn off the splash screen, run the following command:</para>
<screen><userinput>gconftool-2 \
--type bool \
--set /apps/gnome-session/options/show_splash_screen false</userinput></screen>
<para>Alternatively, users can use the <application>Sessions</application>
preference tool to deselect the <guilabel>Show splash screen on login</guilabel>
option.</para>
</sect2>
<sect2 id="performance-4">
<title>So reduzieren Sie die Prozessorlast durch Abschalten der Panel-Animation</title>
<indexterm>
<primary>Panels</primary>
<secondary>Animationen ausschalten</secondary>
</indexterm>
<para>When users show or hide panels, the panels can show or hide
in an animated style. To turn off panel animation, run the following command: </para>
<screen><userinput>gconftool-2 \
--type bool \
--set /apps/panel/global/enable_animations false</userinput></screen>
<para>Alternatively, users can use the <application>Panel</application> preference
tool to deselect the <guilabel>Drawer and panel animation</guilabel> option.</para>
</sect2>
<sect2 id="performance-7">
<title>Verbesserung der Leistung des Dateimanagers</title>
<indexterm>
<primary>Nautilus</primary>
<see>Datei-Manager</see>
</indexterm>
<para>The <application>Nautilus</application> file manager includes some features
that you can modify to improve performance.</para>
<sect3 id="performance-9">
<title>To Modify Performance Preferences</title>
<indexterm>
<primary>Datei-Manager</primary>
<secondary>modifying performance
preferences</secondary>
</indexterm>
<para>The file manager includes performance-related
preferences. Each performance preference can take one of three values. The
values are described in the following table:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="34.46*"/>
<colspec colwidth="65.54*"/>
<thead>
<row rowsep="1">
<entry>
<para>Wert</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>
<literal>always</literal>
</para>
</entry>
<entry valign="top">
<para>Führt die Aktion für sowohl lokale Dateien als auch Dateien in anderen Dateisystemen aus.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>local_only</literal>
</para>
</entry>
<entry valign="top">
<para>Performs the action for local files only. When you
set a performance preference to <literal>local_only</literal>, the CPU usage
is reduced.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>never</literal>
</para>
</entry>
<entry valign="top">
<para>Never performs the action. When you set a performance preference
to never, the CPU usage and the network traffic are reduced.</para>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>The following table describes the performance preferences for the file
manager. For the fastest performance, set the value of the preferences to <literal>never</literal>.</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="43.34*"/>
<colspec colwidth="56.66*"/>
<thead>
<row rowsep="1">
<entry>
<para>Einstellung</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>
<literal>show_icon_text</literal>
</para>
</entry>
<entry valign="top">
<para>Specifies when to preview the content of text files
in the icon that represents the file. To never preview the content of text
files, run the following command: </para>
<screen><userinput>gconftool-2 \
--type string \
--set /apps/nautilus/preferences/show_icon_text never</userinput></screen>
<para>Alternativ können Benutzer die folgenden Schritte ausführen:</para>
<orderedlist>
<listitem>
<para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Preview</guilabel>.</para>
</listitem>
<listitem>
<para>Select an option for the <guilabel>Show text in icons</guilabel>
preference.</para>
</listitem>
</orderedlist>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>show_directory_item_counts</literal>
</para>
</entry>
<entry valign="top">
<para>Specifies when to show the number of items in folders.
To never show the number of items in folders, run the following command:</para>
<screen><userinput>gconftool-2 \
--type string \
--set /apps/nautilus/preferences/show_directory_item_counts never</userinput></screen>
<para>Alternativ können Benutzer die folgenden Schritte ausführen:</para>
<orderedlist>
<listitem>
<para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Preview</guilabel>.</para>
</listitem>
<listitem>
<para>Select an option for the <guilabel>Count number of items</guilabel>
preference.</para>
</listitem>
</orderedlist>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>show_image_thumbnails</literal>
</para>
</entry>
<entry valign="top">
<para>Specifies when to show thumbnails of image files.
To never show thumbnails, run the following command:</para>
<screen><userinput>gconftool-2 \
--type string \
--set /apps/nautilus/preferences/show_image_thumbnails never</userinput></screen>
<para>Alternativ können Benutzer die folgenden Schritte ausführen:</para>
<orderedlist>
<listitem>
<para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Preview</guilabel>.</para>
</listitem>
<listitem>
<para>Select an option for the <guilabel>Show thumbnails</guilabel>
preference.</para>
</listitem>
</orderedlist>
</entry>
</row>
<row>
<entry valign="top">
<para>
<literal>preview_sound</literal>
</para>
</entry>
<entry valign="top">
<para>Specifies when to preview the content of sound files.
To never preview the content of sound files, run the following command:</para>
<screen><userinput>gconftool-2 \
--type string \
--set /apps/nautilus/preferences/preview_sound never</userinput></screen>
<para>Alternativ können Benutzer die folgenden Schritte ausführen:</para>
<orderedlist>
<listitem>
<para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Preview</guilabel>.</para>
</listitem>
<listitem>
<para>Select an option for the <guilabel>Preview sound files</guilabel>
preference.</para>
</listitem>
</orderedlist>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect3>
<sect3 id="performance-10">
<title>So deaktivieren Sie die Seitenleiste, die Werkzeugleiste und die Adressleiste</title>
<indexterm>
<primary>Datei-Manager</primary>
<secondary>Seitenleiste abschalten</secondary>
</indexterm>
<para>The file manager includes preferences that enable
you to turn off the side pane and the toolbar. To improve file manager performance,
turn off the side pane and the toolbar.</para>
<para>Um die Seitenleiste zu deaktivieren, führen Sie den folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 \
--type bool \
--set /apps/nautilus/preferences/start_with_sidebar false</userinput></screen>
<para><indexterm><primary>file manager</primary><secondary>toolbar, turning off</secondary></indexterm>Um die Werkzeugleiste zu deaktivieren, führen Sie folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 \
--type bool \
--set /apps/nautilus/preferences/start_with_toolbar false</userinput></screen>
<para>You can also turn off the location bar. Users can use the <keycombo><keycap>Ctrl</keycap><keycap>L</keycap></keycombo> keyboard shortcut to display a location bar
when required. </para>
<para><indexterm><primary>file manager</primary><secondary>location bar, turning
off</secondary></indexterm>To turn off the location bar, run the following
command:</para>
<screen><userinput>gconftool-2 \
--type bool \
--set /apps/nautilus/preferences/start_with_location_bar false</userinput></screen>
</sect3>
<sect3 id="performance-11">
<title>Den Desktop abschalten</title>
<indexterm>
<primary>Datei-Manager</primary>
<secondary>Desktop abschalten</secondary>
</indexterm>
<indexterm>
<primary>Desktop</primary>
<secondary>turning
off</secondary>
</indexterm>
<para>The file manager contains a preference that
enables users to use <application>Nautilus</application> to manage the desktop.
You can disable the desktop to improve performance. However, if you disable
the desktop, you cannot do the following:</para>
<itemizedlist>
<listitem>
<para>Use the file manager to change the pattern or color of the
desktop background. </para>
</listitem>
<listitem>
<para>Use the desktop objects, such as <guilabel>Trash</guilabel>.
The desktop objects are not displayed on the desktop. </para>
</listitem>
</itemizedlist>
<para>Um den Desktop zu deaktivieren, führen sie folgenden Befehl aus:</para>
<screen><userinput>gconftool-2 \
--type bool \
--set /apps/nautilus/preferences/show_desktop false</userinput></screen>
</sect3>
</sect2>
</sect1>
<sect1 id="performance-12">
<title>Reducing X Window System Network Traffic</title>
<indexterm>
<primary>reducing</primary>
<secondary>X Window System network traffic</secondary>
</indexterm>
<indexterm>
<primary>X Window System network traffic,
reducing</primary>
</indexterm>
<indexterm>
<primary>Netzwerkverkehr, reduzieren</primary>
</indexterm>
<para>This section describes preferences that you can
set to reduce X Window System network traffic on the GNOME Desktop. </para>
<sect2 id="performance-14">
<title>To Use Theme Options Which Create Less Network Traffic</title>
<indexterm>
<primary>Themen</primary>
<secondary>window frame options</secondary>
<tertiary>and network traffic</tertiary>
</indexterm>
<indexterm>
<primary>Themen</primary>
<secondary>and network traffic</secondary>
</indexterm>
<para>Remote
display protocols do not transfer every pixel in a block of pixels if all
pixels in the block are the same color.</para>
<para>To reduce X Window System network traffic, use a window frame theme
option that uses solid colors. That is, use one of the following window frame
options:</para>
<itemizedlist>
<listitem>
<para>Atlanta</para>
</listitem>
<listitem>
<para>Esco</para>
</listitem>
</itemizedlist>
<para>For information on how to change theme options, see <xref linkend="performance-3"/>.</para>
</sect2>
<sect2 id="performance-15">
<title>To Reduce Network Traffic by Turning Off Display of Icons in Menus</title>
<indexterm>
<primary>Menüsymbole</primary>
<secondary>and network traffic</secondary>
</indexterm>
<para>Some items in menus display an icon beside the item. If
the icon is located on another file system, this feature can increase X Window
System network traffic. This feature can also increase X Window System network
traffic if the panels are displayed on a remote host. </para>
<para>For information on how to turn off this feature, see <xref linkend="performance-2"/>.</para>
</sect2>
</sect1>
<sect1 id="performance-17">
<title>Reducing Color Usage and Improving Display Quality</title>
<indexterm>
<primary>reducing</primary>
<secondary>color usage</secondary>
</indexterm>
<indexterm>
<primary>color usage</primary>
<secondary>reducing</secondary>
</indexterm>
<indexterm>
<primary>display quality, improving</primary>
</indexterm>
<para>Viele moderne Computersysteme unterstützen 24 Bit Farbtiefe oder 16777216 Farben. Jedoch verwenden viele Benutzer noch Systeme mit 8 Bit Farbtiefe, also 256 Farben.</para>
<para>The GNOME Desktop uses the <firstterm>websafe color palette</firstterm>.
This palette is a general-purpose palette of 216 colors, which is designed
to optimize the use of color on systems that support 8-bit color. However,
some visual components of the GNOME Desktop are designed for systems that
support 24-bit color.</para>
<para>The following display problems might occur on systems that support 8-bit
color:</para>
<itemizedlist>
<listitem>
<para>Windows, icons, and background images might appear grainy.
Many themes, background images, and icons use colors that are not in the
websafe color palette. The colors that are not in the palette are replaced
with the nearest equivalent or a dithered approximation. This use of replacement
colors causes the grainy appearance.</para>
</listitem>
<listitem>
<para>Applications that do not use the websafe color palette have
less colors available. Color errors might occur. Some colors might not appear
in the user interface of the application. Some applications might crash if
the application cannot allocate colors.</para>
</listitem>
<listitem>
<para>Color flashing might occur when users switch between applications
that use the websafe color palette, and applications that do not use this
palette. The applications that do not use the websafe color palette might
use a custom colormap. When the custom colormap is used, other visual components
might lose colors, then become unviewable.</para>
</listitem>
</itemizedlist>
<para>Der folgende Abschnitt beschreibt, wie sich das Erscheinungsbild des GNOME-Desktops für Systeme optimieren lässt, die lediglich 8 Bit Farbtiefe unterstützen.</para>
<sect2 id="performance-20">
<title>To Use Theme Options That Use the Websafe Color Palette</title>
<indexterm>
<primary>Themen</primary>
<secondary>window frame options</secondary>
<tertiary>and color usage</tertiary>
</indexterm>
<indexterm>
<primary>Themen</primary>
<secondary>and color usage</secondary>
</indexterm>
<para>Some window
frame theme options use colors that are in the websafe color palette. Bright
and Esco use colors from the websafe color palette. Bright and Esco do not
have the grainy appearance of other window frame options on 8-bit color displays.
Use Bright or Esco for the best color display on 8-bit visual modes. </para>
<para>For information on how to change theme options, see <xref linkend="performance-3"/>.</para>
</sect2>
<sect2 id="performance-21">
<title>To Reduce Color Usage by Turning Off Display of Icons in Menus</title>
<indexterm>
<primary>Menüsymbole</primary>
<secondary>and color usage</secondary>
</indexterm>
<para>Some items in menus display an icon beside the item. If
the icon contains colors that are not in the websafe color palette, this feature
can increase the number of colors used.</para>
<para>For information on how to turn off this feature, see <xref linkend="performance-2"/>.</para>
</sect2>
<sect2 id="performance-18">
<title>To Reduce Color Usage by Turning Off the Splash Screen</title>
<indexterm>
<primary>Begrüßungsbildschirm</primary>
<secondary>and color usage</secondary>
</indexterm>
<para>You can turn off the splash screen to make more colors available
for the GNOME Desktop and for applications.</para>
<para>For information on how to turn off the splash screen, see <xref linkend="performance-6"/>.</para>
</sect2>
<sect2 id="performance-19">
<title>To Reduce Color Usage by Using a Solid Color for the Background</title>
<indexterm>
<primary>Hintergrund</primary>
<secondary>einfache Farbe verwenden</secondary>
</indexterm>
<para>Use a solid color for the desktop background. Use of a solid
color reduces the number of colors used by the GNOME Desktop. </para>
<para>To set a solid color for the background, run the following commands: </para>
<screen><userinput>gconftool-2 \
--type string \
--set /desktop/gnome/background/picture_options none</userinput></screen>
<screen><userinput>gconftool-2 \
--type string \
--set /desktop/gnome/background/color_shading_type solid</userinput></screen>
<screen><userinput>gconftool-2 \
--type string \
--set /desktop/gnome/background/primary_color #<replaceable>Hexadezimalfarbwert</replaceable></userinput></screen>
<para>Alternatively, users can use the <application>Background</application>
preference tool to choose a solid color for the background.</para>
</sect2>
</sect1>
</chapter>
<chapter id="lockdown-0">
<title>Deaktivieren von GNOME-Desktop-Funktionen</title>
<highlights>
<para>Dieser Abschnitt beschreibt, wie Sie einzelne Funktionsmerkmale des GNOME-Desktops deaktivieren können.</para>
</highlights>
<sect1 id="lockdown-1">
<title>Einführung in die Deaktivierung von Funktionsmerkmalen des GNOME-Desktops</title>
<indexterm>
<primary>Funktionen abschalten</primary>
<secondary>Einführung</secondary>
</indexterm>
<indexterm>
<primary>lockdown</primary>
<see>Funktionen abschalten</see>
</indexterm>
<para>The GNOME Desktop includes features that you can use
to restrict access to certain functions in the GNOME Desktop. The disable
features are useful in various situations where you want to restrict the actions
that users can perform on a computer. For example, you might want to prevent
command line operations on a computer that is for public use at a trade show.
The disable features are also known as <emphasis>lockdown</emphasis> features.</para>
<para>You set <application>GConf</application> keys to disable features. For
information about how to set <application>GConf</application> keys, see <xref linkend="gconf-0"/>. You can also use the <application>Configuration Editor</application> application to set <application>GConf</application> keys in
a user configuration source. For more information about the <application>Configuration Editor</application> application, see the <citetitle>GConf Editor
Manual</citetitle>.</para>
</sect1>
<sect1 id="lockdown-manual">
<title>Locking Down Setting Manually</title>
<sect2 id="lockdown-2">
<title>Bildschirm sperren und Abmelden deaktivieren</title>
<indexterm>
<primary>Funktionen abschalten</primary>
<secondary>lock screen</secondary>
</indexterm>
<indexterm>
<primary>Funktionen abschalten</primary>
<secondary>log
out</secondary>
</indexterm>
<para>To disable the lock screen and log out functions, set the <literal>/apps/panel/global/disable_lock_screen</literal> key and the <literal>/apps/panel/global/disable_log_out</literal> key to <literal>true</literal>.</para>
<para>When you disable
the lock screen and log out functions, the following items are removed from
the panels:</para>
<itemizedlist>
<listitem>
<para><guimenuitem>Lock Screen</guimenuitem> and <guimenuitem>Log
Out <replaceable>user</replaceable></guimenuitem> menu items from the <guimenu>Main Menu</guimenu>.</para>
</listitem>
<listitem>
<para><guimenuitem>Lock</guimenuitem> and <guimenuitem>Log Out</guimenuitem>
menu items from the <menuchoice><guimenu>Add to Panel</guimenu><guimenuitem>Actions</guimenuitem></menuchoice> menu. To open this menu, right-click on
a vacant space on a panel, then choose <menuchoice><guimenu>Add to Panel</guimenu><guimenuitem>Actions</guimenuitem></menuchoice>.</para>
</listitem>
<listitem>
<para><guimenuitem>Lock Screen</guimenuitem> and <guimenuitem>Log
Out <replaceable>user</replaceable></guimenuitem> menu items from the <guimenu>Actions</guimenu> menu in the <application>Menu Bar</application> applet.</para>
</listitem>
</itemizedlist>
<para>Also, any <guibutton>Lock Screen</guibutton> buttons and <guibutton>Log Out</guibutton> buttons on panels are disabled.</para>
</sect2>
<sect2 id="lockdown-12">
<title>Deaktivieren von Befehlszeilenoperationen</title>
<indexterm>
<primary>Funktionen abschalten</primary>
<secondary>Befehlszeile</secondary>
</indexterm>
<para>To disable operations from a command line, set the <literal>/desktop/gnome/lockdown/disable_command_line</literal> key to <literal>true</literal>.</para>
<para>When you disable command line operations, the following
changes occur in the user interface:</para>
<itemizedlist>
<listitem>
<para>The <guimenuitem>Run Application</guimenuitem> menu item is
removed from the following menus:</para>
<itemizedlist>
<listitem>
<para>
<guimenu>Hauptmenü</guimenu>
</para>
</listitem>
<listitem>
<para><guimenu>Actions</guimenu> submenu in the <guimenu>Add to
Panel</guimenu> menu</para>
</listitem>
<listitem>
<para><guimenu>Actions</guimenu> menu in the <application>Menu Bar</application> applet</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Any <guibutton>Run</guibutton> buttons on panels are disabled.</para>
</listitem>
</itemizedlist>
<para>To disable command line operations, you must also remove menu items
that start terminal applications. For example, you might want to remove menu
items that contain the following commands from the menus:</para>
<itemizedlist>
<listitem>
<para>Der Befehl für das <application>GNOME Terminal</application>, welcher <command>/usr/bin/gnome-terminal</command> lautet.</para>
</listitem>
<listitem>
<para>
<command>/usr/bin/xterm</command>
</para>
</listitem>
<listitem>
<para>
<command>/usr/bin/setterm</command>
</para>
</listitem>
</itemizedlist>
<para>Die Einträge werden aus den folgenden Menüs entfernt:</para>
<itemizedlist>
<listitem>
<para>
<guimenu>Hauptmenü</guimenu>
</para>
</listitem>
<listitem>
<para>
<menuchoice>
<guimenu>Zum Panel hinzufügen</guimenu>
<guimenuitem>Einen Anwendungsstarter aus dem Anwendungsmenü kopieren</guimenuitem>
</menuchoice>
</para>
</listitem>
</itemizedlist>
<para>To disable command line operations, you must also disable the <application>Command Line</application> applet. To disable the <application>Command Line</application> applet, add the applet to the <literal>/apps/panel/global/disabled_applets</literal> key. When you disable the <application>Command Line</application>
applet, the <application>Command Line</application> applet is removed from
the <guimenu>Main Menu</guimenu> and the <menuchoice><guimenu>Add to Panel</guimenu><guimenuitem>Utility</guimenuitem></menuchoice> menu. </para>
</sect2>
<sect2 id="lockdown-11">
<title>Deaktivieren der Panel-Konfiguration</title>
<indexterm>
<primary>Funktionen abschalten</primary>
<secondary>Panel-Einstellungen</secondary>
</indexterm>
<para>To disable panel configuration, set the <literal>/apps/panel/global/locked_down</literal> key to <literal>true</literal>.</para>
<para>When you disable
panel configuration, the following changes occur in the user interface:</para>
<itemizedlist>
<listitem>
<para>The following items are removed from the panel popup menu,
and from the drawer popup menu:</para>
<itemizedlist>
<listitem>
<para>
<guimenuitem>Zum Panel hinzufügen</guimenuitem>
</para>
</listitem>
<listitem>
<para>
<guimenuitem>Dieses Panel entfernen</guimenuitem>
</para>
</listitem>
<listitem>
<para>
<guimenuitem>Eigenschaften</guimenuitem>
</para>
</listitem>
<listitem>
<para>
<guimenuitem>Neues Panel</guimenuitem>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Das Kontextmenü des Anwendungsstarters ist deaktiviert.</para>
</listitem>
<listitem>
<para>Die folgenden Einträge sind aus dem Kontextmenü des Applets entfernt:</para>
<itemizedlist>
<listitem>
<para>
<guimenuitem>Aus dem Panel entfernen</guimenuitem>
</para>
</listitem>
<listitem>
<para>
<guimenuitem>Lock</guimenuitem>
</para>
</listitem>
<listitem>
<para>
<guimenuitem>Verschieben</guimenuitem>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>The <guimenu>Main Menu</guimenu> popup menu is disabled. </para>
</listitem>
<listitem>
<para>The launcher drag feature is disabled, so that users cannot
drag launchers to, or from, panels.</para>
</listitem>
<listitem>
<para>The panel drag feature is disabled, so that users cannot drag
panels to new locations.</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="lockdown">
<title>Lockdown Editor</title>
<para>As of GNOME 2.14, a graphical lockdown editor called
<application>Pessulus</application> has been included to ease the task of
disabling desktop settings.</para>
<sect2 id="lockdown-start">
<title>Erste Schritte</title>
<para>To run the lockdown editor:</para>
<itemizedlist>
<listitem>
<para>Click the <menuchoice>
<guimenu>System</guimenu>
<guisubmenu>Administration</guisubmenu>
<guimenuitem>Lockdown Editor</guimenuitem>
</menuchoice></para>
</listitem>
<listitem>
<para>Run the <command>pessulus</command> command in a terminal
window.</para>
</listitem>
</itemizedlist>
<para>You will see a window with several different tabs. Each of the tabs
represents a different category of desktop settings that can be disabled.
In the next section, we will discuss each category and provide a brief
description for each setting that can be disabled.</para>
</sect2>
<sect2 id="lockdown-disabling">
<title>Funktionen deaktivieren</title>
<para>To disable a setting, make sure the checkbox next to the setting's
description is checked. Most settings will take effect immediately,
however some settings will require that the application be restarted in
order to take effect.</para>
<para>When <application>pessulus</application> starts, it will try to get
a connection to the GConf mandatory configuration source. This address for
this configuration source is
<literal>xml:merged:<replaceable>$prefix</replaceable>/etc/gconf/gconf.xml.mandatory</literal>.
If the user that is running <application>pessulus</application> has access
to this configuration source, then a lock icon will be displayed next to
the checkbox for each setting. Clicking the lock will toggle whether or
not the setting is mandatory. If the setting is mandatory, then regular
users will not be able to change or override the setting. If the user
running pessulus does not have access to the mandatory configuration
source, then the lock icon will not appear. In this case, all disabled
settings will simply be stored in the user's default configuration source
and can be modified later using other tools such as
<application>gconf-editor</application> or
<application>gconftool-2</application>. For more information on GConf and
mandatory configuration sources, see <xref linkend="gconf-26"/>.</para>
<para>The following subsections will give a brief description of the
settings that can be disabled for each category.</para>
<note>
<para>Depending on the applications you have installed, you may see
fewer categories than those described in this section.</para>
</note>
<sect3 id="lockdown-disabling-general">
<title>Allgemein</title>
<variablelist>
<varlistentry>
<term>Befehlszeile deaktivieren</term>
<listitem>
<para>Den Benutzer daran hindern, auf das Terminal zuzugreifen oder eine auszuführende Befehlszeile anzugeben. Dies verhindert beispielsweise den Zugriff auf den Panel-Dialog »Anwendung ausführen«.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Drucken deaktivieren</term>
<listitem>
<para>Den Benutzer am Drucken hindern. Dies verhindert beispielsweise den Zugriff auf den Druckdialog aller Anwendungen.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Druckeinstellungen deaktivieren</term>
<listitem>
<para>Prevent the user from modifying print settings. For example,
this would disable access to all applications' "Print Setup"
dialogs.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Speichern auf Festplatte verbieten</term>
<listitem>
<para> Prevent the user from saving files to disk. For example,
this would disable access to all applications' "Save as"
dialogs.</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3 id="lockdown-disabling-panel">
<title>Panel</title>
<variablelist>
<varlistentry>
<term>Lock down the panels</term>
<listitem>
<para>Falls dieser Schlüssel WAHR ist, unterbindet das Panel jegliche Änderungen an der Panel-Konfiguration. Applets müssen jedoch möglicherweise einzeln gesperrt werden. Damit diese Einstellungen wirksam werden, muss das Panel neu gestartet werden.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Erzwungenes Beenden deaktivieren</term>
<listitem>
<para>Falls dieser Schlüssel WAHR ist, erlaubt es das Panel dem Benutzer nicht, das Beenden einer Anwendung zu erzwingen. Dies wird durch das Entfernen des »Anwendung beenden«-Knopfes bewerkstelligt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>»Bildschirm sperren« deaktivieren</term>
<listitem>
<para>Falls dieser Schlüssel WAHR ist, erlaubt es das Panel dem Benutzer nicht, den Bildschirm zu sperren. Dies wird durch das Entfernen der »Bildschirm sperren«-Menüeinträge bewerkstelligt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Abmelden deaktivieren</term>
<listitem>
<para>Falls dieser Schlüssel WAHR ist, erlaubt es das Panel dem Benutzer nicht, sich abzumelden. Dies wird durch das Entfernen der »Abmelden«-Menüeinträge bewerkstelligt.</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3 id="lockdown-disabling-browser">
<title>Epiphany Webbrowser</title>
<variablelist>
<varlistentry>
<term>Erzwungenes Beenden deaktivieren</term>
<listitem>
<para>Dem Benutzer ist nicht gestattet, Epiphany zu beenden.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Beliebige URLs deaktivieren</term>
<listitem>
<para>Dem Benutzer die Möglichkeit nehmen, eine URL für Epiphany einzugeben.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Bearbeiten von Lesezeichen deaktivieren</term>
<listitem>
<para>Dem Benutzer die Möglichkeit nehmen, seine Lesezeichen zu bearbeiten.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Chronik deaktivieren</term>
<listitem>
<para>Alle Chronik-Informationen durch Deaktivieren der Navigationsknöpfe »Zurück« und »Vor« verbergen. Dies betrifft auch den Chronik-Dialog und die Lesezeichen.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>JavaScript-Kontrolle über Chrome deaktivieren</term>
<listitem>
<para>Disable JavaScript's control over window chrome.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Bearbeiten von Werkzeugleisten deaktivieren</term>
<listitem>
<para>Dem Benutzer die Möglichkeit nehmen, seine Werkzeugleisten zu bearbeiten.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Vollbild-Modus erzwingen</term>
<listitem>
<para>Sperrt Epiphany im Vollbildmodus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Menüleiste verbergen</term>
<listitem>
<para>Hide the menubar by default. The menubar can still be
accessed using F10.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Unsichere Protokolle deaktivieren</term>
<listitem>
<para>Deaktiviert das Laden von Inhalten mit Hilfe unsicherer Protokolle, wobei http: und https: sichere Protokolle sind.</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3 id="lockdown-disabling-screensaver">
<title>GNOME-Bildschirmschoner</title>
<variablelist>
<varlistentry>
<term>Bei Aktivierung sperren</term>
<listitem>
<para>Setzen Sie diesen Wert auf TRUE (Wahr), um den Bildschirm zu sperren, wenn der Bildschirmschoner aktiviert wird.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Abmelden zulassen</term>
<listitem>
<para>Setzen Sie diesen Wert auf TRUE (Wahr), um bei gesperrtem Bildschirm eine Option zum Abmelden nach einer festgelegten Zeit anzuzeigen. Die Verzögerung wird im Schlüssel »logout_delay« festgelegt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Benutzerwechsel zulassen</term>
<listitem>
<para>Setzen Sie diesen Wert auf TRUE (Wahr), um einen Benutzerwechsel an einem gesperrten Bildschirm zu ermöglichen.</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
</sect1>
</chapter>
<appendix id="appendixa-0">
<title>Versteckte Ordner</title>
<highlights>
<para>Dieser Anhang beschreibt die verborgenen Ordner, die der GNOME-Desktop zu den persönlichen Ordnern der Benutzer hinzufügt.</para>
</highlights>
<indexterm>
<primary>Versteckte Ordner</primary>
</indexterm>
<indexterm>
<primary>.* directories</primary>
<see>Versteckte Ordner</see>
</indexterm>
<para>A hidden
directory is a directory that has a name that begins with a period (.). <xref linkend="appendixa-TBL-2"/> describes the hidden directories that the GNOME
Desktop adds to the home directories of users. </para>
<table frame="topbot" id="appendixa-TBL-2">
<title>Verborgene Ordner in den persönlichen Ordnern der Benutzer</title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="colspec0" colwidth="33*"/>
<colspec colname="colspec1" colwidth="67*"/>
<thead>
<row rowsep="1">
<entry>
<para>Ordner</para>
</entry>
<entry>
<para>Beschreibung</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry valign="top">
<para>
<filename>.config</filename>
</para>
</entry>
<entry valign="top">
<para>This is the default location for the environment variable <envar>XDG_CONFIG_HOME</envar>,
if it is not set. User defined menus can be created at <filename>menus/applications.menu</filename>.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.fonts</filename>
</para>
</entry>
<entry valign="top">
<para>Contains fonts specific to a particular user. When a user installs a font by dragging it
to the <filename>fonts:///</filename> URI in nautilus, it is copied to this location.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.esd_auth</filename>
</para>
</entry>
<entry valign="top">
<para>Contains the authentication cookie for the GNOME
sound daemon. The GNOME sound daemon is the Enlightened Sound Daemon (ESD).</para>
<para><emphasis>ACHTUNG: Dies ist eine Datei, kein Ordner.</emphasis></para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.gconf</filename>
</para>
</entry>
<entry valign="top">
<para>Contains the <application>GConf</application> configuration
source for the user. When the user sets a preference, the new preference information
is added to this location.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.gconfd</filename>
</para>
</entry>
<entry valign="top">
<para>Contains the following <application>GConf</application>
daemon details:</para>
<itemizedlist>
<listitem>
<para>Configuration information.</para>
</listitem>
<listitem>
<para>Lock information for objects that are referenced by an <firstterm>Interoperable Object Reference (IOR)</firstterm>.</para>
</listitem>
<listitem>
<para>State information for objects that are referenced by an IOR.</para>
</listitem>
</itemizedlist>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.gnome</filename>
</para>
</entry>
<entry valign="top">
<para>Contains user-specific application data that is
not stored in the <application>GConf</application> repository. </para>
<para><emphasis>NOTE: this directory is deprecated and is only used by
GNOME 1.x applications.</emphasis></para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.gnome2</filename>
</para>
</entry>
<entry valign="top">
<para>Contains user-specific application data that is
not stored in the <application>GConf</application> repository. For example,
this directory contains the following:</para>
<itemizedlist>
<listitem>
<para>Keyboard shortcut information.</para>
</listitem>
<listitem>
<para>Informationen zum Ort des Fensters.</para>
</listitem>
<listitem>
<para>Desktop entry files for panel launchers.</para>
</listitem>
</itemizedlist>
<para>Dieser Ordner kann auch Unterordner enthalten, die anwendungsbezogene Daten speichern.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.gnome2-private</filename>
</para>
</entry>
<entry valign="top">
<para>Ignore this directory. This directory has no function
at the time of publication of this guide.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.local/share</filename>
</para>
</entry>
<entry valign="top">
<para>This is the default location for the environment variable <envar>XDG_DATA_HOME</envar>,
if it is not set. User defined desktop entries can be created in the subdirectory <filename>applications</filename>.
User defined mime types can be created in <filename>mime/packages/Overrides.xml</filename>.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.metacity</filename>
</para>
</entry>
<entry valign="top">
<para>Contains session data for the <application>Metacity</application> window manager.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.nautilus</filename>
</para>
</entry>
<entry valign="top">
<para>Contains file manager data that is specific to the
user. For example, this directory can contain the following: </para>
<itemizedlist>
<listitem>
<para>Metadaten für die Ordner, mit denen der Benutzer arbeitet.</para>
</listitem>
<!--Removed Nautilus themes.-->
<listitem>
<para>Durch den Benutzer hinzugefügte <application>Nautilus</application>-Embleme.</para>
</listitem>
<listitem>
<para><application>Nautilus</application> desktop images.</para>
</listitem>
</itemizedlist>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.themes</filename>
</para>
</entry>
<entry valign="top">
<para>Contains controls theme options, window frame theme
options, and icons theme options that the user adds. The user can add themes
from the <application>Theme</application> preference tool.</para>
</entry>
</row>
<row>
<entry valign="top">
<para>
<filename>.thumbnails</filename>
</para>
</entry>
<entry valign="top">
<para>Contains image thumbnails for the user. The image
thumbnails are used in the file manager. The file manager contains a preference
that the user can select to stop generation of thumbnail images.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</appendix>
<appendix id="appendixb-0">
<title>Security Note on Configuring SMB Printers</title>
<highlights>
<para>This appendix provides a security note related to the configuration
of printers on Windows network shares.</para>
</highlights>
<indexterm>
<primary>Samba</primary>
<see>SMB</see>
</indexterm>
<indexterm>
<primary>Windows-Netzwerkfreigaben</primary>
<see>SMB</see>
</indexterm>
<indexterm>
<primary>SMB</primary>
<secondary>Drucker einstellen</secondary>
</indexterm>
<para>Windows network shares are also referred to as Samba or <firstterm>SMB</firstterm>
shares. When you configure a printer on an SMB share, you must enter a username
and password for the print queue. </para>
<para>The username and password for the print queue is stored as unencrypted
text in the file <filename>/etc/cups/printers.conf</filename>.
This file has read-only permissions for users with root privileges, so any
user with root privileges can read the username and password for the print
queue. </para>
<para>To reduce the impact of possible security violations, ensure that the
username and password required to access the print queue is used only for
the print queue. This ensures that any possible security violation is restricted
to unauthorized use of the print queue.</para>
</appendix>
<glossary id="glossary-1">
<title>Glossar</title>
<!-- these anchors are to maintain backwards compatibility for
obsolete glossary entries -->
<!-- file content sniffer -->
<anchor id="glossary-23"/>
<!-- MIME information file -->
<anchor id="glossary-20"/>
<!-- MIME keys file -->
<anchor id="glossary-21"/>
<!-- MIME type registry -->
<anchor id="glossary-22"/>
<!-- pattern mask -->
<anchor id="glossary-25"/>
<!-- vfolder -->
<anchor id="glossary-9"/>
<!-- vfolder information file -->
<anchor id="glossary-10"/>
<glossentry id="glossary-13">
<glossterm><filename>.desktop</filename>-Datei</glossterm>
<glosssee otherterm="glossary-11"/>
</glossentry>
<glossentry id="glossary-14">
<glossterm><filename>.directory</filename>-Datei</glossterm>
<glosssee otherterm="glossary-12"/>
</glossentry>
<glossentry id="glossary-32">
<glossterm><filename>.omf</filename>-Datei</glossterm>
<glosssee otherterm="glossary-31"/>
</glossentry>
<glossentry id="glossary-18">
<glossterm>application registry</glossterm>
<glossdef>
<para>The application registry is a collection of desktop entry
files which register applications. The location of the application registry
for the GNOME Desktop is <filename>$XDG_DATA_DIRS:$XDG_DATA_HOME/applications/</filename>.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-11">
<glossterm>desktop entry file</glossterm>
<glossdef>
<para>A data file that provides information about an item in a menu.
The desktop entry file specifies the details for the item such as a name,
a command to run, an icon, and so on. Desktop entry files have a <filename>.desktop</filename> file extension.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-12">
<glossterm>directory entry file</glossterm>
<glossdef>
<para>A data file that provides information about a menu. The directory
entry file specifies details such as a name for the menu, a tooltip for the
menu, and an icon to represent the menu. Directory entry files have a <filename>.directory</filename> file extension.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-5">
<glossterm>GConf-Konfigurationsquelle</glossterm>
<glossdef>
<para>A storage location in the <application>GConf</application>
repository. For example, <literal>xml:readonly:/etc/gconf/gconf.xml.defaults</literal>.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-2">
<glossterm>GConf-Einstellungsschlüssel</glossterm>
<glossdef>
<para>An element in the <application>GConf</application> repository
that corresponds to an application preference. For example, the <literal>/apps/gnome-session/options/show_splash_screen</literal> key corresponds to
the <guilabel>Show splash screen on login</guilabel> option in the <application>Sessions</application> preference tool.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-6">
<glossterm>GConf-Pfaddatei</glossterm>
<glossdef>
<para>A file that lists the GConf configuration sources, and the
order in which to search the sources.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-3">
<glossterm>GConf-Schema</glossterm>
<glossdef>
<para>A collective term for a schema key and a schema object.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-4">
<glossterm>GConf-Schema-Definitionsdatei</glossterm>
<glossdef>
<para>A <application>GConf</application> schema definition file
lists the keys in a particular application, and defines the characteristics
of the keys. <application>GConf</application> schemas are generated from schema
definition files. Schema definition files have a <filename>.schemas</filename>
file extension.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-7">
<glossterm>GConf-Schema-Schlüssel</glossterm>
<glossdef>
<para>A key that stores a schema object for a preference key. For
example, <literal>/schemas/desktop/gnome/interface/font_name</literal> is
a schema key for the <literal>/desktop/gnome/interface/font_name</literal>
preference key.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-8">
<glossterm>GConf-Schema-Schlüssel</glossterm>
<glossdef>
<para>An element in a configuration source that contains information
about a preference key. The schema object contains information such as a default
value for the preference key, and documentation on the preference key. </para>
</glossdef>
</glossentry>
<glossentry id="glossary-glob-pattern">
<glossterm>glob pattern</glossterm>
<glossdef>
<para>A glob pattern is used to match a file name by using special
characters such as <literal>*</literal> and <literal>?</literal>. The MIME
system uses glob patterns to assign MIME types based upon filenames and often,
file extensions.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-26">
<glossterm>Interoperable Objektreferenz</glossterm>
<glossdef>
<para>An Interoperable Object Reference (IOR) is a string reference
to a CORBA object. An IOR encodes a hostname and port to which messages can
be sent to control the object. The IOR also contains an object key to identify
the object.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-magic-rule">
<glossterm>magic rule</glossterm>
<glossdef>
<para>A magic rule defines a file's MIME type by specifying
text or binary data to search for at the beginning of the file. Offsets to look for
this data are defined in a magic rule.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-menu-def">
<glossterm>Menu definition files</glossterm>
<glossdef>
<para>Menu definition files define the hierarchy of menus that are used in the
GNOME menu bar.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-27">
<glossterm>MIME</glossterm>
<glossdef>
<para>Multipurpose Internet Mail Extension.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-mime-source-xml">
<glossterm>MIME source XML file</glossterm>
<glossdef>
<para>A MIME source XML file defines how MIME types are resolved for different kinds
of files. There are three ways in which this can be done: using file extensions (glob patterns),
using magic rules and using XML namespaces. MIME source XML files are located
in the <filename>$XDG_DATA_DIRS:$XDG_DATA_HOME/mime/packages</filename> directory.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-16">
<glossterm>MIME-Typ</glossterm>
<glossdef>
<para>A MIME type identifies the format of a file. The MIME type
enables applications to read the file. For example, an email application can
use the <literal>image/png</literal> MIME type to detect that a Portable Networks
Graphic (PNG) file is attached to an email. </para>
</glossdef>
</glossentry>
<glossentry id="glossary-mime-type-database">
<glossterm>MIME-Typen-Datenbank</glossterm>
<glossdef>
<para>The MIME type database is a collection of files
which register MIME types for the desktop environment. The location of
the MIME type database is the directory <filename>$XDG_DATA_DIRS:$XDG_DATA_HOME/mime</filename>.
</para>
</glossdef>
</glossentry>
<glossentry id="glossary-31">
<glossterm>OMF-Datei</glossterm>
<glossdef>
<para>Open Source Metadata Framework file. This is a file that is
associated with the XML file for a manual. The OMF file contains information
about the manual that is used by the Help browser. OMF files have a <filename>.omf</filename> file extension.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-33">
<glossterm>PAM</glossterm>
<glossdef>
<para>Pluggable Authentication Modules.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-28">
<glossterm>Bildschirmschoner</glossterm>
<glossdef>
<para>Ein Bildschirmschoner ist eine Anwendung, die das Bild auf dem Bildschirm ersetzt, wenn dieser nicht benutzt wird. In der GNOME-Arbeitsumgebung wird <application>gnome-screensaver</application> verwendet.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-29">
<glossterm>screensaver display</glossterm>
<glossdef>
<para>Eine Bildschirmschoneranzeige ist eine Anwendung, die das Bild auf dem Bildschirm des Benutzers ersetzt, wenn dieser Bildschirm nicht benutzt wird. </para>
</glossdef>
</glossentry>
<glossentry id="glossary-34">
<glossterm>UDP</glossterm>
<glossdef>
<para>User Datagram Protocol.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-15">
<glossterm>Uniform Resource Identifier</glossterm>
<glossdef>
<para>Ein Uniform Resource Identifier (URI) ist eine Zeichenkette, die einen bestimmten Ort innerhalb eines Dateisystems oder im Web bezeichnet. Beispielsweise ist eine Webadresse eine solche URI.</para>
</glossdef>
</glossentry>
<glossentry id="glossary-24">
<glossterm>websafe color palette</glossterm>
<glossdef>
<para>The websafe color palette is a general-purpose palette of
216 colors. The websafe color palette is designed to optimize the use of color
on systems that support 8-bit color. The websafe color palette is also called
the <emphasis>Netscape color palette</emphasis> and the <emphasis>Netscape
color cube</emphasis>.</para>
</glossdef>
</glossentry>
</glossary>
<!-- If generating PDFs and if you want an index, then uncomment <index/> -->
<!-- <index/> -->
</book>