boen_robot

You can use git config --get user.nameand similarly for email.Seegit --help configfor details.

@Ingolme, @thescientistHave you two really not heard of phpDocumentor or are you being sarcastic ?

IMHO, it would be best to describe that via an attribute, e.g. <price currency="USD">111.50</price> and infer the preceding "$" upon interpretation.

The proper order is to have the PI ("Processing Instruction"; the "<?" thingy) before the root element.Also, for a validator to recognize your declarations, the namespaces everywhere need to match. In this case, your elements are not in a namespace, so the "noNamespaceSchemaLocation" is the proper attribute to use, i.e. <?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="prob12.34d.xsl"?><ArtistListxmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:noNamespaceSchemaLocation="prob12.34d.xsd"> You're not supposed to see both the data and the formatted HTML... The PI is used exactly to tell the browser to hide the data in favor of whatever the result of the XSLT transformation is (which in your case is an HTML page, but could be an SVG instead for example).Also, no browser does either DTD or Schema validation, so you're not going to get any schema related errors in a browser. For that, you'd need to use the server. e.g. PHP's DOMDocument::schemaValidate() which, as you might be guessing, ignores your XML declaration too. So what's the point of that declaration you ask? IDEs - they can offer you auto completion based on the declared schema, and some can even validate your document "on the fly", and tell you an element is invalid at that location as soon as you write it out.

The problem with putting up "a rocket up their support staff" is that we're not the owners, and that's the only one who they respond to. I don't. Sorry.

Sadly, there's nothing either you or we can do.This is a problem with the host - Invisionzone, which they still haven't fixed.

yes. With "@" in front of the node name.

You don't need either DTD or XSD to render XHTML from an XML document. XSLT is enough.DTD or XSD is needed to validate the grammer of an XML document. To actually perform the validation, yes, you need to use a validator.The order I'd advice is XML, (XSLT & XPath), (DOM & XPath), XSD, DTD. XPath needs to be studied together with XSLT and/or DOM, because it doesn't make sence in a vacuum. XSLT on the other hand can't really do anything without XPath. DOM could, but having the "node sence" that XPath provides helps.As for attributes - an attribute can occur once per element, and can't have any children other than its value. If you have a scenario where this is enough (e.g. specifying a URL of sorts, a "flag" of sorts, etc.), an attribute is a perfect thing to use. In all other instances, an element is more appropriate.

The default is the highest supported by the XML parser.The main difference between 1.0 and 1.1 is in what's allowed as tag names - XML 1.0 only allowes a certain (very large!!!) range of printable characters, while XML 1.1 only forbids a certain (very small) range of characters that are either already special (e.g. "<" and ">") or are reserved for potential future expansions (e.g. "{" and "}").There's almost no other difference, which is why you don't see many users use it, and in turn, fewer parsers for it.

You could invert the conditon - always display the start date, and if the dates are NOT the same, display the end date as well, e.g. //Do whatever you do to "show" the date e.g. "echo $event->StartDate;"if ($event->StartDate !== $event->EndDate) {//Do whatever you need to do to also "show" the end date, including outputting a separator, e.g. "echo '-', $event->EndDate;"}

This is supposed to be an overly simplified example... not to be used "for realz".How to fix this should IMHO be explained in later tutorials, but as far this one is concerned - it poses no danger to W3Schools' server, nor can one user touch another, so it's fine.

If you want to programatically detect warnings and analyze them, you have to set an error handler function, and check its arguments. See the set_error_handler() function for details.