MobileRead Forums - Next Version

MobileRead Forums (https://www.mobileread.com/forums/index.php)

- Sigil (https://www.mobileread.com/forums/forumdisplay.php?f=203)

- - Next Version (https://www.mobileread.com/forums/showthread.php?t=333144)

Hi KevinH

Kovid had said he hopes to release the next copy of Calibre this month. ( I will give anyone, who complains about Kovid, if this slips a hard time. Things happen)

Is there likely to be a new version of Sigil before Xmas, to go with the new version of Calibre?

I am a heavy user of both and it would nice to have a new version of each.

Probably but no guarantees.

Quote:

Originally Posted by KevinH (Post 4034549)

Probably but no guarantees.

Thank you.

I definitely was NOT asking for a guarantee. Things happen.

I have the greatest respect for the work you and DiapDealer do in maintaining and developing Sigil and do NOT like it when some posters take it for granted or think they are entitled to tell you the line of development you must take.

I'm sorry.
I've been sick and couldn't visit this forum.
You're probably angry with me.

Hi KevinH

I have proposed an example.
Have you thought about a new version for your team?

I'll help you.
Please give me a little more time as I prepare.

in epub3
I don't know in epub2

About font-size and font-color
Added as below to CSS
(Size and color are examples)

Code:

 /* font-size */

.font-0em50 { font-size:  0.50em; }

.font-0em60 { font-size:  0.60em; }

.font-0em70 { font-size:  0.70em; }

.font-0em75 { font-size:  0.75em; }

.font-0em80 { font-size:  0.80em; }

.font-0em85 { font-size:  0.85em; }

.font-0em90 { font-size:  0.90em; }

.font-1em   { font-size:  1.00em; }

.font-1em10 { font-size:  1.10em; }

.font-1em15 { font-size:  1.15em; }

.font-1em20 { font-size:  1.20em; }

.font-1em30 { font-size:  1.30em; }

.font-1em40 { font-size:  1.40em; }

.font-1em50 { font-size:  1.50em; }

.font-1em60 { font-size:  1.60em; }

.font-1em70 { font-size:  1.70em; }

.font-1em80 { font-size:  1.80em; }

.font-1em90 { font-size:  1.90em; }

.font-2em   { font-size:  2.00em; }

.font-2em50 { font-size:  2.50em; }

.font-3em   { font-size:  3.00em; }



/* font-color*/

.color-black       { color: #000000; }

.color-dimgray     { color: #696969; }

.color-gray        { color: #808080; }

.color-darkgray    { color: #a9a9a9; }

.color-silver      { color: #c0c0c0; }

.color-gainsboro   { color: #dcdcdc; }

.color-white       { color: #ffffff; }

.color-transparent { color: transparent; }



.color-red         { color: #ff0000; }

.color-blue        { color: #0000ff; }

.color-cyan        { color: #00ffff; }

.color-magenta     { color: #ff00ff; }

.color-orangered   { color: #ff4500; }

.color-yellow   { color: #ffff00; }

.color-green   { color: #008000; }

.color-purple   { color: #800080; }

When decorating

Code:

<span class="font-1em20">text</span>

<span class="color-red">text</span>

Reader may not support font-color.
iBooks can be displayed. (I haven't checked all the colors.)

Since epub uses the same standard as the Web, I think the history of Web development will be helpful.

If you have time, support it please.

That looks like CSS that you can add to your personal CSS template - no need to add it to Sigil.

I, on the other hand, would never create a class simply for color or font-size. I adhere to the Keep It Simple Silly methodology and would apply color/size only to a specific class.

Code:

CSS:

p             {font-size:1em; color:black} /*not recommended to put a standardized font-size or color here - just an example*/

p.SpecialPara {font-size:1.8em; color:red}



HTML:

<p>This is a normal paragraph.</p>

<p>This is a normal paragraph.</p>

<p>This is a normal paragraph.</p>

<p>This is a normal paragraph.</p>

<p class="SpecialPara">This is a special paragraph.</p>

<p>This is a normal paragraph.</p>

<p>This is a normal paragraph.</p>

<p>This is a normal paragraph.</p>

instead of:

Code:

HTML:

<p class="font-1em color-black">This is a normal paragraph.</p>

<p class="font-1em color-black">This is a normal paragraph.</p>

<p class="font-1em color-black">This is a normal paragraph.</p>

<p class="font-1em color-black">This is a normal paragraph.</p>

<p class="font-1em80 color-red">This is a special paragraph.</p>

<p class="font-1em color-black">This is a normal paragraph.</p>

<p class="font-1em color-black">This is a normal paragraph.</p>

<p class="font-1em color-black">This is a normal paragraph.</p>



CSS:

 /* font-size */

.font-0em50 { font-size:  0.50em; }

.font-0em60 { font-size:  0.60em; }

.font-0em70 { font-size:  0.70em; }

.font-0em75 { font-size:  0.75em; }

.font-0em80 { font-size:  0.80em; }

.font-0em85 { font-size:  0.85em; }

.font-0em90 { font-size:  0.90em; }

.font-1em   { font-size:  1.00em; }

.font-1em10 { font-size:  1.10em; }

.font-1em15 { font-size:  1.15em; }

.font-1em20 { font-size:  1.20em; }

.font-1em30 { font-size:  1.30em; }

.font-1em40 { font-size:  1.40em; }

.font-1em50 { font-size:  1.50em; }

.font-1em60 { font-size:  1.60em; }

.font-1em70 { font-size:  1.70em; }

.font-1em80 { font-size:  1.80em; }

.font-1em90 { font-size:  1.90em; }

.font-2em   { font-size:  2.00em; }

.font-2em50 { font-size:  2.50em; }

.font-3em   { font-size:  3.00em; }



/* font-color*/

.color-black       { color: #000000; }

.color-dimgray     { color: #696969; }

.color-gray        { color: #808080; }

.color-darkgray    { color: #a9a9a9; }

.color-silver      { color: #c0c0c0; }

.color-gainsboro   { color: #dcdcdc; }

.color-white       { color: #ffffff; }

.color-transparent { color: transparent; }



.color-red         { color: #ff0000; }

.color-blue        { color: #0000ff; }

.color-cyan        { color: #00ffff; }

.color-magenta     { color: #ff00ff; }

.color-orangered   { color: #ff4500; }

.color-yellow   { color: #ffff00; }

.color-green   { color: #008000; }

.color-purple   { color: #800080; }

By NOT giving a class to every paragraph, and only giving one to "special" paragraphs, you keep your code clean. It's MUCH easier to edit when it is clean...plus, if I wanted to change the style of the basic paragraph I only need to change it once, in the CSS, and not have to update the class on EVERY paragraph.

In your example you are using <span> tags, but the concept still applies: You don't need to have a list of all the possible font-sizes/colors in your CSS...just add the ones you need to a specific class for that specific <span>.

Cheers,

No, Sigil is NOT going to include a set of "standard" css just to make things easier for people who do not know or want to learn css.

Epub developers can find css examples many many places on the web and use whatever css they want. And Sigil's clips bar can make adding/using that css quite easy.

Quote:

Originally Posted by slightfever (Post 4034878)

Since epub uses the same standard as the Web, I think the history of Web development will be helpful.

You might find my EpubTemplate Sigil plugin helpful. Simply copy your favorite .css file in the plugin resources folder and select Plugins > Edit > EpubTemplate whenever you want to add it to an .epub file.

Nice plugin! May I add it to the Sigil plugin index from that link or would you rather create its own plugin thread?

Thanks!

Quote:

Originally Posted by Doitsu (Post 4034980)

Quote:

Originally Posted by Thasaidon (Post 4034498)

Keep in mind that we're probably not talking about a jump from version 1.x to 2.0 this year. Calibre's jump to version 5 (and Python3) is a much larger leap than (I think) we're planning for the immediate future. We may very well see minor version increments in the 1.x series before years-end, though.

Quote:

Originally Posted by KevinH (Post 4034981)

Nice plugin! May I add it to the Sigil plugin index from that link or would you rather create its own plugin thread?

IMHO, it's a throwaway plugin. I'll double-check the code to make sure that it works with epubs with non-standard structures and create a separate thread for it.

Sounds good!

Thank you.

Quote:

Originally Posted by Doitsu (Post 4035010)

IMHO, it's a throwaway plugin. I'll double-check the code to make sure that it works with epubs with non-standard structures and create a separate thread for it.

Quote:

Originally Posted by DiapDealer (Post 4035001)

Keep in mind that we're probably not talking about a jump from version 1.x to 2.0 this year. Calibre's jump to version 5 (and Python3) is a much larger leap than (I think) we're planning for the immediate future. We may very well see minor version increments in the 1.x series before years-end, though.

As evidenced by the 400+ replies to the Beta Test thread :D https://www.mobileread.com/forums/pi...pictureid=6468

BR

Luckily, Sigil has been Python 3 based from the very beginning and Sigil does not have to worry about database/library or reader based functionality either as Calibre does.

So our plan for Sigil is for incremental improvements since we just recently reached 1.0 after many many years. For example, the biggest new features in our next release will be support for multiple language spell checking with some minor refinements in Toolbars and bug fixes.

Quote:

Originally Posted by BetterRed (Post 4035117)

As evidenced by the 400+ replies to the Beta Test thread :D https://www.mobileread.com/forums/pi...pictureid=6468

BR

I've been following along. ;)

It's not version 5, but I've been using the Python 3 version of Calibre on Arch for a while now.