Comments In XHTML?

[Fabe]

Can I add comments – /* Comment here.*/ – in my XHTML files?
No problem in the CSS files.
Thanks - Fabe

[KevinH]

Hi,

In xhtml the correct syntax for a comment is:

<!-- This comment is invisible to visitors. -->

[theducks]

Originally Posted by Fabe

Can I add comments – /* Comment here.*/ – in my XHTML files?
No problem in the CSS files.
Thanks - Fabe

Some Comments (above style) in the CSS *Do* cause problems on my Astak PEz (Astak,Lbook,BeBook FW)

They work OK in Calibre, Sigil and EPUBReader , but my reader ignores the Style attributes when present.

I have not 100% nailed down the conditions where they cause the problem because it does not always happen
Removing the Commented line, cures the problem (Sigil's editor and Notepad++ colour them as comments )

[Fabe]

Originally Posted by KevinH

In xhtml the correct syntax for a comment is:
<!-- This comment is invisible to visitors. -->

Of course! Computer languages are like remembering which guest is vegetarian and which is kosher.
Thanks for reminding me. - Fabe

[Hitch]

Originally Posted by theducks

Some Comments (above style) in the CSS *Do* cause problems on my Astak PEz (Astak,Lbook,BeBook FW)

They work OK in Calibre, Sigil and EPUBReader , but my reader ignores the Style attributes when present.

I have not 100% nailed down the conditions where they cause the problem because it does not always happen
Removing the Commented line, cures the problem (Sigil's editor and Notepad++ colour them as comments )

Crap. I use that all the time in my "house" CSS. Works in iPad, iPhone, iBooks; Kindle (converted, obviously, from Sigil-generated or hand-generated ePUB); Nook; Kobo.

Hitch

[theducks]

Originally Posted by Hitch

Crap. I use that all the time in my "house" CSS. Works in iPad, iPhone, iBooks; Kindle (converted, obviously, from Sigil-generated or hand-generated ePUB); Nook; Kobo.

Hitch

You summed it up.

I was documenting others CSS I was tweaking (there are some extremely messy (style sheeted) books out there).
They style every thing. When are they gonna learn. Set A basic P style, the style the EXCEPTIONS, inheriting the basics
The style sheet ends up a few dozen lines and the book loads FAST.

The good thing, is not all comments mess it up, so TEST on a few devices, Not made for the Gorillas in the industry

[Hitch]

Originally Posted by theducks

You summed it up.

I was documenting others CSS I was tweaking (there are some extremely messy (style sheeted) books out there).
They style every thing. When are they gonna learn. Set A basic P style, the style the EXCEPTIONS, inheriting the basics
The style sheet ends up a few dozen lines and the book loads FAST.

The good thing, is not all comments mess it up, so TEST on a few devices, Not made for the Gorillas in the industry

Ducky:

I only have about 30-40 lines of CSS; but I do use commenting to keep it easy to read. One main p style; one for non-indented paras; headers; images. That's pretty much it, but my fu is pretty ePUB-standard (yeah, yeah, I know those video tags aren't ePUB 1.05 compliant, but, gimme a break! Blame Apple.); it's a little unfair to expect those of us slogging along making a living at this to have to code every book for EVERY reader, particularly if they're not industry-standard-compliant, y'know? (And you'll pry those dropcaps from my cold dead hands...)

It's bad enough I have to juggle around svg's and xpgts for ADE with everything else; having to de-comment my CSS is just pushing a chain up a hill. Hell, I struggle with that crap as it IS; if I remove the comments, I'm probably hosed.

Hitch