4 Sep
2018
4 Sep
'18
7:29 a.m.
On Sep 4, 2018, at 7:21 AM, Stefan Paetow <Stefan.Paetow@jisc.ac.uk> wrote:
Hi Alan,
Just following up on this one... Did you ever push something that fixes this? We've tried the latest 3.0.x HEAD and it still persists.
I don't think I pushed a fix. I'm not sure that we can do a simple fix in v3 without changing existing behaviour. And I'm very wary of doing that. Since this can be worked around in "unlang", I think it's best to do it that way for now. Alan DeKok.