ok, i was wondering because some characters were html coded.

As far as I understand it.. there should be no PHP code (besides the variable define) in the localization file. Can you give an example?

Yeah, the characters *should* be encoded in utf8, but they are not in the old files because this rule wasn't enforced before

You are more than welcome to change them if you want to

in the localizationfile in line 86 and 87: in which contens is scanned used??

edit: line 210 and 211:
in the actual german localization roster is translated as members and and alternate als alternate perspective. in which contens is roster or alternate used?

and line 216: where is scope used?

SethDeBlade wrote:in the localizationfile in line 86 and 87: in which contens is scanned used??

edit: line 210 and 211:
in the actual german localization roster is translated as members and and alternate als alternate perspective. in which contens is roster or alternate used?

and line 216: where is scope used?

$lang['realm_ignored'] - doesn't look like this is used

$lang['guild_realm_ignored'] - is used, but I would still translate the above as well

$lang['roster'] - this isn't used either, I think this was just to name our program, but now WoWRoster is hard coded in a lot of places

$lang['alternate'] - this isn't used, I don't know what its for

$lang['scope'] - only used in the menu config, in the button tooltips
Scope is realm, guild, char, util

does "Not Scanned" in $lang['realm_ignored'] stand for not checked?? Or is it more the meaning of not parsed?

Its meant that it wasn't scanned because it wasn't parsed because the upload rules rejected it

I think the "roster" and "alternate" translations were for the old menu buttons. The "roster" button linked to the memberslist. Alternate sorted by guildrank or class, I think.