[WSG] unsubscribe info

2004-12-12 Thread Glenn [futureAustralia.net]
there is no unsubscribe information at the footer of the WSG emails or 
on the email list information page.

where is it?


**
The discussion list for  http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
 

**
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] Changing Standard

2004-12-12 Thread Peter Costello
I might be wrong but I thought it was so you could apply all common
styles to the a and then simplify :link, :hover etc. to red etc.

ie:
a{
font-family:Verdana, Arial, Helvetica, sans-serif;
font-size: .9em;
font-weight: bold;
text-decoration: underline;
color: black;
}
a:link{
color: blue;
}
a:visited{
color:#99;
}
a:hover{
color: red;
text-decoration: none;
}
a:active{
color: red;
text-decoration: none;
}

or have i missed the point?
Cheers
Pete

On Sun, 12 Dec 2004 11:52:39 -, Kornel Lesinski <[EMAIL PROTECTED]> wrote:
> > Why using a:link ?
> >means that the word inside is a link
> > a { color:blue;  text-decoration:underline; }
> > is the same as setting
> > a:link { color:blue; text-decoration:underline; }
> > Link is a redundant tag
> 
> No, it isn't. Think about these:
> 
> foo
> bar
> 
> a {} matches both, and :link matches only the second one.
> Additionally :link matches only unvisited, inavctive, nonfocused links,
> but a{} sets all at once.
> 
> :link will become very important in XHTML2 where
> every element can have href attribute.
> 
> --
> regards, Kornel LesiÅski
> 
> 
> 
> **
> The discussion list for  http://webstandardsgroup.org/
> 
>  See http://webstandardsgroup.org/mail/guidelines.cfm
>  for some hints on posting to the list & getting help
> **
> 
> 


-- 
--
Peter Costello
www.domestik.net
**
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] Validating unicode files

2004-12-12 Thread Kevin Futter
On 13/12/04 8:23 AM, "Matthew Cruickshank"
<[EMAIL PROTECTED]> wrote:

> Hi chaps,
> 
> When it comes to text encoding the character range from 127-255 is, as I
> understand it, disputed territory. In that all kinds of regional hacks
> were used over the years and with Unicode they're no longer neccessary
> so I should avoid this range. I was just copying some text together and
> my xml parser didn't like it because of some characters in this range.
> It seems that even when you tell notepad.exe to save as utf-8 it
> sometimes doesn't.
> 
> So is there a bit of software to validate UTF-8 encoded files?
> 
> 
> .Matthew Cruickshank
> http://holloway.co.nz/

My understanding is that it's a known 'feature' of Notepad to add some
internal proprietary identifier to UTF-8 encoded files that actually render
them invalid, so-to-speak. I'm sure someone else can explain it better than
I just did!

I've found this article quite useful, though it may not necessarily directly
address your problem:

http://www.joelonsoftware.com/articles/Unicode.html

-- 
Kevin Futter
Webmaster, St. Bernard's College
http://www.sbc.melb.catholic.edu.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
**



[WSG] Validating unicode files

2004-12-12 Thread Matthew Cruickshank
Hi chaps,
When it comes to text encoding the character range from 127-255 is, as I 
understand it, disputed territory. In that all kinds of regional hacks 
were used over the years and with Unicode they're no longer neccessary 
so I should avoid this range. I was just copying some text together and 
my xml parser didn't like it because of some characters in this range. 
It seems that even when you tell notepad.exe to save as utf-8 it 
sometimes doesn't.

So is there a bit of software to validate UTF-8 encoded files?
.Matthew Cruickshank
http://holloway.co.nz/
**
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] LOCAL XHTML TESTING - HOW TO DO IT?

2004-12-12 Thread Joey
Download Web Developer Toolbar for firefox for local validating.
http://www.chrispederick.com/work/firefox/webdeveloper/
Then you can see a tool under "Tools" called "Validate Local HTML" that 
should help you out a bit.

Hope this helps
Joey
Charles Slack wrote:
LOCAL XHTML TESTING - HOW TO DO IT?
Hi,
I'm an experienced real time software engineer getting involved in
Web design. I have done a lot of reading, both books and web pages
and, after a lot of heart searching, have arrived at the following
strategy for developing web pages:
 
1. Develop and test the site initially using an XHTML 1.0 strict
DOCTYPE until I have the site working to my satisfaction. This will
be done locally on my PC (I will not upload the site). I hope that
this will set me on the right road to producing well formed XHTML
code which will be ready when more browsers (IE) support XHTML. I
intend to follow the W3C compatibility rules (Annex C) to make sure
that my XHTML is backwards compatible with HTML.
 
2. I realise that there are difficulties presenting XHTML to some
browsers (IE in particular) and that I will end up with the browser
treating my code as HTML in "quirks" mode. For that reason I intend
to change to HTML 4.01 strict DOCTYPE before going live and carrying
out validation and final testing.
 
That's the background. The question is what is the best way of
testing and validating my XHTML code locally? I am not very clear how
browsers, validators/linters, Tidy etc manage doctypes when looking
at code. How can I be sure that they are treating the code as XHTML 
1.0 strict and not HTML?
 
Can anyone point me at any interesting sites or offer any suggestions?
 
Thanks,
 
Charlie

**
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] OFFTOPIC: New URL to The Tao of Webdesign

2004-12-12 Thread Jorge Laranjo
Hi there folks.
Since the http://lesi.host.sk/fueg0/ is not responding, i'm moving The 
Tao of Webdesign to http://thetaoofwebdesign.tk/ or 
http://thetaoofwebdesign.weblog.com.pt/
Hope that thoose of you that read the blog can continue to do so.

--
Atentamente,
Jorge Laranjo
site > http://thetaoofwebdesign.tk
msn > [EMAIL PROTECTED]
aim > [EMAIL PROTECTED]
jabber > [EMAIL PROTECTED]
--
Atentamente,
Jorge Laranjo
site > http://thetaoofwebdesign.tk/
email> [EMAIL PROTECTED]
msn > [EMAIL PROTECTED]
aim > [EMAIL PROTECTED]
jabber > [EMAIL PROTECTED]
**
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] LOCAL XHTML TESTING - HOW TO DO IT?

2004-12-12 Thread Roger Johansson
On 12 dec 2004, at 14.15, Charles Slack wrote:
LOCAL XHTML TESTING - HOW TO DO IT?
An easy way to check how Mozilla based browsers handle it is to change 
the file extension of your XHTML documents from .html to .xhtml. This 
will make Mozilla/Firefox treat it as application/xhtml+xml (check 
"View Page Info"), and alert you of any well-formedness errors.

/Roger
--
http://www.456bereastreet.com/
**
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] LOCAL XHTML TESTING - HOW TO DO IT?

2004-12-12 Thread Kornel Lesinski
For serious testing install web server locally.
There is for example easyphp.org (and many others) that install and  
configure Apache, PHP, MySQL with almost one click.

Then you can configure Apache to send .xhtml files as application/xhtml+xml
or use PHP for that.
httpd.conf:
AddType application/xhtml+xml .xhtml
or
each file:

Once you have proper content-type set browsers (except IE ofcourse) will do
basic validation of document - requiring that your document is well-formed  
XML (XHTML).

--
regards, Kornel Lesiński
**
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] Changing Standard

2004-12-12 Thread Kornel Lesinski
Why using a:link ?
   means that the word inside is a link
a { color:blue;  text-decoration:underline; }
is the same as setting
a:link { color:blue; text-decoration:underline; }
Link is a redundant tag
No, it isn't. Think about these:
foo
bar
a {} matches both, and :link matches only the second one.
Additionally :link matches only unvisited, inavctive, nonfocused links,
but a{} sets all at once.
:link will become very important in XHTML2 where
every element can have href attribute.
--
regards, Kornel Lesiński
**
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] LOCAL XHTML TESTING - HOW TO DO IT?

2004-12-12 Thread Charles Slack




LOCAL XHTML TESTING - HOW TO DO IT?
Hi,I'm an experienced real time software 
engineer getting involved in Web design. I have done a lot of reading, both 
books and web pages and, after a lot of heart searching, have arrived at the 
following strategy for developing web pages:
 
1. Develop and test the site initially using an 
XHTML 1.0 strict DOCTYPE until I have the site working to my satisfaction. 
This will be done locally on my PC (I will not upload the site). I hope that 
this will set me on the right road to producing well formed XHTML code 
which will be ready when more browsers (IE) support XHTML. I intend to 
follow the W3C compatibility rules (Annex C) to make sure that my XHTML is 
backwards compatible with HTML.
 
2. I realise that there are difficulties presenting 
XHTML to some browsers (IE in particular) and that I will end up with the 
browser treating my code as HTML in "quirks" mode. For that reason I intend 
to change to HTML 4.01 strict DOCTYPE before going live and carrying out 
validation and final testing.
 
That's the background. The question is what is the 
best way of testing and validating my XHTML code locally? I am not very 
clear how browsers, validators/linters, Tidy etc manage doctypes when 
looking at code. How can I be sure that they are treating the code as XHTML 
1.0 strict and not HTML?
 
Can anyone point me at any interesting sites or 
offer any suggestions?
 
Thanks,
 
Charlie


Re: [WSG] Changing Standard part2 !!!

2004-12-12 Thread Lyn Patterson
Bert Doorn wrote:
If I want to see
movies, I watch TV or hire a Video or DVD.   If I want to hear music, I
switch on the radio or listen to a CD (or tape, or old-fashioned record). 

I use the web to seek information and like many people I can only get
dial-up (or a very expensive satellite connection) where I live.   I avoid
sites that use bandwidth-hungry (non text) content (the back button on my
browser is very handy there) because most of the information I seek is fine
as words and pictures (and I am impatient).  
 

Yes, Bert, I totally agree.
Lyn

 

**
The discussion list for  http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**