Re: a push @lines2 in pass1
Dumas Patrice <[email protected]> Thu, 6 Feb 2003 18:30:20 +0100
| Newsgroups | gmane.comp.tex.texi2html.devel |
|---|---|
| Message-ID | <[email protected]> |
> <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" /> This one seems right to me. > 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. I am gonna add that to the default texi2html header. > 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? I don't think so. I think all we use are entity which are part of latin1. Anyway I have just read on a w3c page that the default was ISO-8859-1, and it worked well, thus we could stick with ISO-8859-1, and also that although it is the default they said that it was not preferable to set it explicitly, and I guess that's why the validator doesn't take ISO-8859-1 as the default. Pat