diff options
| author | Matthew Barnes <mbarnes@redhat.com> | 2011-11-23 06:53:07 +0800 |
|---|---|---|
| committer | Matthew Barnes <mbarnes@redhat.com> | 2011-11-23 09:42:56 +0800 |
| commit | 2e60b6a4a21105bb4a1e2badd1be51b3e684d165 (patch) | |
| tree | d3cfea8c8660785403ebce50fbedcd7cae23b6cb /data/org.gnome.evolution.plugin.email-custom-header.gschema.xml.in | |
| parent | adf6645d525842692ca625a278e41a66cd02d2b6 (diff) | |
| download | gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.tar gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.tar.gz gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.tar.bz2 gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.tar.lz gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.tar.xz gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.tar.zst gsoc2013-evolution-2e60b6a4a21105bb4a1e2badd1be51b3e684d165.zip | |
Tweak GSettings schemas.
- Don't use the term "eplugin" for modules.
- Use the term "plugin" instead of "eplugin" for plugins.
- Split SpamAssassin settings into a separate schema.
Diffstat (limited to 'data/org.gnome.evolution.plugin.email-custom-header.gschema.xml.in')
| -rw-r--r-- | data/org.gnome.evolution.plugin.email-custom-header.gschema.xml.in | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/data/org.gnome.evolution.plugin.email-custom-header.gschema.xml.in b/data/org.gnome.evolution.plugin.email-custom-header.gschema.xml.in new file mode 100644 index 0000000000..87e526fdb1 --- /dev/null +++ b/data/org.gnome.evolution.plugin.email-custom-header.gschema.xml.in @@ -0,0 +1,9 @@ +<schemalist> + <schema gettext-domain="evolution" id="org.gnome.evolution.plugin.email-custom-header" path="/org/gnome/evolution/plugin/email-custom-header/"> + <key name="custom-header" type="as"> + <default>['Security=Personal;Unclassified;Protected;InConfidence;Secret;Topsecret']</default> + <_summary>List of Custom Headers</_summary> + <_description>The key specifies the list of custom headers that you can add to an outgoing message. The format for specifying a Header and Header value is: Name of the custom header followed by "=" and the values separated by ";"</_description> + </key> + </schema> +</schemalist> |