3 replies to this topic

[Mhoram]

When you use a tp2 in WeiDU 115 and preview versions to install a mod, you do something like

BEGIN ~My mod name~

And then the commando window show you:

Install Component [My mod name]
(Y)es, (N)o, (Q)uit?

Well, spanish, and other lenguages translations, use ´¨ñ, etc. To properly translate a mod to spanish you have to put the ¿tildes? (I don´t know the word in english) because "está" isn´t the same that "esta". When you make a tp2 file like:

BEGIN ~Anillo de los C´rintin-Versión ToB-traducción al Español hecha por Clan Dlan~

Yo see in the command window:

Install Component [Anillo de los C´rintin-Versi3/4n ToB-traducci3/4n al Espa+ol hecha por Clan Dlan]
(Y)es, (N)o, (Q)uit

It´s not an important bug, and WeiDU works perfectly with ¿tildes? when useing strings, but i think you want to know that.

[weimer]

Ah. Unfortunately, the problem here is not with WeiDU but with Windows. WeiDU is doing its best to display the string with your special accented characters (i.e., I'm calling printf() with the string you supplied to me) but the Windows dos prompt either can't display them or remaps them to something else.

Does anyone know a workaround for this?

[Mhoram]

Oh, thanks for all anyway. And don´t worry, is a very little problem, as i told you, the accented strings work and are show perfectly

[Dyara]

I guess the best you can do is to write the strings that should be displayed in the dos window with a dos editor (like 'edit'). At least that´s what I do to display the german umlaut ä, ö and ü.