User talk:Erig

Regarding your website
In the level calculation thing, the new monsters aren't listed (as of the update of winter 2006), just a heads up :)

14:11, 19 December 2006 (PST)

There's a reason for that. Only monsters that have an XP amount are listed there. Currently I have:

+-+--+--++ +-+--+--++ +-+--+--++
 * id | monster                  | xp   | isboss |
 * 146 | orshabaal               | NULL |      1 |
 * 171 | quara constrictor scouts | NULL |     0 |
 * 178 | quara hydromancer scouts | NULL |     0 |
 * 179 | quara mantassin scouts  | NULL |      0 |
 * 180 | quara pincher scouts    | NULL |      0 |
 * 181 | quara predator scouts   | NULL |      0 |
 * 183 | the ron the ripper      | NULL |      0 |
 * 184 | mammoths                | NULL |      0 |
 * 185 | the deadeye devious     | NULL |      0 |
 * 186 | the brutus bloodbeard   | NULL |      0 |
 * 187 | the lethal lissy        | NULL |      0 |
 * 188 | the general murius      | NULL |      1 |
 * 189 | thul                    | NULL |      1 |
 * 190 | morgaroth               | NULL |      1 |
 * 191 | the tiquandas revenge   | NULL |      0 |
 * 192 | ferumbras               | NULL |      1 |
 * 352 | quara predators         | NULL |      0 |
 * 354 | brutus bloodbeard       | NULL |      1 |
 * 355 | lethal lissy            | NULL |      1 |
 * 356 | ron the ripper          | NULL |      1 |
 * 357 | deadeye devious         | NULL |      1 |
 * 358 | tiquandas revenge       | NULL |      1 |
 * 359 | nomads                  | NULL |   NULL |
 * 360 | wyverns                 | NULL |   NULL |
 * 361 | defilers                | NULL |   NULL |
 * 362 | destroyers              | NULL |   NULL |
 * 363 | diabolic imps           | NULL |   NULL |
 * 364 | hellfire fighters       | NULL |   NULL |
 * 365 | lost souls              | NULL |   NULL |
 * 366 | nightmares              | NULL |   NULL |
 * 367 | plaguesmiths            | NULL |   NULL |
 * 368 | spectres                | NULL |   NULL |
 * 369 | apprentice sheng        | NULL |      1 |
 * 370 | munster                 | NULL |   NULL |
 * 371 | lavaholes               | NULL |   NULL |
 * 372 | blightwalkers           | NULL |   NULL |

Care to fill them in? Give me a format like:

update monsterlist set xp=666 where id=146;

so I can copy/paste! :P --Erig 01:51, 20 December 2006 (PST)

You mean, copying the list with the NULL gaps in there with the experience or giving the monster ID something like:

"update monsterlist set xp=10000 where id=146;" whereas the "146;" would be the orshabaal? Tell me, and I'll be pleased to do that. :)

Maverick the hunter 05:36, 20 December 2006 (PST)

The second one.

-

Alright! Here it goes, the order follows from the list you gave to me:

update monsterlist set xp=10000 where id=146; update monsterlist set xp=200 where id=171; update monsterlist set xp=800 where id=178; update monsterlist set xp=100 where id=179; update monsterlist set xp=600 where id=180; update monsterlist set xp=400 where id=181; update monsterlist set xp=500 where id=183; Mammoth wasn't added because it's not in game yet so I can't tell what exp will it be set to. update monsterlist set xp=500 where id=185; update monsterlist set xp=500 where id=186; update monsterlist set xp=500 where id=187; update monsterlist set xp=330 where id=188; update monsterlist set xp=1800 where id=189; update monsterlist set xp=15000 where id=190; update monsterlist set xp=1755 where id=191; update monsterlist set xp=12000 where id=192; update monsterlist set xp=1600 where id=352; the pirates id are duplicated (354, 355, 356, 357 are corresponding to the monsterids 183, 185, 186 and 187, same thing with the tiquandas revenge) update monsterlist set xp=60 where id=359; update monsterlist set xp=515 where id=360; update monsterlist set xp=2500 where id=361; update monsterlist set xp=2000 where id=362; update monsterlist set xp=1950 where id=363; update monsterlist set xp=2200 where id=364; update monsterlist set xp=2500 where id=365; update monsterlist set xp=2150 where id=366; update monsterlist set xp=3000 where id=367; update monsterlist set xp=1350 where id=368; update monsterlist set xp=100 where id=369; update monsterlist set xp=80 where id=370; update monsterlist set xp=3350 where id=372; That's all. :) I hope I helped, 18:54, 20 December 2006 (PST)

Done, thanks! :) --Erig 01:13, 21 December 2006 (PST)

Preview reminder?
Is there a way to provide a reminder for people to preview a page before saving, something in Mediawiki maybe. I don't know if it bothers anyone else but some people will re-edit some article several times without previewing and end up changing nothing. This bothers me just when quick checking Recent changes for neatness, accuracy and vandalism. This is not a huge deal but to somehow implement a message to remind people to preview before saving, since most ignore the button or do not know what it means. --DM ><((°> Contribs <°))>< talk to me 18:36, 17 April 2006 (CDT) 18:46, 23 December 2006 (PST)

Just today i discovered that i cannot use alt +p or +s for previewing and saving my edits. The only connection i see to this happening is i updated firefox from version 1.0.~ to 2.0.0.1. So if you know about this or if this is something to do with wiki, if you can clarify. --DM ><((°> Contribs <°))>< talk to me 18:36, 17 April 2006 (CDT) 18:08, 7 January 2007 (PST)

Firefox 2+ uses Shift+Alt for access keys, not just Alt. --Erig 18:17, 7 January 2007 (PST)

I saw an wiki (Wikipedia maybe?) where the save button was disabled on your first edit and not until you have previewed it at least once the button was enabled. This way people HAVE to preview their edits before saving. Maybe you could add this? --  Alreth &raquo; ' Talk &raquo; ' Contributions &raquo;  07:27, 8 January 2007 (PST)

Amariellus Weak
well 1st i want to gratz you about your job, secondly, the reason of my writing is to ask if someone could controle what people writes cause anybody can wrtite any bull shit and thats not good for this great page

Well, this wiki has been running for a few years now and we've seen some people coming here to spam, remove articles and write false information. But this have hardly been much extra work because the administrators can with 2-3 clicks ban the user, his IP and automatically revert all edits made with the account. Having admins/moderators to check every article before saving it would require A LOT more work and would kill the whole idea of an wiki. --  Alreth &raquo; ' Talk &raquo; ' Contributions &raquo;  07:27, 8 January 2007 (PST)

Logo??
Have you consider adding a logo so it can appear in the Monobook skin?

--Neoarchon 12:25, 22 January 2007 (PST)

Lotteries
I'm sorry to come in the Wiki to report this, but the lottery feature to check the thread where the one responsible for organising the lottery is wrongly set, it's pointing towards the old forum system (index.php?subtopic=thread), whereas the new system is ?action=thread&threadid, not a huge bug, however a bit annoying. :p

Thanks in advance,

Fixed. --Erig 03:35, 28 January 2007 (PST)

Account stealing?
I received this e-mail: Someone (probably you, from IP address 81.227.94.103) requested that we send you a new password for TibiaWiki (http://tibia.erig.net/index.php). The password for user "Genosonic" is now "******". You should log in and change your password now.

If someone else made this request or if you have remembered your password and you no longer wish to change it, you may ignore this message and continue using your old password. Notice I removed the password I got, but I didn't ask for such a thing so someone from that IP is trying to steal my account, can you check on that person? 04:24, 31 January 2007 (PST)

New Policy Proposal
dear Erig, It's been a hot topic lately between editors, the possibility of writting a Policy paragraph about quest-spoiling information on pages without a proper warning. Now that TibiaWiki is finally considered a supported fansite, we wouldn't want people to unintentionally get quest-spoiling information on the wiki, and also, it's been kept like an unwritten policy for a time now (editors are told to remove in-depth spoiling information and/or add warnings to the page). Therefore, Whitelaces wrote a proposal about it on the Policy Talk Page. You'll be able to read more about it on that page. We're now currently looking for other editors' feedbacks and your approval to make it a new Policy paragraph. Best wishes  Nagatho Goldenflag  Talk Contributions 07:53, 12 February 2007 (PST)

Regarding de TibiaWiki
In almost all the articles, you can see the TibiaWiki:General_disclaimer page, from what I suppose, this link is in there for a reason, yet, there is no text in there. Isn't it a good idea to add something up in that page now that the TibiaWiki has became a part of the main website (erig.net)?

Just my two cents, and thanks in advance, 16:17, 18 February 2007 (PST)

Spoiler and Show/Hide Text MediaWiki Extension
While looking for a good way to handle spoilers on normal articles... I came across a MediaWiki extension that someone had written. I took that extension and modified it for easier use, increased flexibility, and cleaner appearance.

Installation instructions are to:

1. copy/paste the code below into a new file "spoiler.php" and place it in the MediaWiki /extensions/ folder.

Next:

2. put the following line in the LocalSettings.php:

require_once("$IP/extensions/spoiler.php");

An example of using this extension after it is installed would be like this:

Whoa... this guy knows everything about that one mysterious place.. check it out:

Player: quest

That One Guy: I bet you can figure it out with my directions. All you need to do is...

Everything in the "spoiler" tags would be hidden by javascript until the user clicked "show/hide spoiler info". I foresee a template being created as a wrapper around this extension in order to set article category, etc.

Just as a warning... I do not have an instance of MediaWiki that I can test this on, so my changes have not been tested yet. If you get any errors after adding this... please record them before you remove the hooks so that they can be fixed.

As with all changes to the wiki, it is entirely at your own discretion if you want to add this or not. I just ask that you let me know one way or the other so that I don't keep bugging you about it.

Thanks!

spoiler.php: 
 * 6) This work is licensed under a Creative Commons Attribution-Noncommercial-Share
 * 7) Alike 2.5 License. Some rights reserved.
 * 8) http://creativecommons.org/licenses/by-nc-sa/2.5/
 * 1) http://creativecommons.org/licenses/by-nc-sa/2.5/


 * 1) Modified February 2007 by Patrick Delancy for use in TibiaWiki ( http://tibia.erig.net/ )

$wgExtensionFunctions[] = "wfSpoilerExtension"; $wgHooks['OutputPageBeforeHTML'][] = 'spoilerParserHook' ;

function wfSpoilerExtension { global $wgParser; # register the extension with the WikiText parser # the first parameter is the name of the new tag. # the second parameter is the callback function for # processing the text between the tags $wgParser->setHook( "spoiler", "renderSpoiler" ); }

function wfSpoilerJavaScript { return "\n". "\n". "function getStyleObject(objectId) {\n". "   // checkW3C DOM, then MSIE 4, then NN 4.\n". "   //\n". "   if(document.getElementById) {\n". "     if (document.getElementById(objectId)) {\n". "	    return document.getElementById(objectId).style;\n". "     }\n". "   } else if (document.all) {\n". "     if (document.all(objectId)) {\n". "	    return document.all(objectId).style;\n". "     }\n". "   } else if (document.layers) { \n". "     if (document.layers[objectId]) { \n". "	    return document.layers[objectId];\n". "     }\n". "   } else {\n". "	  return false;\n". "   }\n". "}\n". "\n". "function toggleObjectVisibility(objectId) {\n". "   // first get the object's stylesheet\n". "   var styleObject = getStyleObject(objectId);\n". "\n". "   // then if we find a stylesheet, set its visibility\n". "   // as requested\n". "   //\n". "   if (styleObject) {\n". "       if (styleObject.visibility == 'hidden') {\n". "           styleObject.visibility = 'visible';\n". "           styleObject.position = 'relative';\n". "       } else {\n". "           styleObject.visibility = 'hidden';\n". "           styleObject.position = 'absolute';\n". "       }\n". "       return true;\n". "   } else {\n". "       return false;\n". "   }\n". "}\n". " \n"; }

function spoilerParserHook( &$parser, &$text ) { $text = wfSpoilerJavaScript. $text; }

function wfMakeSpoilerId { $result = "spoiler_"; for ($i=0; $i<20; $i++) $result .= chr(rand(ord('A'), ord('Z'))); return $result; }

function renderSpoiler( $input, $argv, &$parser ) { # $argv is an array containing any arguments passed to the # extension like .. # Put this on the sandbox page: (works in MediaWiki 1.5.5) #  Testing text **example** in between the new tags
 * 1) The callback function for converting the input text to HTML output

$localParser = new Parser; $outputObj = $localParser->parse($input, $parser->mTitle, $parser->mOptions); $spoilerId = wfMakeSpoilerId;

$output = ""; $output .= ($argv["linktext"] == '' ? 'Click Here to Show/Hide Spoiler Information' : $argv["linktext"]). " \n"; $output .= " \n"; if (!in_array("hidewarning", array_values($argv))) { $output .= "\n"; $output .= "   ". ($argv["headwarningtext"] == ? "Spoiler warning: Quest and/or game spoiling details follow.''" : $argv["headwarningtext"]). "\n"; $output .= " \n"; }   $output .= $outputObj->getText. "\n"; if (!in_array("hidewarning", array_values($argv))) { $output .= "\n"; $output .= "   ". ($argv["footwarningtext"] == '' ? "Spoiler ends here." : $argv["footwarningtext"]). "\n"; $output .= " \n"; }   $output .= " \n"; if ($argv["collapsed"] != "false") { $output .= "\n"; $output .= "   toggleObjectVisibility('" . $spoilerId . "')\n"; $output .= " \n"; }

return $output; } ?>

-- Ecce potestas casei  --  Whitelaces &dagger;  Talk &dagger; -- 13:49, 19 February 2007 (PST)

This has been done. --Erig 23:38, 19 February 2007 (PST)

Fabulous! Thanks, Erig! I think this will help the wiki a lot. You can see the first article I updated with this extension here.

There was a small problem with automatically hiding the spoiler (it should be hidden by default)... it appears that MediaWiki does not render in-line javascript the way I expected.

Can you please make this small change to the spoiler.php file:

replace the entire routine "renderSpoiler" with the following code:

function renderSpoiler( $input, $argv, &$parser ) { # $argv is an array containing any arguments passed to the # extension like .. # Put this on the sandbox page: (works in MediaWiki 1.5.5) #  Testing text **example** in between the new tags
 * 1) The callback function for converting the input text to HTML output

$localParser = new Parser; $outputObj = $localParser->parse($input, $parser->mTitle, $parser->mOptions); $spoilerId = wfMakeSpoilerId;

$output = ""; $output .= ($argv["linktext"] == '' ? 'Click Here to Show/Hide Spoiler Information' : $argv["linktext"]). " \n"; $output .= " \n"; if (!in_array("hidewarning", array_values($argv))) { $output .= ""; $output .= ($argv["headwarningtext"] == ? "Spoiler warning: Quest and/or game spoiling details follow.''" : $argv["headwarningtext"]); $output .= " \n"; }   $output .= $outputObj->getText. "\n"; if (!in_array("hidewarning", array_values($argv))) { $output .= ""; $output .= ($argv["footwarningtext"] == '' ? "Spoiler ends here." : $argv["footwarningtext"]); $output .= " \n"; }   $output .= " \n"; if ($argv["collapsed"] != "false") { $output .= "<script language=\"JavaScript\">\n"; $output .= "toggleObjectVisibility('" . $spoilerId . "')\n"; $output .= " \n"; }

return $output; }

Everything else worked great!

If this still does not work... there is one more change that will definitely work, but it will make the spoiler permanently hidden in browsers with javascript disabled... I would prefer not to do that if possible, but it may be necessary.

Let me know when you have made this change, and I'll test it out.

Thanks Erig!

-- <span title="(latin) Thank you for not smoking">Tibi gratias agimus quod nihil fumas  -- <span style="background-color:White; color:#F06A0F" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Whitelaces &dagger; <span style="font-variant: small-caps;background-color:#F06A0F; color:white" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Talk &dagger; -- 06:50, 20 February 2007 (PST)

Done. --Erig 12:08, 20 February 2007 (PST)

Awesome! It looks great now! Thanks!

--'' <span title="(latin) Don't applaud. Just throw money">Non plaudite. Modo pecuniam jacite '' -- <span style="background-color:White; color:#F06A0F" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Whitelaces &dagger; <span style="font-variant: small-caps;background-color:#F06A0F; color:white" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Talk &dagger; -- 14:27, 20 February 2007 (PST)

About the new spoiler feature
Hello. I wanna suggest you two minor modifications on the spoiler feature, it's not important, but it'll make it look cooler. Look the space between the lines here, and a link

If you look, there's a small space between the spoiler info and the line spoiler warning. But there's not a space between the info and the spoiler end and there should be a small space. Just to make it "better" to read, mostly links etc. The 2° thing is that we must "jump" 2 lines to add the spoiler, else he "eat" half of the upper line... What you think?

--  &dagger; Pudd Knight &dagger;  Talk <span style="small-caps; border: 0px solid #186fc8; background-color:White; color:#186fc8" title="My Contributions"> Contribs  -- 17:24, 26 February 2007 (PST)

Yeah, I see what you mean. It's all simple CSS stuff to fix it, but the complications come with how MediaWiki alters the output. It adds line breaks and paragraph tags pretty regularly based on whitespace. The code below should make a big difference, but since I can't test it, I won't know for sure until Erig makes the update.

Erig... If you could once again replace the "renderSpoiler" function with this code... it should take care of the minor visual problems that Pudd Knight mentioned. Thanks!

function renderSpoiler( $input, $argv, &$parser ) { # $argv is an array containing any arguments passed to the # extension like .. # Put this on the sandbox page: (works in MediaWiki 1.5.5) #  <example argument="foo" argument2="bar">Testing text **example** in between the new tags
 * 1) The callback function for converting the input text to HTML output

$localParser = new Parser; $outputObj = $localParser->parse($input, $parser->mTitle, $parser->mOptions); $spoilerId = wfMakeSpoilerId;

$output = "<span onClick=\"toggleObjectVisibility('" . $spoilerId . "'); return false;\" style=\"" . ($argv["linkstyle"] == '' ? "cursor:pointer; background-color:#ffdddd; color:#000000; font-weight:bold; padding:4px 4px 2px 4px; border:solid red 1px; line-height: 24;" : $argv["linkstyle"] ) . "\">"; $output .= ($argv["linktext"] == '' ? 'Click Here to Show/Hide Spoiler Information' : $argv["linktext"]). " ";   $output .= "<div id=\"" . $spoilerId . "\" style=\"visibility:visible; position:relative; " . ($argv["spoilerstyle"] == '' ? "" : $argv["spoilerstyle"]) . "\">"; if (!in_array("hidewarning", array_values($argv))) { $output .= "<div style=\"" . ($argv["warningstyle"] == '' ? "border-top: 2px red solid; border-bottom: 2px red solid; padding:3px; line-height: 22px;" : $argv["warningstyle"]) . "\">"; $output .= ($argv["headwarningtext"] == ? "Spoiler warning: Quest and/or game spoiling details follow.''" : $argv["headwarningtext"]); $output .= " "; }   $output .= $outputObj->getText. "\n"; if (!in_array("hidewarning", array_values($argv))) { $output .= "<div style=\"" . ($argv["warningstyle"] == '' ? "border-top: 2px red solid; border-bottom: 2px red solid; padding:3px; line-height: 22px;" : $argv["warningstyle"]) . "\">"; $output .= ($argv["footwarningtext"] == '' ? "Spoiler ends here." : $argv["footwarningtext"]); $output .= " "; }   $output .= " "; if ($argv["collapsed"] != "false") { $output .= "<script language=\"JavaScript\">\n"; $output .= "toggleObjectVisibility('" . $spoilerId . "')\n"; $output .= " \n"; }

return $output; }

-- <span title="(latin) I can't believe I ate the whole thing">Non possum credere me totum edisse  -- <span style="background-color:White; color:#F06A0F" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Whitelaces &dagger; <span style="font-variant: small-caps;background-color:#F06A0F; color:white" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Talk &dagger; -- 07:32, 1 March 2007 (PST)

After this change the spoiler doesn't seem to work (spoiler is visible by default, and "Click Here to Show/Hide Spoiler Information" box has like 10 empty lines after and before it) on Hagor and Manafluid pages, even though it seems to work on this page and some others. --Ville-v 05:12, 2 March 2007 (PST)

Yes.... that is because of one small typo.

line-height: 24;

needs to be changed to:

line-height: 24px;

That's what happens when you can't test your code before implementing it. Oh well.

I also notice a couple other small things about the formatting... so I am including the entire routine again.

'''Erig... as soon as you can, please update the "renderSpoiler" routine again with this code:'''

function renderSpoiler( $input, $argv, &$parser ) { # $argv is an array containing any arguments passed to the # extension like .. # Put this on the sandbox page: (works in MediaWiki 1.5.5) #  <example argument="foo" argument2="bar">Testing text **example** in between the new tags
 * 1) The callback function for converting the input text to HTML output

$localParser = new Parser; $outputObj = $localParser->parse($input, $parser->mTitle, $parser->mOptions); $spoilerId = wfMakeSpoilerId;

$output = "<span onClick=\"toggleObjectVisibility('" . $spoilerId . "'); return false;\" style=\"" . ($argv["linkstyle"] == '' ? "cursor:pointer; background-color:#ffdddd; color:#000000; font-weight:bold; padding:4px 4px 2px 4px; border:solid red 1px; line-height: 24px;" : $argv["linkstyle"] ) . "\">"; $output .= ($argv["linktext"] == '' ? 'Click Here to Show/Hide Spoiler Information' : $argv["linktext"]). " ";   $output .= "<div id=\"" . $spoilerId . "\" style=\"visibility:visible; position:relative; " . ($argv["spoilerstyle"] == '' ? "" : $argv["spoilerstyle"]) . "\">"; if (!in_array("hidewarning", array_values($argv))) { $output .= "<div style=\"" . ($argv["warningstyle"] == '' ? "border-top: 2px red solid; border-bottom: 2px red solid; padding:3px; line-height: 22px;" : $argv["warningstyle"]) . "\">"; $output .= ($argv["headwarningtext"] == ? "Spoiler warning: Quest and/or game spoiling details follow.''" : $argv["headwarningtext"]); $output .= " "; }   $output .= "<div id=\"" . $spoilerId . "_content\" style=\"" . ($argv["contentstyle"] == '' ? "padding-top:4px; padding-bottom:4px;" : $argv["contentstyle"]) . "\">". $outputObj->getText. " ";   if (!in_array("hidewarning", array_values($argv))) { $output .= "<div style=\"" . ($argv["warningstyle"] == '' ? "border-top: 2px red solid; border-bottom: 2px red solid; padding:3px; line-height: 22px;" : $argv["warningstyle"]) . "\">"; $output .= ($argv["footwarningtext"] == '' ? "Spoiler ends here." : $argv["footwarningtext"]); $output .= " "; }   $output .= " "; if ($argv["collapsed"] != "false") { $output .= "<script language=\"JavaScript\">\n"; $output .= "toggleObjectVisibility('" . $spoilerId . "')\n"; $output .= " \n"; }

return $output; }

Thanks, Erig!

-- <span title="(latin) Farewell Caesar, they who are about to die salute you.">ave, Caesar, morituri te salutant  -- <span style="background-color:White; color:#F06A0F" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Whitelaces &dagger; <span style="font-variant: small-caps;background-color:#F06A0F; color:white" title="&chi;&rho;&iota;&sigma;to&sigmaf; &alpha;n&epsilon;&sigma;t&eta;, &alpha;&lambda;&eta;&theta;&omega;&sigmaf; &alpha;n&epsilon;&sigma;t&eta;"> Talk &dagger; -- 06:09, 2 March 2007 (PST)