Handling of conversions near punctuation about unidecode HOT 5 CLOSED

I have no objection to that change. I do often deal with ranges like "¼–½" but I'm equally fine to receive "1/4-1/2" as "1/4 - 1/2".

If anyone is out there who's parsing strings like "½¾" or "¾9", they would view the change as a regression, but seems very unlikely. In those cases I'm not even sure we can intuit what the expected behavior ought to be.

from unidecode.

Thank you both for your comments. I'm removing the trailing space in the replacements for fractions. I'll be releasing a new version of Unidecode with this change shortly.

from unidecode.

The extra space was introduced in b8af436 to prevent fractions from merging with adjacent numbers.

from unidecode.

Yes, I think that adding the extra space at the start to prevent the merging is good, but I wonder if the extra trailing space is needed? I can't currently think of any examples where something deliberately adjacent & following a fraction such as ¾ would require a space separation. I expect other trailing numbers would already have a space in the original string. (But preceding numbers may not, in which case I agree introducing a space there is a good thing).

from unidecode.

@IamJeffG Since you contributed the commit that added the spaces, do you have any objection to removing the trailing space?

from unidecode.