1. 02 Jul, 2020 1 commit
  2. 01 Jul, 2020 7 commits
  3. 30 Jun, 2020 3 commits
  4. 29 Jun, 2020 3 commits
  5. 28 Jun, 2020 2 commits
  6. 27 Jun, 2020 5 commits
    • Yuri Chornoivan's avatar
      Update Ukrainian translation · d7e74573
      Yuri Chornoivan authored
    • Yuri Chornoivan's avatar
      Update Ukrainian translation · 240bc3ac
      Yuri Chornoivan authored
    • Jehan's avatar
      libgimp: do not assume there are selected layers. · 3edcaa4b
      Jehan authored
      The list of selected layers may be empty, which doesn't matter much
      because we don't actually do much with this list in current export code.
      In the code modified in this commit, we were only using existing layers
      to set the type of a new layer (which seems very useless right now as
      anyway the layer type has to be the image base type with or without
      alpha, so a with_alpha boolean parameter would be just as good, unless
      we plan to support different color model layers in a same image).
    • Jehan's avatar
      app: fix selected layers in duplicated image. · dadae644
      Jehan authored
      This seems to have been broken since much longer, but it only made a
      problem with recent changes. Since we were duplicating layer groups and
      contents layers at once, the current code could not keep layer selection
      other than at root level in a duplicated image.
      Use the layer paths to make sure we select exactly the right copied
      layers, since the path should not change in a fully duplicated image.
    • Jehan's avatar
      desktop: add a <developer_name> tag. · 257ada49
      Jehan authored
      It just says "The GIMP team" so it's kind of redundant/useless, but I
      noticed that Flathub would just display an empty "Developer" section
      because the tag is absent. Well at least it emphasizes the
      community-developed side of GIMP.
  7. 25 Jun, 2020 4 commits
    • Ell's avatar
      plug-ins: add option to crop layers to image bounds when exporting TIFF · 7f39be86
      Ell authored
      In file-tiff, add an option to crop the layers to the image bounds
      when exporting individual layers (using GIMP_EXPORT_NEEDS_CROP
      added in the previous commit), since TIFF has no concept of global
      image bounds otherwise.  Cropping is enabled by default.
    • Ell's avatar
      libgimp: add GIMP_EXPORT_NEEDS_CROP export capability · 4c8ee413
      Ell authored
      Add a new GIMP_EXPORT_NEEDS_CROP export capability, which causes
      gimp_export_image() to crop the exported image content to the image
      bounds; this is useful for formats that support layers, but have no
      concept of global image bounds, hence cropping is the only way to
      enforce the image bounds.
      When showing the export dialog, give an option to either crop the
      layers to the image bounds, or to resize the image to fit the
    • Ell's avatar
      Issue #5274 - Exporting as TIFF fails for layers with a negative offset · 536bf771
      Ell authored
      When exporting a TIFF file without merging the image, make sure non
      of the exported layers has a negative offset, by offsetting all the
      layers as necessary.  TIFF doesn't support negative page offsets,
      giving an error in libtiff.
    • Sabri Ünal's avatar
      Update Turkish translation · 8732f061
      Sabri Ünal authored
  8. 24 Jun, 2020 5 commits
  9. 21 Jun, 2020 4 commits
    • Anders Jonsson's avatar
      Update Swedish translation · e3085c9d
      Anders Jonsson authored
    • Jehan's avatar
      app, libgimp: protect a bit GDK X Window calls. · 33520a54
      Jehan authored
      The GDK_WINDOWING_X11 build-time macro check is not enough as GDK can be
      built with both X11 and Wayland backends. We need to add a runtime check
      of the type of display.
    • Jehan's avatar
      NEWS: update. · 95454060
      Jehan authored
      Maybe we should also add some details about the API update, but so much
      has been changed already. Maybe later…
    • Jehan's avatar
      app: [Wayland] fix invalid preedit range in text tool. · 2ae1ab50
      Jehan authored
      So it seems that pango_attr_iterator_range() could return G_MAXINT for
      a Pango attribute when it is at the end of the preedit string. Looking
      at Pango code, I see they initialize the attribute end property to
      PANGO_ATTR_INDEX_TO_TEXT_END (G_MAXUINT), later clamped to G_MAXINT by
      pango_attr_iterator_range(). So I guess for the specific case where we
      are at the text end, it is normal. Only weird thing is that this didn't
      happen at all on X11, only in Wayland.
      So let's do our own pre-check. Also double the check by adding a UTF-8
      This fixes preedit text not being displayed and the following warning:
      > Gtk-CRITICAL **: 12:31:25.118: gtk_text_buffer_emit_insert: assertion 'g_utf8_validate (text, len, NULL)' failed
      Even worse, this was potentially an out-of-range reading, though
      fortunately checked early enough.
  10. 18 Jun, 2020 6 commits