RE: [WSG] IE5.5 indenting list items
A link to online sample of this problem, stripped back to just the problem area, and a link to the stripped back css file would help a lot. Thanks Russ ... Thanks Russ, I set up a stripped back test page as suggested and managed to fix the problem. I had the ul set to width:100% and the li set to display:block. Removing width on the UL fixed it. I left the broken test page online in case anyone using IE5Win wants to see the effect. http://cif-dev.opc.com.au/test-menu.html Thanks again Glen ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] Article: MIME and Content Negotiation
designer wrote:
However, I remain confused in the particular case of the PHP approach.
The PHP looks to see
"if(stristr($_SERVER["HTTP_ACCEPT"],"application/xhtml+xml"))" and on
that basis it describes the appropriate prolog, mimetype and charset. So
the final three lines of the php code (where the action takes place :-)
are:
header("Content-Type: $mime; charset=$charset");
header("Vary: Accept");
print $prolog_type;
One therefore assumes that the 'real http headers' ARE being used in
this case. However, if I do that I can only get Chinese unless I get
PHP to echo the meta tag:
Can you please make up a small sample document that clearly demonstrates
this issue occurring and post a URI so that we may see it.
--
Lachlan Hunt
http://lachy.id.au/
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
Re: [WSG] Article: MIME and Content Negotiation
On 16 Jan 2006, at 11:53 pm, designer wrote:
However, I remain confused in the particular case of the PHP
approach. The PHP looks to see "if(stristr($_SERVER
["HTTP_ACCEPT"],"application/xhtml+xml"))" and on that basis it
describes the appropriate prolog, mimetype and charset. So the
final three lines of the php code (where the action takes
place :-) are:
header("Content-Type: $mime; charset=$charset");
header("Vary: Accept");
print $prolog_type;
That sounds very weird. Either your browser is acting up or something
is not properly configured, or your server is doing something odd on
the way.
Is the $charset var set up correctly ? (near the top of the code)
It should read:
$charset = "utf-8";
Philippe
---
Philippe Wittenbergh
[WSG] interesting article on folksonomies...
... in D-Lib magazine, for those interested in such things (flickr, technorati, del.icio.us): http://www.dlib.org/dlib/january06/guy/01guy.html from the introduction: "A folksonomy is a type of distributed classification system. It is usually created by a group of individuals, typically the resource users. Users add tags to online items, such as images, videos, bookmarks and text. These tags are then shared and sometimes refined. A general review of social bookmarking tools, one popular use area of folksonomies, was given in the April edition of D-Lib [1]. In the article the authors elaborate on the approach taken by social classification systems and the motivators behind tagging. They write, "...tags are just one kind of metadata and are not a replacement for formal classification systems such as Dublin Core, MODS, etc Rather, they are a supplemental means to organise information and order search results." In this article we look at what makes folksonomies work. We agree with the premise that tags are no replacement for formal systems, but we see this as being the core quality that makes folksonomy tagging so useful. We begin by looking at the issue of "sloppy tags", a problem to which critics o.f folksonomies are keen to allude, and ask if there are ways the folksonomy community could offset such problems and create systems that are conducive to searching, sorting and classifying. We then go on to question this "tidying up" approach and its underlying assumptions, highlighting issues surrounding removal of low-quality, redundant or nonsense metadata, and the potential risks of tidying too neatly and thereby losing the very openness that has made folksonomies so popular." s. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] Article: MIME and Content Negotiation
Paul Novitski wrote: At 04:02 AM 1/16/2006, Lachlan Hunt wrote: (The charset parameter is only really needed for text/* media types, for XML served with an application/* media type, the XML declaration is recommended for use instead which may be omitted for UTF-8 and UTF-16) http://lachy.id.au/log/2006/01/content-type For clarification, was your first clause above a sentence in its own right? I assume you meant, "(The charset parameter is only really needed for text/* media types. For XML served with an application/* media type... Yes, that's correct. It was just a typo. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
[WSG] Article: MIME and Content Negotiation
"Comments, especially error-spotting and general "bravo" very welcome" One minor inaccuracy. The article written by Neil Crosby is based on an article I wrote in October of the previous year. Oddly enough, it was Russ Weakely who badgered me into writing it in the first place. Simon Jessey Business Email: [EMAIL PROTECTED] Personal Email: [EMAIL PROTECTED] Business Site: http://keystonewebsites.com/ Personal Site: http://jessey.net/
Re: [WSG] Article: MIME and Content Negotiation
At 04:02 AM 1/16/2006, Lachlan Hunt wrote: (The charset parameter is only really needed for text/* media types, for XML served with an application/* media type, the XML declaration is recommended for use instead which may be omitted for UTF-8 and UTF-16) http://lachy.id.au/log/2006/01/content-type For clarification, was your first clause above a sentence in its own right? I assume you meant, "(The charset parameter is only really needed for text/* media types. For XML served with an application/* media type, the XML declaration is recommended for use instead which may be omitted for UTF-8 and UTF-16)." Thanks very much for the article, Lachlan. Paul ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] Article: MIME and Content Negotiation
Lachlan Hunt wrote: [snip]
Did you read my article [1] which Rimantas referred you to? That
explains what you're supposed to do. You need to use real HTTP
headers, not the inferior meta element. The end of that article links
to another that actually explains how to set the charset parameter in
the HTTP headers using various servers and server-side scripting
languages [2].
Well Lachlan, not only did I read it, I printed it out and read it in
bed at around 1.50am! (now that's keen!)
However, I remain confused in the particular case of the PHP approach.
The PHP looks to see
"if(stristr($_SERVER["HTTP_ACCEPT"],"application/xhtml+xml"))" and on
that basis it describes the appropriate prolog, mimetype and charset. So
the final three lines of the php code (where the action takes place :-)
are:
header("Content-Type: $mime; charset=$charset");
header("Vary: Accept");
print $prolog_type;
One therefore assumes that the 'real http headers' ARE being used in
this case. However, if I do that I can only get Chinese unless I get
PHP to echo the meta tag:
echo "content=\"application/xhtml+xml; charset=utf-8\" />";
}
else
{
echo"charset=utf-8\"/>";
}
?>
And I'm confused, because (if I've understood it properly) this should
not be required?
--
Best Regards,
Bob McClelland
Cornwall (UK)
www.gwelanmor-internet.co.uk
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
Re: [WSG] Article: MIME and Content Negotiation
Thanks for the feedback, I made a few amendments / corrections this morning including:xhtml-xml - D'oh! Got it right twice before :owell-formedness versus validation - Got it right once before ;-) (more coffee at proof-reading time) On 16/01/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote: > # The XML Prolog is required for character sets other than UTF-8 and> UTF-16. This is declared on line 1 of your code in the format > version="1.0" encoding="yourChosenCharset" ?> That's the XML declaration, which forms part of the XML Prolog. The XMLProlog is always present and comprises the XML declaration, PIs and theDOCTYPE (although all of those parts are optional in XML 1.0) Ahhh, thanks for the clarification. I should state here I guess that not only did this take all week to write, but it was (and always will be) a learning curve too. > # Only five named character entities are "safe": <, >, &,> " and '.On 4 are safe when using text/html, because ' is undefined in HTMLand is not supported by IE. However, the article of mine that you linked to does cover that issue so it's not a major problem.> Standard Generalized Markup Language (SGML) comments () hide everything - including style and script tags. They're XML comments, which are based on SGML comments but still differin significant ways. I have another article which covers this issue ingreat detail.I pulled that bullet-point because I'd gotten it muddled up. I'll read up your article and word it better in an update. http://lachy.id.au/log/2005/05/script-comments > # Stylesheets need to be referenced with an XML stylesheet> declaration.Wrong! That's just one of the myths in the widely criticised Appendix C.> This is done by creating a fragment identifier, Slightly wrong terminology, a fragment identifier only occurs in a URI(after the #) which references an ID or an anchor in an (X)HTML document.> for example id="myStyle" in each