Is it possible to get a field for the Epigraph of a book? I find Epigraphs to be fascinating and would love to be able to see what books use the same Epigraph.

Just a thought.

That's a nice one. I wonder if people are putting epigraphs into their books.

I'd also love to see dedications...

I record dedications and epigraphs in the Comments field. I, too, would like a CK field for them instead.

Dedications are nice, but sometimes I think they aren't specific enough. But I'm not against anything! The more information we can input the better, imho.

Oooh - me likey- Stephen King makes up his own music lyrics for epigraphs. ^^

I'm obsessed with epigraphs. Right now I'm reading ghostgirl by Tonya Hurley and she has an "epigraph" for every chapter!

Empires of the Word has amazing epigraphs for each chapter. I keep meaning go go back and record them all.

So we're how close to chapter listings (and a way to put in Anthology listings!)???

mmmm...chapter listings.....

>8
I do anthology listings in Comments too.

My kingdom for a dedicated field...

The best epigraphs are Mark Twain's in The Gilded Age.

Message edited by its author, Aug 26, 2008, 3:19am.

Interesting dodge, Mr. Spalding, interesting dodge.

=P

Just keeping the discussion going. Anyway, I get to be a user too! :)

So, user to user and all - how about chapter listings and a way to put in anthologies! How swell would that be?

=)

But, honestly, a comprehensive epigraph listing is one of those really spiffy things that we'd not likely find elsewhere.

#14

Just doing a contents list for anthologies / collections is wimping out IMHO.

Many people have already entered short stories as works. They obviously see some need more than just a plain list (which could quite easily be done in comments).

Personally having short stories as first class objects* in the database should be the eventual goal (although they should be handled slightly differently to books§). Having a simple list of contents will not help in getting to that goal IMO. The real solution is a pretty large amount of work - with a lot of that being on UI design.

* So that short stories can be tagged, combined, CK entered, reviewed, rated and so on.
§ Obviously they need to be tied up so that a book can be exploded to view its contents. Also they may well not appear in the basic library view - but only when a book is exploded. Reverse discovery should be possible as well - for this short story tell me all the works in which it appears.

>16

That would be awesome.

A little hard to work in with the interface, I think, but pretty awesome nonetheless.

But for now, I still think epigraphs would be pretty cool. I love epigraphs.

Are epigraphs the same for the various editions or printings of a book? If not, shouldn't it be referenced to the particular edition or printing.

Is epigraph just another word used to describe the quotes that authors put at the beginning of the book and sometimes at the beginning of each chapter? If so, should the location of each epigraph also be included.

Sorry for the bad grammar on this one. I just couldn't get my thoughts written down correctly.

Epigraphs are almost always not edition specific. I could imagine a sloppy reprint of a classic work omitting an epigraph. And I could imagine a second edition—which, normally is the same "work"—having a different epigraph. They aren't "works" in LT parlance, but I know at least one Eliot poem changed epigraphs when reprinted. But we're at the margins. If such a difference really mattered I at least would have no problem including it in parentheses at the end.

The feature is primarily intended for work-level epigraphs, but there's no reason chapter- or poem-level epigraphs can't be included, with a parenthesis about the location. You'll note the epigraph field allows multiple entries.

Reminded by #11, I've undertaken the slighty mad task of entering Trumbull's mottoes for The Gilded Age.

I'm working through proofreading my transcriptions and adding some formatting. (I've also located many of the original sources and so spotted some printer's errors.)

For chapters with more than one motto, I thought to just have a couple of paragraphs within the entry. This behaves strangely: the <p> is saved okay and displayed and returns on edit, on that one page. But when I return later, it's been stripped out.

For the Egyptian hieroglyphs, I guess an image is required. I can make one from Manuel de Codage format offline and put in an img tag. (Wikipedia does this automatically, but LT's wiki library is much simpler.) Is that kosher?

A bigger question is whether 65 entries is too many for CK. Should I just have one that goes to another page, perhaps outside LT? That's what one would do for a too long review, but those are personal and this wants to be common. Opinions?

Ha. Excellent.

Have you tried just adding returns. Do they get stripped out? I gather Chris has been playing with the spaces, so let me know if it's a problem.

I think it's kosher to reference an image. Let me know if it works.

I think the number isn't a problem.

I want a field for colophons.

;-)

When we do publishers, we should do colophons.

No joke...

Can we have font pages for the colophons? Ooo, or letterer pages? :)

Message edited by its author, Sep 8, 2008, 5:14pm.

I really do think it would be wonderful. You can learn a lot from a colophon; they're fascinating. I've seen some pretty funny ones, too. (See my review of Moose Mousse and other Exotic Recipes.)

As near as I can work out, the algorithm is to strip all tags, and then replace any vertical break with a single <br>. I tried div as well as p and returns. You do get a line break, but no spacing control. When there are two separate multi-line stanzas, this really isn't as nice as I'd like.

img exhibits the same behavior I described before. Looks fine after Save or on subsequent edits on that page. Lost when returning to the page or refreshing.

I've successfully formatted poetry stanzas using br and non-breaking spaces.

Multiple brs were not being reduced to one (at least a few days ago they weren't).

I switched from p to br and it helped a little.

The sequence <br><br> definitely turns into <br> after save and reload for me.

span is being removed as well, making it impossible to control the font.

32-bit Unicode (Cuneiform) is not handled properly. If pasted as UTF-8, it is trashed right away. If pasted as HTML numeric entities, it's okay for one go round. Then it gets converted to characters in the editor and trashed next time. The same thing happens here in Talk: if I enter &lt;br&gt;, it'll be okay until edit, when it will come back as <br> and then become formatting. I think perhaps a clear definition of the data format in each module is called for.

img is still needed.

ETA: Some samples:

XII:

XXV: 𒀀𒂡 𒆗𒆗𒋾

XL:   

Message edited by its author, Sep 17, 2008, 2:12am.

I find if I use <br /><br /> that gets converted into <br><br> and does what I need (a completely blank line)

29: Data format is minimal HTML, clearly. ;)

> 30 CK needs to be editable.

I had XHTML in my original data. But I consciously avoided <br/> here because it is not stable. Save it and it turns into <br>.

So, if you enter <br/><br/>, save it, refresh, edit, save, refresh, you will have <br>. (First time it goes to pre-XHTML; second time it merges.)