Search results

# The engine will have, for each major canon and versification variety, a new header file similar to the previous <tt>canon.h</tt>. ...ded by alternative [[Alternate Versification/Canon Definition Format|canon header]] files.

<header> {HEADER}

<header> {HEADER}

===Header=== ...t the source document from which it is derived <sourceDesc>. A minimal TEI header would look as follows:

...rs within that container. Within that is the Work node. Within that is the Header and then the Body of the text, which are parallel to each other. For a comp =Header=

...ng the output filter '''-o w''' (Red Words of Christ) would require such a header to be added by the user in order to ensure the red letter text can be viewe [[Category:SWORD Frontends|Diatheke]]

* Create a single OSIS file from the separate book files, using the header of the first file and the body of all files. * Construct .confs based on header information from the first provided OSIS file.

...e!</ref> for basic XML documents. This means that we will need a basic XML header to begin our document. This line should do just fine: ==The Header==

...ts to be in the &lt;header&gt; element but ignored. Previously, the p in a header, having been transformed to a div, was taken to be the start of the module' ...ll other is excluded. From a practical perspective, this excludes the OSIS header information.

== Header & footer == ...s can be validated with the canon.xsd XML Schema. The format starts with a header:

==== Allow remote header reference ==== ...ly be to allow @href on the header element, to abstract some or all of the header content. See Troy's [https://groups.google.com/d/topic/openscriptures/kygOM

# The default is the header tag \h # The book names must match the text after each header tag (\h) or the text after the specified '''USFM-TitleTag''' property.

...Pipe filter to convert the files to rudimentary USFM, complete with ID and Header tags, plus the following remarks. The ID and Header for Genesis looks like this:

# Add link from SWORD Project page header [[Category:Projects|Go Bible]]

|Global header note problem (see above). |Global header note problem (see above).

...ers terminated by newlines. A UUID is part of the packet definition. The header is 32 bytes and the UUID (16 bytes) is aligned to the latter half. Maximum After the header, name=value pairs identify a number of required fields. Presence announceme

Removed warnings in header files for unused variables osis2mod: Allow div in header of osis document. From John Zaitseff

* Add a new <code><work osisWork="lemma.MT"></code> to the OSIS header and populate the '''lemma''' attribute of every OT '''w''' element, after t * Insert file history in the OSIS header using the '''revisionDesc''' element (for '''KJV 2.0''' to '''3.1''').<ref>

...> and an appropriate <code>osisRefWork</code> entry within the appropriate header section. The document language needs to be set correctly, ISO 639-1 codes a [[Category:Modules]]