Ron
@Ron
Best posts made by Ron
Latest posts made by Ron
-
RE: MSXML WTF & lot's of head banging against wall
You may be surprised, but the output is 100% W3C compliant HTML 4.01, which is the default output method of a stylesheet. A document is required to provide a character encoding to the user agent either by means of an HTTP "Content-Type" header or a <META> tag in the head of the document:
Specifying the character encoding
By the HTML 4.01 DTD, the META tag is FORBIDDEN to have an ending tag:
Thus, the MSXML parse has guaranteed you a fully compliant HTML 4.01 document, regardless of your ability to send a content type in an HTTP header. Your intention is perhaps to choose the xsl:output method of "xml" as described by PC Paul in an earlier post. Beware that without the proper content type of "application/xhtml+xml" your browser may render it funky. Consider the following:
<html>
<body><textarea/><div>This is "outside the text area"</div></body>
</html>
Fully compliant XML. Fully broken HTML 4.01. IE, Firefox, and Safari render it in a way that you may not expect. Content type is everything.
I hope this can give you some appreciation of the difficulty in standards compliance, and I also hope that you have a better understanding of the perceived problem and can find the solution you're wanting.
-
RE: I try to help these kids, I really do.
@DaveK said:
I have a truly marvellous proof of this proposition, which this WTF is unfortunately too narrow to contain.
Now THAT was funny!
-
RE: Things not to say at a job interview
@codenator said:
At what point did the interview stop? I'm surprised he made it past the 3rd ersponse.
I'm fairly new at the interview process, and the resume looked good and his sample code looked decent enough, so I was trying to find something good about him. Lesson learned ten fold.
How much time did you waste on this waste of space?
-
Things not to say at a job interview
I recently interviewed someone for a developer position. He was a shining example of what not to do at a job interview. So I present a practical guide of things to not say at a job interview:
When asked about your first company: "I purposely ran it into the ground."
When arriving: "I was going to wear jeans, but I decided at the last minute to get dressed up."
When
asked about working with others: "I don't like foreign programmers
because I can't understand them and I end up doing all the work myself."
When asked why you have yet to complete your bachelor's: "School is too easy."
When asked why you chose development as a career path: "Development?"
When asked about teamwork: "I hate working with engineers."
When asked about learning experiences: "Everything I need to know is on the web."
When asked what types of tasks you wouldn't like doing: "I don't want to do bullshit work."
When asked about his lead skills: "The people I've worked with were technical in their own ghetto mind."
When asked to solve a programming type of problem: "I don't know what an algorithm is, but my friend has used them before."
When asked why you want to work for the interviewer's company: "You called me!"
When asked what hobbies or interests you have: "My family is very important. My mother died recently..."
When the floor opens up for you to ask questions: "I don't really know... what position am I interviewing for?"Also, don't submit code as a sample of your work that you copied from a newsgroup. And, yes, this all came from one person.