A fix of 1-10PioneersQuests/l3t_pioneer.xml

[wps]

I started to use this script this morning, and I found a error in l3t_pioneer.xml.

There are 2 quests with the same name "Embedding Runes", somehow the script on svn is the other one.
The quest can't be taken and the quest chain is broken.

It should be 420668, but 424800.

I can't check in the file to svn, so I post it here just in case anyone got this problem too.

[lisa]

if the names are the same then the number shouldn't matter as it uses the GetIdName by using the numbers.

My database has this

Code: Select all

{Name = "Embedding Runes",ID = 420668},
{Name = "Embedding Runes",ID = 424800},

So either ID should work as the names are exactly the same.

Unless you are in a different language and the names are different for the Id's I can't see how it wouldn't work.

[wps]

if the names are the same then the number shouldn't matter as it uses the GetIdName by using the numbers.

My database has this

Code: Select all

{Name = "Embedding Runes",ID = 420668},
{Name = "Embedding Runes",ID = 424800},

So either ID should work as the names are exactly the same.

Unless you are in a different language and the names are different for the Id's I can't see how it wouldn't work.

You're right.
No wonder nobody encountered this before.
The name of these two quests are the same in English, but different in mine.
420668 is the one in Howling Mountains, and other one is in Yrvandis Hollows.

Btw, is there any method to configure micromicro to display unicode characters?
I can't recognize those output strings, because they're not displayed in the correct charset.

Thanks.

[lisa]

I was hoping rock would answer this 1 since I don't really look into the code for other languages.

I thought it was all taken care of by this

Code: Select all

	-- language conversations
	if( bot.ClientLanguage == "RU" ) then
		message = oem2utf8_russian(message);
	else
		message = asciiToUtf8_umlauts(message);	-- for ingame umlauts
	end

Code: Select all

function utf8ToAscii_umlauts(_str)

	-- convert one UTF8 character to his ASCII code
	-- key is the combined UTF8 code
	local function replaceUtf8( _str, _key )
		local tmp = database.utf8_ascii[_key];
		_str = string.gsub(_str, string.char(tmp.utf8_1, tmp.utf8_2), string.char(tmp.ascii) );
		return _str
	end

	_str = replaceUtf8(_str, 195164);		-- ä
	_str = replaceUtf8(_str, 195132);		-- Ä
	_str = replaceUtf8(_str, 195182);		-- ö
	_str = replaceUtf8(_str, 195150);		-- Ö
	_str = replaceUtf8(_str, 195188);		-- ü
	_str = replaceUtf8(_str, 195156);		-- Ü
	_str = replaceUtf8(_str, 195159);		-- ß
	return _str;
end


-- we only replace umlaute, hence only that are important for
-- printing ingame messages
function asciiToUtf8_umlauts(_str)

	-- convert one ASCII code to his UTF8 character
	-- key is the combined UTF8 code
	local function replaceAscii( _str, _key )
		local tmp = database.utf8_ascii[_key];
		_str = string.gsub(_str, string.char(tmp.ascii), string.char(tmp.utf8_1, tmp.utf8_2) );
		return _str
	end

	_str = replaceAscii(_str, 195164);		-- ä
	_str = replaceAscii(_str, 195132);		-- Ä
	_str = replaceAscii(_str, 195182);		-- ö
	_str = replaceAscii(_str, 195150);		-- Ö
	_str = replaceAscii(_str, 195188);		-- ü
	_str = replaceAscii(_str, 195156);		-- Ü
	_str = replaceAscii(_str, 195159);		-- ß
	return _str;
end

[rock5]

I have no idea about languages either. Administrator is the expert I think.

BTW I changed the quest id so next time I commit it will be included. For now you can change it yourself.

Edit: Had 1 idea. Maybe the 3 font sets MM uses are different (although I doubt it). Maybe try a different font. Right click the MM titles bar and select 'default' or 'properties'.

[Jandrana]

Ascii char set should be regarded obsolete when using Windows, because the glyphs for characters with a binary value > 127 are not defined. In good old DOS times, the different code pages were used to print characters with diacritical marks.

Windows uses CP 1252 (mostly referred to as ANSI encoding), which covers most of the latin characters using diacritical marks and nearly all Windows fonts have a complete set of glyphs for this code page. But most modern code in Windows uses UTF16 (wide char api) which lets you cover the whole Unicode character set.

RoM uses UTF8 to encode the strings. So it would be a good idea to translate all strings taken from RoM using MultiByteToWideChar into UTF16. Either keep all strings as UTF16 or translate them back to ANSI using WideCharToMultiByte.