MobileRead Forums - View Single Post

bobcdy · 08-11-2011, 06:18 PM

I'm working on a 16th century English book with literally thousands of changes from normal to italic, and back, text. Although I realize that the / are depreciated tags all the browsers and ADE accept them, I think because is a LOT SHORTER than and the more correct tags would be much more difficult to incorporate into the epub.

Sigil generally accepts the tags but occasionally even v.4 rejects it with Tidy turned off, and Sigil insists on introducing at the start of the offending file a new sgc-1 tag and inserting sgc-1 with other changes in place of , sometimes everywhere in the file. ARGH! I thought that v.4 was done with such annoying inconveniences! At that point I absolutely must replace the tags and other Sigil changes with the css correct and within either the entire file or just the offending paragraph, even though in the other files of the epub the tags are accepted by Sigil without any objection. Any attempt to reintroduce the tags at the specific location causing the problem is met with continuing resistance by Sigil. Of course in a typical epub I might only need a few italics and I prefer using the css approved tags, but when there are many, many italic locations, then the css tags clutter the document.

It's odd but encouraging in that often only a single location within the entire epub will trigger Sigil's response.

Is there any way to insure that Sigil will accept the tags? If not is it possible for the new versions to make that change?

08-11-2011, 06:18 PM	#1
bobcdy Fanatic Posts: 527 Karma: 1048576 Join Date: May 2009 Device: bebook; prs-950; nook simple touch; HTC Jetstream tablet	problem with italics I'm working on a 16th century English book with literally thousands of changes from normal to italic, and back, text. Although I realize that the <i>/</i> are depreciated tags all the browsers and ADE accept them, I think because <i> is a LOT SHORTER than <span class="italic"> and the more correct tags would be much more difficult to incorporate into the epub. Sigil generally accepts the <i> tags but occasionally even v.4 rejects it with Tidy turned off, and Sigil insists on introducing at the start of the offending file a new sgc-1 tag and inserting sgc-1 with other changes in place of <i>, sometimes everywhere in the file. ARGH! I thought that v.4 was done with such annoying inconveniences! At that point I absolutely must replace the tags and other Sigil changes with the css correct <span class="italic"> and </span> within either the entire file or just the offending paragraph, even though in the other files of the epub the <i> tags are accepted by Sigil without any objection. Any attempt to reintroduce the <i> </i> tags at the specific location causing the problem is met with continuing resistance by Sigil. Of course in a typical epub I might only need a few italics and I prefer using the css approved tags, but when there are many, many italic locations, then the css tags clutter the document. It's odd but encouraging in that often only a single location within the entire epub will trigger Sigil's response. Is there any way to insure that Sigil will accept the <i> tags? If not is it possible for the new versions to make that change? Last edited by bobcdy; 08-11-2011 at 06:30 PM.