Jiří Podhorecký

Rebased and squashed the commits.

looks like it's not my fault. What can I do to accept PR?

Affects me too. I'm using a self-signed certificate and have `SSL_VERIFY = False` in my *datapusher_settings.py*, yet still receive the error described above. Relevant line from my nginx error log...

After a brief investigation, it turned out that this particular request is originating from [service provider's web.py](https://github.com/ckan/ckan-service-provider/blob/bb3a4bd9622096fd84eb758894db817e3c43ec9e/ckanserviceprovider/web.py#L734-L737). I'll reopen the issue in the correct repo - https://github.com/ckan/ckan-service-provider/issues/36

We have eventually worked around the problem by adding the self-signed certificate to *requests* and *certify* `cacert.pem` trust stores. But I have tried just now on vanilla CKAN + DataPusher...

Hola, el siguiente mensaje apareció en mi perfil de transifex: > "Hola, pues no pude ver realmente de que se trata lo que has publicado, sería bueno que no solo...

I apologize, but I am unable to correct latest conflict for the PR to be accepted, please help

ok, I sent my translation 9 months ago, since then new texts have been written. So I should complete the current translation and make a new PR. Later... I see...

> Hey, thank you so much for addressing all these comments :)) There are two left, would you mind commenting on them as well? After that, we can wrap up...