1. 19 May, 2019 1 kayıt (commit)
  2. 18 May, 2019 1 kayıt (commit)
  3. 17 May, 2019 1 kayıt (commit)
  4. 14 May, 2019 3 kayıt (commit)
  5. 13 May, 2019 3 kayıt (commit)
  6. 10 May, 2019 3 kayıt (commit)
  7. 09 May, 2019 2 kayıt (commit)
  8. 07 May, 2019 1 kayıt (commit)
  9. 30 Nis, 2019 2 kayıt (commit)
  10. 29 Nis, 2019 1 kayıt (commit)
  11. 28 Nis, 2019 1 kayıt (commit)
  12. 26 Nis, 2019 1 kayıt (commit)
  13. 25 Nis, 2019 1 kayıt (commit)
  14. 23 Nis, 2019 1 kayıt (commit)
    • Miklos Vajna's avatar
      tdf#123684 PPTX import: fix wrong background color for <p:sp useBgFill="1"> · 943a534a
      Miklos Vajna yazdı
      Regression from commit 59339dec
      (tdf#105150 PPTX import: try harder to handle <p:sp useBgFill="1">,
      2017-01-06), the problem was that we gave a white solid fill to a shape
      which is meant to be transparent.
      
      Fix the problem by limiting the scope of the mentioned commit to solid
      colors only, and also extend to code to look for background fill from
      the masterpage as well. This allows not hardcoding the white solid fill
      and leaves the fill style of shapes as transparent where the slide
      background is a bitmap or other more complex fill type.
      
      Change-Id: I0063e88d510250652d2b14856df3bd431681422d
      Reviewed-on: https://gerrit.libreoffice.org/71107Reviewed-by: 's avatarMiklos Vajna <vmiklos@collabora.com>
      Tested-by: Jenkins
      943a534a
  15. 19 Nis, 2019 1 kayıt (commit)
  16. 17 Nis, 2019 2 kayıt (commit)
  17. 15 Nis, 2019 3 kayıt (commit)
  18. 14 Nis, 2019 1 kayıt (commit)
  19. 13 Nis, 2019 1 kayıt (commit)
  20. 12 Nis, 2019 3 kayıt (commit)
  21. 10 Nis, 2019 1 kayıt (commit)
  22. 08 Nis, 2019 2 kayıt (commit)
  23. 06 Nis, 2019 3 kayıt (commit)
  24. 04 Nis, 2019 1 kayıt (commit)
    • Mike Kaganski's avatar
      Get rid of USS macro · 4a4b1df7
      Mike Kaganski yazdı
      The helper marco is used in export code to convert UTF-16 internal
      string representation to UTF-8 used in XML encoding. I suppose that all
      strings here should be already valid UTF-16 (an invalid input should
      have been validated at import/input stage). An invalid string at this
      stage means a programming error in another part of code that breaks this
      precondition, and should not be handled at export stage.
      (See also commit 0267a232.)
      
      This effectively changes flags used in conversion from UTF-16 to UTF-8,
      so that now RTL_UNICODETOTEXT_FLAGS_INVALID_ERROR is used instead of
      RTL_UNICODETOTEXT_FLAGS_INVALID_DEFAULT, so that the result would be
      truncated on invalid bytes instead of inserting U+FFFD, and would fail
      assertion in debug builds.
      Other changed flags don't affect UTF-16-to-UTF-8 conversion.
      
      Change-Id: I12b2cc5378208904c3266924187d6402700ed6f3
      Reviewed-on: https://gerrit.libreoffice.org/69801Reviewed-by: 's avatarMike Kaganski <mike.kaganski@collabora.com>
      Tested-by: 's avatarMike Kaganski <mike.kaganski@collabora.com>
      4a4b1df7