Shoutbox

quote:

---

Originally posted by Choli

Which ones? The tool is supposed to work correctly with Japanese and Korean characters.

---

I actually haven't tested Japanese characters, but Korean chracters actually cause problem. It often fails to complete character composition.

quote:

---

Originally posted by Choli

What do regular expressions have to do with Unicode? The text (Unicode or not) should be entered as is in the text box area and the program reads it and that's all... I don't see the need of regular expresions... the program should process the text without making any difference depending on the encoding or language.

---

I mentioned using regular expressions because it can extract key-value pairs much more efficiently. Also, .NET common controls would perform better than native RichEdit, as I'm seeing some composition issues.
Besides input process, it is indeed not a problem. Everything would work fine.

quote:

---

Originally posted by Choli

Well, of course you're free of writing whatever program you want.... but I don't see a real reason of doing so I think that the program works quite well and there are only a couple of small issues which are not very important and don't prevent the program for working correctly. In addition, I'm planing on doing a new version with more features and with those issues solved (and, of course, full real unicode support ). But that will be during the following months, not tomorrow

---

Well, I hope you fix those issues. Actually I'm skeptical of writing a "public" tool since dealing with bi-directional text is a nightmare.

P.S: Bug report: buttons for browsing paths show weird chracters for me. (Broken Korean characters; supposedly charset issue.)