small caps problem in Sigil - Page 2

Jellby · 08-05-2011, 05:14 AM

And with that you convert a perfectly compliant "font-variant: small-caps", into a not-in-spec "text-transfor: uppercase". It might work in ADE, it might work in "more readers", but it's not a supported property.

Don't misunderstand me, it's probably an acceptable interim solution, but if no one uses small-caps because they are not supported by ADE, then ADE will see no reason to support something nobody uses.

goroke · 08-05-2011, 12:14 PM

Actually, ADE is not my concern; I don't have a mobile device. I use Calibre's reader for most things, and Sigil for editing. Both of them do really bizarre display things when the correct small-caps code and justification are used together. If it were just a matter of them ignoring the instruction and displaying in normal mixed case, I would just live with that and code it all correctly...

As I noted above, the only thing I have to do to make this "perfectly compliant" is to change the definition in my CSS -- unless there is some sort of compliance issue with my placing the kludged "small-caps" code only around the letters to be affected, rather than the correct code around an entire word or phrase.

I read your earlier comments carefully, which is why I used this approach rather than to simply type in regular caps and just use the reduced size and give up on the correct method altogether.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
RTF "small caps" conversion?	sehlat	Calibre	3	06-23-2011 07:24 PM
small caps	yuxi_kelly	ePub	20	06-05-2011 12:04 AM
Small problem with Newegg	GA Russell	Ectaco jetBook	10	10-30-2010 12:03 AM
iLiad Welcome back - small(?) Problem	FGFuzax	iRex	14	10-01-2010 12:29 PM
DR1000 FW2.0 - RC2 - font-variant: small-caps	ThR	iRex	0	06-29-2010 05:31 AM

08-05-2011, 05:14 AM	#16
Jellby frumious Bandersnatch Posts: 7,516 Karma: 18512745 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	And with that you convert a perfectly compliant "font-variant: small-caps", into a not-in-spec "text-transfor: uppercase". It might work in ADE, it might work in "more readers", but it's not a supported property. Don't misunderstand me, it's probably an acceptable interim solution, but if no one uses small-caps because they are not supported by ADE, then ADE will see no reason to support something nobody uses.

08-05-2011, 12:14 PM	#17
goroke Member Posts: 10 Karma: 10 Join Date: Jul 2011 Device: none	Actually, ADE is not my concern; I don't have a mobile device. I use Calibre's reader for most things, and Sigil for editing. Both of them do really bizarre display things when the correct small-caps code and justification are used together. If it were just a matter of them ignoring the instruction and displaying in normal mixed case, I would just live with that and code it all correctly... As I noted above, the only thing I have to do to make this "perfectly compliant" is to change the definition in my CSS -- unless there is some sort of compliance issue with my placing the kludged "small-caps" code only around the letters to be affected, rather than the correct code around an entire word or phrase. I read your earlier comments carefully, which is why I used this approach rather than to simply type in regular caps and just use the reduced size and give up on the correct method altogether.

Advert