i'm in a guild that i'm trying to setup the roster for, i've done it before and had no problem with it except now this guild has a ê in the name.

when i try uploading the information the name of the guild is Thrêat and the roster writes it as Thr?at and it says no guild found.

i only have version 1.6 of the roster and PHP version 4.4.2

gonna try newer version of 1.7 but does anyone know of any fixes if that doesn't just fix it?

Open CP.lua and find your guild name and copy it

And I would suggest upgrading to 1.7.0, just follow the directions VERY carefully
http://www.wowroster.net/wiki/index.php ... ing_Roster

ya i did copy it direclty but haven't updated yet...gonna do it right now.

Another good reason to work with utf8 databases

Yeah, but converting roster to utf-8 would take quite some time

And we would also have to convert uploaded lua files to utf-8 as well

the new verison fixed it...works fine.

zanix wrote:Yeah, but converting roster to utf-8 would take quite some time

And we would also have to convert uploaded lua files to utf-8 as well

http://www.wowroster.net/Forums/viewtop ... .html#4820
(first method for convert database, call this method at the update of the site, second method for set client encoding, call just after database connection) and that's all

And you don't have to convert uploaded lua to utf-8 because it's already the encoding used in those files...

The locale files would have to be combed through and converted
As well as alot of functions that depend on the original coding for word matching would have to be changed as well

In short, this won't happen for 1.7.1

zanix wrote:The locale files would have to be combed through and converted
As well as alot of functions that depend on the original coding for word matching would have to be changed as well

In short, this won't happen for 1.7.1

Truly ? The local files are already utf8 compliants ( html entities like & or € works) and strings used in regexp are already written in utf8 because lua files are in utf8, so stored data are in utf8.

My own version works quite well. Some troubles with Bonus summary but I have not noticed any other problem (some localization problems I think, regexp not realy the same, but that's not the point).

Moreover, version 1.7.0 already works in utf8, except the database that is set in the defaut encoding negociated by php-mysql extension : if the mysql client default encoding is utf8, you don't have to write any code.

If you want, I can check into whole code to verify I'm not telling foolish things.

(yes I know, I'm quite tenacious, but it's my nature , don't take offence ; I bore my workmates with such utf8 considerations because I am convinced that unicode is the better way to solve transcoding problems ; make no mistake, I just want to share my own experience, and when you start to work in utf8, you'd better code all in utf8 without any transcoding)

For the others that are interested in utf8
http://en.wikipedia.org/wiki/UTF-8

I didn't write it will be fine to incorporated in 1.7.1 , I juste wrote that developpements to migrate to utf8 will be easier that you think, and will solve many many localization problems.

Don't get me wrong, we do want to convert to utf-8
I'm just saying that it won't happen until version 1.8

I really apreciate all the info you have given me to convert a latin based db to utf-8

Ok I just misunderstand ( the damned language barrier )

Away from the point :

I'm really interested in taking a more active part, maybe as developper ( it's my job , I write php code all the day ), by the way, if you need one...