Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Why you should validate your HTML and CSS
1 view
Skip to first unread message
Delois
Jan 27, 2012, 5:18:02 AM1/27/12
to
With point of visitors, your website might be different blocks which are
designed well and have interest of its functionality only with point of
search engine
Your visitors don’t care of back hand code of your website and just
focus on visual look and information on website where search engine
require error free pages to index your website. Validating your code
would evaluate small errors that might stop search engine to index your
all the content on web page.
Sometimes error occurred when it is viewed in different browser or
device. You would get ideas on what is require creating robust website
for all browser and device and suggestion regarding that.
Validating all code on web page make sure that all the function works
properly on your website. Sometime giving wrong input to specific
function stop works and it can be found by validation.
In some extreme conditions, due to server errors visitors can’t view the
content or access the website. You can check possible server errors can
cause in different condition.
--
'Web Design New York' (http://www.spinxwebdesignnewyork.com) 'Web Design
NYC' (http://www.spinxwebdesignnewyork.com/web-design-new-york.html)
------------------------------------------------------------------------
Delois's Profile: http://www.httppoint.com/member.php?userid=17043
View this thread: http://www.httppoint.com/showthread.php?t=56263
Message Posted via the webmaster forum http://www.httppoint.com, (Ad revenue sharing).
Jukka K. Korpela
Jan 27, 2012, 5:57:17 AM1/27/12
to
2012-01-27 12:18, Delois wrote:
> With point of visitors, your website might be different blocks which are
> designed well and have interest of its functionality only with point of
> search engine
This looks like a translation. I think many people would prefer reading
> With point of visitors, your website might be different blocks which are
> designed well and have interest of its functionality only with point of
> search engine
the original.
> Your visitors don�t care
Your message contains an octet outside the ASCII range, yet your message
headers have no character code specification. This is Usenet, not HTML,
but a very similar problem occurs in web authoring. If you cannot handle
this basic issue in a simple context like e-mail, are you competent in
giving advice on more sophisticated authoring issues?
> search engine
> require error free pages to index your website.
dead search engine, even if we limit ourselves to very technical aspects
of being error-free. The vast majority of web pages have HTML syntax
errors, CSS syntax errors, or JavaScript code errors, not to mention
incorrect semantics of tags, dysfunct links, violation of WAI rules, etc.
> Validating all code on web page make sure that all the function works
> properly on your website.
"validation".
> Sometime giving wrong input to specific
> function stop works and it can be found by validation.
> In some extreme conditions, due to server errors visitors can�t view the
> content or access the website. You can check possible server errors can
> cause in different condition.
This has nothing to do with HTML validation.
> content or access the website. You can check possible server errors can
> cause in different condition.
--
Yucca, http://www.cs.tut.fi/~jkorpela/
TK
Jan 27, 2012, 8:39:37 AM1/27/12
to
On 1/27/2012 4:57 AM, Jukka K. Korpela wrote:
> 2012-01-27 12:18, Delois wrote:
>
>> With point of visitors, your website might be different blocks which are
>> designed well and have interest of its functionality only with point of
>> search engine
>
> This looks like a translation. I think many people would prefer reading
> the original.
>> Your visitors don�t care
>
> Your message contains an octet outside the ASCII range, yet your message
> headers have no character code specification. This is Usenet, not HTML,
> but a very similar problem occurs in web authoring. If you cannot handle
> this basic issue in a simple context like e-mail, are you competent in
> giving advice on more sophisticated authoring issues?
As a point of interest, in the op's message the ' (apostrophe) displays
> 2012-01-27 12:18, Delois wrote:
>
>> With point of visitors, your website might be different blocks which are
>> designed well and have interest of its functionality only with point of
>> search engine
>
> This looks like a translation. I think many people would prefer reading
> the original.
>> Your visitors don�t care
>
> Your message contains an octet outside the ASCII range, yet your message
> headers have no character code specification. This is Usenet, not HTML,
> but a very similar problem occurs in web authoring. If you cannot handle
> this basic issue in a simple context like e-mail, are you competent in
> giving advice on more sophisticated authoring issues?
correctly. In your quote it displays as a diamond with a ? in the center.
--
TK ~ aka Terry Kimpling
http://wejuggle2.com/
1729, smallest prime number - sum of two cubes, two different ways
Jukka K. Korpela
Jan 27, 2012, 9:02:09 AM1/27/12
to
2012-01-27 15:39, TK wrote:
>>> Your visitors don�t care
>>
>> Your message contains an octet outside the ASCII range, yet your message
>> headers have no character code specification. This is Usenet, not HTML,
>> but a very similar problem occurs in web authoring. If you cannot handle
>> this basic issue in a simple context like e-mail, are you competent in
>> giving advice on more sophisticated authoring issues?
>
> As a point of interest, in the op's message the ' (apostrophe) displays
> correctly.
As I explained in the text quoted above, the original message has a data
>>> Your visitors don�t care
>>
>> Your message contains an octet outside the ASCII range, yet your message
>> headers have no character code specification. This is Usenet, not HTML,
>> but a very similar problem occurs in web authoring. If you cannot handle
>> this basic issue in a simple context like e-mail, are you competent in
>> giving advice on more sophisticated authoring issues?
>
> As a point of interest, in the op's message the ' (apostrophe) displays
> correctly.
error: a byte that is undefined in the implied encoding (ASCII).
> In your quote it displays as a diamond with a ? in the center.
indicating data error. As the Unicode Standard says, it is “used to
replace an incoming character whose value is unknown or unrepresentable
in Unicode.” Of course I know that the OP _meant_ to use U+2019 RIGHT
SINGLE QUOTATION MARK (’) there, but that’s not what the data contains.
Similarly, good browsers display � to indicate character data error (a
byte or byte sequence that does represent a character in the declared or
implied encoding) in HTML. They may do some heuristic error recovery,
though, so some common errors like using windows-1252 encoded U+2019 in
data purported to be ISO-8859-1 are usually silently fixed by applying
automatic switch to windows-1252. But errors don’t stop being errors
just because there is error recovery.
--
Yucca, http://www.cs.tut.fi/~jkorpela/
Ben Bacarisse
Jan 27, 2012, 9:16:36 AM1/27/12
to
TK <tkn...@wejuggle2.com> writes:
> On 1/27/2012 4:57 AM, Jukka K. Korpela wrote:
>> 2012-01-27 12:18, Delois wrote:
>>
>>> With point of visitors, your website might be different blocks which are
>>> designed well and have interest of its functionality only with point of
>>> search engine
>>
>> This looks like a translation. I think many people would prefer reading
>> the original.
>>> Your visitors don�t care
>>
>> Your message contains an octet outside the ASCII range, yet your message
>> headers have no character code specification. This is Usenet, not HTML,
>> but a very similar problem occurs in web authoring. If you cannot handle
>> this basic issue in a simple context like e-mail, are you competent in
>> giving advice on more sophisticated authoring issues?
>
> As a point of interest, in the op's message the ' (apostrophe)
> displays correctly. In your quote it displays as a diamond with a ?
> in the center.
Your newsreader either guessed correctly or it happened to be set to use
> On 1/27/2012 4:57 AM, Jukka K. Korpela wrote:
>> 2012-01-27 12:18, Delois wrote:
>>
>>> With point of visitors, your website might be different blocks which are
>>> designed well and have interest of its functionality only with point of
>>> search engine
>>
>> This looks like a translation. I think many people would prefer reading
>> the original.
>>> Your visitors don�t care
>>
>> Your message contains an octet outside the ASCII range, yet your message
>> headers have no character code specification. This is Usenet, not HTML,
>> but a very similar problem occurs in web authoring. If you cannot handle
>> this basic issue in a simple context like e-mail, are you competent in
>> giving advice on more sophisticated authoring issues?
>
> As a point of interest, in the op's message the ' (apostrophe)
> displays correctly. In your quote it displays as a diamond with a ?
> in the center.
a default that matched the OP’s encoding. Jukka’s newsreader presumably
did not guess correctly. The character you describe is Unicode’s
REPLACEMENT CHARACTER: “used to replace an incoming character whose
value is unknown[...]” so, in some sense, his message did display the
character correctly!
The original message had an octet whose value was 146 (hex 92). In most
Windows single-byte encodings this is a right single quote (the
preferred character to use for apostrophe, despite the name).
--
Ben.
dorayme
Jan 27, 2012, 3:59:07 PM1/27/12
to
In article
<0.fe3bcf0a3c84d02021d0.2012...@bsb.me.uk>,
not the usual font, not so jammed up to the letter on the left as
usual, but near the baseline where commas like to hang out. In fact,
it looked like an apostrophe that had lost the will to fly and had
dropped to eke out the rest of its days among the commas and the full
stops, I hope this is not going to depress me for the rest of the day.
> so, in some sense, his message did display the
> character correctly!
>
There is always a way of looking at things optimistically!
> The original message had an octet whose value was 146 (hex 92). In most
> Windows single-byte encodings this is a right single quote (the
> preferred character to use for apostrophe, despite the name).
Ah, is that so? OK, maybe it did not fall to die.
--
dorayme
<0.fe3bcf0a3c84d02021d0.2012...@bsb.me.uk>,
Ben Bacarisse <ben.u...@bsb.me.uk> wrote:
> TK <tkn...@wejuggle2.com> writes:
>
> > On 1/27/2012 4:57 AM, Jukka K. Korpela wrote:
> >> 2012-01-27 12:18, Delois wrote:
...
> TK <tkn...@wejuggle2.com> writes:
>
> > On 1/27/2012 4:57 AM, Jukka K. Korpela wrote:
> >> 2012-01-27 12:18, Delois wrote:
> >> Your message contains an octet outside the ASCII range, yet your message
> >> headers have no character code specification. ...
> >
> > As a point of interest, in the op's message the ' (apostrophe)
> > displays correctly. In your quote it displays as a diamond with a ?
> > in the center.
>
> Your newsreader either guessed correctly or it happened to be set to use
> a default that matched the OP’s encoding. Jukka’s newsreader presumably
> did not guess correctly. The character you describe is Unicode’s
> REPLACEMENT CHARACTER: “used to replace an incoming character whose
> value is unknown[...]”
In mine, I got, instead of the usual comma, a thinner sort of affair,
> > As a point of interest, in the op's message the ' (apostrophe)
> > displays correctly. In your quote it displays as a diamond with a ?
> > in the center.
>
> Your newsreader either guessed correctly or it happened to be set to use
> a default that matched the OP’s encoding. Jukka’s newsreader presumably
> did not guess correctly. The character you describe is Unicode’s
> REPLACEMENT CHARACTER: “used to replace an incoming character whose
> value is unknown[...]”
not the usual font, not so jammed up to the letter on the left as
usual, but near the baseline where commas like to hang out. In fact,
it looked like an apostrophe that had lost the will to fly and had
dropped to eke out the rest of its days among the commas and the full
stops, I hope this is not going to depress me for the rest of the day.
> so, in some sense, his message did display the
> character correctly!
>
> The original message had an octet whose value was 146 (hex 92). In most
> Windows single-byte encodings this is a right single quote (the
> preferred character to use for apostrophe, despite the name).
--
dorayme
MVP
Feb 4, 2012, 6:12:55 PM2/4/12
to
I try to make sure my pages are as compliant as possible. This way there is
a higher probability they will be rendered as expected.
Once the HTML5 approval processes is done then far better looking web
content will be possible but the complexity will need advanced editing
tools.
http://www.hardcore-games.tk http://www.windows-it.tk
a higher probability they will be rendered as expected.
Once the HTML5 approval processes is done then far better looking web
content will be possible but the complexity will need advanced editing
tools.
http://www.hardcore-games.tk http://www.windows-it.tk
0 new messages