New Build 226 Now Available - Page 2

kbs666 · January 19th, 2017, 09:39 AM

Quote:

Originally Posted by Vargr

I am probably going to regret this, but I will be trying to input some Japanese in my realm - all three alphabets.

Well, in a test realm - after my gameday on Saturday.

I might be stupid, but not that stupid...

Depending on the fonts you have available you should have no trouble. Those are all in one of the MS office fonts IIRC. Once they switched to HTML I took it for granted that meant utf encoding and started using it and haven't had any trouble but I haven't really pushed my luck.

tkarn · January 26th, 2017, 01:41 AM

Updated to .227. Sadly there are the same problems.

daplunk · January 26th, 2017, 01:55 AM

have you logged a fault?

tkarn · January 26th, 2017, 02:00 AM

I logged my problems with .225, and send the automatic report today to LWD.

daplunk · January 26th, 2017, 02:09 AM

Log a new fault just to make sure they know this is an issue with the new build. Unless they are already in contact with you.

tkarn · January 26th, 2017, 02:18 AM

I send an additional email with my .225 case number to the support. The case is still open.

tkarn · February 8th, 2017, 02:55 AM

Updated to .230 today. The converting to other worked fine.

Thank you for your great support.

tkarn Senior Member Join Date: Jun 2007 Posts: 273 January 26th, 2017, 01:41 AM	Updated to .227. Sadly there are the same problems.
#12