aboutsummaryrefslogtreecommitdiffhomepage
path: root/lib/sisu/v3/objects.txt
diff options
context:
space:
mode:
authorRalph Amissah <ralph@amissah.com>2011-08-09 20:25:13 -0400
committerRalph Amissah <ralph@amissah.com>2011-08-09 20:25:13 -0400
commit637e3e53e41104ccb92a0753a0abbf0929c3b933 (patch)
tree80d9069da748d6563ac6d2851ae40b85f3ef34b7 /lib/sisu/v3/objects.txt
parentdebian/changelog (3.0.14-1) (diff)
parentv3: epub, constants, experiment with presentation (diff)
Merge commit 'sisu-3.0.15' into debian/sid
Diffstat (limited to 'lib/sisu/v3/objects.txt')
-rw-r--r--lib/sisu/v3/objects.txt42
1 files changed, 0 insertions, 42 deletions
diff --git a/lib/sisu/v3/objects.txt b/lib/sisu/v3/objects.txt
deleted file mode 100644
index c94e02c4..00000000
--- a/lib/sisu/v3/objects.txt
+++ /dev/null
@@ -1,42 +0,0 @@
-shared_doc_objects.rb
-needed:
- tables code poem block group etc.
- ocn numbers
- hash numbers
-
-#consider a hash of:
-:metadata or :header or @md? #with has or array of metadata, decide on which, may be possible to use param & @md
-:substance, :text or :body #array of hash objects
-
-:obj #actual substantive text or content of object, :obj preferred to :txt as may contain any of the items described in :type
-:type #which may be one of: paragraph, heading? code, verse, block text, table, image/figure?
-:ocn #object citation number
-:lv or :heading? #level, document structure, heading level
-:name #html segment name and location name
-:index #contain book index information if provided
-:hash? #consider, need hash for clean and marked up text, then also for each footnote contained within the object
-:meta #array or hash? :header and :data, however see suggestion that :header or :meta should be separate from :body or :substance
-
-#paragraph operation
-indent 1-9 #if exists want to know how much to indent by, 1-9
-heading #isn't this synonymous with level?
-#keep bold, italic attributes within text?
-
-# :obj container for
-heading?
-paragraph
-block text
-code
-alt
-poem / verse
-table
-image / figure
-
-comment #retain comments?
-
-later investigate use of extroprot (instead of or as well as Marshall)
-consider making easy to represent also as XML
-
-consider:
- additional structure fields to represent document, xml dom, node, sax, pro readily available, can be extended further, con, additional (metaverse) parsing to create them initialy
- xml or html txt field? pro readily available, con bigger objects, more memory