[next-master] Question: can we improve the system of dealing with unencoded open/close punctuation? about mm2spacecenter HOT 5 OPEN

Maybe you don't know about this? robotools/defcon#391 Also, you can use pseudo unicode: split at . see if the first thing has a unicode, use that.

from mm2spacecenter.

To be clear, I'd use something to make a pair list of open/close: BIDI may be good there, then make a mapping file by splitting the suffixes to map to the unicode encoded version, then you can just do a lookup to get the right open/close

from mm2spacecenter.

@benkiel that's a great suggestion! I‘m not going to be working on this for a bit, but @arrowtype this seems like it would be helpful if you're going to keep working on this feature. Thank you both!

from mm2spacecenter.

@benkiel thanks so much for pointing this out!

you can use pseudo unicode: split at . see if the first thing has a unicode, use that.

I think that Wei’s suffix handling feature does essentially this, so it might just be a matter of adapting/extending that to work for open/close punctuation, as well.

And then, using BIDI would probably be a big improvement over our current, simplistic way of just listing a bunch of potential open/close punctuation (which is almost certainly not as comprehensive as BIDI).

from mm2spacecenter.

As a note: I did check whether .case punctuation is handled with the current MM2SC version (0.3.0), and it is not.

from mm2spacecenter.