On Friday, December 7, 2012 at 11:52:17 AM UTC-6, [email protected] wrote: > Op maandag 3 december 2012 10:49:20 UTC+1 schreef Geoff Welsh het volgende: > > [email protected] wrote: > > > > > Hi, > > > > > > > > > > I received a webpage in XHTML 1.0 Strict, but Composer doesn't seem > > > > > to recognize XHTML... When I ask the w3c to validate, I get a lot of > > > > > errors, because Composer deems to chop of the / at the end of <meta > > > > > ... /> and other statements (<br />, etc.) that need the / in Strict > > > > > XHTML. > > > > > > > > > > I then looked at the !DOCTYPE composer puts on new pages: 4.01 > > > > > Transitional. I would at least want 4.01 Strict, or why not HTML5? > > > > > > > > > > The Page Title and Properties under Format is always greyed out, as > > > > > are most of the options under that tab (I can only use Font, Size, > > > > > Style, Paragraph, List and L/R/C/). > > > > > > > > > > !DOCTYPE is unaccessible for modification in any case... > > > > > > > > > > Somebody knows how to solve these questions? Thanks! > > > > > > > > > > > > > I /think/ development of SM Composer stopped a few years ago. It was > > > > continued with the standalone "Nvu" and then "KompoZer", which can > > > > change the DTD, like you ask, according to > > > > > > > > http://en.wikipedia.org/wiki/KompoZer#Standards_compliance > > > > > > > > GW > > Thanks Geoff, > > I learned also that KompoZer now has forked or somehow became BlueGriffon. > I succeeded in changing the DOCTYPE, but the html validator of the W3C group > finds an error in my charset. Apparently, some windows 1252 has creeped into > my files, while I chose ISO 8859-1. Nowhere to find that sticky windows > charset code... > > Guy
Had the exact same issue. But BlueGriffon works awesome, thx! _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
