Quote:
Originally Posted by Jellby
Ah, I see... so it needs some punctuation before the closing quote. I'll see how that works for my next project.
|
Well, without punctuation there isn't anything to work with. You would have to build a dictionary of apostrophable words and use that.
Quote:
Originally Posted by rogue_ronin
I actually use both <a name="chapter_ChapterNumber"> and <h3 id="chapter_ChapterNumber" class="chapter" align="center"> in my files to mark a chapter. A combination of overkill and ignorance. |
Not only an overkill, you are actually producing invalid files - names/ids should be unique.
Quote:
|
Providing the CSS with the markup allows someone to simply change the CSS file to suit their needs. Awesome. Currently, without a new reader, I can't think of a way to write the code in such a way as to ensure forward-compatability.
|
You could use an intermediate converter for that. Calibre, for example, tries to convert CSS into (bastardized) HTML when building a LRF output, because LRF only supports tiny subset of CSS.
Quote:
|
And you've inspired me to consider rewriting my macros to include such things as <em class="psionic">. Which just reads cool.
|
It not only looks cool, you can also use a different font for psionics and different font for other emphasisation.
Quote:
|
As for <span>, I'm still a little confused; I get the <div> styles thing
|
SPAN is pretty much the same thing as DIV, except that DIV works with blocks (creates a newline before and after, among other things) while SPAN just works within one line.
E.g.
Code:
<div class="block">
<p>first paragraph</p>
<p>second paragraph</p>
<h2>header</h2>
<p>more paragraphs</p>
</div>
vs.
Code:
<p>this is a <span style="text-decoration: underline;">sentence</span> where I want the word "sentence" underlined, which I can't do with U-tag in XHTML because it is deprecated.</p>