Hi Luc,
As regards the question what does a screen reader do? I'm afraid I've no
idea.
I think this is best served with the image. One image in the CSS as
opposed to multiple character codes in the HTML.
Yup, but a wanted to stray away from the tradional path ;-)
What i was worried about
Good evening list,
When you use a character code, e.g. #x00BB; as a list marker
(hardcoded in the li), how is that interpreted by a speech browser?
Does the user hear those characters as they appear or are they
converted into 'double right arrow'?
Might be a stupid question but it would prevent
Hi Luc,
I might suggest that 'double right arrow' is purely presentational and
not 'semantically' relevant, so it's not such a good idea to muddy up
the HTML with extraneous code. If you want to avoid using a background
image you could write your CSS in a 'progressive enhancement' fashion
by
Hello John,
JU I might suggest that 'double right arrow' is purely presentational and
JU not 'semantically' relevant, so it's not such a good idea to muddy up
JU the HTML with extraneous code. If you want to avoid using a background
JU image you could write your CSS in a 'progressive
On Sun, Apr 6, 2008 at 12:11 AM, David Hucklesby [EMAIL PROTECTED] wrote:
On Fri, Apr 4, 2008 at 4:16 PM, Kristine Cummins
[EMAIL PROTECTED] wrote:
Can someone tell me how to fix this W3C warning – I'm new to
understanding this part.
On Fri, Apr 4, 2008 at 4:16 PM, Kristine Cummins
[EMAIL PROTECTED] wrote:
Can someone tell me how to fix this W3C warning – I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
On Fri, 4 Apr 2008 20:15:19 -0400, Nikita The Spider
Can someone tell me how to fix this W3C warning - I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Thanks!
***
List Guidelines:
At 1:16 PM -0700 4/4/08, Kristine Cummins wrote:
Can someone tell me how to fix this W3C warning - I'm new to
understanding this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2Fhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Thanks!
In
Can someone tell me how to fix this W3C warning - I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Change this tag in your head section:
meta http-equiv=content-type content=text/html; charset=utf-8 /
To:
meta
FIXED. The URL below will not show any warnings now.
Thanks again.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tim Offenstein
Sent: Friday, April 04, 2008 1:42 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Character Encoding Mismatch
At 1:16 PM -0700 4/4/08, Kristine
The advice below is sufficient if your content is limited to characters in
the ISO-8859-1 repertoire If you are using any characters outside this
repertoire on the site, then i wouldn't use this approach.
As
indicated in a previous email, you could ask your web master to change the
default
On Fri, Apr 4, 2008 at 4:16 PM, Kristine Cummins
[EMAIL PROTECTED] wrote:
Can someone tell me how to fix this W3C warning – I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Kristine,
If your server is already specifying the character
Ishida
To: wsg@webstandardsgroup.org
Sent: Tuesday, November 22, 2005 6:54
PM
Subject: RE: [WSG] Character encoding
mismatch
Thanks, Susan, for pointing to that stuff.Paul, you if
you're using Apache you may also find this particularly useful:"Setting
'charset' inform
/International/
http://people.w3.org/rishida/blog/
http://www.flickr.com/photos/ishida/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susanne Jäger
Sent: 10 November 2005 12:21
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Character encoding
I am getting the followingwarningwhen I
validate my pages:
--
Character Encoding mismatch!
The character encoding specified in the HTTP header
(iso-8859-1) is different from the value in the
meta element (utf-8). I will use the value
from the HTTP header
2005/11/10, Paul Collins [EMAIL PROTECTED]:
I am getting the following warning when I validate my pages:
--
Character Encoding mismatch!
The character encoding specified in the HTTP header (iso-8859-1) is
different from the value in the meta element (utf-8). I will use the
Instead of:
meta http-equiv=Content-Type content=text/html; charset=utf-8;/
Try:
meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 /
This will match what your web server is sending, otherwise change your
web server config if you can :-)
Lloyd
On 11/10/05, Paul Collins [EMAIL
Paul Collins wrote, On 10.11.2005 12:44:
I thought this was the correct way to add special
characters for XHTML, but what I am reading now seems to contradict
this. This is the part of standards where I get a bit confused. Does
anyone have any advice or know of some good articles where they
That seems to work, thanks heaps
Rimantas
- Original Message -
From:
Rimantas
Liubertas
To: wsg@webstandardsgroup.org
Sent: Thursday, November 10, 2005 12:01
PM
Subject: Re: [WSG] Character encoding
mismatch
2005/11/10, Paul Collins [EMAIL PROTECTED]:
I
Thanks Susanne, that's a really good
reference.
Cheers,Paul
- Original Message -
From:
Susanne Jäger
To: wsg@webstandardsgroup.org
Sent: Thursday, November 10, 2005 12:21
PM
Subject: Re: [WSG] Character encoding
mismatch
Paul Collins wrote, On 10.11.2005 12
Street
Sent: 04 June 2005 03:52
To: Web Standards Group mailing list
Subject: [WSG] Character encoding
I've always thought that characters should be marked up with
appropriate entity codes (for example, accented letters,
etc.) in (X)HTML, rather than simply pasted in and left for
character
Gene Falck wrote:
Tidy is one of the programs I have been thinking
of getting, so I would like to hear about any
bugs and bug fixes.
Regards,
Gene Falck
Tidy has evolved from it's beginning with Dave Raggett. Like many
tools, it's great when you learn how to use it, and to work with
For some reason, I feel I have to escape every character that is not a
letter or number.
I was feeling the same, and working on it, when this thread arrived.
At the time it appeared I was looking up numeric entity lists in
Cyrillic and adapting them to a conversion_map function (for PHP).
Vaska.WSG wrote:
For some reason, I feel I have to escape every character that is not a
letter or number.
I was feeling the same, and working on it, when this thread arrived.
At the time it appeared I was looking up numeric entity lists in
Cyrillic and adapting them to a conversion_map
I've always thought that characters should be marked up with appropriate
entity codes...
It's just always felt dirty seeing certain characters not written in their
appropriate entity codes.
Eh, maybe on anglo-saxon websites... The rest of the world has a
different opinion ;)
--
Jan Brasna
On Sat, 4 Jun 2005 18:07:48 -0500, Matt Thommes wrote:
For instance, I always escape a dash (-) with #8211;--- when
using it in a normal sentence.
Thats interesting - I escape such entities as ampersands () and double
quotes (), but not things such as hyphens.
What benefits or problems
Matt Thommes wrote:
What benefits or problems avoided do you perceive by doing this and
what other characters are you escaping?
Lea, I'm not sure why I always escape the dash - perhaps because I can??? :)
I am assuming the dash will someday cause me problems, so I just
escape it now, to
At 04:36 PM 6/4/2005, Lea de Groot wrote:
On Sat, 4 Jun 2005 18:07:48 -0500, Matt Thommes wrote:
For instance, I always escape a dash (-) with #8211;--- when
using it in a normal sentence.
Thats interesting - I escape such entities as ampersands () and double
quotes (), but not things
On Sat, 4 Jun 2005 18:56:16 -0500, Matt Thommes wrote:
For some reason, I feel I have to escape every character that is not a
letter or number.
OK, I'm always up for new Best Practices, but I do need some basis for
adopting changes.
I escape double quotes and ampersands because of the HTML
Hi Matt
You wrote:
Lea, I'm not sure why I always escape the dash - perhaps because I can??? :)
I am assuming the dash will someday cause me problems, so I just
escape it now, to avoid a lot of re-work.
I don't expect an unescaped dash to cause trouble
as it has, AFAIK, no meanings in code.
Hi Geoff,
You wrote:
... I know I have developed sites in the past that I have felt pretty
confident have been a good attempt at best of practice, but age sure shows
their vintage, and I am not talking about the CSS, just thinking of the
(X)HTML.
LOL--that's quite nice compared to what I
I've always thought that characters should be marked up with appropriate
entity codes (for example, accented letters, etc.) in (X)HTML, rather
than simply pasted in and left for character encoding and the user agent
to take care of. I've written a plugin for the WordPress weblog
software that
On Fri, 2005-06-03 at 23:42 -0400, Vlad Alexander wrote:
Hi Joshua,
If you are serving your content as Unicode (UTF-16 or UTF-8), then there is
no need to use entities. If you do need to escape characters and you are
using XHTML, then it's best to use their decimal values rather than
Lee wrote:
Hello Listpeople,
Anyone know if there's an XHTML special char. for ® ?
Can't you use the standard registered entity reference: reg;?
http://www.w3.org/TR/xhtml1/
section C-12.
Best,
.Peter
--
Peter J. Farrell :: Maestro Publishing
blog:: http://blog.maestropublishing.com
email ::
registered trademark reg; #174;
Copied and pasted from
http://www.w3schools.com/html/html_entitiesref.asp
On Tue, 2005-05-17 at 11:58 +0100, Lee wrote:
Hello Listpeople,
Anyone know if there's an XHTML special char. for ?
Kind Regards,
Joshua Street
base10solutions
Website:
On Tue, 17 May 2005 11:58:08 +0100, Lee [EMAIL PROTECTED] wrote:
Anyone know if there's an XHTML special char. for ?
#174;
You should avoid all named entities in XHTML, except quot, amp, lt, gt.
For all other characters use unicode encoding or numeric unicode entity
reference.
--
regards,
Seems to validate - many thanks!
Lee
Joshua Street wrote:
registered trademark reg; #174;
Copied and pasted from
http://www.w3schools.com/html/html_entitiesref.asp
On Tue, 2005-05-17 at 11:58 +0100, Lee wrote:
Hello Listpeople,
Anyone know if there's an XHTML special char. for ?
Kind
I believe it's reg;
~john
_
Dr. Zeus Web Design
http://www.DrZeus.net
content without clutter
on 5/17/2005 11:58 AM Lee said the following:
Hello Listpeople,
Anyone know if there's an XHTML special char. for ® ?
**
The
Why might that be then?
Lee
Kornel Lesinski wrote:
On Tue, 17 May 2005 11:58:08 +0100, Lee [EMAIL PROTECTED] wrote:
Anyone know if there's an XHTML special char. for ?
#174;
You should avoid all named entities in XHTML, except quot, amp, lt, gt.
For all other characters use unicode encoding or
Kornel Lesinski wrote:
#174;
You should avoid all named entities in XHTML, except quot, amp, lt, gt.
For all other characters use unicode encoding or numeric unicode
entity reference.
Then why does the W3 use it in their example?
http://www.w3.org/TR/xhtml1/
section c12
--
Peter J. Farrell ::
On 17 May 2005, at 8:37 pm, Peter J. Farrell wrote:
Kornel Lesinski wrote:
#174;
You should avoid all named entities in XHTML, except quot, amp, lt,
gt.
For all other characters use unicode encoding or numeric unicode
entity reference.
Then why does the W3 use it in their example?
Philippe Wittenbergh wrote:
It is valid for text/html (aka tagsoup). If you serve the document as
application/xhtml+xml, then the browser should ignore named entities
except the 5 ones (quot, amp, lt, gt and apos).
That is not exactly correct. If in a document served as
application/xhtml+xml
On Fri, 2 Jul 2004 13:03:34 +1000, Ben Bishop [EMAIL PROTECTED] wrote:
Your web server (eg Apache) sends the character encoding HTTP header.
In order to match up your HTTP header to your meta-equiv you would
need to make the change server-side, something you might not have
access to do.
Kay Smoljak wrote:
I was under the impression - please correct me if I'm wrong - that if
the server is sending the character encoding, there is no need to also
have the meta tag. Is there any other reason to include it,
client-side?
Take a look at:
...if the server is sending the character encoding...Is there
any other reason to include it, client-side?
ominous toneDid you read the W3C link posted?/ominous tone ;)
I can't speak with any authority on this matter, and not meaning to
break the unwritten rule of not answering unless you know
On Friday 02 July 2004 05:03, Ben Bishop wrote:
Hi Sage,
When I validate my page, I get the following message
The character encoding specified in the HTTP header (utf-8) is
different from the value in the meta element (iso-8859-1).
I'd like to keep the iso-8859-1 value, just because it
When I validate my page, I get the following message (which doesn't
invalidate the page, but I still want to fix it):
The character encoding specified in the HTTP header (utf-8) is
different from the value in the meta element (iso-8859-1). I will
use the value
Sage Olson wrote:
Here's my header:
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
That's not you HTTP header. The HTTP headers are sent by the server
before even the first byte of your document is
Hi Sage,
When I validate my page, I get the following message
The character encoding specified in the HTTP header (utf-8) is
different from the value in the meta element (iso-8859-1).
I'd like to keep the iso-8859-1 value, just because it seems to work
Your web server (eg Apache) sends the
49 matches
Mail list logo
