Re: [WSG] transparency, png IE6 ??

2008-06-17 Thread Michael Persson
I have tried this option and it works on ONE image only, having more than one PNG does not give transparency, so its not a good solution either... I will just go back to gifs and make a background of the image behind to cut the out line with expand 1px, that always work and save struggling

[WSG] Multiple Language Domains

2008-06-17 Thread Paul McCann
Many thanks for the feedback guys. We wont be using a splash page but I have taken the other points on board and will look into them. The quirks mode issue, should not be there, we think the system is putting that in place for us!! Paul

Re: [WSG] transparency, png IE6 ??

2008-06-17 Thread David Hucklesby
On Tue, 17 Jun 2008 11:38:21 +0300, Michael Persson wrote: I have tried this option and it works on ONE image only, having more than one PNG does not give transparency, so its not a good solution either... I will just go back to gifs and make a background of the image behind to cut the out

[WSG] HTML special characters coding

2008-06-17 Thread kevin_erickson
Hello, I am looking for advice on if the best way to code for special characters is to use the actual character or the attribute value or the alt code? i.e. for the ampersand should one use or amp;? Does it matter? I know that Dreamweaver automates some of this but what is the best practice?

Re: [WSG] HTML special characters coding

2008-06-17 Thread Calvin Chan
I have always used the for ampersand. The only time I use the code is when there isn't an actual character on the keyboard. I.e copyright sign. I don't think it matter on which one to use. ~Calvin Calvin Chan www.calvinchan.net On Tue, Jun 17, 2008 at 1:55 PM, kevin_erickson [EMAIL

RE: [WSG] HTML special characters coding

2008-06-17 Thread Essential eBiz Solutions Ltd
Hi Kevin, I use the amp;? Code purely because not all browser's can read on it's own as this tells the browser to expect a special character, which in turn leads to a more user friendly experience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of

Re: [WSG] HTML special characters coding

2008-06-17 Thread T. R. Valentine
On 17/06/2008, kevin_erickson [EMAIL PROTECTED] wrote: Hello, I am looking for advice on if the best way to code for special characters is to use the actual character or the attribute value or the alt code? i.e. for the ampersand should one use or amp;? Does it matter? I know that

Re: [WSG] HTML special characters coding

2008-06-17 Thread Matthew Holloway
kevin_erickson wrote: Hello, I am looking for advice on if the best way to code for special characters is to use the actual character or the attribute value or the alt code? i.e. for the ampersand should one use or amp;? Does it matter? I know that Dreamweaver automates some of this but

Re: [WSG] HTML special characters coding

2008-06-17 Thread Patrick H. Lauke
Matthew Holloway wrote: (I use XHTML and I also want to be parseable as XML so aside from XMLs inbuilt entities of lt; gt; amp; quot; and apos; I tend to use NCRs...). Beyond the inbuilt entities I tend to just use the characters directly in the markup and specify UTF-8 encoding. Has been

Re: [WSG] HTML special characters coding

2008-06-17 Thread Andrew Freedman
kevin_erickson provided the following information on 18/06/2008 6:55 AM: Hello, I am looking for advice on if the best way to code for special characters is to use the actual character or the attribute value or the alt code? i.e. for the ampersand should one use or amp;? Does it matter? I know

Re: [WSG] HTML special characters coding

2008-06-17 Thread Andrew Cunningham
Use amp; nbsp; lt; and gt; All other characters should be actual characters. Use a character encoding that contains all the characters you require. Use of NCRs and other entities should be rare occurances for language challenged environments. Andrew kevin_erickson wrote: Hello, I am

Re: [WSG] HTML special characters coding

2008-06-17 Thread Andrew Cunningham
Patrick H. Lauke wrote: Beyond the inbuilt entities I tend to just use the characters directly in the markup and specify UTF-8 encoding. Has been working reasonably well in all modern browsers. LOL, i enjoyed the wording. Considering the document character set of HTML4 is Unicode, if it

Re: [WSG] HTML special characters coding

2008-06-17 Thread Matthew Holloway
Andrew Cunningham wrote: LOL, i enjoyed the wording. Considering the document character set of HTML4 is Unicode, if it can't be displayed in UTF-8 in a browser, then it can't be displayed using entitiies or NCRs either ;) Generally I agree, although one good thing about entities (including

Re: [WSG] HTML special characters coding

2008-06-17 Thread Sam Sherlock
up as a ? when it's unknown rather than mangled as ’ has caused me truma in the past. now I use UTF-8 aiming to entifyand quotes aswell as £ and such dealing with large amounts of content thats been created in a wyswyg editor can be quite an issue erronus classes nbsp; also some

Re: [WSG] HTML special characters coding

2008-06-17 Thread kevin_erickson
thank you for the good responses. Very helpful. Kevin --- Original Message --- From:Matthew Holloway [EMAIL PROTECTED] Sent:Tue 6/17/08 7:36 pm To:wsg@webstandardsgroup.org Subj:Re: [WSG] HTML special characters coding Andrew Cunningham wrote: LOL, i enjoyed the wording. Considering the

Re: [WSG] HTML special characters coding

2008-06-17 Thread Andrew Cunningham
Matthew Holloway wrote: Andrew Cunningham wrote: LOL, i enjoyed the wording. Considering the document character set of HTML4 is Unicode, if it can't be displayed in UTF-8 in a browser, then it can't be displayed using entitiies or NCRs either ;) Generally I agree, although one good

Re: [WSG] HTML special characters coding

2008-06-17 Thread Matthew Holloway
Andrew Cunningham wrote: a slight correction: NCRs by definition are always know. Ah, we seem to actually agree but we're talking about what's known to different things. Unknown when I used it was in terms of the ability to render it sucessfully (known to the browser as a whole) not just in

Re: [WSG] HTML special characters coding

2008-06-17 Thread Jason Ray
I don't think this is right. It depends what language and character set you have specified the document to be in. If the character is included in the character set, there is no need to use the special code... provided the browser can read that character set... Jason On Wed, Jun 18, 2008 at 8:25

[WSG] IE6/7 not rendering an H1 correctly

2008-06-17 Thread Lynette Smith
www.americanmotorcycles.com.au Have been making some changes at client's request and things have gone wrong. Firefox is fine and renders as intended. The issue is #content h1. IE is not rendering it as per the css. It seems to be ignoring it. When I validated the page, there was 1 error:

Re: [WSG] IE6/7 not rendering an H1 correctly

2008-06-17 Thread Matthew Holloway
Lynette Smith wrote: I've been staring at if for ages and I don't understand this at all and was wondering if this was the reason IE won't render it as intended. Just above the div id=content there's a broken /div tag. -- .Matthew Holloway http://holloway.co.nz/

Re: [WSG] IE6/7 not rendering an H1 correctly

2008-06-17 Thread Lynette Smith
I can't believe I didn't spot that! Thank you! I've been staring at if for ages and I don't understand this at all and was wondering if this was the reason IE won't render it as intended. Just above the div id=content there's a broken /div tag.

[WSG] Re: Multiple Language Domains

2008-06-17 Thread jay
Paul McCann wrote: . The quirks mode issue, should not be there, we think the system is putting that in place for us!! eh? Quirks mode is a function of browsers : see http://en.wikipedia.org/wiki/Quirks_mode and http://www.cs.tut.fi/~jkorpela/quirks-mode.html jay