1. 14 May, 2019 1 commit
  2. 09 Mar, 2019 1 commit
  3. 24 Feb, 2019 1 commit
  4. 22 Feb, 2019 1 commit
  5. 29 Dec, 2018 1 commit
  6. 22 Jun, 2018 1 commit
  7. 16 Jun, 2018 2 commits
  8. 15 Jun, 2018 2 commits
    • Sébastien Wilmet's avatar
      README: some improvements · 2b1a985b
      Sébastien Wilmet authored
      The 0.1 version is quite old, at this point I think nobody will use it,
      so I remove the warning about it.
      
      And since the GTK+ requirement is still 3.20, it's possible to install
      gspell 1.8 or 1.6 on older versions of distributions. It would be
      beneficial, because gspell >= 1.6 works better than the previous
      versions.
      2b1a985b
    • Sébastien Wilmet's avatar
      flatpak: write some notes · ed349b7d
      Sébastien Wilmet authored
      ed349b7d
  9. 23 May, 2018 2 commits
  10. 10 May, 2018 1 commit
  11. 08 Apr, 2018 1 commit
  12. 20 Mar, 2018 1 commit
  13. 10 Mar, 2018 2 commits
  14. 03 Mar, 2018 1 commit
  15. 18 Feb, 2018 1 commit
  16. 20 Jan, 2018 1 commit
  17. 09 Dec, 2017 1 commit
  18. 29 Nov, 2017 1 commit
    • Sébastien Wilmet's avatar
      Use Enchant 2 · 5b50a847
      Sébastien Wilmet authored
      Enchant has a new maintainer and the project is again under development.
      
      There has been some API/ABI breaks in Enchant 2, but they don't affect
      gspell.
      
      Enchant 2 >= 2.1.3 is now parallel-installable with Enchant 1, so it'll
      normally not cause problems for Linux distribution packagers to ship
      Enchant 2 and the next version of gspell. See:
      https://github.com/AbiWord/enchant/issues/162
      
      Strictly speaking, this is an API break for gspell as well, since there
      is the gspell_checker_get_enchant_dict() function that exposes Enchant
      in the public API of gspell. This function has been added in the
      previous development cycle for gnome-builder needs, but gnome-builder
      doesn't use yet this function. I've asked on IRC to the gnome-builder
      developers if it's fine to switch to Enchant 2, and they said that it is
      not a problem. So I prefer to follow a pragmatic approach, in practice
      switching gspell to Enchant 2 will normally not cause problems for
      applications, and that way the apps will automatically benefit from a
      newer version of Enchant (especially gedit which is currently
      unmaintained, so it's unlikely that gedit would have switched to
      gspell-2).
      
      https://bugzilla.gnome.org/show_bug.cgi?id=790994
      5b50a847
  19. 08 Nov, 2017 1 commit
  20. 05 Nov, 2017 1 commit
  21. 02 Nov, 2017 1 commit
  22. 29 Oct, 2017 2 commits
  23. 21 Oct, 2017 1 commit
  24. 16 Oct, 2017 1 commit
  25. 05 Oct, 2017 2 commits
  26. 29 Sep, 2017 1 commit
  27. 25 Sep, 2017 1 commit
  28. 10 Sep, 2017 2 commits
  29. 06 Sep, 2017 1 commit
  30. 02 Sep, 2017 1 commit
  31. 01 Sep, 2017 1 commit
  32. 28 Aug, 2017 1 commit
  33. 27 Aug, 2017 1 commit