How to combine chapter titles and subtitles

[JSWolf]

Originally Posted by Quoth

You like HTML 3?

HTML 3 has nothing to do with this.

[Quoth]

Wanting no CSS is nostalgia for HTML 3.
Wanting bare <p> and <h2> is prehistoric for people typing in Notepad in 1993.

[JSWolf]

Originally Posted by Quoth

Wanting no CSS is nostalgia for HTML 3.
Wanting bare <p> and <h2> is prehistoric for people typing in Notepad in 1993.

It's not prehistoric. It's better code to not have classes when you don't need them. Then way to do eBook sis to keep it simple. And it's as simple as you can get to use <p> and <h2> with no classes where possible. CSS is where they are configured as you need. You use classes when you want to change <p> and/or <h2>.

You get simpler code, better looking code, and more accurate ADE page numbers.

[theducks]

Originally Posted by Beathan

For regex I used:

F: [a-zA-Z]-[a-zA-Z]
R:
but can not manage the Replace string

( ) are the capture zones, so surround each zone with ( ) like did earlier (you can include literals as I did)

replace:
\1 \2
\1 place the first zone
\2 place the second (again, you can include literals actual text)
\2 \1 flips the two captures

[theducks]

Originally Posted by Quoth

Wanting no CSS is nostalgia for HTML 3.
Wanting bare <p> and <h2> is prehistoric for people typing in Notepad in 1993.

I am with you. This is extreme minimalist coding.

I have no issue with using p class= for minor Exceptions:

<p> for general body text would be acceptable to me, because 90% of a book is just the same paragraph style.

But why? <p class='indent'> makes it obvious and the performance hit on a modern reader device is not noticeable.

I find EPUB3 coding really annoying when having to back trace thru 5 levels to find why a stupid title page does not fit on a single screen on my Libra2 (1264 x 1680? ). FWIW I adjust so it also works on my Aura 2 and it looks just fine.

[icallaci]

Originally Posted by theducks

I am with you. This is extreme minimalist coding.

...

But why? <p class='indent'> makes it obvious and the performance hit on a modern reader device is not noticeable.

I find EPUB3 coding really annoying when having to back trace thru 5 levels to find why a stupid title page does not fit on a single screen on my Libra2 (1264 x 1680? ). FWIW I adjust so it also works on my Aura 2 and it looks just fine.

OMG, this is exactly how I feel. I prefer my classes to spell out exactly what each one is doing without requiring me to work my way through multiple previous levels to discover what has been overridden. Ebooks are simple. It's not that hard to define a class that tells you everything you need to know about what it does. (By the way, has anyone noticed that some ebooks published by some college presses tend to have overly complicated CSS? I think they hire students who want to show off, lol.)

[BetterRed]

Originally Posted by icallaci

OMG, this is exactly how I feel. I prefer my classes to spell out exactly what each one is doing without requiring me to work my way through multiple previous levels to discover what has been overridden. Ebooks are simple. It's not that hard to define a class that tells you everything you need to know about what it does. (By the way, has anyone noticed that some ebooks published by some college presses tend to have overly complicated CSS? I think they hire students who want to show off, lol.)

I use the Live CSS panel to make sense of complex CSS… afaik that's the reason it exists.

BR

[icallaci]

Originally Posted by BetterRed

I use the Live CSS panel to make sense of complex CSS… afaik that's the reason it exists.

BR

Thanks, I hadn't known about Live CSS. I'll take a look.

[JSWolf]

I prefer my CSS and my HTML to be as simple as possible. I know what <p> does as it's for most paragraphs. Also, a lot of eBooks have classes that do not say what they do. They make no sense in that respect.

I also know that if I have a chapter heading and it is using <h2>, I know what it does. I know what a <blockquote> does as I've coded it as well.

[Quoth]

If you want simple and reliable and repeatable rendering, use <p class="myquote"> and never blockquote (though fans of semantics in HTML will disagree, but then you don't believe in <em> and <strong>.).

Also you might want h2 for other headings and not just chapters.

There is a good reason CSS was invented. We didn't always have it.

[theducks]

And Unix was not the only place 2-3 letters were used for commands.

Some BPH get it, that there is no need for extremely verbose class names

FP, CN, TX, CT, FM,... They add a digit for variants

I have no problem guessing what those are used for.

For those tiny cases, The editor has the Jump-to CSS feature where I can READ the attributes.

[JSWolf]

Originally Posted by Quoth

If you want simple and reliable and repeatable rendering, use <p class="myquote"> and never blockquote (though fans of semantics in HTML will disagree, but then you don't believe in <em> and <strong>.).

Also you might want h2 for other headings and not just chapters.

There is a good reason CSS was invented. We didn't always have it.

If you want <h2> for something other then chapter headings, that's where a class comes in to play.

As for block text, <blockquote> is best. It's simplifies the code.

I'm not a fan of excess code or code that tried to duplicate something else but in a more complex way.