Shoutbox

Thanks Choli. You offer too much to the community

Funciona a la perfecció, gràcies.

It works perfectly, thanks

This tool has some problem when I open existing translation for update. It shows several empty key-value pairs with exclamation mark icon.

Also it has some problem with typing Japanese or Korean characters.
I'm thinking of writing an equivalent tool in C++ or C#. For unicode and IME compatibility, using .NET for user interface and regular expressions would be a decent option. What is your idea?

quote:

---

Originally posted by touko
It shows several empty key-value pairs with exclamation mark icon

---

That means that your translated file has those sections and/or keys but the original file doesn't.

quote:

---

Originally posted by touko
Also it has some problem with typing Japanese or Korean characters.

---

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

quote:

---

Originally posted by touko
For unicode and IME compatibility, using .NET for user interface and regular expressions would be a decent option

---

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.

quote:

---

Originally posted by touko
I'm thinking of writing an equivalent tool in C++ or C#. What is your idea?

---

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

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.)

quote:

---

Originally posted by touko
I mentioned using regular expressions because it can extract key-value pairs much more efficiently.

---

Currently, the program uses GetPrivateProfileStringW and similar functions, therefore the handling of the *.ini files is as efficient as it can be (because it is handled by Windows) .

quote:

---

Originally posted by touko
since dealing with bi-directional text is a nightmare

---

I totally agree with you. In fact, my program does not handle very well right-to-left languages.

quote:

---

Originally posted by touko
Bug report: buttons for browsing paths show weird chracters for me. (Broken Korean characters; supposedly charset issue.)

---

The text in those buttons is three dots: "..." You shouldn't have any problem viewing them. Are you using the default system font and the correct character encoding in your Windows?

quote:

---

Originally posted by Choli

Currently, the program uses GetPrivateProfileStringW and similar functions, therefore the handling of the *.ini files is as efficient as it can be (because it is handled by Windows) .

---

Oh, I think I couldn't even think about it because I remember MS discouraged using it. Good pointing out.

quote:

---

Originally posted by Choli

The text in those buttons is three dots: "..." You shouldn't have any problem viewing them. Are you using the default system font and the correct character encoding in your Windows?

---

I think it should be, but it shows weird characters for me. DBCS locale (Korean) might be the cause. Once you release the new version with full unicode support, it would be fine (I guess).

quote:

---

Originally posted by touko

quote:

---

Originally posted by Choli
Currently, the program uses GetPrivateProfileStringW and similar functions, therefore the handling of the *.ini files is as efficient as it can be (because it is handled by Windows) .

---

Oh, I think I couldn't even think about it because I remember MS discouraged using it. Good pointing out

---

On a sidenote:
Actually MS never discouraged those APIs. Infact they are the prefered method when you work with INI files.
However, they do discourage (for whatever unclear reason) the use of INI files in favor of the registry for storing small amounts of program settings.

quote:

---

Originally posted by touko

quote:

---

Originally posted by Choli
The text in those buttons is three dots: "..." You shouldn't have any problem viewing them. Are you using the default system font and the correct character encoding in your Windows?

---

I think it should be, but it shows weird characters for me. DBCS locale (Korean) might be the cause.

---

That's very strange though. They should still show three dots as they are basic ascii codes. If they show weird characters, don't you have many other problems with other (non-Korean) applications too?

Prepairing a new sloven version with my friend
alredy testing it



Slovenski,Slovenija

Hi, everyone, I downloaded yesterday the Translator. It worked fine, but it automatically changed my input language to english and I couldn't write my language letters, so I've deleted it. After that, it didn't change my input lang anymore and I was translating "not being annoyed anymore". Today I started to translate with the tool, but when I input the 2 files, it crashes. In the moment, my lang bar disappears and appears again. Is it crashing just because I deleted the English input language? :/