Ventrilo Tech Support

Ventrilo Tech Support (
-   Macintosh Client (
-   -   Cyrillic support (

sdxkokc 09-21-2010 01:33 PM

Cyrillic support
Hey. Ventrillo incorrectly shows Cyrillic

Prog-Rocker 09-21-2010 06:20 PM

the Devs are aware of that problem and are looking into it.

Octavian 12-23-2010 08:05 PM

This problem has been there for years. Can you give us some sort of ETA, please?
I'm trying to figure out which service to purchase for my guild -- Ventrilo or TeamSpeak. And at the moment I can't decide because of this bug.


trankov 03-10-2011 06:06 PM

Maybe I can help you to resolve this long issue
So guys the problem looks like you using one of the 1-bit encodings, but Mac OS X by default using UTF-8, the 2-bit encoding.

That's why English letters displays correctly but non-english shows jabberish.

European (inc. Russian) servers uses UTF-8 codepage. If else, Armory will show jabberish in nicknames but it doesn't. Armory webpage contains HTTP headline "application/xhtml+xml;charset=UTF-8" so, WoW Database uses UTF-8 too.

Apple Interface Builder have to use UTF-8 by default because it's OS system encoding. So the problem is somewhere in compiled modules (not in NIB-file).

The Function, that getting the list of user names, takes them from server in UTF-8, but process them in 1-bit codepage. So, this Function sends the corrupted strings into the userlist display control and it shows them as it got them.

The solution is in the methods that you using for processing strings. I cannot figure out of your programming language and it's methods, but I suggest two possible reasons of the problem.

First, you can use a low-level system strings functions which use byte-to-byte method. And, as if UTF-8 uses 2 bytes for 1 symbol and you may interpret each byte as a symbol, Mac OS X shows 1+zero=OMG.

Second, maybe your programming language uses different methods for Unicode strings and ASCII strings (f.e., Python before version 3). And, when ASCII strings function applying for Unicode string (sorry if I write obvious things, UTF-8 is sort of Unicode), in the exit this problem occurs.

Of course, the reason might be another than these two, but I can't believe this problem can win you.

So, there is not necessary to get the real response from Russian or some other European WoW-server. All that you need is to copy-paste any UTF-8 string from any Russian webpage (try yandex**** for example) and apply your default strings function to it. If you getting different result this is the root of the trouble.

Thank you.

Jaycyn 03-11-2011 01:31 PM

Just to throw in my .02

This could also be and issue with Indianness - Big Indian vs Little Endian byte order or the encoding not specified, or even UTF-16. Conceptually, the code could be something like.

[[[NSString alloc] initWithData:textStream encoding:NSMacOSRomanStringEncoding] autorelease];

unsigned char *bytes=(unsigned char *)[initWithData:textStream bytes];
unsigned char length=*bytes++;

NSString *string=[[NSString alloc] initWithBytes:bytes length: (unsigned int)length encoding: NSUTF8StringEncoding];

Flagship 05-13-2011 10:40 AM

Thanks for the feedback guys. Look at this now.

BlackJack_Krsk 05-29-2011 12:01 AM


When you plan to support Cyrillic languages and other European?

Please, accelerate process!!!

Flagship 05-31-2011 10:47 AM

Cyrillic character set support is done as of today, including several other major languages. So it will be coming in the next release here soon. 05-31-2011 10:30 PM

Flagship, will this also be available for a windows client without the language pack installed?

All times are GMT -5. The time now is 06:54 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.