000/grd -- ============================================> gourd #01
001/hdr -- a brief introduction to z.m.l. xxxxx
002/hdr -- by bowerbird intelligentleman xxxxx
003/bce -- you can "view source" for this document here:// http://zenmagiclove.com/hnews/hnews111111111.zml//
004/grd -- ============================================> gourd#02
005/hdr -- table of contents xxxxx
006/bce -- a brief introduction to z.m.l.// table of contents// preface to this brief introduction// chapter 1 -- review paragraphs// chapter 2 -- review sections// chapter 3 -- text styling in your book// chapter 4 -- poetry and other silly things// chapter 5 -- images in your book// chapter 6 -- linking in your book// chapter 7 -- multi-purpose block-quotes// chapter 8 -- footnotes and endnotes// chapter 9 -- lists in your book// chapter 10 -- epigraphs and epitaphs// chapter 11 -- tables in your book// chapter 12 -- the play is the thing// chapter 13 -- unlucky number 13// chapter 14 -- hyphens and dashes// chapter 15 -- hyphenation stinks// chapter 16 -- two spaces after a sentence// chapter 17 -- preformatted text and code// chapter 18 -- the notes section// chapter 19 -- meta-data for this book//
007/grd -- ============================================> gourd#03
008/hdr -- preface to this brief introduction xxxxx
009/pop -- this is the preface.//
010/grd -- ============================================> gourd#04
011/hdr -- chapter 1
012/hdr -- review paragraphs xxxxx
013/pop -- separate paragraphs with a blank line.
014/pop -- don't indent paragraphs with spaces or tabs.
015/pop -- (indeed, don't use tabs anywhere.)//
016/grd -- ============================================> gourd#05
017/hdr -- chapter 2
018/hdr -- review sections xxxxx
019/pop -- separate the sections -- such as chapters,//but also front-matter sections and so on --//with 4 blank lines above the section header//and 2 blank lines below the section header.
020/pop -- you can alternatively put hash-marks at the//beginning of a header preceded by a space//in the first column. an h2 header will have//two hash-marks, an h3 header three, etc.//you are only allowed to have one h1 header,//the title, and it is defined as the first chunk,//so you needn't use a 1-hash-mark indicator.
021/pop -- every section must have at least one header,//but it can also have two headers, if you like,//such as "chapter 1" and "in the beginning".//separate the two headers with 1 blank line.//and again, the header must be followed by//two blank lines, to separate it from the body.
022/pop -- the first section in the book is the cover/title.//the book's title comes first, the the subtitle(s),//then the author-name. after that, you should//include anything you consider of importance.
023/pop -- the second section is the table of contents.//this is required, so readers know where it is,//and know that it's in a very convenient place.//a table of contents will be auto-created and//injected as the second section of your book//if you do not already have a table of contents//as your second section. the table of contents//in an e-book should always have its items be//linked to the appropriate spots in the book, so//jaguar creates such links for you automatically.//
024/grd -- ============================================> gourd#06
025/hdr -- chapter 3
026/hdr -- text styling in your book xxxxx
027/pop -- italicized words are indicated with underbars,//one at the beginning and another at the end.//the beginning one _must_ have white-space//to its left; likewise, the closing one _must_//have white-space to its right. in a phrase,//each word must have its own underscores.
028/pop -- this word will be in _italics._
029/pop -- this phrase _will_ _be_ _in_ _italics._
030/pop -- *bold* words are indicated with asterisks,//subject to the same rules on white-space.
031/pop -- this word will be in *bold.*
032/pop -- this phrase *will* *be* *bold.*//
033/grd -- ============================================> gourd#07
034/hdr -- chapter 4
035/hdr -- poetry and other silly things xxxxx
036/pop -- use a space in the first column to get centered lines.
037/bce -- t.v. will eat you// (a haiku by bowerbird intelligentleman)
038/bce -- t.v. will eat you// out of a satellite dish// with a tuning fork
039/pop -- use multiple spaces (5 or more, in a consistent number)//to get a chunk that is both left-justified and indented.
040/bpo -- a haiku for you// (by bowerbird intelligentleman)
041/bpo -- haiku have three lines// and seventeen syllables// five, seven, and five
042/pop -- you can vary the spacing, as some poems like to do.
043/bpo -- six spaces at the start of this line// 12 spaces at the start of this line// six spaces at the start of this line// 12 spaces at the start of this line// six spaces at the start of this line// 12 spaces at the start of this line// six spaces at the start of this line// 12 spaces at the start of this line
044/pop -- you can even get downright fweaky!
045/bpo -- six spaces at the start of this line// ten spaces at the start of this line// 14 spaces at the start of this line// 18 spaces at the start of this line// 22 spaces at the start of this line// 18 spaces at the start of this line// 14 spaces at the start of this line// ten spaces at the start of this line// six spaces at the start of this line
046/pop -- sometimes you want to set off an element//by giving it a different form of justification,//and jaguar makes it easy for you to do that.
047/bce -- the input for the 2 chunks that follow has// a space in the first column of all of the lines.
048/bce -- you know about a space in the first column.
049/bce -- a space in the first column will center a line,// or -- applied to each line in a group of lines --// will end up centering the entire block of lines.
050/bjl -- this chunk, and the next chunk as well, has// two spaces at the beginning of each line.
051/bjl -- if you want to explicitly declare a block as// left-justified, start it with _two_ _spaces..._// this puts it at the left margin, with no indent.
052/bjc -- this chunk, and the next chunk as well, has// three spaces at the beginning of each line.
053/bjc -- as reported above, a space in the first column// will center a line. however, it is also the case// that _three_ _spaces_ at the start of a line will// cause that line to be centered.
054/bjr -- this chunk, and the next chunk as well, has// four spaces at the beginning of each line.
055/bjr -- and, to fill out the left-center-right concept,// 4 spaces at the start of a line will cause it to// be right-justified.
056/bce -- so, to review, 1 space = centered// 2 spaces = left-justified// 3 spaces = centered// 4 spaces = right-justified
057/pop -- note also that you can use this convention inside//a paragraph, so if you want an interior line there// such as this one, for instance//to be centered, just put it on its own line and//put a space in its first column to get that effect.//jaguar will precede it and follow this special line//with a hard-linebreak (or, in .html, the "br" tag),//so that is a way that you can _force_ _a_ _linebreak,_//and over-rule html's philosophical desire to wrap.
058/pop -- and, of course, the other types of justification// like using 4 spaces for right-justification//will work as well. so if you want to center a line// just precede it with 3 spaces at the start,//or, when you want a left-justified line to appear//in the middle of an otherwise fully-justified line,// you will just put 2 spaces at its beginning,//and voila, that will give you the effect you want.//note that this is a good way to highlight a u.r.l.// > http://gutenberg.org//that is located in the middle of a paragraph.//
059/grd -- ============================================> gourd#08
060/hdr -- chapter 5
061/hdr -- images in your book xxxxx
062/pop -- to include an image in your book, just enter its u.r.l.
063/bce -- http://z-m-l.com/go/alice/checking_watch.png
064/pop -- "what is the//use of a book,"//thought alice,//"without pictures//or conversation?"
065/bce -- http://z-m-l.com/go/alice/alice_cramped.png xxxxx
066/pop -- you can put a caption on your image if you like,//above it, or below it, or even _one_ _of_ _each._ xxxxx
067/bce -- here's a caption placed above a picture// http://z-m-l.com/go/alice/checking_watch.png xxxxx
068/bce -- http://z-m-l.com/go/alice/checking_watch.png// here's a caption placed below a picture xxxxx
069/bce -- and here's a caption placed above a picture...// http://z-m-l.com/go/alice/checking_watch.png// with another caption placed below the picture xxxxx
070/pop -- and, using the methodology discussed above,//you can even insert a picture _inside_//https://dl.dropboxusercontent.com/u/26394889/hellobone.jpg//a paragraph, if you must, but you should//be aware that this will cause some funkiness//in some e-book viewer-apps, so you shouldn't//try to get too fancy. in general, it will be best//if you set off pictures, either above or below//the text that refers to them, for best results. xxxxx
071/pop -- and, of course, the justification techniques that//we just discussed in chapter 4 can also be used//to set the "float" characteristic for your images. xxxxx
072/pop -- to center an image, precede its u.r.l. with 1 space:
073/bjc -- http://z-m-l.com/go/alice/checking_watch.png xxxxx
074/pop -- to "float" the image to the left, use 2 spaces:
075/bjl -- http://z-m-l.com/go/alice/checking_watch.png xxxxx
076/pop -- to center an image, precede its u.r.l. with 3 spaces:
077/bjc -- http://z-m-l.com/go/alice/checking_watch.png xxxxx
078/pop -- and to "float" it to the right, you'd use 4 spaces:
079/bjr -- http://z-m-l.com/go/alice/checking_watch.png xxxxx
080/pop -- notice that when you use a single space, the image//will "expand" to fill the available width and/or height//of the screen which is currently being used to view it.//in most cases, that's exactly what your readers want,//so that is the recommended way of proceeding here.
081/pop -- on the other hand, using the 2/3/4 spaces method//means the image will get shown at its original size.
082/pop -- when you use the 2/3/4 spaces option for a picture,//text might -- or might not -- be "floated" around it,//but you shouldn't count on that, because it simply//won't be possible on some screens, and can cause//undesirable effects even on large-enough screens.//
083/grd -- ============================================> gourd#09
084/hdr -- chapter 6
085/hdr -- linking in your book xxxxx
086/pop -- remember how, in chapter 2, we said//that the table of contents should be//hot-linked to the appropriate spots?//so jaguar creates them automatically.
087/pop -- similarly, there are often places in a book//that reference other chapters in the book.//in these cases, it's nice to have a hotlink//that transports the reader to the chapter//that is being referenced; it is convenient.
088/pop -- so jaguar automates those links for you,//too. just use the header (or subheader)//of the gourd, and jaguar will auto-link it.
089/pop -- for instance, the beginning of this chapter//has a reference to chapter 2. if a reader//clicked on those words -- "chapter 2" --//they will automatically go to chapter 2.//(and likewise with each of the references//to "chapter 2" here in this paragraph too.)
090/pop -- such internal links are one type needed,//but you also might want _external_ links,//ones that will jump out to some webpage.
091/pop -- to make an external link, just list the u.r.l.
092/bce -- http://gutenberg.org
093/pop -- jaguar will create that link automatically.
094/pop -- a core element of the jaguar philosophy//is that a book's elements be transparent,//so there is no way to "hide" a link behind//some text. the u.r.l. must be fully exposed.
095/pop -- however, if the u.r.l. would be too bulky to//include there, you _can_ put it in a footnote.
096/pop -- i get 10 times more traffic from Google[g]//than from yahoo[y] and microsoft-bing[m] combined.
097/pfn -- [g] http://google.com
098/pfn -- [y] http://search.yahoo.com
099/pfn -- [m] http://bing.com//
100/grd -- ============================================> gourd#10
101/hdr -- chapter 7
102/hdr -- multi-purpose block-quotes xxxxx
103/pop -- you can get a blockquote like this.
104/bce -- : 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[1] are created equal.
105/pop -- or like this:
106/bce -- > 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[2] are created equal.
107/pop -- you should note that the first method//(using the colon) rewraps the lines, and//the second (using the right-angle-bracket)//does not rewrap the lines. so use the one//which meets your needs better in each case.//
108/grd -- ============================================> gourd#11
109/hdr -- chapter 8
110/hdr -- footnotes and endnotes xxxxx
111/pop -- your book can have footnotes.[3]
112/pop -- for a footnote, place the footnote-referent in//square brackets.[3a]
113/pop -- note that there must be _no_ white-space//to the left of the referent, but that there//_must_ be whitespace to the right of it.
114/pop -- this is just a dummy paragraph,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
115/pop -- this is another dummy paragraph,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
116/pop -- this is a third dummy paragraph,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
117/pop -- and a fourth dummy paragraph,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
118/pop -- here's dummy paragraph #5,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
119/pop -- this is a sixth dummy paragraph,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
120/pop -- and the seventh dummy paragraph,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
121/pop -- here's dummy paragraph #8,//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.
122/pop -- i hope 9 dummy paragraphs is enough//to get some separation between//the footnote referent up above//and the actual footnote below,//so you can see the jump when//you click between the two of them.[4]
123/pfn -- [3] you can put the footnote right underneath//the paragraph which contains it, or at the end//of the chapter containing it, or in a section at//the end of the book with all the other footnotes.//
124/grd -- ============================================> gourd#12
125/hdr -- chapter 9
126/hdr -- lists in your book xxxxx
127/pop -- you can use '' * '' at the beginning of a gourd//to make a list, an "unordered" list" that has//the usual circular bullet-point as its marker.
128/bce -- *// * one// * two// * three// * four// * five// * six// * seven// * i forget what 8 was for.// * number 9, number 9...
129/pop -- as you can see in this example, every item//must be prefaced with the same character//as the first one. and, in this example here,//the first item is _blank,_ which means that//this list will have some spacing at the top,//which serves to separate it from whatever//chunk appeared right before it. if you want//the list to snuggle with what came before,//you would eliminate that empty first item.
130/bce -- ***
131/pop -- you can also use '' o '' for a list, a tag that//will use an _unfilled_ _bullet_ as its marker.
132/bce -- o mercury// o venus// o earth// o mars// o jupiter// o saturn// o uranus// o neptune// o pluto// o
133/pop -- this list has an empty item at the end of it,//which means it will be separated from the//chunk that _follows_ it, i.e., this paragraph.
134/bce -- ***
135/pop -- you can also use '' + '' for a list you want//to be indented one level, and which uses//a filled square marker as its bullet-point.
136/bce -- + some// + where// + over// + the// + rainbow// + blue// + birds// + fly.
137/bce -- ***
138/pop -- and you can also use '' - '' to make a list,//one that gets indented _two_ levels and//uses the unfilled bullet as its marker.
139/bce -- - mary's// - violet// - eyes// - made// - johnny// - stay// - up// - nights.// - period.
140/bce -- ***
141/pop -- as you might imagine, you can combine//these indented lists for a multi-level list.
142/bce -- * this is the first point at the first level// + this item is at the second level// + this item is also at the second level// - now we've moved to the third level// - one more at the third level// * now we're back at the very first level// * again, another point at the top level// + here's an item at the second level// + and another item at that level// + and yet another item at that level// - out to the third level.// - and out to the third level again.
143/bce -- ***
144/pop -- you can also use '' = '' to create a list;//a tag with an unfilled circle as its bullet.
145/bce -- = the// = equals// = sign// = uses// = a// = solid// = square// = as// = its// = bullet.
146/bce -- ***
147/pop -- finally, you can use '' x '' to make a list.
148/bce -- x the// x letter// x "x"// x makes// x an// x "x"// x with// x no// x bullet.
149/pop -- the '' x '' prefix has _no_ bullet at all.//as we will now see, that has benefits.
150/bce -- ***
151/pop -- sometimes you want a numbered list...
152/pop -- here's an example of an unordered list//that masquerades as a numbered list,//with the number specifically included,//thanks to its use of the '' x '' tag.
153/bce -- x 1. one// x 2. two// x 3. three// x 4. four// x 5. five// x 6. six// x 7. seven// x 8. i still forget what 8 was for.// x 9. number 9, number 9...
154/bce -- ***
155/pop -- here's another "numbered list", again//with the number specifically included,//but we mix things up a bit, to show//how to do non-sequential numbers.
156/bce -- x 101. one// x 202. two// x 3. three// x 4444. four// x 55555. five// x 6. six// x 77. seven// x 88. i still forget what 8 was for.// x 9. number 9, number 9...
157/pop -- that example seems kind of silly, yes,//but there are many meaningful ones.
158/bce -- x 9800bc -- north america gets inhabited// x 1492 -- columbus "discovers" america// x 1620 -- pilgrams land on plymouth rock// x 1622 -- "indians" feed starving pilgrims// x 1809 -- white men start "indian" genoicide// x 1964 -- civil rights act passes congress
159/bce -- ***
160/pop -- and finally, another numbered list, except//this time it's a plain html ordered list,//so the browser does the numbering. for this,//the tag is a '' # '' hash (a.k.a., a number sign).
161/bce -- # one// # two// # three// # four// # five// # six// # seven// # i still forget what 8 was for.// # number 9, number 9...//
162/grd -- ============================================> gourd#13
163/hdr -- chapter 10
164/hdr -- epigraphs and epitaphs xxxxx
165/bjr -- _there's_ _an_ _old_ _proverb_// _that_ _says_ _just_ _about_// _whatever_ _you_ _want_ _it_ _to..._// _--_ _slashdot_
166/pop -- sometimes a chapter starts with a nice pithy quote,//which is usually _italicized,_ and often right-justified.
167/pop -- so you wanna be able to handle that kind of thing.[5]//
168/grd -- ============================================> gourd#14
169/hdr -- chapter 11
170/hdr -- tables in your book xxxxx
171/pop -- you can have tables in your book, simple ones.//just use multiple-spaces to separate the cells.
172/bce -- | table 1 column 1 column 2// | plain-text yes yes// | x.m.l. no yes// | html yes no// | .rtf no yes// | .pdf no no
173/bce -- ***
174/pop -- you can also use or-bars to separate the cells.
175/bce -- | table 1 | column 1 | column 2// | plain-text | yes | yes// | x.m.l. | no | yes// | html | yes | no// | .rtf | no | yes// | .pdf | no | no xxxxx
176/bce -- ***
177/pop -- you can even combine these two approaches,//but understand that or-bars take precedence.
178/bce -- | table 1 | column 1 | column 2// | plain-text | yes | maybe// | x.m.l. | no | yes// | html | yes | no// | .rtf | no | yes// | .pdf | no | no//
179/grd -- ============================================> gourd#15
180/hdr -- chapter 12
181/hdr -- the play is the thing xxxxx
182/pop -- jaguar auto-bolds the first word of a paragraph//if it is followed with a colon. this is handy//when you are doing the dialog for a play.
183/pin -- dale: that's not what p.g. is all about.
184/pin -- bowerbird: i think it's important to//give people a good e-book experience.
185/pin -- dale: that's your opinion.
186/pin -- bowerbird: yes it is.
187/pin -- steve: (weakly) i can't...
188/pin -- dale: no it isn't.
189/pin -- steve: (weakly) get a...
190/pin -- bowerbird: is too.
191/pin -- steve: (weakly) word in edgewise...
192/pin -- dale: is not.
193/pin -- lurkers: will you two cut it out?
194/pin -- bowerbird: is so.
195/pin -- dale: is not...
196/pop -- fade to black.[6]//
197/grd -- ============================================> gourd#16
198/hdr -- chapter 13
199/hdr -- unlucky number 13 xxxxx
200/pop -- there is no 13th floor in most buildings.//
201/grd -- ============================================> gourd#17
202/hdr -- chapter 14
203/hdr -- hyphens and dashes xxxxx
204/pop -- use a double-dash -- like these here -- to get//an em-dash in your .html output. it's best to//put spaces around your double-dashes, or else//they can sometimes cause word-wrap problems...
205/pop -- don't use a single-dash - like this bad example -//where you want an em-dash, or it will look _bad._
206/pop -- even http://medium.com and http://kottke.org//make that mistake. it's rather embarrassing, eh?//
207/grd -- ============================================> gourd#18
208/hdr -- chapter 15
209/hdr -- hyphenation stinks xxxxx
210/pop -- do not hyphenate your text. e-books don't need it.//and you never know exactly how the text will reflow.//
211/grd -- ============================================> gourd#19
212/hdr -- chapter 16
213/hdr -- two spaces after a sentence xxxxx
214/pop -- many typesetters set a little bit of extra space//between sentences, so the separation is clear.//i support that, as i think it makes it look nicer.
215/pop -- now some people try to get this nicer look via//the old typewriter-trick of putting 2 spaces at//the end of a sentence. but that doesn't work//when the text is turned to .html. and further,//the extra spaces mess with our editing process,//where we often search the text for 2-spaces,//just to make sure we haven't inadvertently//introduced extra spaces in unwanted places.
216/pop -- so the best tactic to use these days is to put//only one space after a sentence, and _hope_//browsers will soon support better typography.//
217/grd -- ============================================> gourd#20
218/hdr -- chapter 17
219/hdr -- preformatted text and code xxxxx
220/pop -- sometimes you might have a need to present//preformatted text, or computer-language code.
221/pop -- for these situations, you will use the ` backtick.
222/pop -- inside a paragraph, or some other element,//the `backtick` acts just like the italics `_`//and bold `*` markers. it will serve to have//the text that it surrounds displayed in the//`preformatted` .html tag -- which is `pre.`
223/pop -- however, the backtick can also be used as//a block tag, to signal that an entire chunk//should be shown using the html "code" tag.
224/pop -- while the '' ` '' can be used to start each line,//that would cause the code in the input file to//be "polluted" with these backticks, so it'll be//best to start the chunk with an empty tag:
225/bce -- `//// the backtick code in the line above//// signifies this chunk is source-code,//// to be shown with .html's "code" tag,//// i.e., monospaced and preformatted.// <script type="text/javascript">// $(document).ready(function () {// gdi=setInterval(function(){doit()},1000)// })// </script>//// this is known in light-markup circles as//// "a fenced block", since the backtick(s)//// up top sets a "fence" around the code.//// the code block is then usually followed//// by a closing "fence" of backtick(s), but//// in z.m.l., a blank line closes all elements,//// so we don't need a "closing" fence here.//// however, this does mean that the code//// cannot contain any blank lines inside it,//// so you must stay cognizant of that fact.//// comment out blank lines in your code.
226/pop -- be aware that you can also add a note to//the opening backtick tag that describes//what the code does, the language, etc.
227/bce -- ` // javascript document.ready function// <script type="text/javascript">// $(document).ready(function () {// gdi=setInterval(function(){doit()},1000)// })// </script>//
228/grd -- ============================================> gourd#21
229/hdr -- chapter 18
230/hdr -- the notes section xxxxx
231/pfn -- [1] in later years, it was made clear that//lincoln was referring to all "people", and//not just men, that women are equally equal.
232/pfn -- [2] again, in later years, it was made clear//lincoln was referring to all "people", and//not just men, that women are equally equal.
233/pfn -- [3a] personally, i don't think we need to//make a distinction between footnotes//and endnotes any more, i believe that//all the types of notes should be stored//at the end of the file, like these notes,//but i think the person should be able to//_display_ them at the point of reference//in the actual body of the text. therefore,//they are actually a sort of hybrid between//footnotes _and_ endnotes, combining the//strengths and convenience of both types.
234/pfn -- [4] this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.
235/pop -- look, it even has a second paragraph!//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.
236/pop -- oh no! a third paragraph. way too long!//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.//this is a test footnote. because of that,//it's going to go on and on and on.
237/pfn -- [5] this is another test footnote. but it will be short.
238/pfn -- [6] you probably shouldn't mix footnotes and endnotes,//like i have done in this book, because that'll just make it//confusing for your readers. so choose one or the other.//
239/grd -- ============================================> gourd#22
240/hdr -- chapter 19
241/hdr -- meta-data for this book xxxxx
242/pop -- here's the meta-data...
243/bce -- o title = a brief introduction to z.m.l.// o author = bowerbird intelligentleman// o purpose = a brief introduction to z.m.l.// o markup = zen markup language (.zml)// o isbn = urn:isbn:0000000000000// o publisher = jaguar(ps)// o subject = a brief introduction to z.m.l.// o rights = copyright 2013 -- all rights reserved