Jump to content

boen_robot

Members
  • Posts

    8,493
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by boen_robot

  1. Actually, no. It requres some kind of extension before you are even able to run any code for the XSLT processor. I don't know what extension exactly is needed and how to install it. If you're able to figure it out by going through the manual or something, please let me know.
  2. I tryed using two of theese scripts today. Only the last one called gets rendered. How come ? I mean... they target different pairs of XMLs, XSLTs and containers (both divs), both are in their own files and called with the scr attribute of the script element. What could be wrong ?
  3. W3C has a Schema validator. However, they don't have XML or XSLT validators. The only way you could validate an XSLT would be to get it's XHTML output via server side scripting language and validate it instead.
  4. The order of the pseudo classes is wrong. It must be exactly like this to work: a:link {text-decoration:none; color:gray;}a:visited {text-decoration:none; color:gray;}a:hover {text-decoration:none; background-color:#C7C7C7;}a:active {text-decoration:none; color:gray;} That's why I prefer not to use the :link pseudo class. You can't go wrong with it.[edit] I think so Jonas... That's why as I said, I prefer not to use it .[/edit]
  5. See the source code of this page, and you'll see for yourself that it won't work. Entities are THE way to go.
  6. An important thing to note is that the method Jonas describes is going to style your menu through every page. However, if you want to change data, you would have to use some third language that would force a single data to appear everywhere. It could be a server side include, XSLT executed with JS and so on.
  7. Try to use "times" instead(notice the small starting letter). If not, you could always use serif instead. As far as I know, Times New Roman is generic serif font, but I'm not sure.
  8. boen_robot

    XML Link

    <HTML><xml id="cdRecord" src="record.xml"></xml><TABLE dataSrc="#cdRecord" cellSpacing="1" cellPadding="2" width="100%" border="0" height="70"> <tr><td><A dataFld="FullName" href="topic.asp?dataFld=&FullName"> Cannot link to King Manchester from record.xml </a></td><tr></TABLE></HTML> If it doesn't work, try making an empty span inside the anchor and apply the dataFld attribute to it instead.
  9. It's probably too late. In fact, I'm sorry that I forgot this topic, but you should see PMXHT (Praetje's Method of XML to HTML Translation ) for the solution.
  10. boen_robot

    XML Link

    Some of the attributes don't have quotes. Either that, or you are using Firefox or Opera. Data Islands are not avaiable for any other browsers after all.
  11. What happens instead? The script is displayed as plain text? Where is it from? Another file? In the XSLT file directly? Aanother file imported with the src attribute in the XSLT? Else?
  12. Just four letters: XSLT . It holds the answer to every of your questions and a lot more.
  13. Just for the protocol. I see "exeption occured" every time there's something wrong in the XSLT. Are you sure your XSLTs are ALL correct? If any of the used ones is wrong, this would crash the whole thing, so it would be pretty obvious why do you see such error.
  14. You must use entity codes to write the special XHTML characters. Forum boards such as this have a PHP file that automatically transforms special characters into entities, but without it, you must manually type for example > every time you need to write >.I can't say anything about the scrollbars though.
  15. The only way I know is a server side scripting language(PHP, ASP(.NET), Cold Fusion, etc.). There's no way by using client side technologies only. If there was, then XML's security would be critical.
  16. boen_robot

    XML Storage

    In my point of view, MSAccess is useless anyways, but that's only my opinion.XML is not meant for replacing a database engine such as Access or MySQL. It's suppose to be used everywhere you would rather include only plane text on the visual parts of the site. The reson being to "separate data from presentation". Such thing would be for example a menu. Instead of making a server side include, you could store all the presentation for it in the ASP file (or in XSLT and use ASP to execute it- that's what I would prefer) and keep all the data in XML. When you want to add/edit/remove a menu item, you would only edit that easy-to-read-file, instead of going deeply into the whole system's hard-to-read-and-find core.
  17. Conditional statements maybe? <xsl:if test="EmployeeName=Joe"> If you would like to have more than one employee selected, there are several ways to do this. I would personally go to grouping the table row in another template and use the "apply-templates" element to apply it for every desired employee.
  18. boen_robot

    CSS "Exclusion"

    <style>body {display: none;}.doNotHide {display: block;}</style> maybe this?after all, the fact that doNotHide is a class name and (supposibly) belongs to a child of body, it means it's treated with higher priority, making everything besides it invisible.Just notice that in the above case, your elements from this class should be block elements. Otherwise, they'll get the features of block elements.
  19. And how would this tutorial be written? What it should contain?... honestly... I have never seen such tutorial. I can't image how would such thing be like.
  20. Creating tableless layout is a matter of skill, not about knowing the possible things. A single pointer in the table section of the HTML tutorial about not using tables for layout would be enough.
  21. boen_robot

    DTD for XML

    The only wrong I see here is the first line. It has to go(be removed). What it shows is DTD's basic syntax. It's not suppose to be part of the DTD. Also, at the end of the whole code, there's the "]>" missing.
  22. Execuse me for being so honest, but: hahaha . I never though I would see someone confusing Schema with XSLT. I mean, the overall fact that you've written something and use the XSL namespace should tell you at least that .Schema is a way to define legal building blocks of XML documents.XSLT is a way to transform XML documents to other documets from the XML family, another XML or just a plain text.Anyway... back to the problemYour XSLT actually worked when I tested it. The only adjustment I made was the reference to the XSLT file, because I stored the XSLT in the same folder as the XML, so I didn't needed the "C:\". Try this for starters...I also notice that you want XML output, but you haven't pointed any XML tags to use. XSLT uses XPath expression that extract the content of the desired element or attribute. This means that you must "manually" write the names of the new XML elements and attributes.Try this XSLT: <?xml version="1.0" encoding="utf-8"?><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="xml" encoding="utf-8" indent="yes" version="1.0"/><xsl:template match="/"><goods_nom_item> <xsl:for-each select="//goods_nom_item"> <id><xsl:value-of select="@id"/></id> <expimp><xsl:value-of select="expimp[@typ]"/></expimp> <dat_start><xsl:value-of select="//dat_start"/></dat_start> <dat_end><xsl:value-of select="//dat_end"/></dat_end> </xsl:for-each></goods_nom_item></xsl:template></xsl:stylesheet> My tests display the output as a text though. There isn't any XML tree shown. I haven't tryed converting XML-to-XML so I don't know if that's how it's suppose to be.
  23. Darn good point what vshris said . By the way, I think that if the background was... how do you say... light brown, beige, fown? Anyway... such a background would be more in W3Schools theme. Of couse if such is used, it would requre black text too.
  24. What do you mean by "export"? If you want a link to it, you could always do something like <xsl:variable name="href" select="XPath to the node containing the URL to the video" /><a href="{$href}"><xsl:value-of select="title of the movie if there is one?" /></a> And if you want to embed it in the XHTML output, you could use the <object>. <xsl:variable name="name" select="XPath to the node containing the name of the video" /><xsl:variable name="href" select="XPath to the node containing the URL to the video" /><objectclassid="clsid:22D6F312-B0F6-11D0-94AB-0080C74C7E95"><param name="{$name}" value="{$href}" /></object> P.S. Not sure which videos is this classid going to play...If I haven't understood correctly, please paraphrase yourself.
×
×
  • Create New...