Re: [WSG] Sending correct MYME-TYPE and content
Pierre-Henri Lavigne wrote:
Regards to http://www.w3.org/MarkUp/2004/xhtml-faq#ie I just discovered,
I was just wondering if we could use :
?php
if (stristr($_SERVER[HTTP_ACCEPT],application/xhtml+xml)) {
You need to check the q value.
e.g. If a browser sends this:
Accept: text/html;application/xhtml+xml;q=0.5
text/html is preferred over application/xhtml+xml.
header(Content-Type: application/xhtml+xml; charset=UTF-8);
You don't need to include the charset parameter in this header for XML
MIME types (this does not apply to text/html). XML is designed as a
self describing format and does not need the information to be there.
Although, it does little harm by including it. There is, however, a
mostly theoretical issue of the document being transcoded by an
intermediate server, which wouldn't update the XML declaration.
printf(?xml version=\1.0\ encoding=\UTF-8\ ?\n);
printf(!DOCTYPE html PUBLIC \-//W3C//DTD XHTML 1.1//EN\
\http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd\;\n);
No browser actually supports XHTML 1.1 properly. There are some small
but significant differences from XHTML 1.0, which makes XHTML 1.1 useless.
Either use XHTML 1.0, or omit the DOCTYPE completely. There is no
DOCTYPE sniffing for XML, and so the DOCTYPE only serves 2 purposes.
Validation and named entity references. For entity references to work
(e.g. copy;), it actually requires a validating parser, although
$contentType=application/xhtml+xml; charset=utf-8;
} else {
header(Content-Type: text/html; charset=UTF-8);
printf(?xml version=\1.0\ encoding=\UTF-8\ ?\n);
In this case, the document is being served as text/html, and so it *is*
HTML, not XHTML. Do not include the XML declaration. It triggers
quirks mode in IE6 and earlier.
printf(?xml-stylesheet type=\text/xsl\ href=\copy.xsl\ ?\n);
That is a processing instruction for XML. It does not work in HTML!
But assuming you are intending that XSL stylesheet to be applied by IE,
like in the FAQ entry you cited, the document needs to be served with an
XML MIME type that is recognised by IE, such as application/xml
(preferred) or text/xml (not recommended). copy.xsl also needs to be
served as text/xsl.
However, DON'T DO THAT! Applying that XSLT transformation is a massive
performance hit for IE. Depending on the size of the document, it can
take several seconds to transform before rendering anything, which is a
bad user experience.
All it does is effectively change all the unrecognised XML elements in
the DOM into recognised HTML elements, and so you gain no benefit over
using ordinary HTML.
printf(!DOCTYPE html PUBLIC \-//W3C//DTD XHTML 1.0 Strict//EN\
\http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\;\n);
Why did you choose XHTML 1.0 here, but XHTML 1.1 earlier? IE fails to
recognise either one of them, and so it makes absolutely no difference,
even if you are apply the XSLT.
The rest of my comments ignore the intended XSL transformation and
assume this is being served as text/html. In which case, this document
is HTML, not XHTML. Use either an HTML 4.01 Strict DOCTYPE or an HTML5
doctype, which is simply:
!DOCTYPE html
The DOCTYPE is only really needed in HTML for triggering standards mode,
though if you wish to validate using an SGML parser (like the W3C
validator) then you'd need to use the HTML4 DOCTYPE. (There are
alternatives for checking the conformance of an HTML5 document).
$contentType=text/html; charset=utf-8;
}
?
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
That's correct for XHTML, but incorrect for HTML. HTML should use the
following instead:
html lang=en
head
titleHehe/title
meta http-equiv=Content-Language content=en-us /
That meta element is completely useless. If you wish to specify the
Content-Language, do so using an HTTP header. However, you should do
some research on the actual purpose of that header and determine if you
really need to use it at all.
meta http-equiv=Content-Type content=?php printf($contentType);? /
You do not need that at all, although you may wish to include it in HTML
(not XHTML) so that users who save the document will still have
encoding information.
For XHTML, it outputs:
meta http-equiv=Content-Type content=application/xhtml+xml;
charset=utf-8 /
This is completely useless. The meta element is ignored in XHTML and
changing the MIME type makes no difference. Browsers do not pay
attention to the MIME type declared there because they need to have
already decided which parser to use before they begin parsing. They
also pay no attention to the charset parameter either because XML rules
apply for determining the character encoding, which has already been
determined at this point.
For HTML, it outputs:
meta http-equiv=Content-Type content=text/html; charset=utf-8 /
The meta element is only somewhat useful for HTML. When no other
encoding information is available, only the
Re: [WSG] Sending correct MYME-TYPE and content
On 2/11/07, Lachlan Hunt [EMAIL PROTECTED] wrote:
Pierre-Henri Lavigne wrote:
Regards to http://www.w3.org/MarkUp/2004/xhtml-faq#ie I just discovered,
I was just wondering if we could use :
?php
if (stristr($_SERVER[HTTP_ACCEPT],application/xhtml+xml)) {
You need to check the q value.
e.g. If a browser sends this:
Accept: text/html;application/xhtml+xml;q=0.5
text/html is preferred over application/xhtml+xml.
header(Content-Type: application/xhtml+xml; charset=UTF-8);
You don't need to include the charset parameter in this header for XML
MIME types (this does not apply to text/html). XML is designed as a
self describing format and does not need the information to be there.
Although, it does little harm by including it. There is, however, a
mostly theoretical issue of the document being transcoded by an
intermediate server, which wouldn't update the XML declaration.
Will you care to elaborate this? You're saying that since xml is
self-describig there is no need to include the encoding parameter in
content-type. This is not accurate. By including the content type, you are
letting the HTTP client know of the encoding to use to parse the body of the
HTTP response. The purpose of the encoding in the preamble in XML documents
is similar to meta tags used for encoding in HTML documents. In the absence
of the encoding parameter in the content type, the client has to parse the
preamble using some default/safe encoding, and then reparse the complete
response with the encoding found in the preamble. The encoding parameter in
the content type saves this trouble.
Subbu
--
--
http://www.subbu.org
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] print style sheet with dropdown menu
On 2/10/07, Tee G. Peng [EMAIL PROTECTED] wrote: Hi I have an accessible question that I can't decide. With a site that has drop down menu controls by JS, is it important to make the submenu links show in print style? I feel it's not important and not needed because user who prints the page out can't click the submenu link anyway; on the other hand I feel it's important to have them show as a good reference, to let user knows how many pages and links the site has. If you have pages with articles on them, usually the user wants to print the actual articles. The typical trend (and the one I followed when I designed a print stylesheet) is to remove the navigation completely, and just print the title of the page and the article. If users really want to print a sitemap, then you could just make a sitemap page! -- -- Christian Montoya christianmontoya.net .. designtocss.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Books - CSS/Standards/Accessibility
On 10/02/2007, at 5:01 AM, Andy Woznica wrote: If hypothetically we were thinking of running a course covering CSS design techniques, Standards and Acessibility, is there a top five book list to complement such an undertaking. Two books on accessibility: 1. Access by Design: A Guide to Universal Usability for Web Designers, Sarah Horton A great primer which is now online: http://universalusability.com/ 2. Web Accessibility: Web Standards and Regulatory Compliance, Thatcher et al A great mixture of theory, case study and specific technique. kind regards Terrence Wood *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Sending correct MYME-TYPE and content
Subbu Allamaraju wrote: On 2/11/07, Lachlan Hunt [EMAIL PROTECTED] wrote: header(Content-Type: application/xhtml+xml; charset=UTF-8); You don't need to include the charset parameter in this header for XML MIME types (this does not apply to text/html). XML is designed as a self describing format and does not need the information to be there. Will you care to elaborate this? You're saying that since xml is self-describig there is no need to include the encoding parameter in content-type. Yes. http://www.w3.org/TR/2004/REC-webarch-20041215/#xml-media-types In the absence of the encoding parameter in the content type, the client has to parse the preamble using some default/safe encoding, and then reparse the complete response with the encoding found in the preamble. The encoding parameter in the content type saves this trouble. While that is true under some conditions for HTML when you declare the encoding using the meta element instead of at the protocol level, it is not true for XML. An XML parser never needs to reparse anything. The algorithm in the XML recommendation has been carefully designed to ensure that the encoding can always be reliably determined, or else it is a fatal error. See Appendix F. http://www.w3.org/TR/REC-xml/#sec-guessing -- Lachlan Hunt http://lachy.id.au/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Site Check - amplify.com.au
Hi all We have just completed a redesign/redevelopment of the www.amplify.com.auwebsite, and would appreciate any feedback, especially from Mac users. Many thanks -- Scott Swabey www.lafinboy.com www.thought-after.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Keyboard accessible DHMTL navigation
Return Receipt Your Re: [WSG] Keyboard accessible DHMTL navigation document: wasLisa Kerrigan/StateDevPolicy/DSD received by: at:12/02/2007 09:44:01 AM ** Department of Innovation, Industry and Regional Development, Government of Victoria, Victoria, Australia. This e-mail and any attachments may contain privileged and confidential information. If you are not the intended recipient, you may not distribute reproduce this e-mail or the attachments. If you have received this message in error, please notify us by return e-mail. ** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Site Check - amplify.com.au
I like it, I don't like the plus minus concept on the navigation though, it implies you can close/open multiple navigation options at once (like any of those tree lists can) which is not needed in a navigation. Instead of the plus minus I'd use a concept of bullet point and highlighted bullet point. -Original Message- From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On Behalf Of Scott Swabey Sent: Monday, 12 February 2007 9:33 AM To: wsg@webstandardsgroup.org Subject: [WSG] Site Check - amplify.com.au Hi all We have just completed a redesign/redevelopment of the www.amplify.com.au website, and would appreciate any feedback, especially from Mac users. Many thanks -- Scott Swabey www.lafinboy.com www.thought-after.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Site Check - amplify.com.au
Just had a quick look in Firefox, but it seems to come unstuck pretty quickly when your browser window is smaller than 1024 x 780 and if you resize the text more than twice. And isn't your Google analytics code s'posed to go in the body of your page? On Mon, 12 Feb 2007 08:32:47 +1000, Scott Swabey [EMAIL PROTECTED] wrote: Hi all We have just completed a redesign/redevelopment of the www.amplify.com.auwebsite, and would appreciate any feedback, especially from Mac users. Many thanks -- Tyssen Design Web print design services www.tyssendesign.com.au Ph: (07) 3300 3303 Mb: 0405 678 590 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Standards War - HTML 5 vs XHTML 2.0
Paul Ross wrote: I was there at the WSG Sydney meeting last Thursday and was very interested to hear Lachlan Hunt (the tallest WSG member according to Russ) talking about the Future of HTML. Thanks, I'm glad you liked it. :-) Lachlan's talk raised a lot of questions (which I wished I'd asked at the meeting but felt like a noob at the time). HTML 5 was new to most people at the meeting, there's no need to feel like a noob when everyone else around is too. :-) Is this a fork in the specs road or a standards war in the making? No, I wouldn't call it a standards war, the major browser vendors have already unanimously decided what they will be implementing. It is a minor fork in the road, but it's not a big issue since the other alternative is a dead end. XHTML 2.0 is effectively dead and is relatively safe to ignore. HTML 5 is the most relevant spec. In many ways, it's already far more relevant than HTML 4.01. There are numerous, significant problems with XHTML 2.0, which make it extremely difficult, if not impossible, to implement interoperably in the real world. Although, we recognise the fact that there are some features in XHTML 2 that people like, and many of them have already been incorporated in, or being considered for, HTML5. If anyone is interested in learning more about, or getting involved with, HTML5, there are several things that you can do. Read the blog, FAQ or wiki; ask questions in the forum, #whatwg on IRC or the new whatwg help mailing list; or read the specs and contribute to the main mailing list. More information about these is available from the WHATWG home page. http://whatwg.org/ -- Lachlan Hunt http://lachy.id.au/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Site Check - amplify.com.au
I agree... I like the simple design but the menu looks too un-important imho, it looks like it has been added on as an after thought and hence sticks out a bit and doesnt seem to gel with the overall design Apart from the menu, the rest looks good. One side note though: The logo seems to be cut off on the right hand side, the Y on Amplify is not complete (using Firefox 2.0) On 2/12/07, Samuel Richardson [EMAIL PROTECTED] wrote: I like it, I don't like the plus minus concept on the navigation though, it implies you can close/open multiple navigation options at once (like any of those tree lists can) which is not needed in a navigation. Instead of the plus minus I'd use a concept of bullet point and highlighted bullet point. -Original Message- *From:* listdad@webstandardsgroup.org [mailto: [EMAIL PROTECTED] *On Behalf Of *Scott Swabey *Sent:* Monday, 12 February 2007 9:33 AM *To:* wsg@webstandardsgroup.org *Subject:* [WSG] Site Check - amplify.com.au Hi all We have just completed a redesign/redevelopment of the www.amplify.com.auwebsite, and would appreciate any feedback, especially from Mac users. Many thanks -- Scott Swabey www.lafinboy.com www.thought-after.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- JP2 Designs http://www.jp2designs.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Books - CSS/Standards/Accessibility
If hypothetically we were thinking of running a course covering CSS design techniques, Standards and Acessibility, is there a top five book list to complement such an undertaking. Some excellent suggestions have been made; however I'd also try to get the students used to looking for their own resources online. For example, put them onto A List Apart, get them to look at speaker lists for major events and so on. Tell them that Jakob Nielsen often does great research but his conclusions go well with a proverbial grain of salt. Plenty of students won't care but for those who do, it would be great to get them used to the idea that the industry is changing rapidly and they can be as much a part of that as they want to. One thing... if you get any questions on scripting, I'd recommend pointing them to the Hijax methodology and the book DOM Scripting by Jeremy Keith. If anyone thinks that standards are restrictive, point them to Transcending CSS by Andy Clarke. I hope this helps :) cheers, Ben -- --- http://weblog.200ok.com.au/ --- The future has arrived; it's just not --- evenly distributed. - William Gibson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Books - CSS/Standards/Accessibility
Speaker lists for some major events indicate who is best at sales training promotion to the Australian government and standards are low in my opinion. I would not attend some of these conferences due to the focus of some commercial interests in circumventing the Australian 1992 Disability Discrimination Act's legal implications for W3C validity and accessibility. Try this resource Ben I made it, you be the judge, it is Australian but also compares UK and USA sites. http://www.hereticpress.com/Dogstar/Publishing/AustWeb.html Tim On 12/02/2007, at 12:01 PM, Ben Buchanan wrote: If hypothetically we were thinking of running a course covering CSS design techniques, Standards and Acessibility, is there a top five book list to complement such an undertaking. Some excellent suggestions have been made; however I'd also try to get the students used to looking for their own resources online. For example, put them onto A List Apart, get them to look at speaker lists for major events and so on. Tell them that Jakob Nielsen often does great research but his conclusions go well with a proverbial grain of salt. Plenty of students won't care but for those who do, it would be great to get them used to the idea that the industry is changing rapidly and they can be as much a part of that as they want to. One thing... if you get any questions on scripting, I'd recommend pointing them to the Hijax methodology and the book DOM Scripting by Jeremy Keith. If anyone thinks that standards are restrictive, point them to Transcending CSS by Andy Clarke. I hope this helps :) cheers, Ben -- --- http://weblog.200ok.com.au/ --- The future has arrived; it's just not --- evenly distributed. - William Gibson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** The Editor Heretic Press http://www.hereticpress.com Email [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Books - CSS/Standards/Accessibility
On 2/11/07, Ben Buchanan [EMAIL PROTECTED] wrote: If hypothetically we were thinking of running a course covering CSS design techniques, Standards and Acessibility, is there a top five book list to complement such an undertaking. Some excellent suggestions have been made; however I'd also try to get the students used to looking for their own resources online. For example, put them onto A List Apart, get them to look at speaker lists for major events and so on. Tell them that Jakob Nielsen often does great research but his conclusions go well with a proverbial grain of salt. Hey, tell them to subscribe to this list. I was the only student in my web design class that kept up with WSG and CSS-D and I was always miles ahead of my classmates when it came to CSS and accessibility. -- -- Christian Montoya christianmontoya.net .. designtocss.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Site Check - amplify.com.au
Hi Samuel On 12/02/07, Samuel Richardson [EMAIL PROTECTED] wrote: I like it, I don't like the plus minus concept on the navigation though, it implies you can close/open multiple navigation options at once (like any of those tree lists can) which is not needed in a navigation. Instead of the plus minus I'd use a concept of bullet point and highlighted bullet point. The left nav was originally a tree view style nav, and the plus minus icons fitted with the open/close action of the onclick events. The last minute decision was to remove this effect - a good decision I believe - but the icons were left. I'll get them replaced in the .1 release. Regards -- Scott Swabey www.lafinboy.com www.thought-after.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Books - CSS/Standards/Accessibility
On 2/12/07, Christian Montoya [EMAIL PROTECTED] wrote: Hey, tell them to subscribe to this list. I was the only student in my web design class that kept up with WSG and CSS-D and I was always miles ahead of my classmates when it came to CSS and accessibility. I am currently a student, but I have been studying CSS, web standards, and accessibility for at least the past two and a half years. I am miles ahead of my entire class in almost every subject. Even stuff that is new to me doesn't seem hard to pick up. I enjoy the web, and learning about it is fun to me. I think this is key for any student - you must enjoy what you're learning. Learning itself is not hard. The web is the single greatest resource out there. E-zines, blogs, forums, mailing lists - there is no shortage of information. Teach the students to take advantage of as much as they can - the web design community seems very keen to welcome newcomers and help anyone who is struggling. -- Australian Web Designer - http://www.blakehaswell.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Site Check - amplify.com.au
Hi John On 12/02/07, John Faulds [EMAIL PROTECTED] wrote: Just had a quick look in Firefox, but it seems to come unstuck pretty quickly when your browser window is smaller than 1024 x 780 and if you resize the text more than twice. Could you elaborate a little on this please. I am aware of background issues, in that the header background doesn't resize to fill the new screen width, but don't see/notice anything else. And isn't your Google analytics code s'posed to go in the body of your page? The Google code is placed in the head as per Google specs for e-commerce sites, to enable tracking of orders and receipts. The e-commerce parts of the site will follow in release 2. Regards -- Scott Swabey www.lafinboy.com www.thought-after.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Books - CSS/Standards/Accessibility
Speaker lists for some major events indicate who is best at sales training promotion to the Australian government and standards are low in my opinion. I would not attend some of these conferences due to the True, I perhaps should have made it clear that I'm talking about standards-focussed events like Web Directions South/North, @Media, Webstock, etc. Just like you wouldn't recommend any old book on web development... :) -- --- http://www.200ok.com.au/ --- The future has arrived; it's just not --- evenly distributed. - William Gibson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] blockquote in xhtml strict
Hi, I have a block of text that uses blockquote u I came because this is one of the best.. - john doe in my markup: div img src=images/jd.jpg alt=john doe width=83 height=58 / blockquoteI came because this is one of the best.. span- john doe/span /blockquote It gives me validation error: You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a paragraph/p) or forgetting to quote an attribute value (where characters such as % and / are common, but cannot appear without surrounding quotes). After some reading about 'blockquote' element in xhtml strict from google search, I added p tag and removed the span pblockquoteI came because this is one of the best.. span- john doe/span /blockquote /p now it gives me this: The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as p or table) inside an inline element (such as a, span, or font). What am I missing? Thanks! tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] print style sheet with dropdown menu
On Feb 11, 2007, at 9:28 AM, Christian Montoya wrote: If you have pages with articles on them, usually the user wants to print the actual articles. The typical trend (and the one I followed when I designed a print stylesheet) is to remove the navigation completely, and just print the title of the page and the article. If users really want to print a sitemap, then you could just make a sitemap page! Hi Kevin and Christian, Thanks for the suggestion. The site has a site map and there is breadcrumb, so I guess the navigatino is not needed. tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] blockquote in xhtml strict
Hi, Just did some research and found this: http://www.w3schools.com/tags/tag_blockquote.asp Differences Between HTML and XHTML The blockquote tag is supposed to contain only block-level elements within it, and not just plain text. To validate the page as strict XHTML, you must add a block-level element around the text within the blockquote tag, like this: blockquote phere is a long quotation here is a long quotation/p /blockquote Hope this helps. Dylan. On 2/12/07, Tee G. Peng [EMAIL PROTECTED] wrote: Hi, I have a block of text that uses blockquote u I came because this is one of the best.. - john doe in my markup: div img src=images/jd.jpg alt=john doe width=83 height=58 / blockquoteI came because this is one of the best.. span- john doe/span /blockquote It gives me validation error: You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a paragraph/p) or forgetting to quote an attribute value (where characters such as % and / are common, but cannot appear without surrounding quotes). After some reading about 'blockquote' element in xhtml strict from google search, I added p tag and removed the span pblockquoteI came because this is one of the best.. span- john doe/span /blockquote /p now it gives me this: The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as p or table) inside an inline element (such as a, span, or font). What am I missing? Thanks! tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] blockquote in xhtml strict
The p has to go inside the blockquote, not the other way around. You probably also want to use the cite tag instead of a span for the name of the quoted person. On Mon, 12 Feb 2007 13:46:07 +1000, Tee G. Peng [EMAIL PROTECTED] wrote: Hi, I have a block of text that uses blockquote u I came because this is one of the best.. - john doe in my markup: div img src=images/jd.jpg alt=john doe width=83 height=58 / blockquoteI came because this is one of the best.. span- john doe/span /blockquote It gives me validation error: You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a paragraph/p) or forgetting to quote an attribute value (where characters such as % and / are common, but cannot appear without surrounding quotes). After some reading about 'blockquote' element in xhtml strict from google search, I added p tag and removed the span pblockquoteI came because this is one of the best.. span- john doe/span /blockquote /p now it gives me this: The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as p or table) inside an inline element (such as a, span, or font). What am I missing? Thanks! tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Tyssen Design Web print design services www.tyssendesign.com.au Ph: (07) 3300 3303 Mb: 0405 678 590 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] blockquote in xhtml strict
Hello Tee, This might be the way to go. It's what I do and I think it's a pretty good practice: blockquote cite=url-of-source-if-applicable p This is the body of text quoted. This is the body of text quoted. cite-- Who said it/cite /p /blockquote The cite attribute within the blockquote element wouldn't be used if not available. The cite element, though, should be used. I actually apply a decorative end-quote background image to my cite element (and a decorative leading quote image to the blockquote itself). It would be fine to place the cite element outside of the paragraph, which might be preferred if it is a multi-paragraph quote. Hope this helps. Respectfully, Mike Cherim PS. You can see an example here: http://green-beast.com/beastblog/index.php/2007/01/13/making-blockquotes/ (this is a support blog for a WordPress theme). - Original Message - From: Tee G. Peng [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Sunday, February 11, 2007 10:46 PM Subject: [WSG] blockquote in xhtml strict Hi, I have a block of text that uses blockquote u I came because this is one of the best.. - john doe in my markup: div img src=images/jd.jpg alt=john doe width=83 height=58 / blockquoteI came because this is one of the best.. span- john doe/span /blockquote It gives me validation error: You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a paragraph/p) or forgetting to quote an attribute value (where characters such as % and / are common, but cannot appear without surrounding quotes). After some reading about 'blockquote' element in xhtml strict from google search, I added p tag and removed the span pblockquoteI came because this is one of the best.. span- john doe/span /blockquote /p now it gives me this: The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as p or table) inside an inline element (such as a, span, or font). What am I missing? Thanks! tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] blockquote in xhtml strict
On Feb 11, 2007, at 11:09 PM, lisa herrod wrote: On 12/02/07, John Faulds [EMAIL PROTECTED] wrote: Hmmm I thought the dash would have thrown an error...? No? It depends whether it's been typed in directly via your keyboard (the key next to the 0) or whether it's a character that's been copied from another program (like Word) and needs converting to something like ndash; . Thanks john, yes. So Tee, which was it? Hi Lisa, John's assumption has its place ( have experienced that quite often whenever clients sent me texs in Word) but not with this particular case. I had the blockquote tag wrapped inside the p tag. It should be other around as George, Christian, Dylan and Mike pointed out. Always have difficulty to understand the error message the markup validator shows, English as the third language has making it even worse; I am always grateful I can seek for help from this list. Regards, tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
