I guess svg and mathml doctype are more strict with the characters, I'll
choose NCRs and utf-8
--
Regards,
Dani Iswara
http://daniiswara.net/
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
I still use encoded characters in attributes sometimes, for example in
alt text that needs quote makr. I can't think of an example off hand,
but I assume entities are still needed for that?
-Alastair
***
List Guidelines:
On 17 Jun 2008, at 23:46, 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.
On 18 Jun 2008, at 00:19, Andrew Cunningham wrote:
Use amp; nbsp;
Rick Lecoat
So let me see if I have this right: as long as my page declares an
encoding (I use UTF-8) I don't need to encode the entities, I
can just
type them straight into the markup. Is that correct?
Make sure that your whole environment is UTF-8 (your code editor, any database
Can others with experience with this please confirm (or not) what Patrick has
said?
Thanks.
Kevin
--- Original Message ---
From:Patrick Lauke [EMAIL PROTECTED]
Sent:Wed 6/18/08 6:10 am
To:wsg@webstandardsgroup.org
Subj:RE: [WSG] HTML special characters coding
Rick Lecoat
So let me see if I
]
Sent:Wed 6/18/08 6:10 am
To:wsg@webstandardsgroup.org
Subj:RE: [WSG] HTML special
characters coding
Rick Lecoat
So let me see if I have this right: as long as my page declares
an
encoding (I use UTF-8) I don't need to encode the
entities, I
can just
type them straight into
the markup
On 18/06/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Can others with experience with this please confirm (or not) what Patrick has
said?
Thanks.
Yes, Patrick is correct.
I would add one caveat. If you use UTF-8 (personally, I see no reason
to anything else), you should not use ASCII
On Thu, June 19, 2008 12:40 am, T. R. Valentine wrote:
Yes, Patrick is correct.
I would add one
caveat. If you use UTF-8 (personally, I see no reason
to
anything else), you should not use ASCII characters (hex) 81-9F /
(dec) 129-159 which includes stuff like 151; for an em dash
and 150;
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?
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
Of kevin_erickson
Sent: 17 June 2008 21:55
To: wsg@webstandardsgroup.org
Subject: [WSG] HTML special characters coding
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
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
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
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
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
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
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
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
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
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
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
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
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
23 matches
Mail list logo