style link type=css

[AlanHK]

I imported a KF8 into Sigil using the KindleImport plugin to make an epub2.

This looked OK, but when I started checking out styles, clicking on any style in the code window to "Go to link or style" gave the message
"No CSS style named ".Center" found, or stylesheet not linked".

But the style clearly was being applied in the preview. The inspector showed the relevant line in the style file.
Epubcheck showed no errors.

Eventually I looked at the Book Browser list and clicked "Link stylesheets", to see no stylesheet was linked. Though it was, and the styles were working.

Used the link popup to add the stylesheet and saw that the new link was

<link href="../Styles/style.css" type="text/css" rel="stylesheet"/>

the original link was

<link rel="stylesheet" href="../Styles/style.css"/>

i.e., the original link had no type="text/css".

So either Sigil should recognise this as a valid style link, or add the "type" code on opening or with "mend code".

[KevinH]

In xhtml for epub2, type is required according to the spec.

For html5, type is not required according to the html living spec.

Not sure about xhtml version of html5 for epub3.

Sigil always assumes it should be used and when linking in a stylesheet, it will add it.

[AlanHK]

Originally Posted by KevinH

In xhtml for epub2, type is required according to the spec.

Epubcheck didn't mind.

Originally Posted by KevinH

Sigil always assumes it should be used and when linking in a stylesheet, it will add it.

The problems arise when it opens a file without the type. It can't work with it properly, but doesn't raise any flag that there is a problem.

[BeckyEbook]

I really understand this problem and encounter it relatively often, so for me, finding a working solution was crucial.

There was already a discussion on this topic:
https://www.mobileread.com/forums/sh...d.php?t=229308

The problem can be solved in several ways.
a) As suggested by @KevinH – create a validation plugin that will check and report on this issue.

b) Patch for the sanitychecker built into Sigil (\python3lib\sanitycheck.py), which will report the problem when checking (F7).

Spoiler:

Insert before comment "# other special cases"

        # BECKY START
        if tname == "link":
            if "rel=\"stylesheet\"" in s:
                if "type=\"text/css\"" not in s:
                    error_msg = 'Missing type="text/css" in css link tag'
                    self.errors.append((self.tag_start[0], self.tag_start[1], error_msg))
                    self.has_error = True
                    return None, None, None
        # BECKY END

c) Quick-and-dirty patch to clean the code (Mend). Of course, this only applies to those two people who will want to build their own version of Sigil
I know that this is not a perfect solution, but it works fine for my needs.

Spoiler:

File: \src\BookManipulation\CleanSource.cpp
Insert after line 208, before return newsource;

    // Becky START
    QString css_before = " rel=\"stylesheet\"";
    QString css_after  = " type=\"text/css\" rel=\"stylesheet\"";
    newsource.replace(css_before, css_after);
    // Becky END

Personally, I use options b and c.

[DiapDealer]

Are you guys running into this in a lot of epubs found out in the wild, or this mainly limited to epubs being generated by KindleUnpack (which includes the KindleImport plugin)?

[KevinH]

If only from KindleImport we can fix it in KindleUnpack. If you are seeing this in the wild, I can try to update GumboInterface.cpp to make sure type is properly added to link that have rel="stylesheet" so that Mend will work.

[KevinH]

I have updated GumboInterface.cpp both Mend and Mend and Prettify to now "fix" these cases by adding in the type="text/css" if missing. That way it is correct for html4, epub2, html5, and epub3.

I have just pushed this to master.

[KevinH]

I also added a variant of BeckyEbook's sanitycheck.py patch so it can be caught easily.

Thank you BeckyEbook!

[BeckyEbook]

To clarify: I really see a lot of such files in the wild. If it were rare, I wouldn't bother with it.

I just built the master version and I'm happy. So I can say THANK YOU!

[KevinH]

@BeckyEbook
If you have any additional Sigil/PageEdit patches that you typically apply when you build your own tree that might be of use to others, please post them and we will consider integrating them into master for the next release.

Thanks!

KevinH