View Single Post
Old 12-04-2011, 01:09 PM   #15
ghostyjack
Guru
ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.ghostyjack ought to be getting tired of karma fortunes by now.
 
ghostyjack's Avatar
 
Posts: 718
Karma: 1085610
Join Date: Mar 2009
Location: Bristol, England
Device: PRS-T1, 1825PT, Galaxy Tab, One X, TF700T, Aura HD, Nexus 7
And I thought I was the only one who see's a need for both <i> & <em> and <b> & <strong>.

I routinely utilise all of them, depending on if it is symantic or document structure. This way I can better control the file.

e.g. a ship name needs to be in italics as you are not emphasising the name. So I'd expect a sentence to be like: "This is <em>not</em> HMS <i>Warspite</i>." This way I can immediately see which elements are being stressed, and which are structure.

So for me, bold and italic buttons need to be using bold and italic tags. I'd also like to have emphasis and strong buttons as well in Sigil, so that I can directly apply the correct tag instead of having the scan the file afterwards and may the switch to the other tags where needed.

On a side note, John, is there any likelyhood that the buttons will ever be made to work in code view?
ghostyjack is offline   Reply With Quote