PlaneShift

Support => Technical Help: IN GAME bugs (after loading world) => Topic started by: Arheos on January 01, 2006, 08:25:41 am

Title: In-game text problem - squares for EOF
Post by: Arheos on January 01, 2006, 08:25:41 am

I did look in the forums but couldn\'t find something similar. Sorry if it\'s somewhere out there already.
Here\'s the problem:
When the NPC\'s talk back to me with long sentences, instead of changing lines (carriage return) I see a square.
Same thing when I read one of the books as you can see from the image.
The system it runs on is Win2K.
Anyone to shed some light in this?

(http://img511.imageshack.us/img511/3748/planeshifttxtproblem0dq.jpg) (http://imageshack.us)

If the image is too big or not allowed tell me and I will put a simple link to it.
Thank you

Title:
Post by: stfrn on January 01, 2006, 08:40:30 am

The cause of this problem is that the gui can only display ascii characters- but any unicode characters can be inputed. MSword for one likes to use it\'s own symbols instead of common punction such as the \"\" in that picture.

Title:
Post by: Arheos on January 01, 2006, 07:16:11 pm

So everyone has this problem or is there a workaround?

Title:
Post by: Nilrem on January 01, 2006, 07:35:58 pm

I too have them, if that\'s what bothers you.
Seems then that it\'s a common issue. ;)

Title:
Post by: Arheos on January 01, 2006, 08:19:46 pm

I wouldn\'t go as far as bother.
Just didn\'t want to be the only one and not know an answer.
Now I do. ;)

Title:
Post by: res on January 09, 2006, 09:07:33 pm

Quote

Originally posted by stfrn
The cause of this problem is that the gui can only display ascii characters- but any unicode characters can be inputed. MSword for one likes to use it\'s own symbols instead of common punction such as the \"\" in that picture.

CS _can_ display Unicode characters (given the font supports them). However, you need to feed the output routines UTF-8 encoded strings.

Title: it happens to us all
Post by: c-2501 on January 10, 2006, 11:24:07 am

basically its a production fault, albeit a fairly minor one, nothing to worry about, and as far as i know cant be fixed client side (at least not simply).