Adding a stylesheet in Sigil

[holdit]

Just want to make sure I get this right, I have a word doc which is made using two separate fonts. I already converted the .doc to html, opened in Sigil and realize that in order for the font to appear it needs to be added in the font folder and then create a separate css page to layout the tags.

But in the body of the html inside Sigil I see the the original definitions so how do I go about adding a css page which will have the font display in the tags irs supposed to?

Do I leave the orginal text/css which is in the body of the html or remove it.

if I remove I know I would have to re style the whole document.

Any help?

HI

[Doitsu]

Originally Posted by holdit

Do I leave the orginal text/css which is in the body of the html or remove it.

You don't need to add a separate stylesheet, but most book designers find a separate stylesheet easier to manage.

Adding a stylesheet is relatively easy. Right-click the Styles folder in the Book Browser and select Add blank stylesheet. Then select all styles in the .html file(s) and cut & paste them into the blank stylesheet. Then select your .html file(s) in the Book Browser, right-click them, select Link StyleSheets and tick the check box before your stylesheet.

Font embedding is explained in the online help.

[holdit]

OK so if I decided NOT to add a separate stylesheet, how do I go about this? Do I just embed the font in the folder in Sigil and make sure the spelling is correct?

here is an excerpt of the sales from the html doc


<div class="WordSection1">
<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Times New Roman&quot;">&nbsp;</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Times New Roman&quot;">&nbsp;</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Times New Roman&quot;">&nbsp;</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:64.0pt;font-family:&quot;Comic Sans MS&quot;">Math Problem Solving Menus</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Comic Sans MS&quot;">&nbsp;</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Comic Sans MS&quot;">&nbsp;</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Comic Sans MS&quot;">&nbsp;</span></p>

<p align="center" class="FreeForm" style="text-align:center"><span style="font-size:18.0pt;font-family:&quot;Comic Sans MS&quot;">&nbsp;</span></p>

[theducks]

Those are Licensed fonts. Embedding is expensive.
Since the Font Family names are pretty common, you could depend on the reading system to supply them

All yo may need on the stylesheet, if you choose to a similar looking Open Sourced font is the @font lines declaration for each family that links the Family name to the font file you are using.



I keep the following 'CSS clip'

@font-face {
font-family: "\1";
font-style: normal;
font-weight: normal;
src:url(../Fonts/\1.ttf);
}

Replace the 2@ '\1' with the appropriate names

You could leave the family name as 'Times New Roman' and link a different (Free) file to SUBSTITUTE that:

@font-face {
font-family: "Times New Roman";
font-style: normal;
font-weight: normal;
src:url(../Fonts/liberation.ttf);
} << Just an example

[Toxaris]

I would seriously clean that Word HTML mess up, this will cause issues for you in the end. Even filtered HTML is still full of reduntant and unnecessary code that will cause unexpected things in readers like fonts not scalable and other things.

[holdit]

OK whats the best way to clean up the un needed code that word leaves?

[eschwartz]

Try using the Atlantis Word Processor for any future writing which needs to be converted to EPUB, it's supposed to be VERY clean. It should also do a good job of cleaning up the code if you open an MSWord doc and resave with Atlantis -- how well this compares to MSWord's filtered html setting I haven't got a clue, because I basically know this from Google+MobileRead lurking, but it could be worth a try.

Or try using Open/LibreOffice, which tends to output cleaner code to begin with, and has the Writer2ePub extension, although I believe this achieves its wonders by ignoring tag soup and assuming there isn't fancy weird stuff in the document. Again, try opening, in LibreOffice this time, saving as a native .odt and then using the export tool.

[mrmikel]

If you have a newer version of Word, you can use the tools listed under Toxaris' messages. They are Word macros, so he can help you out if you run into a problem. But they have been used extensively so I would expect they would do you well.

AWP works well and leaves you working in a word processor until the moment you export to epub. It takes a bit of getting used to but the learning curve is not bad.

Unless you use the Comic Sans a lot, you might get by by making images of the items for which you use the Comic Sans. That way you don't get stuck with the vagaries of font embedding, which is something of a world unto itself.

[Notjohn]

Just to point out: any file with the extension *.css in the folder you're working in will be incorporated into the epub on the fly. One doesn't have to do anything to make that happen.

I clean up my Word 2000 docs by running them through word2cleanhtml.com online, adding a template and style sheet (see http://notjohnkdp.blogspot.com for examples).

[DiapDealer]

Originally Posted by Notjohn

Just to point out: any file with the extension *.css in the folder you're working in will be incorporated into the epub on the fly. One doesn't have to do anything to make that happen.

I don't follow.

[theducks]

Huh!

I can create all the stylesheets in the world
and none of them will be used until I make a Link entry in the HTML file

The easy way: Rightclick on the file(s) in the book browser: Link stylesheets (select)

Note: any previous linked sheets references will be removed. process exceptions seperatly

[DiapDealer]

Even if you're talking about importing or opening an (x)html file with Sigil, no css files in the same folder will be pulled in along with it if they're not properly linked in the file first.

(and in that case, any css file that is properly linked in the (x)html file will be incorporated into the epub--regardless of what folder it's in, but it all starts with proper linking)