Hi Clayton, I just changed skins to Monobook and now things look different in the preview (the original page still looks fine). The nowiki tag appears to be ignored in the preview. I tried the Simple skin and it does the same thing.
Regards, Ivan. On Tue, Jul 21, 2009 at 10:02 PM, Clayton<ccorn...@openoffice.org> wrote: > Taking this back to the list so others can possibly contribute. > >> A screen-cap wouldn't be useful, but the attached file might. I saved >> the Preview, HTML-only, out of Ff. > > That actually is helpful.. sort of. I compared your saved html file > with the same Preview on my side... > > >> <a name="Paragraph:_.3Cp.3E_..._.3C.2Fp.3E"></a><h3> <span >> class="mw-headline"> Paragraph: <p> ... </p> </span></h3> > > This exact section on my side (after saving locally) looks like this: > > <a name="Paragraph:_.3Cp.3E_..._.3C.2Fp.3E"></a><h3> <span > class="mw-headline"> Paragraph: <p> ... </p> </span></h3> > > Notice that the <p> tags are rendered *correctly* in my Preview. The > <p> tags in this heading are wrapped by a <nowiki> tag, so should NOT be > rendered as <p> tags... but for some reason in your case, the <nowiki> > tag seems to be ignored. When the tag is ignored, you would see exactly > what you describe - a broken H3. > > I'm also seeing a lot of other differences in the HTML between my copy > and yours. > > Example: > TJ's preview > ----------- > <tbody><tr> > <td valign="top"><a > href="http://wiki.services.openoffice.org/wiki/Image:Documentation_caution.png"; > class="image" title="Image:documentation_caution.png"><img > alt="Image:documentation_caution.png" > src="index.php_files/Documentation_caution.png" border="0" height="40" > width="40"></a></td><td>Do > not use <br/> or CR/LF for marking paragraphs. CR and LF are > ignored, except within <pre>...</pre> and > <listing>...</listing> areas. The <br/> tag is only > for rare cases of explicit linebreaks. > <pre> /** does this and that. > > This sentence should start with a "<p>". If not, > it still belongs to the previous paragraph! > > This still belongs to the first paragraph. <br/> > As this sentence is as well! > */ > </pre> > <p>Consider using <tt>&lt;</tt> for < and <tt>&gt;</tt> for > >, as shown in the example above. > </p> > ----------- > > My preview: > ----------- > <tr> > <td valign="top"><a href="/wiki/Image:Documentation_caution.png" > class="image" title="Image:documentation_caution.png"><img > alt="Image:documentation_caution.png" > src="/w/images/e/ef/Documentation_caution.png" width="40" height="40" > border="0" /></a></td><td>Do not use <br/> or CR/LF for marking > paragraphs. CR and LF are ignored, except within <pre>...</pre> and > <listing>...</listing> areas. The <br/> tag is only for rare cases of > explicit linebreaks. > <pre> > /** does this and that. > > This sentence should start with a "<p>". If not, > it still belongs to the previous paragraph! > > This still belongs to the first paragraph. <br/> > As this sentence is as well! > */ > </pre> > <p>Consider using <tt><</tt> for < and <tt>></tt> for >, as shown > in the example above. > </p> > ----------- > > Note the differences... missing <tbody> on my preview... TJ's uses a lot > of < and > notation where my preview uses < and >. > > Anyone else have a clue why one user would see one preview and the rest > of us another? A char set? A configuration setting? > > C. > -- > Clayton Cornell ccorn...@openoffice.org > OpenOffice.org Documentation Project co-lead > StarOffice - Sun Microsystems, Inc. - Hamburg, Germany > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@website.openoffice.org > For additional commands, e-mail: dev-h...@website.openoffice.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@website.openoffice.org For additional commands, e-mail: dev-h...@website.openoffice.org
![http://wiki.services.openoffice.org/wiki/Image:Documentation_caution.png"](http://wiki.services.openoffice.org/wiki/Image:Documentation_caution.png"){kind=link}