Vaska, you¨re still mixing those:
I think you are mixing two things which should be separated.
The first problem is the language of the page (defined in the header)
The second problem is how to create a non-ascii character
He is right.
It is a tricky business because for a French typist I
Vaska, you¨re still mixing those:
I think you are mixing two things which should be separated.
The first problem is the language of the page (defined in the header)
The second problem is how to create a non-ascii character
He is right.
I've already identified that I will be using utf-8.
Patrick!
Am Donnerstag, 2. Juni 2005 um 18:11:30 haben Sie geschrieben:
I agree with you in all points but this one. Even in XHTML 1.0 the
lang-Attribute is needed.
At the risk of splitting very fine hairs even further: *needed* or
*allowed* ? I'd tend to think the latter...
You are right!
Hello all,
I have the task of adding a bunch of PDF and Word files to a web site I
work on, that currently conforms to WAI Priority 1 guidelines.
My first question is that if I convert the PDF files to HTML to make
them more accessible, am I right in thinking that this is only half my
job
At 05:36 AM 6/3/2005, you wrote:
snip
Secondly, with the Word documents, if there is an easier way to convert
them to HTML? At the moment I am saving as HTML from Word, taking them
into Dreamweaver and using 'Clean up Word HTML'. After that I use 'Find
and replace' to strip out all font, span
Angela Galvin wrote:
Hello all,
I have the task of adding a bunch of PDF and Word files to a web site I
work on, that currently conforms to WAI Priority 1 guidelines.
My first question is that if I convert the PDF files to HTML to make
them more accessible, am I right in thinking that this
On Fri, 2005-06-03 at 06:36, Angela Galvin wrote:
Secondly, with the Word documents, if there is an easier way to convert
them to HTML?
I use an open source program, antiword, to convert the Word docs to text
and then just add the necessary markup. (And, of course, edit out the
Word
Mary Krieger wrote:
If you copy and paste the text into the 'content' part of your standard
page, the line breaks will show you where the paragraph and headings
are.
I'm using Homesite so I just select and repeat the similar code ( first
p, then h1, h2 etc) from one end of the document to the
Ha! The shoe's on the other foot, eh Russ?
Good show Maxine,
~d
--
Douglas Clifton
[EMAIL PROTECTED]
http://loadaveragezero.com/
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
Douglas Clifton wrote:
Ha! The shoe's on the other foot, eh Russ?
I can't believe the WCAG 1.0 Guidelines and Checkpoints for Flash link
in section 6 goes to a .swf file. o_O
--
Love does not demand its own way.1 Corinthians 13:5
Team OS/2 ** Reg. Linux User #211409
Felix
Completely true - the irony!
The original post is here:
http://www.markme.com/accessibility/archives/007344.cfm
Unfortunately, it too goes off to the same flash file.
Russ
I can't believe the WCAG 1.0 Guidelines and Checkpoints for Flash link
in section 6 goes to a .swf file. o_O
Hi there,
My first question is that if I convert the PDF files to HTML to make
them more accessible, am I right in thinking that this is only half my
job done? If the original file wasn't marked up correctly in the first
place before being saved as PDF (with headings, etc) does this mean
Russ,
One of the topics you discuss is your stance on the XHTML vs HTML
debate. Your links support your stance -- I've read these before, and
find them interesting and insightful, however they are trying to
convince the reader of their point and I prefer a balanced argument. In
looking for
Russ wrote:
[quote]
At the risk of being burned at the stake, I think that unless you are willing
to serve your pages as application/xhtml+xml with content negotiation, then you
are probably better off staying with HTML 4.01 at this time.
[/quote]
Let me be the first to gather the kindling :-)
Any pointers?
Hi Ben,
When interviewed, I was reluctant to express an opinion on this topic for
the very reasons you describe - the XHTML vs HTML argument quickly turns
from facts to opinion - similar to the font size and liquid vs fixed width
debates.
I completely agree with Vlad that Hixies
Having never seen/heard a screen reader in action, I am uncertain about how
to make some aspects of coding user-friendly for those using screen readers.
Specifically, I find my alt tags are almost always the same as my captions.
For example, if I insert an image of Joe Smith, my code might look
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
18 matches
Mail list logo
