01-29-2014, 05:13 PM | #16 | |
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
Not too sure on the situation of most ereaders, but ADE itself does not support smallcaps.... and many of these readers are ADE based. Last edited by Tex2002ans; 01-29-2014 at 05:16 PM. |
|
01-29-2014, 05:36 PM | #17 |
Grand Sorcerer
Posts: 27,552
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Mantano's built on Adobe's RMSDK, as well. I've never tested it, but would expect it to ignore font-variant just like ADE does.
|
01-29-2014, 06:31 PM | #18 | |
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
Maybe I am just going crazy... or maybe it was a feature built into the Premium versions? |
|
01-29-2014, 07:09 PM | #19 |
Grand Sorcerer
Posts: 27,552
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
|
01-30-2014, 05:35 AM | #20 |
Wizard
Posts: 3,720
Karma: 1759970
Join Date: Sep 2010
Device: none
|
different book - same topic
each chapter of this book opens with a small-caps phrase which appears in all capitals in sigil book view, but appears as lower case on the sony reader. e.g. <p class="calibre5"><span class="calibre9">the cage opens at the front, a double loop</span> of chain hingeing its door at the bottom. At the top, a thicker chain and a fist-sized padlock keep the cage safely shut.</p> .calibre9 { font-variant: small-caps } so is there any way, short of retyping the start of every chapter , to add some CSS that ADE/sony does understand which will make that opening phrase display in caps ? update - well google is telling me there is no CSS workaround, but could sigil's own regex engine fix this easily. I need a regex that will transform all letters within a class ="calibre9" span to uppercase Last edited by cybmole; 01-30-2014 at 06:10 AM. |
01-30-2014, 07:53 AM | #21 | |
Well trained by Cats
Posts: 29,809
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
I cut this from my saved searches, so it has MY line numbers Code:
104\Name=Cleanup/Upper the case 104\Find="<span class=\"calibre9\">(.+?)</span>" 104\Replace="<span class=\"calibre9\">\\U\\1</span>" |
|
01-30-2014, 08:01 AM | #22 | |
Grand Sorcerer
Posts: 5,584
Karma: 22735033
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
Find:<span class="calibre9">(.*?)</span> Replace:<span class="calibre9">\U\1\E</span> For more information on converting to and from upper case characters see this older post of mine. However, if you start out with upper case text, you'll probably also need to convert the text to lower case. Otherwise you'll get all caps text. .calibre9 { text-transform: lowercase; font-variant: small-caps; } @theducks: You'll need to add \E at the end; otherwise the final </span> will also be capitalized. |
|
01-30-2014, 08:11 AM | #23 |
Wizard
Posts: 3,720
Karma: 1759970
Join Date: Sep 2010
Device: none
|
thanks - I had experimented & used 2 passes because I did not know about the \E,
so I did a 2nd pass to change /SPAN to /span seems to have done the trick interestingly, there's a sequel to this book which has similar formatting, except that in the sequel, they put the opening phrases into caps. thus it looked ok even when small-caps failed to kick in. publishers learning from their mistakes - whatever next |
01-30-2014, 08:48 AM | #24 | |
Well trained by Cats
Posts: 29,809
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
|
|
01-30-2014, 11:21 PM | #25 |
Obsessively Dedicated...
Posts: 3,200
Karma: 34977896
Join Date: May 2011
Location: JAPAN (US expatriate)
Device: Sony PRS-T2, ADE on PC
|
Very nice regex info in this thread, thanks guys.
I guess those of us who use embedded small-caps fonts instead of gambling on support for "transform" and "font-variant" are going to have to mend our ways. Edit to add: For the lead-in on a new chapter, I usually use all-caps styled for .7em bold, following a large drop-cap or large initial cap. I use the small-caps font for stuff inline in other text, such as "signatures" or signs, etc. Last edited by GrannyGrump; 01-31-2014 at 12:38 AM. |
02-01-2014, 01:25 AM | #26 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
B i l f o r d C h u r c h (Assume all the non-bolded letters are smallcaps). OR, the first word is aligned horizontally, but the next one is as you see the example. We tried everything, and even consulted with both Josh and Liz about it. Something in ADE's software just...don't like it, nohow, noway. Whatever the issue is, it's a dog to make work, no matter what you do with those smallcaps/smallcap variants, faux smallcaps, etc. Now, I haven't tried it since 2.0, I don't think...but man, it was the pits back then. I don't think I've given it a whirl since, as it was a lot of fuss for something fairly minor. FWIW. Hitch |
|
02-03-2014, 03:31 AM | #27 |
Wizard
Posts: 3,720
Karma: 1759970
Join Date: Sep 2010
Device: none
|
a final? (maybe) word on all this small caps stuff.
In all the books I've seen it used, in whatever variant, I have yet to see it used intelligently - ever. By which I mean ending it with attention to context, at the end of a sentence, or phrase. It seems that publishers decide to always small cap the first N words, or the first N centimetres. So you get small caps intro chunks that consist of sentence + one word, or all-but-one word of a phrase, or even ones bug out half way through someone's name, at the FN/LN boundary. Maybe it's all down to machine typesetting, surely in ye golden olden days of human typesetting ther'd be a little more sense applied ? & its not impossible to write regex that ends the small caps if a full stop or comma is detected. |
02-03-2014, 03:57 AM | #28 | |
Obsessively Dedicated...
Posts: 3,200
Karma: 34977896
Join Date: May 2011
Location: JAPAN (US expatriate)
Device: Sony PRS-T2, ADE on PC
|
Hitch said
Quote:
@cybmole, I agree. I personally like to use a logical phrase or sentence fragment, not necessarily the same number of words for each chapter. I really don't like the "single word" set off this way -- a short word like "the" or "but" looks like an orphan child sitting there in its solitary all-caps splendor. Even if traditional publishers have been using that for several centuries now (at least since the mid-1800's). |
|
02-03-2014, 04:38 AM | #29 | |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Quote:
You would think that this made a lot of sense to include on an e-reader... |
|
02-03-2014, 05:29 AM | #30 | ||
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Quote:
I sometimes try to include the first few words that make some sense, as in "When Peter Jones asked...", "The old manor house was...", "During the following years they met...", etc. Quote:
Use font-variant and :first-line, and nothing will actually be lost (you will not see the small-caps in most readers, but is it so important?) Last edited by Jellby; 02-03-2014 at 05:32 AM. |
||
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Valid code for August 2012 Baen Bundle | Papi47 | Deals and Resources (No Self-Promotion or Affiliate Links) | 0 | 12-13-2012 02:52 PM |
Fictionwise Code 55% - valid to 05/14/12 | Josieb1 | Deals and Resources (No Self-Promotion or Affiliate Links) | 21 | 05-14-2012 02:55 PM |
Valid ePub, but not valid enough for iBooks | MichaelGray | ePub | 46 | 01-14-2011 08:22 AM |
50% Off Promo Code for KoboBooks.com - Valid Dec. 15 Only | G0AT | Kobo Reader | 10 | 12-18-2010 09:42 AM |
Why does it have to be so complicated? (Good reader for PDF's) | drumknott | Which one should I buy? | 5 | 11-14-2009 05:43 AM |