Re: Missing LOCALE in post-commit hook leads to weird behaviour of `svnlook log` with unicode characters – broken transliterations

Stefan Sperling : > On Sat, Jan 27, 2018 at 06:35:17PM +0100, H.-Dirk Schmitt wrote: > > All the commit messages content transfered is broken as described > > above. > > > > This happens because the post-commit hook is running with a very > > reduced set of

Missing LOCALE in post-commit hook leads to weird behaviour of `svnlook log` with unicode characters – broken transliterations

I found a very weird behaviour of `svnlook log` that IMHO is a bug (or at least a serious missing documentation issue). Introduction Consider a log message like: 'Unicode Test → ø ÄÖÜ' `svnlook log` invoked in a normal terminal session shows the proper content. This works because t

Missing LOCALE in post-commit hook leads to weird behaviour of `svnlook log` with unicode characters – broken transliterations

I found a very weird behaviour of `svnlook log` that IMHO is a bug (or at least a serious missing documentation issue). Introduction Consider a log message like: 'Unicode Test → ø ÄÖÜ' `svnlook log` invoked in a normal terminal session shows the proper content. This works because t

Feature Request: svn status should provide a conflict check functionality via exit code

ve an --check-conflict option which would ensure an non-zero exit code if any conflict is detected. Best Reagrads, H.-Dirk Schmitt