02-15-2017, 12:05 PM | #31 |
A Hairy Wizard
Posts: 3,094
Karma: 18727053
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
You are quite right! I guess putting that section inside the spoiler wasn't the best choice - it might've caused someone confusion over what I meant. Thanks for the clarification!
|
02-15-2017, 01:09 PM | #32 | |||
Head of lunatic asylum
Posts: 349
Karma: 77620
Join Date: Jun 2012
Location: UTC +1
Device: Tolino Vision 3HD
|
Yes. That were my minimization measures. Your comments were very instructive!
Quote:
Quote:
Code:
- Please do not use empty paragraph tags (<p class="calibre69"> </p>) to create a space between items/paragraphs <p class="space"> is editable via CSS p.space {whatever} - that's an advantage. I will follow you using <p class="space"> for 'non-standard spaces' between paragraphs. I studied code & CSS - I understand everything but this: Code:
p {whatever styling you want your standard (98% of the book) paragraph}
Quote:
Additional question: Is lang="de" superfluous? Code:
<html xmlns="http://www.w3.org/1999/xhtml" lang="de"
Last edited by chaot; 02-15-2017 at 01:24 PM. |
|||
Advert | |
|
02-15-2017, 01:37 PM | #33 | |
A Hairy Wizard
Posts: 3,094
Karma: 18727053
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
Instead of: Code:
<p class="normalpara">This is a normal paragraph.</p>
<p class="normalpara">This is a normal paragraph.</p>
<p class="normalpara">This is a normal paragraph.</p>
<p class="normalpara">This is a normal paragraph.</p>
<p class="red">This is a special paragraph.</p>
<p class="normalpara">This is a normal paragraph.</p>
<p class="normalpara">This is a normal paragraph.</p>
<p class="normalpara">This is a normal paragraph.</p>
CSS:
p.normalpara {margin:0; text-indent:1.2em; font-size:1em}
p.red {color:red}
Code:
<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="red">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>
CSS:
p {margin:0; text-indent:1.2em; font-size:1em}
p.red {color:red}
|
|
02-15-2017, 01:51 PM | #34 |
Head of lunatic asylum
Posts: 349
Karma: 77620
Join Date: Jun 2012
Location: UTC +1
Device: Tolino Vision 3HD
|
|
02-15-2017, 08:09 PM | #35 | |
null operator (he/him)
Posts: 20,565
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
Until the advent of the calibre editor I converted my DOCX's to EPUB via calibre's conversion facility. However when the calibre editor's ability to Import DOCXs was introduced (without CSS flattening that happens in calibre conversions) I switched using it. I tried several other conversion tools (not the online ones, I do too many to consider using them) and found them unsuitable for my purposes. I have used Word Styles religiously since they were first introduced last century - e.g. I never format paragraphs individually. An exception is italicising words or phrases. Consequently I never got boatloads of CSS entries, even when I was calibre converting ex Word RTFs to EPUBs I didn't get a lot of the cruft some complain about. Occasionally I would 'rename' the 'blockN' and 'calibreN' CSS entries to have names similar to the Style names in the Word Template, so 'block4' might become 'first_para'. But more recently I have switched to using the Sigil DOCXImport plugin, this has a facility that allows me to create and store mappings between a Word Template file to an EPUB CSS file. This means I get close to a one for one mapping between Word's Styles and the stylesheet entries with similar names. As a bonus the underlying tool (Mammoth converter) marks italicised text with <em> instead of <i> etc. So how do I avoid the calibre generated CSS entries - mainly by using Word as a word processor rather than a typewriter, and secondly by not using calibre as my final DOCX->EPUB conversion tool. I sometimes do 'interim' conversions to get a feel for what the EPUB will look like, or to do multilingual spell checking, or to look at a Calibre or Sigil report - for this I use calibre's conversion facility, pressing 'C' and 'Shift+V' is too easy. I rarely look at the EPUB code at this stage. BR Last edited by BetterRed; 02-15-2017 at 08:16 PM. Reason: typos |
|
Advert | |
|
02-15-2017, 08:39 PM | #36 | |
Grand Sorcerer
Posts: 27,547
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Glad to see the plugin is proving to be useful. |
|
02-20-2017, 11:44 AM | #37 | ||
Head of lunatic asylum
Posts: 349
Karma: 77620
Join Date: Jun 2012
Location: UTC +1
Device: Tolino Vision 3HD
|
Quote:
In order to get my CSS clearer I name them somehow 'appropriately', e.g. <p class="no_h4_ital"> for something what looks like header, but doesn't function as one. <p class="no_h4_ital"> Quote:
Some funny details! Spoiler:
Last edited by chaot; 02-20-2017 at 12:53 PM. Reason: semantically→appropriately |
||
02-20-2017, 12:10 PM | #38 |
Resident Curmudgeon
Posts: 73,943
Karma: 128903250
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
<em> and <i> are the same thing. Both italicize the text.
|
02-20-2017, 12:17 PM | #39 |
Head of lunatic asylum
Posts: 349
Karma: 77620
Join Date: Jun 2012
Location: UTC +1
Device: Tolino Vision 3HD
|
The result looks the same, both italic; semantically they are different.
Last edited by chaot; 02-21-2017 at 12:10 PM. Reason: ,→; |
02-20-2017, 12:32 PM | #40 |
Resident Curmudgeon
Posts: 73,943
Karma: 128903250
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
There is NO difference between <i> & <em> and <b> & <strong>. I can change what each of them does via CSS. I can change <i> so it look bold and I can change <b> so it looks italicized. <em> and <strong> can also be modified via CSS. Both pairs have the same default. So really, the pairs are no different.
|
02-20-2017, 01:39 PM | #41 | |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
Quote:
Dale |
|
02-20-2017, 05:07 PM | #42 | ||
null operator (he/him)
Posts: 20,565
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
At its core Writer is reverse engineered Word '9?, many features like Templates and Styles are functionally similar to Word, an exception is macro's, Word is limited to VBA, Writer gives greater choice - e.g Python. I use LO Writer on the occasional ODT, normally I save as DOCX from Writer and work with that in Word. But sometimes I have to work with the ODT directly, but I save it as DOCX for the purposes of creating an EPUB via Sigil's DOCXImport PI. Quote:
Code:
# Uncomment these next two if you don't like the default <em> and <strong> #b => b #i => i BR |
||
02-21-2017, 05:09 AM | #43 | ||
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
The article below goes into more detail with some examples: http://html5doctor.com/i-b-em-strong-element/ You may also want to read W3C's page, "Using <b> and <i> elements": https://www.w3.org/International/que...a-b-and-i-tags Quote:
Also, there could potentially be differences in Text-to-Speech engines. <em> might be spoken with more emphasis on the words, while <i> could be spoken normally. Last edited by Tex2002ans; 02-21-2017 at 05:12 AM. |
||
02-21-2017, 07:08 AM | #44 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
In fact I'd go so far as to say that all the TTS/Voice combos I've ever tried (Windows and Android) appear to ignore all i/em/b/strong tags completely. I wish they did aurally emphasise italic and/or bold text, but they don't. Maybe one day ... |
|
02-21-2017, 11:52 AM | #45 |
null operator (he/him)
Posts: 20,565
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
@jackie_w - I think I've sampled most 'voices' from Acapela etc and to me they all sound like Milton Keynes looks - pleasantly boring. TTS seems to have barely progressed since I used DecTalk boxes in call centre voice response units in the 1980's, the sound quality is a lot better but the rest...
The problem is that the intonation one might use on italicised text in an ironical statement would be different to that one might use in an adversarial challenge. TTS needs to do deep linguistic analysis (syntax + semantics + idiom, cant, figurative speech, metaphor etc) of the text and get the right base intonation, before it has any chance of using an appropriate tone for italics. If that were available then the studios wouldn't be using regular actors to do the voice overs for animated movies. And radio broadcasters could get rid of their newsreaders. If the BBC used what's available now, we wouldn't have to listen to the sneers that drip from their newsreaders tongues whenever they have to mention people of whom they don't approve. BR Last edited by BetterRed; 02-21-2017 at 11:55 AM. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
xpath to insert chapter breaks - but chapter name cut off ? | Rob557 | Conversion | 2 | 03-06-2014 06:59 AM |
Troubleshooting Kindle K3 (keyboard) losing chapter head spacing. | timecheck00 | Amazon Kindle | 5 | 11-30-2012 08:57 PM |
Pocket eDGe and Full-size eDGe: Head to Head Comparison | alefor | enTourage Archive | 28 | 12-01-2010 07:44 PM |
Chapter Head Text Over Image | theducks | ePub | 10 | 09-03-2010 03:32 PM |
Video Head to Head of Kindle and Reader | Kingston | Which one should I buy? | 30 | 01-24-2008 08:03 PM |