Shoutbox

I found a rather strange bug... :/ Take a look at the screenshot:



The :-[ :-[ :-[ is displayed wrongly in the textboxes. It appears that some certain display-direction controllers have been inserted...

Anyway, it's nothing serious for that entry, but if this happens for other, "regular" entries then it'd be a pain in neck

quote:

---

Originally posted by Mnjul
I found a rather strange bug... :/ Take a look at the screenshot:



The :-[ :-[ :-[ is displayed wrongly in the textboxes. It appears that some certain display-direction controllers have been inserted...

Anyway, it's nothing serious for that entry, but if this happens for other, "regular" entries then it'd be a pain in neck

---

That's really weird...
* Matti wonders how that comes...

quote:

---

Originally posted by Mnjul
I found a rather strange bug... :/ Take a look at the screenshot:



The :-[ :-[ :-[ is displayed wrongly in the textboxes. It appears that some certain display-direction controllers have been inserted...

Anyway, it's nothing serious for that entry, but if this happens for other, "regular" entries then it'd be a pain in neck

---

I suspect this is due to your used language in Windows or something. IIRC you have had other problems too with other programs because you're using Chinese Windows or something, no?

This would be the same cause I's suspect.

Note: I don't have this bug (English Windows)

hehe... that's a known bug, but as noone had reported it before, I assumed that I was the only who knew about it

When I noticed the bug, it was with the text "3,1", which is used in a special key in the spanish translation. It happened something similar: the symbol (in this case, the comma) appears after the following character: "31,". I tried to fix it, but I still don't know why it happens.

In my tests, I saw a very interesting thing: Just after opening the translator, the first key you display does not have the problem: Make this test, Mnjul, Cookie...: Open the translator, select the files and go to that key. It should be displayed correctly. Now, go to another key and go back to the first one. The problem is there In order to "fix" the problem, you have to close and restart the translator again.

quote:

---

Originally posted by Mnjul
Anyway, it's nothing serious for that entry, but if this happens for other, "regular" entries then it'd be a pain in neck

---

Don't worry. Under very concrete circumstances, it may happen with other texts, but as long as I know, it happens in texts that have a comma "," or a dash "-" between non-letter characters and without spaces. For example: ":-[", "2,3", "333-444" and not these ones: "2, 3", "qqq-www". These texts which cause the bug are the less common ones.

But these is an important thing to say: This is only a bug concerning the display of the text. What you write in the text area, goes directly to the file and it is written correctly, even if after that, it is displayed wrong.

Anyway, if you doubt, I'd suggest to review the file for those texts that may have commas of dashes without spaces.

Thanks for reporting

quote:

---

Originally posted by Choli
In my tests, I saw a very interesting thing: Just after opening the translator, the first key you display does not have the problem: Make this test, Mnjul, Cookie...

---

indeed... confirmed... selecting after selecting other keys and I too have it...

RichEditControl bug?

quote:

---

Originally posted by CookieRevised
RichEditControl bug?

---

mmm.... I'm not very sure... take into accout that in order to show the text, the translator program creates the RTF code to be put in the RichEditControl, ie: the text I get from the file is not directly sent to the control so there may be a bug in there.... on the other hand, if the bug is there, why is the text shown correctly the 1st time?

Does it work for translation with Messenger Plus! Live?

EDIT: Well it works... I'll try translate in Greek

Choli add "Search" function.

Options:

"Search in translated text"

and

"Search in untranslated text"

quote:

---

Originally posted by [Sebek]
Choli add "Search" function.

Options:

"Search in translated text"

and

"Search in untranslated text"

---

for stuff like that I suggest to use a simple (or advanced, whatever you prefer) texteditor to create your language (eg: notepad).

The Translation tool is "only" a tool. It is not meant as the unique and only thing to make your entire translation in. If you do that, you'll find that your translation will actually contain many bugs, inconsistancies, etc...

Out of experience I can say that it is far easier to use your texteditor first (and to start a new translation, make a copy of the English file and use that as your base), and afterwards check your translation for missing keys and what not against the original english one with this Translation Tool.



PS1: The above is meant in case you do use the tool as an unique and only thing to make your translation in... Despite that, a search function would be nice...

PS2: There is also a Translator Script for Plus!Live, which is in essence almost the same as this standalone tool. Also made by Choli.

^^ EDIT:

quote:

---

Originally posted by Apatik
Seems like the thread is in a private forum

---

God!!! This is the 6541654614th time already... Why are all those things in the beta testing forum (and why don't I check it first ).... /me goes to report for moving it

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by [Sebek]
Choli add "Search" function.

Options:

"Search in translated text"

and

"Search in untranslated text"

---

for stuff like that I suggest to use a simple (or advanced, whatever you prefer) texteditor to create your language (eg: notepad).

The Translation tool is "only" a tool. It is not meant as the unique and only thing to make your entire translation in. If you do that, you'll find that your translation will actually contain many bugs, inconsistancies, etc...

Out of experience I can say that it is far easier to use your texteditor first (and to start a new translation, make a copy of the English file and use that as your base), and afterwards check your translation for missing keys and what not against the original english one with this Translation Tool.



PS: The above is meant in case you do use the tool as an unique and only thing to make your translation in... Despite that, a search function would be nice...

---

Yes, you're right but it would be nice if we have there all in one, ultimate translation tool for Messenger Plus!