| At line 25 changed one line |
| JSPWiki uses XHTML, not HTML. First, let's not mix up browser behaviour with markup standards; they're two different things. And yes, all XHTML tag, attribute names and fixed values must be in lowercase. Whereas HTML was SGML-based, XHTML is XML-based. One of SGML's numerous features that XML doesn't have (permit) is wrapping of case. Another is called tag minimization (i.e., not requiring end tags), and then there's how empty elements are handled. In HTML, {{<meta>}}, {{<img>}} and the other elements whose declared content model is {{EMPTY}} could simply be represented as a single tag, with their end tags inferred. In XHTML the W3C's XML Working Group managed to find a relatively elegant solution for empty elements that actually worked in existing Web browsers: by adding "{{ />}}" (note that the space preceding the slash is __required__) there was something that worked and was SGML-legal, via a minor change to the SGML declaration for XML (the machine-readable declaration for the profile). |
| ---- |
| At line 27 changed one line |
| So what this comes down to, as it always has been, is ''declaring'' the markup language you're using and then sticking to it. If you've declared you're using XHTML you should precede an appropriate DOCTYPE declaration with the XML declaration ({{<?xml version="1.0" encoding="UTF-8"?>}}). |
| First, let's not mix up browser behaviour with markup standards; they're two different things. |
| At line 29 added 13 lines |
| JSPWiki uses XHTML, not HTML. And yes, all XHTML element type names ("tag names"), attribute names and fixed values __must__ be in lowercase. Whereas HTML was SGML-based, XHTML is XML-based. One of SGML's numerous features that XML doesn't have (i.e., permit) is wrapping of case. Another is called ''tag minimization'' (i.e., not requiring end tags), and then there's how empty elements are handled. In HTML, {{<meta>}}, {{<img>}} and the other elements whose declared content model is {{EMPTY}} could simply be represented as a single tag, with their end tags inferred. There is no such feature in XML. The W3C's XML Working Group managed to find a relatively elegant solution for empty XML elements that actually worked in existing Web browsers: by adding "{{ />}}" (note that the space preceding the slash is __required__) here was something that worked and was SGML-legal, via a minor change to the SGML declaration for XML (the machine-readable declaration for the profile). |
| ! Invalid (in XHTML): |
| {{{ |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"> [uppercase] |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> [no empty tag markup] |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> [missing space] |
| }}} |
| ! Valid (in XHTML): |
| {{{ |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> |
| }}} |
| So what this comes down to, as it always has been, is ''declaring'' the markup language you're using and then sticking to it. If you've declared you're using XHTML you should also precede an appropriate DOCTYPE declaration with the XML declaration ({{<?xml version="1.0" encoding="UTF-8"?>}}). That's not strictly necessary but is good practice and gives validation tools a clue that you're using XML. |
|
| At line 69 changed one line |
| !!2004/08/26 - Java2Html PlugIn: Neverending loop in attachemnt loading |
| !!2004/08/26 - Java2Html Plugin: Neverending loop in attachemnt loading |
| At line 294 changed one line |
| I'd like to second the motion of adding the MRG template's PrintFriendly.jsp and an accompanying link to execute that JSP (whether on the left menu or in the list of links at the bottom of each page) to the JSPWiki core. |
| I'd like to second the motion of adding the MRG template's ~PrintFriendly.jsp and an accompanying link to execute that JSP (whether on the left menu or in the list of links at the bottom of each page) to the JSPWiki core. |
| At line 300 changed one line |
| I don't actually want to add PrintFriendly.jsp, because I don't want to add any new top-level JSP pages unless absolutely necessary (and with the new WikiForm -plugin, after a bit of polishing, we can probably start getting rid of a bunch of the old ones as well). |
| I don't actually want to add ~PrintFriendly.jsp, because I don't want to add any new top-level JSP pages unless absolutely necessary (and with the new WikiForm -plugin, after a bit of polishing, we can probably start getting rid of a bunch of the old ones as well). |
| At line 356 changed one line |
| * Hi, JanneJalkanen. My name is Jin Zeng and I live in Beijing of China. Thanks for your great work, I am using your JSPWiki v2.0.52. It works well.In order to input Chinese, I set JSPWiki to use UTF-8. It also does well.Further more, I want the prompt message displayed in Chinese. So I think I need to do some change in the JSP source file.For example, I edited a file named FindContent.jsp. However, the characters I input was displayed in irregular character can not be read.How do I fix this problem then? -- Jin Zeng |
| * Hi, JanneJalkanen. My name is Jin Zeng and I live in Beijing of China. Thanks for your great work, I am using your JSPWiki v2.0.52. It works well.In order to input Chinese, I set JSPWiki to use UTF-8. It also does well.Further more, I want the prompt message displayed in Chinese. So I think I need to do some change in the JSP source file.For example, I edited a file named ~FindContent.jsp. However, the characters I input was displayed in irregular character can not be read.How do I fix this problem then? -- Jin Zeng |
| At line 368 changed one line |
| IE 5.5 and 6 do not like {{document.forms[1].text}}, because they use another Document Object Model (I suppose IE6 can be made to like it by changing the DOCTYPE of the page, but I haven't tried that yet). Simple solution: edit {{default/EditTemplate.jsp}} by deleting the {{onload}} instruction on lines 14 and 18. Better solution (if you want to keep the functionality): add an ID to the main FORM of the editing page, and replace {{document.forms[1].text.focus()}} using the {{getElementByID()}} function... [Wouter] |
| IE 5.5 and 6 do not like {{document.forms[1].text}}, because they use another Document Object Model (I suppose IE6 can be made to like it by changing the DOCTYPE of the page, but I haven't tried that yet). Simple solution: edit {{default/~EditTemplate.jsp}} by deleting the {{onload}} instruction on lines 14 and 18. Better solution (if you want to keep the functionality): add an ID to the main FORM of the editing page, and replace {{document.forms[1].text.focus()}} using the {{getElementByID()}} function... [Wouter] |
