Gajim - 2017-06-08


  1. Coder Hello everyone! Why I can't install smiles on gajim. I can't see them
  2. QuentinC2 Coder: you can add me if you want help with your VPN : quentin@o2r.fr
  3. Coder QuentinC2, thanks done it
  4. mimi89999 Unicode emoticons are not supported by Gajim.
  5. pep. lovetox: you don't gain "nothing" with mam:2, that's the one with the stanzaId right? You gain guarantees that you couldn't have before
  6. mimi89999 lovetox: Did you ping Asterix about python3 nbxmpp nightly package?
  7. lovetox pep, you misunderstood me
  8. lovetox you read "The XEP changes for :2 are for nothing"
  9. lovetox i said, it gains you nothing in current gajim
  10. lovetox which is true because we dont make use of the changes
  11. lovetox so it makes sense to run a server that support 2 as you have many users that maybe use other clients, but right now it makes no sense to switch to a different gajim branch just because it can interact with :2
  12. lovetox maybe if you just want to support :2 and not :1 or :0 :)
  13. bot Philipp Hörist pushed 4 commits to branch _refs/heads/master_ of _gajim_ <https://dev.gajim.org/gajim/gajim>: *92b0a155* <https://dev.gajim.org/gajim/gajim/commit/92b0a15521fd973bec9020ff9840d2032a54558b> Pass use_agent to GPG init instead of overwrite *2872993b* <https://dev.gajim.org/gajim/gajim/commit/2872993b0cd22ae72b2138e3dd2dcc2a0b882888> Remove unused GPG code *1bf66b85* <https://dev.gajim.org/gajim/gajim/commit/1bf66b857a27855a241dbb7cd10958018a1959b2> Always pass utf8 encoded strings to python-gnupg self.encoding which we set in the init is only intended to decode gpg´s stderr which uses a system specific encoding. if we dont encode the data we pass to python-gnupg ourself, it will fallback and use self.encoding. This might be of no concern if self.encoding is set to 'utf8' and when we are on Linux which has a preferred encoding of 'utf8'. But if we are on Windows the preferred encoding for stderr is most of the time not 'utf8'. If python-gnupg tries to decode a stderr stream that is for example encoded with 'cp1252' with our set encoding of 'utf8' this will fail. The solution is to pre-encode the data before we pass it to python-gnupg, so it does not have to use self.encoding as a fallback. And set self.encoding='latin1' because latin1 will not yield exceptions on decoding errors. Also gpg itself will fallback to latin1 as stderr encoding when it cant determine the preferred encoding of a system. self.decode_errors is used for something differently, and has no influence on the situation. Fixes #8644 *2296e75d* <https://dev.gajim.org/gajim/gajim/commit/2296e75d0dbc23816bcd2e7e662315c7b92c537a> Replace unicode char in print message
  14. mimi89999 ‎lovetox‎: Can you fix the exception on '[' in IQ stenzas?
  15. lovetox i can try to make a patch that you can test
  16. lovetox as i cant thest this issue myself
  17. lovetox mimi89999, you can try this branch https://dev.gajim.org/lovetox/gajim/commits/fixstringprep
  18. lovetox mimi89999, i pinged asterix, and he is working on it :)
  19. bot Philipp Hörist pushed 1 commit to branch _refs/heads/gajim_0.16_ of _gajim_ <https://dev.gajim.org/gajim/gajim>: *cc42fba0* <https://dev.gajim.org/gajim/gajim/commit/cc42fba09bcf837042e5bd72c81f1448738b1617> Set transient for ErrorDialog Fixes #8649
  20. bot Philipp Hörist pushed 3 commits to branch _refs/heads/gajim_0.16_ of _gajim_ <https://dev.gajim.org/gajim/gajim>: *2da22cf3* <https://dev.gajim.org/gajim/gajim/commit/2da22cf37f8663e6acf9429a595c38df9c825ac1> Pass use_agent to GPG init instead of overwrite *35f8893b* <https://dev.gajim.org/gajim/gajim/commit/35f8893bf556fdd516a8933b04db8a8805e5be65> Remove unused GPG code *5433b2a2* <https://dev.gajim.org/gajim/gajim/commit/5433b2a20b45e821cbbbee5f2590b0c4fe869953> Always pass utf8 encoded strings to python-gnupg self.encoding which we set in the init is only intended to decode gpg´s stderr which uses a system specific encoding. if we dont encode the data we pass to python-gnupg ourself, it will fallback and use self.encoding. This might be of no concern if self.encoding is set to 'utf8' and when we are on Linux which has a preferred encoding of 'utf8'. But if we are on Windows the preferred encoding for stderr is most of the time not 'utf8'. If python-gnupg tries to decode a stderr stream that is for example encoded with 'cp1252' with our set encoding of 'utf8' this will fail. The solution is to pre-encode the data before we pass it to python-gnupg, so it does not have to use self.encoding as a fallback. And set self.encoding='latin1' because latin1 will not yield exceptions on decoding errors. Also gpg itself will fallback to latin1 as stderr encoding when it cant determine the preferred encoding of a system. self.decode_errors is used for something differently, and has no influence on the situation. Fixes #8644
  21. bot Philipp Hörist pushed 1 commit to branch _refs/heads/master_ of _gajim_ <https://dev.gajim.org/gajim/gajim>: *c8115e41* <https://dev.gajim.org/gajim/gajim/commit/c8115e4164496da3527486507cb0c0acb8000b39> Set transient for ErrorDialog Fixes #8649