James Riley

I'm sure some people have questions about your intentions with these hashes, but hey, information is free, so i'll just presume you're a good person. Also anyone who still uses md5 sort of deserves to get their hashes cracked so. John The Ripper is the classic password hash cracker, it has wordlist mode (where you can provide a dictionary of thousands of words and it'll try them all), and incremental mode (where it'll try every possible combination (this takes a long time). You'll need to format your hashes in unix passwd file format for it to pick them up. If you've got a decent graphics card IGHASHGPU could be for you. It uses your GPU as a massively parallel processor which speeds things up very much.

Icecast is a good free tool for doing online radio/media streaming. I'd recommend reading through their documentation here: http://www.icecast.org/docs/icecast-trunk/icecast2_introduction.html

Why would you want to do this? Table-based designs are bane on web design. What's your ultimate aim? perhaps there's a better way of getting there.

Bare in mind W3Schools are not connected to the W3C in any way. I wouldn't give their certification much value.

I agree with zed that doing it properly is always better, google translate gives very poor translations, for an example of this try translating some text then translating it back to english and see how mangled it is. However, if you still want it, what you seek is available here. http://translate.google.com/translate_tools

Using CSS Opacity like recommended above by Wickham will result in the whole div being transparent, including text. You can get around that by having text in another div and absoluting that ontop, but that's a hassle. What it'd do is use a transparent PNG as your background for the div, then you don't need to worry about css support. IE5.5/6 don't support transparent pngs, but with http://www.twinhelix.com/css/iepngfix/demo/ you can support even them. Other tips that can improve your site. In the gallery you're using the full images scaled down with html for the thumbnails, this causes the page to take an age to download, you really need proper thumbnail images downscaled to the right size. Also on the large background image you have on the homepage, it looks visually very good, however it takes an age to download due to it's 800kb size, quickly you can cut that more than in half without visible loss of quality. Additionally it's not progressively loading, im not sure whats causing that.

I think the misunderstanding here is the difference between what the html/css specifications say, and what browsers will actually render. Browsers are *very* forgiving, and will allow you to do any number of invalid things (another common one that browsers let you do, but is invalid is wrapping a div (block level element) with an anchor (inline element) <a href="/"> <div> Hello </div> </a> *this is invalid It's often called "tag soup", if you put in something vaguely html like browsers will render it. However that doesn't mean you should ignore specifications, browsers may render alot of bad code, they dont necessarily all render it in the same way, so if you want consistency, specs are the way to go. All in all, if it doesn't go through the w3c html/css validators, don't do it, even if it works.

You want the :active pseudo-class <style> .menu { background-image: url("image/one.png"); } .menu:active { background-image: url("image/two.png"); } </style> <a class="menu">Menu Item</a> Something like that, the two.png will be used when the item is active. However to avoid a brief flash when the images change its wise to use the same image, for example : then use background-position: in the active to swap to the active one. Edit: :active will show while you're clicking on the element, :visited will show forever after theyve visited a page once.

I think CSS Sticky Footer is what you want : http://www.cssstickyfooter.com/using-sticky-footer-code.html

Hidden fields in forms are usually used for session tokens to prevent CSRF attacks, but can also be used to attach information to a form submission that you might not really need the user to see. For example, I have a "Request a Quote" form on a website that sends a email to the site owner with details about the user. It has a hidden field that is automatically filled in php with the Offer the user was looking at before they click on the link. The user doesn't really need to see this information, she knows what offer she was just looking at, but the site owner does so he can create a quote for that offer. To explain the CSRF attacks, if, say a bank website has some form which posts to transfer-cash.php, If on my site i can use some evil stuff to POST to that script with cashTo=my_account ammountCash=99999, because the POST is running on the users' side it'll send his cookies with it, and if he's already authenticated with the bank then the request will go through and I've just stole his money. To protect against these attacks if you add a hidden session token every time you present a form, then require this matching token be provided before you process the form, then it help mitigate some of this.

Yeah, its definitely your javascript block replace: <script type="text/javascript"> now = new Date theYear=now.getYear() if (theYear < 1900) theYear=theYear+1900 document.write(theYear) </script> with <script type="text/javascript"> //<![CDATA[ var now = new Date(); var theYear = now.getYear(); if (theYear < 1900) { theYear = theYear + 1900; } document.write(theYear); //]]> </script> At no extra price, free of charge i've gone fixed up your javascript too.

You'd have to post the whole document for me to say more but in the original error message it output a snippit of the error that looks like javascript "if (theYear < 1900)"

#top_bar_hidden{ margin: 0px 0px 0px 8px; } You have an 8px margin-left on your div, that'll explain the gap.

.page h1.entry-title { display:none; } Is probably what you want. Wordpress puts classes on the <body> tag telling you what sort of page it is (page, single) so you can select on those in css.

It seems that you have a website coded in xhtml which you are delivering with the application/xml+xhtml content type. While this is what the standards say is the "correct" way to deliver xhtml, it unfortunately does not work at all in Internet Explorer so is generally avoided. However when you deliver as application/xml+xhtml good browsers are put into xml standards mode, this means any invalid xml will stop all rendering of the website (as opposed to the way they usually switch to quirks and try to render around your problem) All of this is a long explanation, but not really helpful so i'll get to the solution. You can either a) change your htaccess/server configuration to deliver your files as text/html change your xhtml so that it is valid. Valid xhtml requires closing tags for everything, requires lower case tagnames, requires boolean attributes written in full (like <option selected="selected">) requires quotes around attributes, and requires all markup characters (such as < > & ") to be escaped or in CDATA sections. This last bit is what you're code is erroring on. the line that is highlighted appears to be some javascript where you're using the less-than test. If you were to wrap you javascript like <script type="text/javascript"> //<![CDATA[ if (thing > 10) { alert("test & test"); }; //]]> </script> you wouldn't have the problem.