Post by George on Jul 26, 2020 10:49:34 GMT -5
Hi,
I'm thinking of having a stab at making SPFLite properly UniCode. i.e. convert internal data handling from ASCII to UTF-16.
It would not handle the surrogate pair stuff (i.e. characters above U+FFFF, but I doubt that would be a problem for 99.9% of UniCode users.
Is there interest? Worth doing?
I'm not sure if I would just create a parallel version and continue maintaining the ASCII version, or just maintain the UniCode capable version. I have a feeling the UniCode version would suffer somewhat performance-wise, but I'm not sure how much.
If I go the two version approach, they would still share the CFG file along with the various Macro, Auto etc. folders. (Hopefully)
Comments?
George
I'm thinking of having a stab at making SPFLite properly UniCode. i.e. convert internal data handling from ASCII to UTF-16.
It would not handle the surrogate pair stuff (i.e. characters above U+FFFF, but I doubt that would be a problem for 99.9% of UniCode users.
Is there interest? Worth doing?
I'm not sure if I would just create a parallel version and continue maintaining the ASCII version, or just maintain the UniCode capable version. I have a feeling the UniCode version would suffer somewhat performance-wise, but I'm not sure how much.
If I go the two version approach, they would still share the CFG file along with the various Macro, Auto etc. folders. (Hopefully)
Comments?
George