Bible Drop Box
Music and songs
The Bible Drop Box allows the submitter to optionally include a text file that contains Bible metadata. Metadata is a technical term that refers to information about that Bible translation, such as the language of the translation, the year of publication, the names of the translators, the copyright information, etc. This information can then by used by the automated Bible Drop Box software to insert the appropriate fields when it creates modules for use by Bible study programs, and when it creates print format Bibles, e.g., PDF files.
Basically, the metadata file is a simple text file with lines formatted like this:
FieldName=Your data field here
There are no spaces around the equals sign or in the field name, and capital letters must match exactly. (See sample data below.)
The submitted metadata text file should be a UTF-8 encoded text file with a .txt file extension, with each field starting at the beginning of a new line. If a field is very long, it may continue onto the next line by using a backslash (\) at the end of the previous line to indicate that the line continues. (You may also wish to have a space before the backslash so that when the lines are rejoined, the formatting is more readable because nothing is automatically inserted otherwise.)
The text file may be produced by any text editor (or word processor if the file is saved as a simple text file). Either Windows or Linux/Unix style line-endings will be accepted. Blank lines are ignored. Lines beginning with a hash character (#) are considered to be comment lines and are ignored. The order of the fields in the file makes no difference (unless a field name is repeated). It is important that the spelling of the field names exactly match (including the capital letters).
If a SSF file is submitted as part of a zipped USFM Bible (usually produced by UBS/SIL Paratext), that SSF information will automatically be included as Bible metadata. If a metadata text file is also separately submitted, any identically named fields in this file will supercede the SSF information.
The software does attempt to intelligently discover or deduce some information if you don't supply it directly.
Once you have gone to the trouble of making a Bible metadata file, make sure that you keep a copy of it in case you wish to resubmit your Bible data for reprocessing in the future (especially as we add new output formats).
Highly recommended for all non-English submissions.
|Encoding||Specifies the encoding of the submitted Bible text, e.g., utf-8 (default) or ISO-8859-1|
|LanguageName||The name of the (main) language of the work|
|ISOLanguageCode||The 3-letter ISO-639-3 language code|
|OldTestamentName||Your translation of Old Testament|
|NewTestamentName||Your translation of New Testament|
|DeuterocanonName||Your translation of Deuterocanon (if required)|
|FrontMatterName||Your translation of Front Matter|
|BackMatterName||Your translation of Back Matter|
Note that the Bible Drop Box will usually (depending on the submitted format) expect UTF-8 as the default encoding anyway.
More fields will become available as we improve the export functions, and then continue working on the automated typesetting functions.
If you are submitting a Bible in a format that doesn't include the book names and abbreviations, you can optionally submit this data in the metadata file. Book codes are specified using the BOS system represented by BBB below. If any of these fields are supplied as well as fields in the actual Bible file(s), this metadata information will be ignored. A blank text file containing blank entries for the most common books codes can be found here suitable for copying and pasting into your file.
|BBBLongName||The long title for this book|
|BBBShortName||The short name for this book|
|BBBAbbreviation||The abbreviation used for this book|
The following additional fields are often used by Sword modules—more information here.
|WorkTitle||The title of this translation|
|WorkAbbreviation||A short abbreviation that can be used to identify this work|
|WorkDescription||A longer description (perhaps a sentence or two)|
|CopyrightDate||Often just the year|
|CopyrightNotice||The copyright notice which would normally be displayed|
|Licence||A description of the licence that the word is released under, e.g., Creative Commons Attribution Share-Alike|
|About||A description about the aims or intended audience of the work|
|id||Not sure where this comes from?|
|title||e.g., New Rather Imaginary Non-version|
|description||A sentence or paragraph describing this version|
|author||Author of the translation—a string that could include an email address|
|creator||Creator of the module—a string that could include an email address|
|source||Source of the text—a string that could include a web link|
|editorial.comments||Information concerning the creation of this module|
|about||Can be a paragraph with html formatting|
The following additional fields can be used by PhotoBibles to override default settings:
|PBPixelWidth||Width of JPGs||240|
|PBPixelHeight||Height of JPGs||320|
|PBMaxChars||Chars per line||23|
|PBMaxLines||Lines per page||12|
|PBTextFont||Font for Bible text||Charis-SIL|
|PBHeadingFont||Font for headings||Andika|
Note: PhotoBibles are not made by default by the Bible Drop Box. The box has to be checked when a submission is made. Operator intervention is currently required for different JPG sizes (pixel width and height). Please contact us in advance for that.
OldTestamentName=Zee Ooold TestiBit
NewTestamentName=Zee Noo TestiBit
WorkTitle=My Newfangled Englect Mistranslation
WorkDescription=An irrelevant new transposition just for testing in the modern digital world
CopyrightNotice=Copyright © 2013 by Transpositors Internotional
About=A translation that's not in progress and never will be. \
So don't hold your breath waiting for it.
about=About for <b>MySword</b> (lowercase about) needs a separate \
entry and note that this about field specifically \
allows embedded html formatting like the bolding above.
GENLongName=The First Book of Moses
Please use the Contact Page to let us know of any corrections or improvements to these instructions, and/or any other methods to get Bibles onto people's devices. Thanks.