Help:Manual Docinfo: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
No edit summary
Line 5: Line 5:
<h2>Scribus Document Information</h2>  
<h2>Scribus Document Information</h2>  
<h3>Overview</h3> <p align="justify">There are a couple of important points to consider in the doc info fields: 1) Scribus supports an initiative called the [http://dublincore.org/ Dublin Core Initiative]. Dublin Core, for short, is a set of specification on document meta-data.  2) The other feature is the fields on the first tab are used in PDF export, as well as also being part of Dublin Core meta-data. This data can be used by special indexing servers which can index PDF files, as well as Acrobat Reader. The second tab contains meta-data in Dublin Core form which can also be used for using a database to track Scribus files.</p> <table width="100%"><tr><td align="center">[[File:Help_docinfo.png|alt="PDF Doc Info|PDF Doc Info]]</td></tr></table> <p>The second tab is document info which is strictly Dublin Core, thus defined by the specifications:</p>  <table width="100%"><tr><td align="center">[[File:Help_docinfo2.png|alt="Dublin Core Properties"|Dublin Core Properties in Document]]</td></tr></table>  <table width="550" border="0" align="center">  <tbody>    <tr>      <td align="left" >Publisher</td>      <td align="justify" > The person or organization responsible for making the document available or for putting into print.</td>    </tr>    <tr>      <td align="left">Contributors</td>      <td align="justify"> A person or organization responsible for making contributions to the content of the document.</td>    </tr>    <tr>      <td align="left">Date</td>      <td align="justify"> A date associated with an event in the life cycle of the document, in YYYY-MM-DD format, as per ISO 8601.</td>    </tr>    <tr>      <td align="left">Type</td>      <td align="justify"> The nature or genre of the content of the document, eg. categories, functions, etc.</td>    </tr>    <tr>      <td align="left">Format</td>      <td align="justify"> The physical or digital manifestation of the document. Media type and dimensions would be worth noting. RFC2045,RFC2046 for MIME types are also useful here.</td>    </tr>    <tr>      <td align="left">Identifier</td>      <td align="justify"> An unambiguous reference to the document within a given context such as ISBN or URI.</td>    </tr>    <tr>      <td align="left">Source</td>      <td align="justify"> A reference to a document from which the present document is derived, eg. ISDN or URI.</td>    </tr>    <tr>      <td align="left">Language</td>      <td align="justify"> The language in which the content of the document is written, usually a ISO-639 language code. Optionally suffixed with a hyphen and an ISO-3166 country code, eg. en-GB, fr-CH.</td>    </tr>    <tr>      <td align="left">Relation</td>      <td align="justify"> A reference to a related document, possibly using a formal identifier such as a ISBN or URI.</td>    </tr>    <tr>      <td align="left">Coverage</td>      <td align="justify"> The extent or scope of the content of the document, possibly including location, time and jurisdiction ranges.</td>    </tr>    <tr>      <td align="left">Rights</td>      <td align="justify"> Information about rights held in and over the document, eg. copyright, patent or trademark.</td>    </tr>  </tbody> </table>
<h3>Overview</h3> <p align="justify">There are a couple of important points to consider in the doc info fields: 1) Scribus supports an initiative called the [http://dublincore.org/ Dublin Core Initiative]. Dublin Core, for short, is a set of specification on document meta-data.  2) The other feature is the fields on the first tab are used in PDF export, as well as also being part of Dublin Core meta-data. This data can be used by special indexing servers which can index PDF files, as well as Acrobat Reader. The second tab contains meta-data in Dublin Core form which can also be used for using a database to track Scribus files.</p> <table width="100%"><tr><td align="center">[[File:Help_docinfo.png|alt="PDF Doc Info|PDF Doc Info]]</td></tr></table> <p>The second tab is document info which is strictly Dublin Core, thus defined by the specifications:</p>  <table width="100%"><tr><td align="center">[[File:Help_docinfo2.png|alt="Dublin Core Properties"|Dublin Core Properties in Document]]</td></tr></table>  <table width="550" border="0" align="center">  <tbody>    <tr>      <td align="left" >Publisher</td>      <td align="justify" > The person or organization responsible for making the document available or for putting into print.</td>    </tr>    <tr>      <td align="left">Contributors</td>      <td align="justify"> A person or organization responsible for making contributions to the content of the document.</td>    </tr>    <tr>      <td align="left">Date</td>      <td align="justify"> A date associated with an event in the life cycle of the document, in YYYY-MM-DD format, as per ISO 8601.</td>    </tr>    <tr>      <td align="left">Type</td>      <td align="justify"> The nature or genre of the content of the document, eg. categories, functions, etc.</td>    </tr>    <tr>      <td align="left">Format</td>      <td align="justify"> The physical or digital manifestation of the document. Media type and dimensions would be worth noting. RFC2045,RFC2046 for MIME types are also useful here.</td>    </tr>    <tr>      <td align="left">Identifier</td>      <td align="justify"> An unambiguous reference to the document within a given context such as ISBN or URI.</td>    </tr>    <tr>      <td align="left">Source</td>      <td align="justify"> A reference to a document from which the present document is derived, eg. ISDN or URI.</td>    </tr>    <tr>      <td align="left">Language</td>      <td align="justify"> The language in which the content of the document is written, usually a ISO-639 language code. Optionally suffixed with a hyphen and an ISO-3166 country code, eg. en-GB, fr-CH.</td>    </tr>    <tr>      <td align="left">Relation</td>      <td align="justify"> A reference to a related document, possibly using a formal identifier such as a ISBN or URI.</td>    </tr>    <tr>      <td align="left">Coverage</td>      <td align="justify"> The extent or scope of the content of the document, possibly including location, time and jurisdiction ranges.</td>    </tr>    <tr>      <td align="left">Rights</td>      <td align="justify"> Information about rights held in and over the document, eg. copyright, patent or trademark.</td>    </tr>  </tbody> </table>
{{OPL}}

Revision as of 18:29, 29 March 2012


Table of Contents

Scribus Document Information

Overview

There are a couple of important points to consider in the doc info fields: 1) Scribus supports an initiative called the Dublin Core Initiative. Dublin Core, for short, is a set of specification on document meta-data. 2) The other feature is the fields on the first tab are used in PDF export, as well as also being part of Dublin Core meta-data. This data can be used by special indexing servers which can index PDF files, as well as Acrobat Reader. The second tab contains meta-data in Dublin Core form which can also be used for using a database to track Scribus files.

"PDF Doc Info

The second tab is document info which is strictly Dublin Core, thus defined by the specifications:

"Dublin Core Properties"
<tbody> </tbody>
Publisher The person or organization responsible for making the document available or for putting into print.
Contributors A person or organization responsible for making contributions to the content of the document.
Date A date associated with an event in the life cycle of the document, in YYYY-MM-DD format, as per ISO 8601.
Type The nature or genre of the content of the document, eg. categories, functions, etc.
Format The physical or digital manifestation of the document. Media type and dimensions would be worth noting. RFC2045,RFC2046 for MIME types are also useful here.
Identifier An unambiguous reference to the document within a given context such as ISBN or URI.
Source A reference to a document from which the present document is derived, eg. ISDN or URI.
Language The language in which the content of the document is written, usually a ISO-639 language code. Optionally suffixed with a hyphen and an ISO-3166 country code, eg. en-GB, fr-CH.
Relation A reference to a related document, possibly using a formal identifier such as a ISBN or URI.
Coverage The extent or scope of the content of the document, possibly including location, time and jurisdiction ranges.
Rights Information about rights held in and over the document, eg. copyright, patent or trademark.
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later. Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder. A copy of the license is included in the section entitled "Text of the Open Publication License."