/*<![CDATA[*/ - Strange Comment

[Fabe]

I manually add some BOLDS in Book View and Sigil adds comments: /*<![CDATA[*/ & /*]]>*/ in Code View. It goes like this:

ORIGINAL

<style type="text/css">
p.sgc-1 {font-weight: bold;}
</style>

CHANGES TO

<style type="text/css">
/*<![CDATA[*/
p.sgc-1 {font-weight: bold;}
/*]]>*/
</style>

No harm, no foul, but I think they look extraneous and I want to eliminate them. A simple find & replace (with nothing) was unsuccessful. Can I eliminate them and if so, how?

I am running Sigil version 0.2.4 Thanks. - Fabe

[DaleDe]

They may look strange but they have their use. Google CDATA.

[Fabe]

Originally Posted by DaleDe

They may look strange but they have their use. Google CDATA.

Can you elaborate?

[KevinH]

Originally Posted by Fabe

Can you elaborate?

Just "google CDATA" which explains what it is for and why it may be needed. Here, for example, is a wikipedia article on it.

http://en.wikipedia.org/wiki/CDATA

[Fabe]

Thanks KevinH. Based on information in the link you provided, I see no use whatsoever for this extraneous code to be in my epub. - Fabe

[DiapDealer]

I see no use whatsoever for this extraneous code to be in my epub.

Maybe not, but it certainly can't hurt. And depending on what device (or application) a reader opens your epub with... it may make all the difference in readability.

While wrapping inline-css statements may happen less often than inline-javascript, it's still fairly common practice.

Better safe than sorry, I say.

[Fabe]

Originally Posted by DiapDealer

... depending on what device (or application) a reader opens your epub with... it may make all the difference in readability. ... Better safe than sorry, I say.

DiaoDealer, your response begs the question, Why?

In the ePub where I was adding in-line bolds, I worked a little harder on my pre-epub set-up and was able to create <p class"bold"> for 95% of the phrases where I needed them. I can manually add the class phrase for the rest and believe with a little more insight I will be able to capture those too.

So, my need to do in-lines is gone, I will not worry over extraneous comment lines. - Fabe

[DiapDealer]

Originally Posted by Fabe

DiaoDealer, your response begs the question, Why?

Simply put: you can't possibly foresee how every single epub reader (device or app) will choose to process in-line css statements. And I choose to believe that the Sigil developers didn't just toss that feature in willy-nilly... they must have seen a need.

This of course is all moot if you're planning on eliminating in-line css statements in your epub anyway.

[Fabe]

Originally Posted by DiapDealer

Simply put: you can't possibly foresee how every single epub reader (device or app) will choose to process in-line css statements. And I choose to believe that the Sigil developers didn't just toss that feature in willy-nilly... they must have seen a need.

This of course is all moot if you're planning on eliminating in-line css statements in your epub anyway.

Point taken, but I'll admit, I only write ePubs for 4 readers: iPad, Kindle, Nook and Kobo.

As to " the Sigil developers didn't just toss that feature in willy-nilly..." I think Valloric has a sense of humor that runs to the willy-nilly. :-) - Fabe