1. 10 Dec, 2018 1 commit
  2. 04 Dec, 2018 2 commits
  3. 31 Oct, 2018 1 commit
  4. 26 Apr, 2018 1 commit
  5. 13 Apr, 2018 1 commit
  6. 12 Apr, 2018 2 commits
  7. 13 Mar, 2018 1 commit
  8. 12 Mar, 2018 1 commit
    • Philip Withnall's avatar
      gdatetime: Fix locale handling for nl_langinfo() calls · 12f11090
      Philip Withnall authored
      With the various macros we use to provide fallbacks for missing
      nl_langinfo() fields, the locale handling can become quite complex:
      nl_langinfo() returns strings encoded in the current locale, but C_()
      returns strings encoded in UTF-8 (by GLib convention — you do actually
      need to call bind_textdomain_codeset() to achieve this).
      There are various format specifiers, especially with the new %Ob, %OB,
      %Oh specifiers, which conditionally call nl_langinfo() or something
      based on C_(). This makes encoding handling difficult.
      Add additional macros which indicate whether the macros they’re paired
      with return something encoded in the current locale, or encoded in
      UTF-8. The user of the macro can then use these to work out whether to
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
  9. 28 Feb, 2018 1 commit
  10. 16 Feb, 2018 1 commit
  11. 15 Jan, 2018 2 commits
  12. 28 Nov, 2017 2 commits
  13. 16 Nov, 2017 1 commit
  14. 11 Sep, 2017 1 commit
    • Robert Ancell's avatar
      GDateTime: Support parsing ISO 8601 strings · 491f835c
      Robert Ancell authored
      This supports a subset of ISO 8601 since that is a commonly used standard for
      storing date and time information. We support only ISO 8601 strings that contain
      full date and time information as this would otherwise not map to GDateTime.
      This subset includes all of RFC 3339 which is commonly used on the Internet and
      the week and ordinal day formats as these are supported in the GDateTime APIs.
      (Minor modification by Philip Withnall to change API versions from 2.54
      to 2.56.)
  15. 15 Aug, 2017 1 commit
  16. 26 Jul, 2017 1 commit
    • Debarshi Ray's avatar
      gdatetime: Silence -Wmaybe-uninitialized · a7926117
      Debarshi Ray authored
      GCC 6.3.1 thinks that tmp is being used uninitialized:
        gdatetime.c: In function ‘format_ampm’:
        gdatetime.c:2248:7: warning: ‘tmp’ may be used uninitialized in this
          function [-Wmaybe-uninitialized]
               g_free (tmp);
      It is not an actual problem because the code in question is guarded by
      "if (!locale_is_utf8)" and "#if defined (HAVE_LANGINFO_TIME)", and it
      does get initialized under those circumstances. Still, it is a small
      price to pay for a cleaner build and having actual problems stand out
      more prominently.
  17. 21 Jun, 2017 1 commit
  18. 05 May, 2017 1 commit
  19. 02 May, 2017 1 commit
  20. 03 Apr, 2017 4 commits
  21. 04 Jan, 2017 1 commit
  22. 22 Nov, 2016 1 commit
  23. 16 May, 2016 1 commit
    • LRN's avatar
      g_date_time_format_locale: ensure locale encoding is used · 6a1e8e8f
      LRN authored
      Fallback code for g_date_time_format_locale() fetches translated
      strings (such as day and month names) from .mo catalogues via
      gettext. These strings always come in UTF-8 encoding, because
      that is the encoding that glib sets when it initializes gettext
      for itself.
      However, the non-fallback code uses nl_langinfo() and expects
      its results to be in locale-dependent encoding.
      This mismatch can result in UTF-8 strings being converted to UTF-8,
      producing gibberish.
      Fix this by converting UTF-8 strings to locale-dependent encoding
      before using them. Also fix the code that was already doing the locale->UTF-8
      conversion to not convert the strings when they are already UTF-8-encoded.
  24. 07 Nov, 2015 1 commit
    • Philip Withnall's avatar
      glib: Add missing (nullable) and (optional) annotations · 25a7c817
      Philip Withnall authored
      Add various (nullable) and (optional) annotations which were missing
      from a variety of functions. Also port a couple of existing (allow-none)
      annotations in the same files to use (nullable) and (optional) as
      appropriate instead.
      Secondly, add various (not nullable) annotations as needed by the new
      default in gobject-introspection of marking gpointers as (nullable). See
      This includes adding some stub documentation comments for the
      assertion macro error functions, which weren’t previously documented.
      The new comments are purely to allow for annotations, and hence are
      marked as (skip) to prevent the symbols appearing in the GIR file.
  25. 10 May, 2015 1 commit
  26. 24 Dec, 2014 1 commit
  27. 28 Jun, 2014 1 commit
  28. 30 Mar, 2014 1 commit
  29. 20 Feb, 2014 1 commit
  30. 06 Feb, 2014 1 commit
  31. 01 Feb, 2014 1 commit
  32. 20 Nov, 2013 1 commit
    • Dan Winship's avatar
      Replace #ifdef HAVE_UNISTD_H checks with #ifdef G_OS_UNIX · 158dde05
      Dan Winship authored
      In Windows development environments that have it, <unistd.h> is mostly
      just a wrapper around several other native headers (in particular,
      <io.h>, which contains read(), close(), etc, and <process.h>, which
      contains getpid()). But given that some Windows dev environments don't
      have <unistd.h>, everything that uses those functions on Windows
      already needed to include the correct Windows header as well, and so
      there is never any point to including <unistd.h> on Windows.
      Also, remove some <unistd.h> includes (and a few others) that were
      unnecessary even on unix.
  33. 31 Oct, 2013 1 commit