Identification Information

From Bibledit

Contents

[]

Syntax Notes

Required spaces are indicated with _. Parameters are indicated in ALLCAPS or by a special character such as the hash mark #. Optional or suggested information is shown as normal text in (Parentheses).

[]

\id_CODE_(Name of file, Book name, Language, Last Edited By, Date)

  • Identification line.

Example of use:

\id MAT 41matgua.ptx UTF8 Matthew Guarani-Paraguay Tito Lahaye mm/dd/yyyy
[]

\ide_ENCODING

  • Character encoding specification.
  • This marker should be used to specify the character encoding of the text in the file. For example: CP-1252, CP-1251, UTF-8, UTF-16, OR Custom <specify font name>. If the character encoding does not conform to a standard, but is rather a custom/hacked solution for the project, a minimum of the name of the font used for the project should be included. However, for archive purposes texts which relied upon a custom encoding solution should be converted to UTF-8 or UTF-16.

Example of use:

\ide UTF-8 
\ide CP-1252 
\ide Custom (TGUARANI.TTF)
[]

\rem

  • Used for adding brief comments by a translator, translation consultant, or CAP officer.

Example of use:

\rem Assigned to <translator's name> 
\rem First Draft complete, waiting for CAP checks
[]

\h_Sample text...

  • Running header.
  • This version may be used when only one level of \h is in use within the project.
  • The book title heading to be included at the top of each printed page (entered only once at the beginning of the file following \id).
  • In the instance where a text has two or more levels or components to the running header, the number should be used to mark these separately. See also \h# below.
[]

\h#_Sample text...

  • Running header (additional components).

Example of use ():

\h Matthew
[]

\toc1_Sample text...

  • Long table of contents text.
[]

\toc2_Sample text...

  • Short table of contents text.

Example of use ():

\toc1 The Gospel Accoring to Matthew
\toc2 Matthew
Personal tools