🐛 customization.getnames: respect protected names

[tdegeus]

Fixes #327

I worked on #327 all while not noticing #331 .

Not surprisingly the solution is the same, with the difference that the current PR only breaks at spaces outside a sequence protected by "{...}" in line with the rest of the implementation of getnames. This reduces some of the worries discussed there I believe

Update: I was reading #331 and realised that I could do things better (safer). It does account for escaped brackets too. I think that this PR should be merged in favour of #331 . BTW, it seems to fix #9 as well that I happen to find in the tests . Note that there is a panic-switch: in case of unmatched brackets the split is entirely not applied. Instead there could be an error (or warning) in my opinion.

For reference, I took the implementation from my own code ( https://github.com/tdegeus/texplain/blob/21d0d50aa10a6a9a3ee437e0c374d088142da709/texplain/__init__.py#L80 ) licensed MIT

@QuantumNovice @MiWeiss

[MiWeiss]

Hi @tdegeus

Thanks a lot for this PR! I guess we're very close to merging it.

P.S. Next time you work on any issues you identify (which would be highly appreciated), please leave a corresponding remark in the issue. I'll then assign it to you, making sure that no one else works on the issue. Sorry to @QuantumNovice - I'll reply to you in your PR.

[tdegeus]

Indeed, I'm very sorry @QuantumNovice . I started working on it even after your latests commit. So I was frustrated with myself and wanted to close my PR. However, the discussion you guys had over there made me realise that I actually had something to contribute on top of #331 in terms of escaped brackets, as that is something that I had solved in the passed.

[MiWeiss]

lgtm! thanks!