Re: a push @lines2 in pass1
Derek Robert Price <[email protected]> Thu, 06 Feb 2003 10:56:26 -0500
| Newsgroups | gmane.comp.tex.texi2html.devel |
|---|---|
| Organization | Ximbiot <http://ximbiot.com> |
| Message-ID | <[email protected]> |
Pat,
I don't know enough about the XML declaration to tell you how to embed
content type. The HTTP Content-Type field is part of the HTTP protocol,
supplied by the web server, and I don't see how they would find that in
an uploaded document anyhow. I can show you a sample META tag:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
. . .
</head>
In this example, the HTML META tag is used to set the http-equiv
content-type, i.e. perform the equivalent of setting the HTTP
Content-Type field. Then notice that the content type is given a MIME
type of text/html which would be appropriate for text2html output, then
the charset is set.
My knowledge stops short of which charset we now use. I'm used to using
whatever the standard U.S. charset is, and I look up the numbers every
time (ISO-8859-1?). You've been fiddling with odd (to me) character
support, so are we outputting UTF-8 now?
Derek
--
*8^)
Email: [email protected]
Get CVS support at <http://ximbiot.com>!
--
I will not burp in class.
I will not burp in class.
I will not burp in class...
- Bart Simpson on chalkboard, _The Simpsons_
Dumas Patrice wrote:
>It is commited now.
>
>
>
>>>Please use http://validator.w3.org/file-upload.html
>>>or some such when you change texi2html output.
>>>
>>>
>
>I just tried but I get (with texi2html.html, xemacs.html):
>=============================================================================
>I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to validate the document. The sources I tried are:
>
> * The HTTP Content-Type field.
> * The XML Declaration.
> * The HTML "META" element.
>
>And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation.
>
>Since none of these sources yielded any usable information, I will not be able to validate this document. Sorry. Please make sure you specify the character encoding in use.
>
>IANA maintains the list of official names for character sets.
>Valid XHTML 1.0! The W3C Validator Team
>==============================================================================
>
>I can try to understand the issue and fix it, but maybe somebody is more
>knowledgeable than me on that point.
>
>Pat
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>