Diacritics problem

dani20
11 May 2011, 07:18
Hello,
I'm trying to use Romanian language, but I can't type all diacritics. It works well with ă, î, â, but instead of ș, ț, I get only question marks. Is there a way I could solve this problem?
Thank you.

Alex
11 May 2011, 08:10
Do you see the question marks when typing in QDK, or is it only when you play the game that you see them?

If you could send me an example .asl game file (either attach here or email me at alex@axeuk.com) I'll take a look.

dani20
11 May 2011, 08:58
Thanks for your quick answer :)
I get question marks both in QDK and when I play the game. Also I tried defining a new verb containing diacritics; the verb seems to work in game - it does what it should do - but it displays question marks instead of diacritics.

Also I have the same problem when I try to create a new LDF file. I tried to save the file using both Unicode and UTF-8 encoding, but it displays strange characters in the program.

I uploaded an ASL file containing a single room, an object and a verb with diacritics.

Alex
11 May 2011, 09:11
Thanks. In the ASL file I can see those characters are stored as "?" in the file, so QDK isn't even saving them properly.

I can see if I paste those characters in to a room description box, they paste OK, but when I click the "ASL" button on the toolbar they've been replaced.

I'll have a look to see if this can be fixed easily in Quest 4. These kinds of characters can often cause problems with VB6 programs (which Quest 4 is - Quest 5 should work with these without a problem).

dani20
11 May 2011, 09:38
If the program is made in VB6 I don't think there is an easy solution for solving this problem. I remember I had a lot of trouble using Romanian diacritics when I made some Visual Foxpro 6 programming, long time ago :)

It seems like I have to wait version 5... also a Mac version would be very nice ;)
Good job, anyway. I tried a few other programs, but I like QDK most.

Alex
11 May 2011, 09:55
Thanks. Yes, I've just had a bit more of a look into this and it doesn't look like something I can quickly fix - but I did a quick test in Quest 5 and it all seems to work fine there. Should be only a few months :)