this is the book's title

by jim


table of contents

this is the book's title
table of contents
Standard Post
Photo Gallery Post
Post With Unordered List
Post With Ordered List
Post With Blockquote
Post With Photo
Post With Styled Text
Post With Headings
Header One
Header Two
-- Header Three
-- -- Header Four
-- -- -- Header Five
-- -- -- -- Header Six
Post With Preformatted Text
Post With Inline Image
Post With Embedded Media
Uber Post
-- Header
-- Another Header

Standard Post

welcome!

note that i've copied in some "real" text -- from my test-suite -- to replace the lorem ipsum that mr. barraud was using.

this is a document intended to demonstrate the range of features common throughout the e-texts in the project gutenberg library, and indeed to the majority of printed books.

project gutenberg is a volunteer effort -- please see http://gutenberg.org -- digitizing the text of public-domain books, for viewing and distribution in cyberspace.

it was begun by michael hart in 1971, with the goal of creating 10,000 e-texts, a milestone that was achieved in 2003, with boosts from distributed proofreaders -- at http://pgdp.net -- an advance that allows people to proofread online, thousands of 'em doing a page at a time, using bits and pieces of their spare time.

if you want to support the p.g. library with some kind of software or markup system, you should be able to handle its features, and you can use this file as a "test-suite" to verify that your system is fully capable.

this document should be self-explanatory. tabs have been substituted with "~tab~", so that they will become visible to you, so they can be changed back for your testing. other than that, no changes should be needed.

if you find any inconsistencies in this test-suite, do please let us know immediately. thank you.


Photo Gallery Post

ok, i reworked this gallery, so the code would pull the pictures from a local copy, so as to save mr. barraud his bandwidth, but they are set to link to his showpage on his site for each respective shot, as a mechanism for giving him credit. there's a whole bunch of .css code here that i don't understand, so i just copied it in as-is.


Post With Unordered List

another subsection of chapter 18

here's another example of a list:

like poems, items in a list generally want to stick together on the same page, if possible.

still gotta be able to handle lists...


Post With Ordered List

a subsection of chapter 18

sometimes you want to indent the items. here's an example of an indented list:

  1. 1. one
  2. 2. two
  3. 3. three
  4. 4. four
  5. 5. five
  6. 6. six
  7. 7. seven
  8. 8. i still forget what 8 was for.
  9. 9. number 9, number 9...

still gotta be able to handle lists...


Post With Blockquote

multi-purpose block-quotes

sometimes you wanna quote a whole bunch of stuff from someone. this is often called a "block-quote".

many of the project gutenberg e-texts contain block-quotes of one various type or another.

here's an example of a block-quote, a letter.

dear leslie,

how are you? i am fine.
the weather is nice here.
but i wish it was half
as beautiful as you are.

and i wish you were here.

love,
bowerbird

typically, block-quotes are indented on both the left and right sides.

here's another block-quote, from a speech.

four score and seven years ago, our
forefathers set forth upon this continent
a new nation, conceived in liberty and
dedicated to the proposition that
all men are created equal.[2]

there are a number of different situations throughout the e-texts that might call for this type of indentation. for now, we will just subsume them all under "block-quote"; perhaps later we will see fit to break out a more finely-grained analysis if we find any of the cases merit their own class.


Post With Photo

Photo Caption1

Photo Caption1

"what is the use of a book," thought alice, "without pictures or conversation?"

pictures in your book

most of the p.g. e-texts are text-only. but some of them do have pictures, so your system must be able to show 'em.

put a picture here, or maybe a button that someone could click in order to view that picture...

gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures... gotta be able to handle pictures...


Post With Styled Text

text "styling"

project gutenberg was born a very long time ago, before word-processors and personal computers.

a rumor is that michael used a keypunch machine (it's ok if you're too young to know what that is) to enter a good number of the original e-texts...

computers didn't even have lower-case characters in the early days, so the whole book was capitalized! luckily, before long we got lower-case characters.

but still, some "luxuries" like italicized and bold text were not possible, so michael developed a convention where a word that was bold or italics in the original was entered in all-upper-case, to show the emphasis.

because the e-texts are stored as raw ascii text, that convention lives on, to this day, in some files. by this time, however, we need to be able to handle styled text, so your systems must be able to do so.

here is some text that is marked as strong, which usually means bold.. and here is a link to project gutenberg, which isn't "styling", so i don't know why it's here, but just go with it for now. and here's a bit of text that is marked as "em", short for "emphasis", which usually means italic. and, for good measure, here's "strong em", which is pseudo-speak for "bold italics".

of course, you can also use b to get bold, and i to get italics, but then some knucklehead who only knows how to parrot back something that he was taught in school will try to give you a lecture about "the necessity to separate content from presentation", and who needs crap like that? so just use strong and em to get them off your back, while you cross your fingers behind your back and silently curse them in languages they do not understand.

and, now we demonstrate line-through, just to jack off show off, since you almost never see line-through used in a book.

ditto with underline, since that is typewriter-speak for italics, and therefore beneath the dignity of any typographer. besides, underlines on the web usually mean "hotlink", so if you underline something that is not a link, you will just confuse people. so don't do that.


Post With Headings

[[note, ok, this is really weird, because in the middle of the document, we have every header level making a unique appearance. this obviously obviates the structure of the document, so if it doesn't make sense, that's your good reason why...]]


Header One

ok, now let's not be ridiculous. a level-one header -- h1 -- is for the title of the book. that's all. you shouldn't have a level-one header popping up here in the middle of a chapter, it doesn't make any sense. so look for this whole chapter to be eliminated in the next version of this file.


Header Two

likewise, the level-two header is -- in this book -- the chapter header, namely the title of each post. so we can't have one of these popping up in the middle of a post either. so look for this chapter to disappear too.


Header Three

here's the level-three header, which can exist here, nestled right after a level-two header.


Header Four

likewise, a level-four header is possible here...


Header Five

and a level-five header is possible here... but notice that the level-five header here has some funky negative spacing. it's weird.


Header Six

and here's a level-six header. don't see one of those every day, do you? now, some people will try to tell you that -- under each header-level, you have to have at least two headers. they transferred that objection over from the things they learned about outlines. those rules do not apply here. you can have one header at each level, like we did here, if you want to, and don't let anyone tell you otherwise.


Post With Preformatted Text

here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text... here is some preformatted text...

this is the first line,
and this is the second line,
and this is the third line,
and this is the fourth line,
and this, my friends, is the fifth line, which goes to show a line can be long,
and this is the sixth,
and this is the seventh...

that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text... that was some preformatted text...


Post With Inline Image

Photo Caption2

Photo Caption2

ok, here mr. barraud was putting in some inline images. i'll have to check to see what he was doing, and how to replicate it properly.

there are some very idiosyncratic "class" statements here, such as "size-medium wp-image-757 alignright", so it appears he's using the .css naming to specify a certain presentation, which strikes me as being suspect, but what do i know?

basie it seems that here, he was just demonstrating a paragraph wrapping around an image. when i think of "inline images", i usually think of much smaller pictures, like key-cap images, that are expected to be roughly the size of their adjoining text. but maybe that's my misunderstanding...


Post With Embedded Media

video101! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video!

video102! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video!

video103! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video! video! step up and get your you-tube video! video! right here. come and get it! fresh hot video!


Uber Post

this is the "uber" post... it also violates the expectation as to level-hierarchy... so portions of it will be changed, so as not to do that...


Header

there's a header in the "uber" post, with this paragraph below it, followed by a list with 4 non-items in it...

this is the paragraph that follows the list in the "uber" post... again, there shouldn't be a level-one header here, underneath a level-two header. so i will be changing the header of this section to a level-three header.

basie this looks like the code that went in the "posts with inline images" entry...

if it actually is repeated code, then i could probably ignore this.

there was a null link in this paragraph, so i just deleted the whole thing.


Another Header

zen markup language

i'll be changing this to a level-three header as well, just like the one above it, because it seems to be located at the same level, not subsumed.

this test-suite document is a demonstration of z.m.l. -- "zen markup language" -- a system by which a set of simple formatting rules can take the place of complicated markup languages.

this document is "marked up" in z.m.l. and will spring to life when displayed by a z.m.l.-viewer.

as the experts say:

furthermore, a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages. a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages. a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages. a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages. a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages. a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages. a z.m.l.-viewer can perform all of the tasks necessary to implement the features that this test-suite represents: the hot-linking, the styling, different layouts, tables, pictures, formatting for plays, the lists, the whole thing, without the difficulty of heavy markup languages.

and you know those experts are never wrong, are they?

here's another list, popping up for no good reason, but 3 bad reasons.

  1. bad reason #1
  2. bad reason #2
  3. bad reason #3

the meta-data chapter

a lot of people think "meta-data" is important. i think they're full of poop, but why not make 'em happy?

so give them their own section -- call it the "meta-data section" -- and then let them put whatever makes 'em happy into that section.

you will find the meta-data section toward the very end of this document, where it belongs, after the "real" data.

the end

we hope you've enjoyed this test-suite document. if you have any questions, feel free to ask them.

this is a draft, so please suggest improvements. and if you want to make your own test-suite, do!

oh yeah, since he attained the 10,000 e-text mark, michael has a new goal now -- one million e-texts!

maybe you can help him with his new goal? :+)

http://gutenberg.org

have a nice day.

the end.

meta-data

* title = the test-suite for project gutenberg
* author = bowerbird intelligentleman
* for = project gutenberg
* website = http://gutenberg.org
  1. * title = the test-suite for project gutenberg
  2. * author = bowerbird intelligentleman
  3. * for = project gutenberg
  4. * website = http://gutenberg.org

Valid XHTML 1.0 Transitionalvalidate?