1. 12 Apr, 2012 1 commit
    • Allison Karlitskaya's avatar
      glib-compile-schemas: warn about bad dconf paths · 6560b374
      Allison Karlitskaya authored
      For quite some time the recommended usage of GSettings and dconf has
      been to use paths like /org/gnome/example/.  Use of /apps/ has spilled
      over from GConf and is continuing to make its way into a number of
      applications as they port.
      
      glib-compile-schemas will now warn about these types of paths being
      used.  This generates a lot of noise, but hopefully it will reduce the
      number of ported applications making this mistake.
      6560b374
  2. 28 Jan, 2012 1 commit
    • Allison Karlitskaya's avatar
      glib-compile-schemas: get strict about whitespace · 9a7a98bf
      Allison Karlitskaya authored
      It's important to have strict rules for handling of whitespace in
      translated strings in GSettings schema files so that the tools
      extracting the messages will end up with the same messages as the
      runtime calling gettext().
      
      The rules are designed to be simple and unambiguous yet cover most
      normal uses in a convenient way.
      
      Those rules are as follows (with rationale):
      
        - for <default> tags, the text content has its leading and trailing
          whitespace stripped off, but internal whitespace is not modified in
          any way.
      
          This allows for slightly more flexible use of whitespace without
          causing that whitespace to appear in the strings for translation.
      
        - for <summary> and <description> tags, the content is split into
          paragraphs.  Paragraphs are separated by two or more sequential
          newline characters.  Each paragraph has its leading and trailing
          whitespace removed and all other whitespace is normalised to a
          single ascii space character.  Finally, the paragraphs are rejoined,
          inserting exactly two newlines between them.
      
          This allows for longer explanations (particularly in the description
          tag) using a natural format that, when normalised, will display
          nicely in toolkits.
      
      This patch implements the rules for <default> tags.  The schema compiler
      currently ignores <summary> and <description> tags.
      9a7a98bf
  3. 24 Jan, 2012 1 commit
  4. 07 Nov, 2011 1 commit
  5. 17 Oct, 2011 1 commit
  6. 17 Sep, 2011 1 commit
  7. 10 Sep, 2011 1 commit
  8. 19 Jul, 2011 1 commit
  9. 07 Jun, 2011 1 commit
  10. 27 May, 2011 1 commit
  11. 03 May, 2011 1 commit
    • Dan Winship's avatar
      Fix usage of _GNU_SOURCE · e56498ee
      Dan Winship authored
      _GNU_SOURCE must be defined before including any other (system)
      header, so defining it in glib-unix.h (and hoping no one has included
      anything else before that) is wrong. And the "#define _USE_GNU"
      workaround for this problem in gnetworkingprivate.h is even wronger
      (and still prone to failure anyway due to single-include guards).
      
      Fix this by defining _GNU_SOURCE in config.h when building against
      glibc. In theory this is bad because new releases of glibc may include
      symbols that conflict with glib symbols, which could then cause
      compile failures. However, most people only see new releases of glibc
      when they upgrade their distro, at which point they also generally get
      new releases of gcc, which have new warnings/errors to clean up
      anyway.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=649201
      e56498ee
  12. 11 Apr, 2011 1 commit
  13. 08 Apr, 2011 2 commits
  14. 31 Mar, 2011 1 commit
  15. 19 Feb, 2011 1 commit
  16. 12 Feb, 2011 1 commit
  17. 28 Nov, 2010 1 commit
  18. 17 Oct, 2010 1 commit
  19. 04 Oct, 2010 2 commits
  20. 01 Oct, 2010 3 commits
    • Allison Karlitskaya's avatar
      Bug 628937 - gracefully handle broken schemas · 3e771509
      Allison Karlitskaya authored
      Implement the second feature requested in the bug: silently ignore
      override files that attempt to override schemas that are not currently
      installed.
      
      Also, support 'strictness' being optional for other errors when parsing
      override files (ie: inability to open the file, unknown key name, parse
      errors, out of range).  We don't completely back out the file in this
      case — as that is difficult with the current implementation — but just
      ignore the override for the single key.
      3e771509
    • Allison Karlitskaya's avatar
      glib-compile-schemas: improve error accuracy · bd290081
      Allison Karlitskaya authored
      We wrote "<enum> must contain at least one <value>" for empty <flags>.
      Fix that.
      bd290081
    • Allison Karlitskaya's avatar
      Bug 628937 - gracefully handle broken schemas · e40f3932
      Allison Karlitskaya authored
      Implement the first of two features requested in the bug: when
      encountering a broken .xml schema file, back out the changes in that
      file and continue to parse other files.
      
      This prevents a single broken .xml file from messing up GSettings for
      everyone else.
      
      Add a --strict option to get the old behaviour.  Use this from the test
      cases.
      e40f3932
  21. 09 Sep, 2010 2 commits
  22. 03 Aug, 2010 1 commit
  23. 30 Jul, 2010 1 commit
  24. 28 Jul, 2010 2 commits
  25. 10 Jul, 2010 1 commit
  26. 02 Jul, 2010 2 commits
  27. 01 Jul, 2010 1 commit
    • Allison Karlitskaya's avatar
      Bug 622124 - implement flags for GSettings · 5383c711
      Allison Karlitskaya authored
      Add a <flags> tag to the schema file format and a flags='' attribute to
      go along with.  Add some extra test cases for those.
      
      Add new g_settings_{get,set}_flags() calls and support binding to
      GParamSpecFlags properties.  Add test cases.
      5383c711
  28. 30 Jun, 2010 2 commits
  29. 29 Jun, 2010 2 commits
  30. 28 Jun, 2010 1 commit
    • Allison Karlitskaya's avatar
      Bug 622565 - compile-schemas fails when no schemas · 8a7d9906
      Allison Karlitskaya authored
      Neutralise and deprecate the --uninstall option in the schema compiler
      and remove it from gsettings.m4.
      
      Make the new default behaviour a compromise between the old default
      behaviour and the previous --uninstall option:
      
        - never return a failure code if no schema files are found
      
        - issue a warning instead
      
        - remove the gschemas.compiled file if it exists
      8a7d9906
  31. 17 Jun, 2010 1 commit