[TYPO3] CSS woes

[Christopher]

Hi,

On 3/9/06, Patrick O'Hara <pdohara at practicalprogrammer.org> wrote:
> See Below
>
> On 3/8/06, Christopher <bedlamhotel at gmail.com> wrote:
> >
> > Hi,
> >
> > On 3/8/06, Patrick O'Hara <pdohara at practicalprogrammer.org> wrote:
> > > Thanks for the response, but no I do not have a meta tag in my template.
> > > Something in Typo3 is generating the meta tag.
> >
> > I've never seen a 'us-ascii' charset meta element in a typo3 site.
> > I've hardly ever seen us-ascii specified as a charset in _any_ website
> > in fact. Typo3 will add _one_ meta element specifying the iso-8859
> > charset by default, it will _not_ add that second one--it has to be
> > there as a result of one of only four things that I can think of:
> >
> > a) If using TV, it's in the original template and you've selected it
> > when mapping the template
> > b) You've specified it using "page.charset =" (though I still don't
> > know how that could get you _two_ specified charsets...)
> > c) Possibly an extension put it there (but this would be a strange
> > thing for an extension to do...)
> > d) Maybe it's there because you're using one of the deprecated static
> > templates in your main TS template (if so, switch to css-styled
> > content instead).
> >
> >
> > -Christopher
> > _______________________________________________
> > TYPO3-english mailing list
> > TYPO3-english at lists.netfielders.de
> > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
> >
>
> Here is what I have.  Perhaps you can see something here that looks odd.
>
[snip]
>
> I have no constants defined.  I have the following static includes:
> styles.content
> content
> cSet stylesheet
> cSet
>
> and I have these static includes from extensions:
> CSS Styled IMGTEXT
> CSS Styles Content
> HTML/CSS Styling
>
> If there is anything else you would like to see let me know.  I am pretty
> much ready to "give up", and live with the fact that Typo3 is creating an
> invalid page.

Why are you ready to give up? I suggested four possible places where
such a thing could possibly  come from, and while you've ruled out (a)
and possibly (b), there are still (c) and (d) to consider. Try
removing each extension in turn and regenerating the page. If it's
still there, the most likely candidate will be one of the static
templates--get rid of those and use css-styled-content instead!

-Christopher