Oh. I just realised I answered you directly. Not publicly. Google.What can
you do?
Regards.
m quite sure diacritics and such are covered by UTF-8. After all, Arabic
and Hebrew are. You're concerned about the transition though, if I read you
correctly?
We're sorta committed to UTF-8 as it is. Unless someone shows me a language
more obscure than "Modern Greek (Polytonic) or "Friulian",or the RTL-ones
like Arabic or Hebrew I am not concerned. I'm quite sure they'll survive
any potential shift. In fact I think it can only become better. Regardless
of method.
But that's just my completely unbacked optimism shining through. :)
As always, you're welcome to a second opinion. Anyone?
I'm quite sure diacritics and such are covered by UTF-8. After all, Arabic
and Hebrew are. You're concerned about the transition though, if I read you
correctly?
We're sorta committed to UTF-8 as it is. Unless someone shows me a
language more obscure than "Modern Greek (Polytonic) or "Friulian",or the
RTL-ones like Arabic or Hebrew I am not concerned. I'm quite sure they'll
survive any potential shift. In fact I think it can only become better.
Regardless of method.
But that's just my completely unbacked optimism shining through. :)
As always, you're welcome to a second opinion. Anyone?
To be brutally honest, I considered replacing the GUI with WxWidgets
to be portable and all, but only MFC has the "sexiness" expexted by it's
users. Dockable toolbars and tabbed dockable windows etc. You can tell me
all you want that as long as the functionality is the same it won't matter,
but I'm not convinced.
Which makes me kinda curious and worried about the MAC users.
I guess this ones's for me. If you mean whether HUNSPELL supports
Korean or similar, the answer is yes. It even supports Hebrew. An RTL
language. I don't know whether Korean is RTL, but replacing SPELL32.DLL
isn't easy. To say the least....
I apologize if I have overlooked something, but...is there any kind
of
NFC/NFD support in Hunspell currently? If not, it appears that a
spell-checker designed for NFC data will not work if the client app
sends it NFD, and vice versa.
If there is no such support, it might be something that I would
consider adding. It surprises me to think that this is not a
significant need.
Oh. I just realised I answered you directly. Not publicly. Google.What can
you do?
Regards.
m quite sure diacritics and such are covered by UTF-8. After all, Arabic
and Hebrew are. You're concerned about the transition though, if I read you
correctly?
We're sorta committed to UTF-8 as it is. Unless someone shows me a language
more obscure than "Modern Greek (Polytonic) or "Friulian",or the RTL-ones
like Arabic or Hebrew I am not concerned. I'm quite sure they'll survive
any potential shift. In fact I think it can only become better. Regardless
of method.
But that's just my completely unbacked optimism shining through. :)
As always, you're welcome to a second opinion. Anyone?
Regards,
Soren
On Fri, Oct 26, 2018 at 8:48 PM sbrothy@gmail.com wrote: