incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1175536 [8/11] - /incubator/ooo/ooo-site/trunk/content/bibliographic/
Date Sun, 25 Sep 2011 19:39:01 GMT
Added: incubator/ooo/ooo-site/trunk/content/bibliographic/detailed enhacement proposals.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/detailed%20enhacement%20proposals.html?rev=1175536&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/bibliographic/detailed enhacement proposals.html (added)
+++ incubator/ooo/ooo-site/trunk/content/bibliographic/detailed enhacement proposals.html Sun Sep 25 19:38:58 2011
@@ -0,0 +1,478 @@
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title></title>
+</head>
+
+<body lang="en-US" link="#6666CC" bgcolor="#ffffff">
+<h2><a name="Project"></a>OpenOffice Bibliographic Project Discussion and
+Issues</h2>
+
+<p>2005-December-4</p>
+
+<h3>Contents</h3>
+<ol>
+  <li><a href="#1">Document Style Options</a></li>
+  <li><a href="#2">Revert to declared style</a></li>
+  <li><a href="#3">And symbols to the automatic footnote numbering
+  scheme.</a></li>
+  <li><a href="#4">Provide Support for Footnote Citation Styles by Adapting
+    the Field Editor for the Bibliography Tables.</a></li>
+  <li><a href="#5">Modify the &#x2018;Bibliographic Entry&gt;Edit&#x2019;
+    Panel to support appropriate field entry options for the citation type
+    selected.</a></li>
+  <li><a href="#6">Defining citations and references different treatment may
+    be needed for first and subsequent use of the citation.</a></li>
+  <li><a href="#7">There needs to be a mechanism for transferring the
+    internal Document Bibliographic entries to and from the database to allow
+    import and export from OpenOffice.</a></li>
+  <li><a href="#8">Some of the Bibliographic Databasefields need to be
+    increased in length.</a></li>
+  <li><a href="#9">Should we persist with the DBASE Bibliographic Database
+    ?</a></li>
+  <li><a href="#10">It would be nice to have search capability to Internet
+    Bibliographic Databases</a></li>
+</ol>
+<hr>
+
+<p align="right"><em>A printer friendly PDF version of this page is available
+<a href="detailed.pdf">detailed.pdf (63Kb)</a></em></p>
+
+<h3><a name="1">1. Add a selection option for 'Document Style' to cover whole
+document.</a></h3>
+
+<p>We need to add user selection for a 'Document Style' to apply to a whole
+document. I see two options for doing this -</p>
+<ol>
+  <li><p>Adding a new tab-panel 'Document Styles' to File&gt;Properties.</p>
+    <p>or</p>
+  </li>
+  <li><p>Adding a new tab-panel 'Document Styles' to Format&gt;Page. (Does
+    Page format only apply to the current section or the whole document ?)</p>
+  </li>
+</ol>
+
+<p>This tab-panel would contain a 'Document Style' selection list which
+include the supported styles eg APA, ASA, Chicago, MLA, German DIN, French
+ISO, etc. {need to collect full list.}. Also we need provision for the users
+to create their own styles. (See the list of BibTeX supported styles <a
+href="bibtex-defs.html">BibTeX supported styles.)</a></p>
+
+<h4><a name="1.1">1.1</a>. Document Style Options</h4>
+
+<p>Other options in the tab panel could be such things as -</p>
+<ul>
+  <li><p>Style Data import / export; (Endnote <sup>(TM)</sup> and Refman
+    <sup>(TM)</sup> provide style definitions to the general public which
+    could be imported if their import format was decoded)</p>
+  </li>
+  <li><p>'Strictly Enforce Style' (Y/N), This would prevent the user
+    modifying the document style aspects defined by the Style Manual. This
+    could make the OO word processor easier to use as many of the functions
+    would be grayed-out. The user would not be so bewildered with choice. The
+    user could at any time turn off 'Strictly Enforce Style', and have access
+    to all settings.</p>
+  </li>
+</ul>
+
+<p>There would also need to be provision for options which are provided by
+the selected style that the user can choose. Eg. The Chicago Style allows
+selection of either in-text, footnote or endnotes, or a dual footnote
+comments endnote citation scheme. Perhaps a 'Style Option' tab would handle
+this.</p>
+
+<p>The information associated with Document Style would include the following
+methods for Bibliographic citation -</p>
+<ul>
+  <li>in-text</li>
+  <li>footnotes</li>
+  <li>endnotes</li>
+  <li>endnotes and footnotes. (requires symbols detailed in item 2 the field
+    formats for Bibliographic citation and Bibliographic Tables (Reference
+    Lists and Bibliographic Lists).</li>
+  <li>special editing for Bibliographic Tables eg repeated author names
+    indicated by a three-em dash eg. (they should be a continuous line not
+    dashes)-</li>
+</ul>
+
+<blockquote>
+  <font>Charles Dickens, <i>A Tale of Two Cities.</i> London: Penguin Books,
+  2000.<br>
+  <span style="font-family: courier">&#x2014;&#x2014;&#x2014;</span>.
+  <i>Nicholas Nickelby.</i> London: Penguin Classics, 1956.<br>
+  <span style="font-family: courier">&#x2014;&#x2014;&#x2014;</span>.
+  <i>Oliver Twist</i>. New York, Random House,1965.</font><br>
+</blockquote>
+
+<h4>1.2. Other Style considerations</h4>
+
+<p>Page formating constraints (the MLA Manual specifies page margins (need to
+check details)<br>
+There may be particular requirements for Section, Chapter and Heading
+styles.</p>
+
+<div align="right">
+<a href="#Project">Top of Page</a></div>
+
+<h4>1.3. Conversion code</h4>
+
+<p>When a new 'Document Style' was selected there would need to be some
+format conversion process that would be applied to an existing document. This
+would change the citation style from the current to the new, the trickiest
+ones to do would be 'author-date in-text' to footnote or endnote or visa
+versa.</p>
+
+<p>An Issue: In order to allow a user change citation methods it will be
+necessary to consider how we treat the footnote entry. It seems to me there
+are two options. Utilise the standard footnote entry code, or to have a
+special citation footnote.</p>
+
+<h3><a name="2">2. Revert to declared style</a></h3>
+
+<p>Is there a 'revert to declared style' function in OpenOffice ? In MS Word
+there is a function that resets text to the declared format. It removes all
+user made minor adjustments with fonts, margins etc. This facility is
+probably required to make the above work and very useful in it own right.</p>
+
+<h3><a name="3">3. And symbols to the automatic footnote numbering
+scheme.</a></h3>
+
+<p>The Chicago Manual of Style stipulates that when Endnotes and Footnotes
+are both used the Endnotes are consecutively numbered (1,2,3 ...) and for the
+Footnotes symbols are to be used. The series they suggest are -</p>
+
+<table width="100%" border="0" cellspacing="0">
+  <tbody>
+    <tr>
+      <td><img src="sym1.gif" name="Graphic1"
+        alt="a list of symbols like # * ect." align="left" width="188"
+        height="47" border="0"></td>
+    </tr>
+    <tr>
+      <td>As more symbols are needed they are doubled and trebled -</td>
+    </tr>
+    <tr>
+      <td><img src="sym2.gif" name="Graphic2"
+        alt="a list of symbols like ## ** ### *** ect." align="left"
+        width="570" height="50" border="0"><br clear="left">
+      </td>
+    </tr>
+  </tbody>
+</table>
+The proposal is to add this set of symbols to the automatic numbering options
+for footnotes.
+
+<p>The processing of the footnotes will need to be adjusted for symbols, as
+the symbol sequence is restarted at the initial symbol ( * ), for each new
+page they are use on.</p>
+
+<h3><a name="4">4.</a> Provide Support for Footnote Citation Styles by
+Adapting the Field Editor for the Bibliography Tables.</h3>
+The current Insert&gt;Indexes and Tables&gt;'Bibliographic Entry' mechanism
+[<a href="biblio1_html_4a7d5d98.png">screen image</a>] which is use to select
+fields and format Tables [including the bibliographic table] should be
+extended to enable defining footnote citation fields. Currently Bibliographic
+Entry has only two options available - selection from bibliographic database
+or document content. Then there is the selection box for the 'short name';
+which is the reference string to be inserted with the text, eg.
+[CharlesE1978]. This mechanism needs to be extended to the footnote or
+endnote method. These methods require this information in a more complex
+format in a footnote or endnote; for example<sup>34</sup>,<br>
+
+
+<blockquote>
+  <font>34. T.M. Charles-Edwards,"Honour and status in Some Irish and Welsh
+  Prose Tales.",<i>Eriu</i>, xxxvi, 1978.</font></blockquote>
+
+<p>The Bibliographic Entry selection box should be changed from 'short name'
+to 'citation type' - Book, Article, Journal Article, Collection etc. A new
+button 'Customise Citation Styles' would bring up a new field selection and
+formating panel very similar (maybe identical) to the table format editor.
+Note that the Citation Style and style options will have been set in the new
+File&gt;Properties tab-panel 'Document Styles' mentioned above at section 1.
+Also the 'Customise Citation Styles' button would be inoperative and greyed
+out if 'Strictly Enforce Style' is set to 'Yes', so as not mess up the style
+settings.</p>
+
+<p>Note: when the citation formats are defined and provided for the various
+Document Style Conventions the average user will not have to use this. All
+the fields will be predefined.</p>
+
+<div align="right">
+<a href="#Project">Top of Page</a></div>
+
+<h3><a name="5">5</a>. Modify the &#x2018;Bibliographic Entry&gt;Edit&#x2019;
+Panel to support appropriate field entry options for the citation type
+selected.</h3>
+
+<p>Currently the Insert&gt;Indexes and Tables&gt;Bibliographic
+Entry&gt;Edit&gt;New Panel [<a href="biblio1_html_1bd246eb.gif">screen
+image</a>] offers a selection box that allows the user to selection citation
+type from a pick list eg Book, Article, Manual, Incollection etc. And is
+presented with a selection of 29 fields in which to place their data. The
+preferred action would be that the selection of a citation type would
+indicate which fields are Required, Optional, or Ignored for that citation
+type. See a screen-print of sixpack as an example of such an <a
+href="sixpack.jpg">editor</a> .</p>
+
+<p>The list of citation types and fields that are used in BibTeX are given
+below and should be considered as a minimum requirement.</p>
+<dl>
+    <dd><strong>article</strong> - An article from a journal or magazine.
+      Required fields: <tt>author</tt>, <tt>title</tt>, <tt>journal</tt>,
+      <tt>year</tt>. Optional fields: <tt>volume</tt>, <tt>number</tt>,
+      <tt>pages</tt> , <tt>month</tt>, <tt>note</tt>.</dd>
+    <dd><strong>Book</strong> - A book with an explicit publisher. Required
+      fields: <tt>author</tt> or <tt>editor</tt>, <tt>title</tt>,
+      <tt>publisher</tt> , <tt>year</tt>. Optional fields: <tt>volume</tt> or
+      <tt>number</tt> , <tt>series</tt>, <tt>address</tt>, <tt>edition</tt>,
+      <tt>month</tt> , <tt>note</tt> .</dd>
+    <dd><strong>Booklet</strong> - A work that is printed and bound, but
+      without a named publisher or sponsoring institution. Required field:
+      <tt>title</tt>. Optional fields: <tt>author</tt>, <tt>howpublished</tt>
+      , <tt>address</tt>, <tt>month</tt>, <tt>year</tt>, <tt>note</tt>.</dd>
+    <dd><strong>Conference</strong> - The same as <tt>INPROCEEDINGS</tt> ,
+      included for <i>Scribe</i> compatibility.</dd>
+    <dd><strong>Inbook</strong> - A part of a book, which may be a chapter
+      (or section or whatever) and/or a range of pages. Required fields:
+      <tt>author</tt> or <tt>editor</tt>, <tt>title</tt>, <tt>chapter</tt>
+      and/or <tt>pages</tt>, <tt>publisher</tt>, <tt>year</tt> . Optional
+      fields: <tt>volume</tt> or <tt>number</tt>, <tt>series</tt>,
+      <tt>type</tt> , <tt>address</tt>, <tt>edition</tt>, <tt>month</tt>,
+      <tt>note</tt>.<br>
+      <strong>Incollection</strong> - A part of a book having its own title.
+      Required fields: <tt>author</tt>, <tt>title</tt>, <tt>booktitle</tt>,
+      <tt>publisher</tt>, <tt>year</tt>. Optional fields: <tt>editor</tt>,
+      <tt>volume</tt> or <tt>number</tt>, <tt>series</tt>, <tt>type</tt>,
+      <tt>chapter</tt> , <tt>pages</tt>, <tt>address</tt>, <tt>edition</tt>,
+      <tt>month</tt> , <tt>note</tt>.<br>
+      <strong>Inproceedings</strong> - An article in a conference
+      proceedings. Required fields: <tt>author</tt>, <tt>title</tt>,
+      <tt>booktitle</tt>, <tt>year</tt>. Optional fields: <tt>editor</tt>,
+      <tt>volume</tt> or <tt>number</tt>, <tt>series</tt>,
+      <tt>pages</tt>,<tt>address</tt>, <tt>month</tt> ,
+      <tt>organization</tt>, <tt>publisher</tt>, <tt>note</tt> .<br>
+      <strong>Manual</strong> - Technical documentation. Required field:
+      <tt>title</tt>. Optional fields: <tt>author</tt>,
+      <tt>organization</tt>, <tt>address</tt>, <tt>edition</tt>,
+      <tt>month</tt>, <tt>year</tt>, <tt>note</tt>.<br>
+      <strong>Mastersthesis</strong> - A Master's thesis. Required fields:
+      <tt>author</tt>, <tt>title</tt>, <tt>school</tt>, <tt>year</tt> .
+      Optional fields: <tt>type</tt>, <tt>address</tt>, <tt>month</tt>,
+      <tt>note</tt> .<br>
+      <strong>Misc</strong> - Use this type when nothing else fits. Required
+      fields: none. Optional fields: <tt>author</tt>, <tt>title</tt>,
+      <tt>howpublished</tt>, <tt>month</tt>, <tt>year</tt>, <tt>note</tt>.<br>
+      <strong>Phdthesis</strong> - A PhD thesis. Required fields:
+      <tt>author</tt>, <tt>title</tt>, <tt>school</tt>, <tt>year</tt> .
+      Optional fields: <tt>type</tt>, <tt>address</tt>, <tt>month</tt>,
+      <tt>note</tt>.<br>
+      <strong>Proceedings</strong> - The proceedings of a conference.
+      Required fields: <tt>title</tt>, <tt>year</tt>. Optional fields:
+      <tt>editor</tt>, <tt>volume</tt> or <tt>number</tt>, <tt>series</tt>,
+      <tt>address</tt> , <tt>month</tt>, <tt>organization</tt>,
+      <tt>publisher</tt>, <tt>note</tt>.<br>
+      <strong>Techreport</strong> - A report published by a school or other
+      institution, usually numbered within a series. Required fields:
+      <tt>author</tt>, <tt>title</tt>, <tt>institution</tt>, <tt>year</tt>.
+      Optional fields: <tt>type</tt>, <tt>number</tt>, <tt>address</tt> ,
+      <tt>month</tt>, <tt>note</tt>.<br>
+      <strong>Unpublished</strong> - A document having an author and title,
+      but not formally published. Required fields: <tt>author</tt>,
+      <tt>title</tt>, <tt>note</tt>. Optional fields: <tt>month</tt>,
+      <tt>year</tt>.</dd>
+</dl>
+
+<p><a href="bibtex-defs.html">The full text with field definitions and usage
+hints.</a></p>
+
+<div align="right">
+<a href="#Project">Top of Page</a></div>
+
+<h3><a name="6">6.</a> Defining citations and references different treatment
+maybe needed for first and subsequent use of the citation.</h3>
+
+<p>There is a tedious and fault prone aspects of the footnote / endnote
+citation method - the maintenance the Initial and Subsequent citations in the
+correct order as one edits the text. In the mad rush to complete the paper as
+the deadline approaches, a piece of text is moved and the Initial Citation
+reference now comes after the Subsequent reference, and the examiner gives
+you a red mark.</p>
+
+<p>I do not know enough about the internals of OpenOffice to suggest how this
+would be implemented. Two options would be to include a check after
+bibliographic entry or to check and adjust when the update fields function is
+activated. This would require the citation field to have an identifier which
+signified that a citation's initial and subsequent appearances were related
+to the same reference in order to check if the current Initial citation is
+still the initial one after some text editing. That is not using string
+matching but reference identifiers.</p>
+
+<p>This also requires that with style that require it all of the citation
+formats will have two versions; the full initial one and the shorter
+subsequent one.</p>
+
+<p>Example. An Initial Reference -</p>
+
+<blockquote>
+  <font>'Oisin and Patrick' in <i>Irish Myths and Legends</i>, Lady Gregory.
+  (London: Running Press, 1989), 412-421.</font></blockquote>
+
+<p>A Subsequent Reference -</p>
+
+<blockquote>
+  <font>'Oisin and Patrick' in <i>Irish Myths and Legends</i>,
+450.</font></blockquote>
+or just -
+
+<blockquote>
+  <font>'Oisin and Patrick', 25.</font></blockquote>
+
+<h4>6.1. Some Implementation Issues</h4>
+
+<p>In order to allow a user change citation methods it will be necessary to
+consider how we treat the footnote / endnote entry. It seems to me there are
+two options. Utilise the standard footnote / endnote entry code, or to have a
+special citation footnote.</p>
+
+<p>I will give some examples. A document has in-text author-date citations.
+This is what is currently implemented. eg.</p>
+
+<blockquote>
+  <font>The story of Finn (Gregory1989) is central to our
+argument.</font>/</blockquote>
+
+<p>We now change the citation setting to footnote method and it deletes the
+In-text field, creates a footnote and places the citation field into the
+footnote.</p>
+
+<blockquote>
+  <font>The story of Finn<sup>1</sup> is central to our argument.<br>
+  </font> -----<br>
+  <font>1. Lady Gregory,<i>Irish Myths and Legends</i> ,. (London: Running
+  Press, 1989)</font></blockquote>
+
+<p>This seems simple enough. But what happens if we are starting with the
+footnote / endnote style, and change to the in-text style. Will it be just as
+simple a matter to find all the bibliographic entries, go to the footnote /
+endnote reference, delete the footnote / endnote and insert a new in-text
+author-date citations? What do we do if the user has added extra text into
+citation footnote / endnote ? -</p>
+
+<blockquote>
+  <font>1. Lady Gregory ,<i>Irish Myths and Legends</i>,. (London: Running
+  Press, 1989) Note that this was originally published in
+1903.</font></blockquote>
+
+<p>Do we than leave the footnote / endnote with just the added text? And
+deleted if there was no added text ?</p>
+
+<blockquote>
+  <font>The story of Finn (Gregory1989) <sup>1</sup> is central to our
+  argument. eg.<br>
+  -----</font><br>
+  <font>1. Note that this was originally published in
+1903.</font></blockquote>
+As more symbols are needed they are doubled and trebled - The proposal is to
+add this set of symbols to the automatic numbering options for footnotes.
+
+<p>Would it help to have a special field for footnote / endnote or citations,
+and if we did how do we deal with added comments? A user writable text area
+with the citation field ?</p>
+
+<div align="right">
+<a href="#Project">Top of Page</a></div>
+
+<h4>6.2 The inset citation dialog will need to support types of citations
+within a citation style.</h4>
+
+<p>This will be required in order to support the following type of citation
+system -</p>
+
+<p>If I quote a document(book/journal/article etc.) without a page it looks
+like</p>
+
+<p>"This method is very reliable (AUTHOR YEAR)"<br>
+f.e. "This method is very reliable (BASLER 2003)<br>
+or<br>
+"But AUTHOR (YEAR) showed that..."<br>
+f.e. "But WILSON(2002) showed that this method is not very reliable."<br>
+If a page or some pages are quoted (direct or indirect) it must look like<br>
+"'This method is very reliable' (AUTHOR YEAR:12)"<br>
+f.e. "'This method is very reliable' (BASLER 2003:12)"<br>
+or<br>
+"'This method is very reliable' (BASLER 2003:12 ff.)"<br>
+or<br>
+"AUTHOR (YEAR:12) stated 'This method is very reliable.'"<br>
+f.e. "BASLER (2003:12) stated 'This method is very reliable.'"<br>
+or<br>
+"BASLER (2003:12 f.) concludes that this method is very reliable.'"</p>
+
+<p><br>
+Some comments on that:<br>
+1. The AUTHOR(s) must be in small capitals (as every person everywhere in the
+text).<br>
+2. One author: "AUTHOR 2003" Two authors: "AUTHOR1 &amp; AUTHOR2 2003" Three
+or more: "AUTHOR1 ET AL. 2003"</p>
+
+<p>If there are more than one publication of an author in the same year it
+must look like:<br>
+"BASLER 2003a" and "BASLER 2003b" a.s.o.<br>
+In the bibliography the above example would look like<br>
+BASLER, M. (YEAR): Book title. City1 et al.<br>
+or<br>
+BASLER, M. &amp; D. WILSON (YEAR): Book title. City1 et al. or BASLER, M. D.,
+WILSON, A. NONAME &amp; B. NONAME (YEAR): Book title. City1 et al.</p>
+
+<p>Note that in the bibliography index ALL authors including their initials
+must be stated, in the text citations only the first, followed by "ET AL."</p>
+
+<div align="right">
+<a href="#Project">Top of Page</a></div>
+
+<h3><a name="7">7.</a> There needs to be a mechanism for transferring the
+internal Document Bibliographic entries to and from the database to allow
+import and export from OpenOffice.</h3>
+
+<p>Currently if a users creates Bibliographic entries with the
+Insert&gt;Indexes and tables&gt;Bibliographic Entry&gt;New function, these
+entries can not be easily exported from the document.</p>
+
+<p>As the first priority there needs to be an export and import of
+bibliographic data in the BibTeX format. As this is the most common format
+and the one most other bibliographic tools will utilise.</p>
+
+<h3><a name="8">8. Some of the Bibliographic Database fields need to be
+increased in length.</a></h3>
+
+<p>Some users have run into the field length limit of the varchar datatype
+(or of the Input form). At least Title and Authors, and possibly some others
+should be made longvarchar. Currently if the user changes the field
+definitions in the database the bibliographic functions - Bibliographic
+Entry, and Bibliographic Table cease to work on the altered table. Some
+journal articles have hundreds of authors !</p>
+
+<h3><a name="9">9.</a> Should we persist with the DBASE Bibliographic
+Database?</h3>
+
+<p>Or, to replace it with storage in BibTeX format and utilise other
+OpenSource (eg. sixpack or pybliographer) work (code or design) for a BibTeX
+editor and browser. We should also check the OpenOffice Database project for
+their view and plans.</p>
+
+<h3><a name="10">10.</a> It would be nice to have search capability to
+Internet Bibliographic Database</h3>
+
+<p>P.S from an Institute of Biochemistry requested the ability to connect and
+query on-line databases (like Medline), or at least import records from saved
+queries. He wrote - "PubMed for example would allow your browser to save the
+queries in several formats that are easy to import."</p>
+
+<div align="right">
+<p><a href="#Project">Top of Page</a></p>
+</div>
+<hr>
+
+<p>By <a href="mailto:dnw@openoffice.org">David N. Wilson</a></p>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/detailed enhacement proposals.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/detailed.pdf
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/detailed.pdf?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/detailed.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/developer.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/developer.html?rev=1175536&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/bibliographic/developer.html (added)
+++ incubator/ooo/ooo-site/trunk/content/bibliographic/developer.html Sun Sep 25 19:38:58 2011
@@ -0,0 +1,30 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="content-type" content="text/html; charset=us-ascii">
+  <title></title>
+  <link>
+  <meta http-equiv="content-type" content="text/html; charset=us-ascii">
+</head>
+
+<body lang="en">
+<h2>Bibliographic <a name="Project" id="Project">Project</a>'s Developer
+Page</h2>
+
+<table width="95%" border="0">
+  <tbody>
+    <tr>
+      <td>This page has been rolcated to a wiki page <a
+        href="http://wiki.services.openoffice.org/wiki/Bibliographic_Project's_Developer_Page">wiki.services.openoffice.org/wiki/Bibliographic_Project's_Developer_Page</a>
+
+        <p></p>
+      </td>
+      <td>
+        <div align="right">
+        <a href="#Project"></a></div>
+      </td>
+    </tr>
+  </tbody>
+</table>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/developer.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/developer.pdf
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/developer.pdf?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/developer.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.html?rev=1175536&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.html (added)
+++ incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.html Sun Sep 25 19:38:58 2011
@@ -0,0 +1,468 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="content-type" content="text/html; charset=us-ascii">
+  <title></title>
+  <link>
+  <meta http-equiv="content-type" content="text/html; charset=us-ascii">
+</head>
+
+<body lang="en">
+<h2><a name="Bibliograp" id="Bibliograp">Bibliographic</a> <a name="Project"
+id="Project">Project</a>'s Developer Page</h2>
+
+<table width="98%" border="0">
+  <tbody>
+    <tr>
+      <td>Last Modified 2005-December-9</td>
+      <td style="text-align: right"><em>A printer friendly PDF version of
+        this page is available <a href="developer1.pdf">developer1.pdf
+        (36Kb)</a></em></td>
+    </tr>
+  </tbody>
+</table>
+
+<h3>Contents</h3>
+<ul>
+  <li><a href="#Projects">Project Overview</a></li>
+  <li><a href="#L1071">1st Stage, Bibliographic Facility Redevelopment</a>
+    <ul>
+      <li>Modify the Writer document-read and document-save modules to
+        support the new OpenDocument enhanced citation format.</li>
+      <li>Modify the writer code to insert and display the new format
+        citations.</li>
+      <li>Add support in the OOo save file package for storage of document
+        bibliographic data an the code changes necessary to read and save
+        that bibliographic data.</li>
+      <li>Modify the Writer save-file read and save modules to support the
+        new the bibliographic data file in the document save package.</li>
+    </ul>
+  </li>
+</ul>
+<ul>
+  <li><a href="#L1075">2nd Stage, Bibliographic Facility Redevelopment</a>
+    <ul>
+      <li>Add Backwards and Forwards Compatability Logic to Writer</li>
+      <li>Add Z39.50 and SRU/W support for the Bibliographic modules.</li>
+      <li>Design and Build a basic Graphical User Interface (GUI)</li>
+    </ul>
+  </li>
+</ul>
+<ul>
+  <li><a href="#Further">Further References</a></li>
+  <li><a href="#started">How to get started</a></li>
+  <li><a href="#Sample">Sample code</a></li>
+  <li><a href="#Contacts">Contacts</a></li>
+</ul>
+<hr>
+
+<h3>Project <a name="Overview" id="Overview">Overview</a></h3>
+The Bibliographic Project (OOoBib) plans to enhance the bibliographic
+functions of the OpenOffice.org Writer (wordprocessing) application to
+achieve:
+<ol>
+  <li>Enhance bibliographic formatting to support:
+    <p>a. complex features required of commonly used citation styles like APA
+    and Chicago.</p>
+    <p>b. automatically switching between potentially radically different
+    citation styles (ie. footnote to in-text).</p>
+  </li>
+  <li>Enhance data model to support a broader range of reference types.</li>
+  <li>Add support for connection to remote database.</li>
+</ol>
+
+<p>Our current objective is to design and build OOoBib version 0.1, which
+will contain the most basic functions for an usable bibligraphic facility
+with the above features.</p>
+
+<table border="0" width="100%">
+  <tbody>
+    <tr>
+      <td><h3><a name="L1071" id="L1071">1st Stage</a>, Bibliographic
+        Facility Redevelopment</h3>
+      </td>
+      <td align="right"><p><a href="#Bibliograp">top of page</a></p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<h4>Summary</h4>
+
+<p>As our first step, we will implement the most simple changes to the OOo
+core code (the API basic code, and UNO mappings, but not yet the user
+interface code) necessary to implement basic support for:</p>
+<ol>
+  <li>Support saving and reading enhanced citation support in
+  OpenDocument</li>
+  <li>Ability to insert and display citations in OpenOffice Writer using the
+    new format. (Note this task does not include the GUI interface to insert
+    the citation in the new format, only the UNO interface to provide the
+    basic function.</li>
+  <li>Storage of document bibliographic data in the OOo document save package
+    and the code changes necessary to read and save that bibliographic
+  data.</li>
+</ol>
+
+<p>When these basic functions are built into OOo and are made assessable via
+the UNO, we can then use rapid prototyping development methods to design and
+build prototype GUI interfaces and bibliographic formatting engines. We will
+be able to use any of the programming languages which have OpenOffice
+bindings: C++, Java, Python and, of course, OpenOffice Basic. We believe that
+we will find more developers who can work in these languages than by
+insisting on C++ code from the start. Also it is much easier to build
+prototypes using Java, Python and OpenOffice Basic than in C++.</p>
+
+<p><strong>NB</strong>. When we have designed, built and tested the
+prototypes and they have been accepted by the OOo community we intend to
+rebuild them in C++ and to have them made part of the core OpenOffice
+application.</p>
+<hr>
+
+<p><strong>Skills required</strong> - good C++ programming and some XML
+skills with knowledge of, or willingness to learn, the OpenOffice UNO (see
+the <a
+href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">Openoffice
+Developer's Guide</a>)</p>
+<hr>
+
+<h4>1. Modify the Writer document-read and document-save modules to support
+the new OpenDocument enhanced citation format.</h4>
+
+<p>Implement the citation and bibliography changes to the OOo Writer save
+file (in Open Document format) accepted by the <a
+href="http://lists.oasis-open.org/archives/office/200409/msg00023.html">OpenDocument
+Technical Committee</a>. The changes to the document schema are detailed in
+our <a
+href="http://bibliographic.openoffice.org/XML-bibliography-proposal.pdf">OpenDocument
+XML Citation Proposal.pdf</a></p>
+
+<p>Here are two examples of the new citation format. The first is a standard
+author-year style, with additional page number details:</p>
+
+<p><code>&lt;cite:citation
+xmlns:cite="http://purl.org/NET/xbiblio/cite/1.0"</code><br>
+<code>
+xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"&gt;</code><br>
+<code> &lt;cite:citation-source&gt;</code><br>
+<code> &lt;cite:biblioref cite:key="Veer1996a"&gt;</code><br>
+<code> &lt;cite:detail cite:units="pages" cite:begin="23"
+cite:end="24"/&gt;</code><br>
+<code>&lt;/cite:biblioref&gt;</code><br>
+<code>&lt;/cite:citation-source&gt;</code><br>
+<code>&lt;cite:citation-body&gt;</code><br>
+<code> &lt;text:span text:style-name="Citation"&gt;(Veer,
+1996:</code><code>23-24)&lt;/text:span&gt;</code><br>
+<code>&lt;/cite:citation-body&gt;</code><br>
+<code>&lt;/cite:citation&gt;</code></p>
+
+<p>The second is a footnoted example.</p>
+
+<p><code>&lt;cite:citation
+xmlns:cite="http://purl.org/NET/xbiblio/cite/1.0"</code><br>
+<code>
+xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"&gt;</code><br>
+<code> &lt;cite:citation-source&gt;</code><br>
+<code> &lt;cite:biblioref cite:key="Veer1996a"/&gt;</code><br>
+<code> &lt;/cite:citation-source&gt;</code><br>
+<code> &lt;cite:citation-body&gt;</code><br>
+<code> &lt;text:note text:id="ftn0" text:note-class="footnote"&gt;</code><br>
+<code> &lt;text:note-citation&gt;1&lt;/text:note-citation&gt;</code><br>
+<code> &lt;text:note-body&gt;</code><br>
+<code> &lt;text:p text:style-name="Footnote"&gt;Peter van der Veer
+(1996)</code><br>
+<code>Riots and Rituals: The</code><code> Construction of Violence and Public
+Space in HindU</code><code>Nationalism, In Paul Brass Ed., Riots</code><code>
+and Pogroms (New York:NYU Press) 154&#x2013;76.&lt;/text:p&gt;</code><br>
+<code> &lt;/text:note-body&gt;</code><br>
+<code> &lt;/text:note&gt;</code><br>
+<code> &lt;/cite:citation-body&gt;</code><br>
+<code>&lt;/cite:citation&gt;</code></p>
+
+<p>To compare this to the current format see <a
+href="implementation.html">implementation</a>. The changes to the document
+schema need to be supported by the document save and load modules. These are
+detailed into the <a href="#Further">Further References</a> below.</p>
+
+<h4>2. Modify the writer code to insert and display the new format
+citations</h4>
+
+<p>The bibliographic modules in OOo Writer need to modified to support the
+new schema. The modules that need to be modified are</p>
+<ul>
+  <li><a href="implementation.html#text">Bibliography</a></li>
+  <li><a href="implementation.html#text1">textfield/Bibliography</a></li>
+  <li><a href="implementation.html#text2">FieldMaster/Bibliography</a></li>
+  <li><a href="implementation.html#text3">BibliographyDataField</a></li>
+</ul>
+
+<h4>3. Add support in the OOo save file package for storage of document
+bibliographic data.</h4>
+
+<p>Currently the Writer saves a complete copy of the bibliographic data
+associated with a citation, with each ciation. We propose to separate the
+citation and the bibliographic data, by leaving just the citation details in
+the document save file and place the detailed bibliographic data in a
+seperate bibliographic data file the OOo save file package.</p>
+
+<p>The task is to complete the design of the bibliographic data file and add
+support for it in the OOo save file package.</p>
+
+<h4><strong>4. Modify the Writer save-file read and save modules to support
+the new the bibliographic data file in the document save
+package.</strong></h4>
+
+<p>The relevant component is "<a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/frame/XComponentLoader.html">interface
+XComponentLoader</a>" which supports <em>loadComponentFromURL</em> and
+<em>storeAsURL.</em></p>
+
+<h4>5. Refine and Improve the CITEPROC bibliographic formating engine.</h4>
+
+<p>Experience XSLT programers are needed to work on this core component of
+the Bibliographic facility. It is functioning and a book has been published
+which used it to format the bibliographic table and citations.</p>
+
+<p>We propose to build Bibliographic table and citation formating using XSLT
+style-sheets with a process called <a
+href="http://bibliographic.openoffice.org/citeproc/index.html">CiteProc</a>.
+Also see <a href="http://www.silmaril.ie/bibliox/biblioxdoc.html">BiblioX</a>
+for technical discusion of this approach.</p>
+<hr>
+
+<table border="0" width="100%">
+  <tbody>
+    <tr>
+      <td><h3><a name="L1075" id="L1075">2nd Stage</a>, Bibliographic
+        Facility Redevelopment</h3>
+      </td>
+      <td align="right"><p><a href="#Bibliograp">top of page</a></p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<h4>1. Add Backwards and Forwards Compatability Logic to Writer</h4>
+
+<p>An important object of Bibliographic Enhancement project is to maintain
+document file backwards compatibility with older versions of OpenOffice. To
+achieve this when Bibliographic Entries are inserted into a Document they are
+stored with the same format as is currently the case. A new bibliographic
+entry tag will be will be added with the enhanced citation functions, each
+citation will contain a key that will point to the bibliographic data which
+will be saved in the document save package. To preserve backwards
+compatability we will need to also maintain the old bibliographic ciation and
+dtat storage in the document. Older version of OpenOffice, without the
+bibliographic enhacments, in the OOo 2.X .ods format, will read the old
+format of the bibliographic citations and ignore the bibliographic data file
+in the save package. A suggested approach is illustrated in this <a
+href="backwards.png">flowchart.</a></p>
+
+<p>When a major revision of the save package format is introduced the support
+of the older bibliographic representations can be dropped form the document
+save file.</p>
+
+<h4>2. Add Z39.50 and SRU/W support for the Bibliographic modules.</h4>
+
+<p>Build <a href="biblio-sw.html#ZING">Z39.50</a> and <a
+href="biblio-sw.html#ZING">SRU/W</a> based internet searching facility using
+the <a href="http://www.indexdata.dk/yaz/">YAZ</a> toolkit. This would enable
+searching for and retrieving bibliographic data from internet sources and
+storing them in a document or bibliographic database.</p>
+
+<p>Also build Z39.50 and SRU/W server capability into OOo to enable users to
+share their bibliographic (and other) databases over the internet. One of the
+<a href="http://www.indexdata.dk/">Indexdata</a> toolkits could probably used
+as a basis.</p>
+
+<p>The modules that may need to be modified are:</p>
+<ul>
+  <li><a href="implementation.html#text">Bibliography</a></li>
+  <li><a href="implementation.html#text1">textfield/Bibliography</a></li>
+  <li><a href="implementation.html#text2">FieldMaster/Bibliography</a></li>
+  <li><a href="implementation.html#text3">BibliographyDataField</a></li>
+</ul>
+
+<p><strong>NB</strong>: We are considering using SWU/W as the standard method
+for OOo retrieving bibliographic data from any source. So that even a local
+Bibliographic database would also be accessed through SWU/W methods. The user
+would just select a local or remote source and the same access mechanism
+would be used.</p>
+
+<h4>3. Design and Build a basic Graphical User Interface (GUI). To provide
+-</h4>
+<ul>
+  <li>Basic citation insertion</li>
+  <li>Basic bibliographic data entry</li>
+  <li>Citation and bibliographic table formating using Citeproc.</li>
+  <li>Basic Bibliographic database access</li>
+  <li>Basic bibliographic internet search and database storage.</li>
+</ul>
+
+<table border="0" width="100%">
+  <tbody>
+    <tr>
+      <td><hr>
+
+        <h3><a name="Further" id="Further">Further</a> References</h3>
+
+        <p>For an overview of the Bibliographic project's major components
+        and a context diagram see <a
+        href="components.html">components.html.</a> There is information
+        about the current OpenOffice Bibliographic <a
+        href="implementation.html">implementation</a>.</p>
+
+        <p>A start has been made to the Specification for this work (see the
+        <a
+        href="http://bibliographic.openoffice.org/servlets/ProjectDocumentList?folderID=266">
+        Projects Specifications folder</a> on the Documents and Files page).
+        Also see a attempt at an <a
+        href="mindmap/content-analysis.html">analysis</a> of the proposed
+        Bibliographic enhancement components and their relationships.</p>
+
+        <p>The best place to start for finding out about development in
+        OpenOffice is the <a
+        href="http://development.openoffice.org/index.html">OpenOffice.org
+        For Developers</a> page. An important resource is the Developer's
+        guide which is part of the SDK (software development kit) or
+        available online on at <a
+        href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html</a></p>
+
+        <p style="margin-bottom: 0cm">The <a
+        href="http://api.openoffice.org">OOo API</a> is based on <a
+        href="http://udk.openoffice.org">UNO (Universal Network Objects)</a>
+        is the interface-based component model of OpenOffice.org. UNO offers
+        interpretability between different programming languages, different
+        object models, different machine architectures and different
+        processes; either in a local network or even via the Internet. UNO
+        components can be implemented in and accessed from any programming
+        language for which a UNO language binding exists. We currently
+        provide several language bindings for UNO which allows to use the API
+        from Java, C++, OpenOffice.org Basic, Python and Common Language
+        Infrastructure (CLI).</p>
+
+        <p>Implementing the new citation element in <em>xmloff</em> (the
+        XmlOffice module) is a routine task. The Sun developers want to do it
+        together with our programmer, so that he/she can learn how
+        <em>xmloff</em> works.</p>
+
+        <p>To modify the Writer save-file read and save modules to support
+        the new the bibliographic data file in the document save package, and
+        to support <a href="backwards.png">backwards and forwards</a>
+        compatability logic to Writer the "<a
+        href="http://api.openoffice.org/docs/common/ref/com/sun/star/frame/XComponentLoader.html">interface
+        XComponentLoader</a>", which supports <em>loadComponentFromURL</em>
+        and storeAsURL, needs to be enhanced. See the Development Guide
+        explanation for - <a
+        href="http://api.openoffice.org/docs/DevelopersGuide/OfficeDev/OfficeDev.xhtml#1_1_5_Handling_Documents">6.1.5
+        Handling Documents</a>.</p>
+
+        <p>There is also a demonstration client program for the <a
+        href="http://www.indexdata.dk/yaz/">YAZ</a> toolkit (C &amp; C++). -
+        <a href="http://www.indexdata.dk/irtcl/">IRTCL</a> that can perform
+        the reference searches. (Requires YAZ and Tcl/Tk libraries be
+        installed). It does everything but save or export the results !
+        However it is good model of how to use the toolkit and could be used
+        as the basis for or model of a prototype internet searching facility.
+        <a href="http://bibliographic.openoffice.org/irclient.jpeg">Screen
+        pic</a>, <a href="irclient-setup.png">screen pic2</a>.</p>
+
+        <p>A demonstration internet searching facility that writes selected
+        bibliographic records back to the OOo bibliographic database has been
+        written in Python - <a
+        href="http://bibliographic.openoffice.org/files/documents/124/1675/PyOOBib-02.zip">PyOOBib</a>,
+        <a
+        href="http://bibliographic.openoffice.org/files/documents/124/2446/file_2446.dat?filename=PyOOBib%20Instructions%2esxw">instructions</a>
+        are available. Various problems with OOo Python have lead to us
+        concluding that YAZ in C++ would be a better foundation than the
+        Python code.</p>
+
+        <p>There is <a
+        href="http://xml.openoffice.org/package.html">description</a> of the
+        OOo save-file XML Package, and is a <a
+        href="http://xml.openoffice.org/faq.html#4">FAQ</a> about it.</p>
+      </td>
+      <td align="right"><a href="#Bibliograp">top of page</a></td>
+    </tr>
+  </tbody>
+</table>
+<hr>
+
+<table border="0" width="100%">
+  <tbody>
+    <tr>
+      <td><h3>How to get <a name="started" id="started">started</a></h3>
+      </td>
+      <td align="right"><p><a href="#Bibliograp">top of page</a></p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<p>Access to the source code for this project is available for download via
+CVS. A child work space has been created for us called "metabib" which
+contains a copy of the <a
+href="http://xml.openoffice.org/source/browse/xml/xmloff"><em>xmloff</em></a><em>
+</em>(OpenOffice.org XML File Format Definition) and<em> </em><a
+href="http://sw.openoffice.org/source/browse/sw/">sw</a> (the word processor
+application component and the WYSIWYG HTML editor component) code.</p>
+
+<p>The down load size will be about 1GB(?). And you will need about 2GB of
+disk space to compile the metabib CWS (Child-Work-Space). ( <a
+href="http://eis.services.openoffice.org/EIS2/servlet/cws.ShowCWS?Id=3272&amp;Path=SRC680%2Fmetabib ">Web
+access to CWS</a> ).  If you can not handle that size download then ask us
+about sending it to you on cdroms.</p>
+
+<p>Administration process - you first need to sign the JCA and then obtain
+the ssh key. After that we will show you how you can access the 'CWS'. It's
+basically a CVS branch. The most complicated thing is the setup of your
+tools, such that you can participate in the OOo development --- but, when you
+have got the ssh key we will show you.</p>
+
+<p>See <a href="http://development.openoffice.org/index.html">OpenOffice.org
+For Developers</a> for general development information.</p>
+<hr>
+
+<table border="0" width="100%">
+  <tbody>
+    <tr>
+      <td><h4><a name="Sample" id="Sample">Sample</a> Code</h4>
+      </td>
+      <td align="right"><a href="#Bibliograp">top of page</a></td>
+    </tr>
+  </tbody>
+</table>
+<ul>
+  <li>Sample python code that reads and outputs some of the fields of the
+    records in the bibliographic database. <a
+    href="http://udk.openoffice.org/python/samples/biblioaccess.py">biblioacess.py</a></li>
+  <li>Sample OpenOffice Basic program to write records to the bibliographic
+    database <a href="Bibwrite.html">bibwrite.html</a>
+    <li>A python script that reads RIS format files containing one or more
+    references and inserts them into the default
+    OpenOffice.orgBibliography/'biblio' database. <a
+    href="biblio-sw.html#RISImport.">RISImport.py</a></li>
+  </li>
+  <li>Henrik Just's LaTeX and BibTeX export filter <a
+    href="http://www.hj-gym.dk/~hj/writer2latex/">http://www.hj-gym.dk/~hj/writer2latex/</a></li>
+  <li>Applications which interact with Openoffice- <a
+    href="biblio-sw.html#Bibus">Bibus</a> (WxPython) and <a
+    href="biblio-sw.html#B3">B3</a> (Java).</li>
+  <li>A Perl module <a
+    href="http://search.cpan.org/~jmgdoc/OpenOffice-OODoc/OODoc/Intro.pod">OpenOffice::OODoc</a>
+    provides a simple way to access document elements in the (closed i.e. not
+    interactive with OOo) document save file. An <a
+    href="bibquery.perl">example</a> which retrieves bibliographic details is
+    provided.</li>
+</ul>
+
+<h3><a name="Contacts" id="Contacts">Contacts</a></h3>
+
+<p>Question or comments can be put to the Bibliographic Project development
+list <a
+href="mailto:dev@bibliographic.openoffice.org">dev@bibliographic.openoffice.org</a>
+or to the project co-leader <a href="mailto:dnw@openoffice.org">David
+Wilson.</a></p>
+<hr>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.pdf
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.pdf?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/developer1.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/enhanced-save-package-description.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/enhanced-save-package-description.html?rev=1175536&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/bibliographic/enhanced-save-package-description.html (added)
+++ incubator/ooo/ooo-site/trunk/content/bibliographic/enhanced-save-package-description.html Sun Sep 25 19:38:58 2011
@@ -0,0 +1,486 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
+  <title></title>
+  <meta name="AUTHOR" content="David Wilson">
+  <meta name="CREATED" content="20060104;15195400">
+  <meta name="CHANGEDBY" content="David Wilson">
+  <meta name="CHANGED" content="20060104;15211100">
+  <style>
+        <!--
+PRE.cjk { font-family: "Gothic", monospace }
+TH P { font-style: italic }
+-->
+
+
+
+
+
+
+
+        </style>
+</head>
+
+<body lang="en-AU" dir="ltr">
+<p align="center"><font size="4" style="font-size: 16pt"><b>Current and
+Proposed Bibliographic enhancements to the contents of the writer save
+package</b></font></p>
+
+<table width="100%" border="1" cellpadding="4" cellspacing="0">
+  <col width="50%"><col width="50%" align="left"><tbody>
+    <tr valign="top">
+      <th><p>Current Writer save file contents.xml example</p>
+      </th>
+      <th><p>Proposed Writer save file contents.xml example</p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td><pre class="western"><font size="2"><u><b>Document Header Stuff</b></u></font>
+
+<font size="2">&lt;?xml version="1.0" encoding="UTF-8"?&gt;</font>
+<font size="2">&lt;office:document-content xmlns:office=
+"urn:oasis:names:tc:opendocument:xmlns:office:1.0
+" xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0
+" xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0
+" xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0
+" xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0
+" xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0
+" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:dc=
+"http://purl.org/dc/elements/1.1/" 
+xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0" 
+
+xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0
+" xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0
+" xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0
+" xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0
+" xmlns:math="http://www.w3.org/1998/Math/MathML
+" xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0
+" xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0
+" xmlns:ooo="http://openoffice.org/2004/office" xmlns:ooow=
+"http://openoffice.org/2004/writer" xmlns:oooc=
+"http://openoffice.org/2004/calc" xmlns:dom=
+"http://www.w3.org/2001/xml-events" xmlns:xforms=
+"http://www.w3.org/2002/xforms" xmlns:xsd=
+"http://www.w3.org/2001/XMLSchema" xmlns:xsi=
+
+"http://www.w3.org/2001/XMLSchema-instance" office:version="1.0"&gt;</font>
+<font size="2">&lt;office:scripts/&gt;</font>
+<font size="2">&lt;office:font-face-decls&gt;</font>
+<font size="2">&lt;style:font-face style:name="Tahoma1" svg:font-family="Tahoma"/&gt;</font>
+<font size="2">&lt;style:font-face style:name=
+"Gothic" svg:font-family="Gothic" style:font-pitch="variable"/&gt;</font>
+<font size="2">&lt;style:font-face style:name=
+"Mincho" svg:font-family="Mincho" style:font-pitch="variable"/&gt;</font>
+<font size="2">&lt;style:font-face style:name=
+"Tahoma" svg:font-family="Tahoma" style:font-pitch="variable"/&gt;</font>
+<font size="2">&lt;style:font-face style:name=
+"Times New Roman" svg:font-family=
+"&amp;apos;Times New Roman&amp;apos;" style:font-family-generic="roman" 
+style:font-pitch="variable"/&gt;</font>
+<font size="2">&lt;style:font-face style:name="Arial" svg:font-family="Arial"
+ style:font-family-generic="swiss" style:font-pitch="variable"/&gt;</font>
+<font size="2">&lt;/office:font-face-decls&gt;</font>
+<font size="2">&lt;office:automatic-styles&gt;</font>
+<font size="2">&lt;style:style style:name="P1" style:family="paragraph" 
+style:parent-style-name="Bibliography_20_1"&gt;</font>
+<font size="2">&lt;style:paragraph-properties&gt;</font>
+<font size="2">&lt;style:tab-stops/&gt;</font>
+<font size="2">&lt;/style:paragraph-properties&gt;</font>
+<font size="2">&lt;/style:style&gt;</font>
+<font size="2">&lt;style:style style:name="Sect1" style:family="section"&gt;</font>
+<font size="2">&lt;style:section-properties style:editable="false"&gt;</font>
+<font size="2">&lt;style:columns fo:column-count="0" fo:column-gap="0cm"/&gt;</font>
+<font size="2">&lt;/style:section-properties&gt;</font>
+<font size="2">&lt;/style:style&gt;</font>
+<font size="2">&lt;/office:automatic-styles&gt;</font>
+<font size="2">&lt;office:body&gt;</font>
+<font size="2">&lt;office:text&gt;</font>
+<font size="2">&lt;text:sequence-decls&gt;</font>
+<font size="2">&lt;text:sequence-decl text:display-outline-level="0" text:name="Illustration"/&gt;</font>
+<font size="2">&lt;text:sequence-decl text:display-outline-level="0" text:name="Table"/&gt;</font>
+<font size="2">&lt;text:sequence-decl text:display-outline-level="0" text:name="Text"/&gt;</font>
+<font size="2">&lt;text:sequence-decl text:display-outline-level="0" text:name="Drawing"/&gt;</font>
+<font size="2">&lt;/text:sequence-decls&gt;</font></pre>
+      </td>
+      <th align="left"><pre class="western" style="margin-bottom: 0.5cm"><font size="2"><u><b>Document Header Stuff</b></u></font></pre>
+
+        <p><br>
+        <br>
+        </p>
+
+        <p><font size="2">The same with added-</font></p>
+
+        <p><br>
+        <br>
+        </p>
+
+        <p><br>
+        <br>
+        </p>
+        <pre class="western" style="margin-bottom: 0.5cm"><font size="2">&lt;style:Biblio biblio-style:name=
+"APA-en" 
+biblio-style-type=”intext-author-date”/&gt;</font></pre>
+
+        <p><i><b>The document style, selected by the user to determine the
+        style </b></i><br>
+        <i><b>sheet used to format the citations and bibliographic
+        table.</b></i></p>
+
+        <p><i><b>Biblio-style-types could be</b></i></p>
+        <ul>
+          <li><p><i><b>intext-author-date</b></i></p>
+          </li>
+          <li><p><i><b>number</b></i></p>
+          </li>
+          <li><p><i><b>footnote</b></i></p>
+          </li>
+        </ul>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td><pre class="western"><font size="2"><b><u>Document Text Contents</u></b> </font>
+
+<font size="2">&lt;<b>text:p text</b>:style-name="Standard"&gt;</font>
+
+<font size="2">Sample document with a citation </font>
+
+<font size="2">&lt;text:bibliography-mark text:identifier="Veer1996a" 
+text:bibliography-type="book" text:address="New York" </font>
+<font size="2">text:author="Peter van der Veer" text:booktitle="Riots and Pogroms" 
+text:editor="Paul Brass" </font>
+<font size="2">text:pages="154-76" </font>
+<font size="2">text:publisher="NYU Press" </font>
+<font size="2">text:title="The Construction of Violence and Public Space in 
+Hindu Nationalism" 
+text:year="1996" </font>
+<font size="2">text:isbn="1223213123"&gt;</font>
+
+<font size="2">[Veer1996a]</font>
+
+<font size="2">&lt;/text:bibliography-mark&gt; </font>
+
+<font size="2">and a bibliographic table.</font>
+
+<font size="2">&lt;/<b>text</b>:p&gt;</font></pre>
+
+        <p style="margin-bottom: 0cm"><br>
+        </p>
+        <pre class="western"><font size="2">&lt;text:p text:style-name="Standard"/&gt;</font>
+        </pre>
+
+        <p><i><b>Note: that the bibliographic reference data is copied in for
+        each citation. The only way to to change or correct this data is to
+        fix the data in the database and delete and re-insert the
+        citation.</b></i></p>
+      </td>
+      <td><pre class="western"><font size="2"><b><u>Document Text Contents</u></b> </font>
+
+<font size="2">&lt;<b>text:p text</b>:style-name="Standard"&gt;</font>
+
+<font size="2">Sample document with a citation </font>
+
+&lt;text:bibliography-mark text:id="bib3"&gt;
+        
+<font size="2">&lt;cite:citation&gt; </font>
+<font size="2">&lt;cite:citation-source&gt;</font>
+<font size="2">&lt;cite:biblioref cite:key="Veer1996a"&gt;</font>
+<font size="2">&lt;cite:detail cite:units="pages" cite:begin="23" cite:end="24"/&gt;</font>
+<font size="2">&lt;/cite:biblioref&gt; </font>
+<font size="2">&lt;/cite:citation-source&gt;</font>
+<font size="2">&lt;text:citation-body text:style-name="citation"&gt;</font>
+<font size="2">(Veer, 1996:23-24)</font>
+<font size="2">&lt;/text:citation-body&gt;</font>
+
+<font size="2">&lt;/cite:citation&gt;</font>
+<font size="2">&lt;/text:bibliography-mark&gt;</font>
+
+<font size="2">and a bibliographic table.</font>
+
+<font size="2">&lt;/text:p&gt;</font></pre>
+
+        <p style="margin-bottom: 0cm"><br>
+        </p>
+        <pre class="western" style="margin-bottom: 0.5cm"><font size="2">&lt;text:p text:style-name="Standard"/&gt;</font></pre>
+
+        <p><i><b>Note: The bibliographic reference data is not included with
+        the citation. <br>
+        It is contained a bibliographic data file, and access by the key
+        “Veer1996a” <br>
+        See bottom of document for an example.</b></i></p>
+
+        <p><br>
+        </p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td><pre class="western" style="font-style: normal"><u><b>Bibliographic Table </b></u>
+
+&lt;<b>text:bibliography</b> text:style-name="Sect1" 
+text:protected="true" 
+text:name="Bibliography1"&gt;
+<font size="2">&lt;text:bibliography-source&gt;</font>
+
+<font size="2"><i><b>Format description for each document type supported in the table.
+Only “book” has been changed from the default.</b></i></font>
+
+<font size="2">&lt;<b>text:index-title-template</b> text:style-name=
+"Bibliography_20_Heading"&gt;Bibliography&lt;/text:index-title-template&gt;</font>
+
+<font size="2">&lt;<b>text:bibliography-entry-template text:bibliography-type="article</b>" 
+text:style-name="Bibliography_20_1"&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="author"/&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="title"/&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="year"/&gt;</font>
+<font size="2">&lt;/text:bibliography-entry-template&gt;</font>
+
+<font size="2">&lt;<b>text:bibliography-entry-template text:bibliography-type="book</b>" 
+text:style-name="Bibliography_20_1"&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="author"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt; (&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="year"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt;)&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="title"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt;, In&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="editor"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt; Ed.,&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="booktitle"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt; (&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="address"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt;:&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="publisher"/&gt;</font>
+<font size="2">&lt;text:index-entry-span&gt;)&lt;/text:index-entry-span&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="pages"/&gt;</font>
+<font size="2">&lt;/text:bibliography-entry-template&gt;</font>
+
+<font size="2">&lt;<b>text:bibliography-entry-template text:bibliography-type="booklet</b>" 
+text:style-name="Bibliography_20_1"&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="author"/&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="title"/&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="year"/&gt;</font>
+<font size="2">&lt;/text:bibliography-entry-template&gt;</font>
+
+<font size="2">&lt;<b>text:bibliography-entry-template text:bibliography-type="conference</b>"
+ text:style-name="Bibliography_20_1"&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="author"/&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="title"/&gt;</font>
+<font size="2">&lt;text:index-entry-bibliography text:bibliography-data-field="year"/&gt;</font>
+<font size="2">&lt;/text:bibliography-entry-template&gt;</font></pre>
+
+        <p><br>
+        <br>
+        </p>
+
+        <p><br>
+        <br>
+        </p>
+
+        <p style="text-decoration: none"><i><b>To save space I have deleted
+        the repetitive definitions for:</b></i></p>
+        <pre class="western"> 
+<font size="2"><b>custom1, custom2, custom3, custom4, custom5, email, inbook, incollection,
+ inproceedings, journal, manual, mastersthesis, misc, phdthesis,
+ proceedings,techreport, unpublished, www</b></font>
+
+<font size="2">&lt;/text:bibliography-source&gt;</font>
+<font size="2">&lt;text:index-body&gt;</font>
+<font size="2">&lt;text:index-title text:style-name="Sect1" 
+text:name="Bibliography1_Head"&gt;</font>
+<font size="2">&lt;text:p text:style-name=
+"Bibliography_20_Heading"&gt;Bibliography
+&lt;/text:p&gt;</font>
+
+<font size="2"><i><b>The Actual generated text of the bibliographic table</b></i></font>
+
+<font size="2">&lt;/text:index-title&gt;</font>
+<font size="2">&lt;text:p text:style-name="P1"&gt;</font>
+<font size="2">Peter van der Veer (1996) The Construction of Violence and Public 
+Space in Hindu Nationalism, In Paul Brass Ed., Riots and Pogroms 
+(New York: NYU Press) 154-76</font>
+<font size="2">&lt;/text:p&gt;</font>
+
+<font size="2">&lt;/text:index-body&gt;</font>
+<font size="2">&lt;<b>/text:bibliography</b>&gt;</font></pre>
+      </td>
+      <td><pre class="western">&lt;<b>text:bibliography</b> 
+
+text:style-name="Sect1" 
+text:protected="true" 
+text:name="Bibliography1"
+
+&gt;
+<font size="2">&lt;text:bibliography-source&gt;</font>
+
+<font size="2">&lt;/text:index-title&gt;</font>
+<font size="2">&lt;text:p text:style-name="P1"&gt;</font>
+<font size="2">Peter van der Veer (1996) The Construction of Violence and Public Space <br>in Hindu Nationalism, In Paul Brass Ed., Riots and Pogroms (New York: NYU Press) 154-76</font>
+<font size="2">&lt;/text:p&gt;</font>
+
+<font size="2">&lt;/text:index-body&gt;</font>
+<font size="2">&lt;<b>/text:bibliography</b>&gt;</font></pre>
+
+        <p><i><b>Note: the text is generated using the Citproc formatter,<br>
+        using the csl style sheet selected by user in a document style<br>
+        selection GUI and stored in the save package.</b></i></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td><pre class="western"><font size="2"><u><b>End Stuff </b></u></font>
+
+<font size="2">&lt;text:p text:style-name="Standard"/&gt;</font>
+<font size="2">&lt;/office:text&gt;</font>
+<font size="2">&lt;/office:body&gt;</font>
+<font size="2">&lt;/office:document-content&gt;</font></pre>
+      </td>
+      <td><p><font size="2">Same</font></p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<p style="page-break-before: always"></p>
+<hr>
+
+<table width="100%" border="1" cellpadding="4" cellspacing="0">
+  <col><col><tbody>
+    <tr valign="top">
+      <th><p>No current equivalent</p>
+      </th>
+      <th><p>Sample proposed bibliographic reference-data file
+        biblio-data.xml.</p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td><p><br>
+        <br>
+        </p>
+
+        <p><br>
+        </p>
+      </td>
+      <td><p><i><b>Note the Format of this file is not fixed yet. <br>
+        This is just an example of a possible format.</b></i></p>
+        <pre class="western">&lt;?xml version="1.0" encoding="utf-8"?&gt;
+&lt;?oxygen RNGSchema="file:/Users/darcusb/Projects/citeproc/schemas/
+mods-tight.rnc" type="compact"?&gt;
+&lt;modsCollection xmlns="http://www.loc.gov/mods/v3" 
+xmlns:xlink="<a href="http://www.w3.org/1999/xlink">http://www.w3.org/1999/xlink</a>"&gt;
+
+&lt;!-- mods sample data --&gt;
+
+&lt;<b>mods ID="Veer1996a"</b>&gt;
+&lt;name type="personal"&gt;
+&lt;namePart type="given"&gt;Peter&lt;/namePart&gt;
+&lt;namePart type="family"&gt;van der Veer&lt;/namePart&gt;
+&lt;role&gt;
+&lt;roleTerm authority="marcrelator" type="text"&gt;author&lt;/roleTerm&gt;
+&lt;/role&gt;
+&lt;/name&gt;
+&lt;titleInfo&gt;
+&lt;title&gt;Riots and Rituals&lt;/title&gt;
+&lt;subTitle&gt;The Construction of Violence and Public Space in Hindu
+ Nationalism&lt;/subTitle&gt;
+&lt;/titleInfo&gt;
+&lt;genre&gt;chapter&lt;/genre&gt;
+&lt;subject&gt;
+&lt;topic&gt;riots&lt;/topic&gt;
+&lt;topic&gt;public space&lt;/topic&gt;
+&lt;geographic&gt;India&lt;/geographic&gt;
+&lt;/subject&gt;
+&lt;relatedItem type="host" xlink:type="simple" xlink:href="BrassP1996a"&gt;
+&lt;name type="personal"&gt;
+&lt;namePart type="given"&gt;Paul&lt;/namePart&gt;
+&lt;namePart type="family"&gt;Brass&lt;/namePart&gt;
+&lt;role&gt;
+&lt;roleTerm type="text"&gt;editor&lt;/roleTerm&gt;
+&lt;/role&gt;
+&lt;/name&gt;
+&lt;titleInfo&gt;
+&lt;title&gt;Riots and Pogroms&lt;/title&gt;
+&lt;/titleInfo&gt;
+&lt;originInfo&gt;
+&lt;dateIssued encoding="w3cdtf"&gt;1996&lt;/dateIssued&gt;
+&lt;issuance&gt;monographic&lt;/issuance&gt;
+&lt;publisher&gt;NYU Press&lt;/publisher&gt;
+&lt;place&gt;
+&lt;placeTerm&gt;New York&lt;/placeTerm&gt;
+&lt;/place&gt;
+&lt;/originInfo&gt;
+&lt;typeOfResource&gt;text&lt;/typeOfResource&gt;
+&lt;genre&gt;book&lt;/genre&gt;
+&lt;part&gt;
+&lt;extent unit="page"&gt;
+&lt;start&gt;154&lt;/start&gt;
+&lt;end&gt;176&lt;/end&gt;
+&lt;/extent&gt;
+&lt;/part&gt;
+&lt;/relatedItem&gt;
+&lt;recordInfo&gt;
+&lt;recordCreationDate encoding="w3cdtf"&gt;2004-01-24&lt;/recordCreationDate&gt;
+&lt;recordIdentifier source="citekey"&gt;Veer199a&lt;/recordIdentifier&gt;
+&lt;/recordInfo&gt;
+&lt;/mods&gt;</pre>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<hr>
+
+<table border="1" cellpadding="4" cellspacing="0">
+  <col><col><thead>
+    <tr valign="top">
+      <th><p>Current Manifest.xml</p>
+      </th>
+      <th><p><b>Proposed Manifest.xml</b></p>
+      </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr valign="top">
+      <td><pre class="western">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org
+//DTD Manifest 1.0//EN" "Manifest.dtd"&gt;
+&lt;manifest:manifest xmlns:manifest=
+"urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"&gt;
+ &lt;manifest:file-entry manifest:media-type=
+"application/vnd.oasis.opendocument.text
+" manifest:full-path="/"/&gt;
+ &lt;manifest:file-entry manifest:media-type=
+"application/vnd.sun.xml.ui.configuration" 
+manifest:full-path="Configurations2/"/&gt;
+ &lt;manifest:file-entry manifest:media-type="" 
+manifest:full-path="Pictures/"/&gt;
+ &lt;manifest:file-entry manifest:media-type=
+"text/xml" manifest:full-path="content.xml"/&gt;
+ &lt;manifest:file-entry manifest:media-type=
+"text/xml" manifest:full-path="styles.xml"/&gt;
+ &lt;manifest:file-entry manifest:media-type=
+"text/xml" manifest:full-path="meta.xml"/&gt;
+ &lt;manifest:file-entry manifest:media-type="" 
+manifest:full-path="Thumbnails/thumbnail.png"/&gt;
+ &lt;manifest:file-entry manifest:media-type="" 
+manifest:full-path="Thumbnails/"/&gt;
+ &lt;manifest:file-entry manifest:media-type=
+"text/xml" manifest:full-path="settings.xml"/&gt;
+&lt;/manifest:manifest&gt;</pre>
+      </td>
+      <td><p><i><b>The same with the bibliographic reference data
+        locator</b></i></p>
+
+        <p><br>
+        <br>
+        </p>
+        <pre class="western" style="margin-bottom: 0.5cm">&lt;manifest:file-entry manifest:full-path=<br>"bibliographic/data/biblio-data.xml"/&gt;</pre>
+
+        <p><i><b>and the style sheet locator</b></i></p>
+        <pre class="western">&lt;manifest:file-entry manifest:full-path=<br>"bibliographic/styles/APA-en.csl"/&gt;</pre>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<p><br>
+<br>
+</p>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/enhanced-save-package-description.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/equation.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/equation.png?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/equation.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/er-relationships.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/er-relationships.gif?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/er-relationships.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/frfbs-er1.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/frfbs-er1.png?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/frfbs-er1.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/bibliographic/frfbs-er2.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/bibliographic/frfbs-er2.png?rev=1175536&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/bibliographic/frfbs-er2.png
------------------------------------------------------------------------------
    svn:mime-type = image/png



Mime
View raw message