From CrossWire Bible Society

Revision as of 13:17, 22 August 2013 by Yvand (Talk | contribs)
Jump to: navigation, search


From paper to sword

Printed editions are 'tagged' using these special characters:

Textual Unicode value[1] French English Examples Frequency
U+2731 Alinéa Large space between paragraph. Gen.49.3 Gen.49.5 Lev.14.1 490
U+2606 Grand alinéa Larger space between paragraph. Gen.2.4 Gen.3.1 Exod.1.8 504
U+2605 Petit alinéa (texte poétique) Small space between paragraph (poetics) Ps.42.1 Ps.73.1 Isa.36.1 17
  1. The default module font in some front-end applications may not display these special symbols. It would therefore make sense to specify a font that does in the conf file.

Divine Names are tagged as:

Textual Unicode value Original Examples Frequency
L'Éternel YHWH Gen.2.4 Gen.3.1 Exod.3.2
Dieu Elohim Gen.1.1 Gen.4.25 Exod.1.17
∗Dieu U+2217 El Gen.14.18 Gen.16.13 Exod.6.3 212
†Dieu U+2020 Eloah Deut.32.15 Neh.9.17 Job.3.4 50
∗Seigneur U+2217 Jehovah Matt.1.20 Matt.2.13 Mark.1.3 137

Module History

About years

John Nelson Darby did the initial French translation. The New Testament was first published in 1859. He did some corrections in editions published in 1872, 1875 and 1878. The Old Testament was first published in 1885 (he died in 1882).

The last printed edition was done in 1975; a major change was to update chapter number from roman numerals to arabic numerals. There is no known significant modification in all the editions done since Darby's death.


Currently, the last revision of the CrossWire beta module FreJND is version 1.16 dated 2008-06-13.

The Text Source is from Bibliquest. There are two whole Bible downloads available from Bibliquest:

Skc (maintainer of FreJND) developped a tool to convert the text source (encoded in HTML) into the OSIS format, available on


French Bibles generally have versification differences compared to the KJV. The current module does not specify a versification in the conf file. The output from emptyvss indicates that there is a real issue that needs fixing:

Leviticus 6:24-30
Numbers 12:16
I Samuel 23:29
Job 38:39-41
Job 41:26-34
Psalms 13:6
Ezekiel 20:45-49
Hosea 11:12
Jonah 1:17
Matthew 23:14
Acts 8:37
Acts 15:34
II Corinthians 13:14

Many of these are locations detailed in [1].

Known issues

Bugs in the converter tool

Unfixed issues

This issue concerns only some notes in the NT. It appears if a verse mixes standard notes and crossReference notes.
See Matt.4.10 Heb.3.11 for instance.
Skc> Hard to fix, as crossReferences are parsed first and then standard notes
The presence of a cluster in the source involves a new paragraph. But it doesn't work if the cluster does not follow a paragraph of notes.
Examples for Clustermoyen can be found in Gen.11.27, Gen.25.12.
Examples for Clustersecondaire can be found in the Psalms, for instance Ps.3.7, Ps.4.2, Ps.5.3, Ps.27, Ps.14.1.
Skc> Still exists?
Yvand> Yes, the osisRef and osisID attributes still contains the osisID of the previous book (for example for the note in Rev : osisRef="Jude.1.0" osisID="Jude.1.0_1" but n="a")
Yvand> (I do not know what is best but in my opinion, the alphabetic numeration of notes should start at the beginning of a chapter. So if a note is present in the booktitle (only 2 cases) it shouldn't start the numeration of the chapter. But what value should we use for the n attribute? x? *?)
The issue seems to concern only two verses, these verses contain notes which should use the same n attribute!
The note d in Zech.5.3 must be c ; as well the note i in Isa.24.16 must be h.
This is due to a limitation in which doesn't allow same duplicate note ** or ***, so darby.patch forces to create a new note.
Some notes refer to other notes (in another passage), and so uses * (or ** etc.) to refer to a particular notes in a verse.
Two examples have been noticed, see the note e in Judg.13.19 and in the note in 1Chr.26.18 (** should be replaced by the given note attribute).
I guess these two particular cases should be corrected manually.

Suggestions, ideas for improvement

A patch (for osis2html.xslt) has been send to the developper.
For example <reference osisRef="Exod.22.26">Exode 22:26</reference>-27 should be replaced by <reference osisRef="Exod.22.26-27">Exode 22:26-27</reference> in Job.24.9 (note). According to the OSIS Manual, this syntax is valid.
SKc> Hard to do it right.
In the OSIS file, you can found <verse sID="{sID}" osisID="{osisID}" n="{n}"/><l> ... </l><verse eID="{eID}"/> which is valid against XML Schema.
But it is more logical/coherent to put verse tags in a l tag.
Currently the chapter titles are Chapter N, except in the Psalms in which it is PSAUME N.
I suggest to replace PSAUME N by Psaume N.
The regular expressions s/<\/i>((\s|-|,)+)<i>/\1/g, s/<i>((\s|-|\.|,|;)+)<\/i>/\1/g and s/<i>((\s|-|\.|,|;)+)/\1<i>/g eradicates numerous useless i tags.
As in the paper version, my opinion is that spacing tags shouldn't be in Psalms headers but at the beginning of verse 1.
See for example Ps.3, Ps.9, Ps.16 etc.
Currently notes in book titles (Song, Rev are concerned) are moved to a paragraph foregoing the chapter content.
As well, notes in chapter titles (Ps.25, Ps.34, Ps.37, Ps.111, Ps.112, Ps.119, Ps.145, Lam.1 are concerned) are also moved at the beginning of a paragraph below.
Skc> I don't think that OSIS or frontend allow notes on books or chapters.

Resolved issues

Two dots (instead of a single dot) are present in the last note of the headers of Ps.34, Ps.60, Ps.111, Ps.112.
The problem seems to occur when there are more than one note in a Psalm header.
Sometimes it captures other characters (mostly dots) in the note
See for example Matt.2.6, Matt.2.15, Matt.2.18, Matt.4.10 (about 31 notes concerned) includes the dot of the sentence, as others don't (like Matt.1.23, Matt.3.3)
The regular expression s/([0-9]\])(&#160;|\.)<\/i>/\1<\/i>\2/g can solve the problem.
See for example John.21.5 (twice, after ":" and after "?"), John.18.22, John.18.28, Exod.6.2 (before the parenthesis) etc.
It appears if a line ends with <i...> or <span...>, tidy doesn't add a space when indenting (although there is a newline)!

Upstream issues (Bibliquest)

See User:Yvand/Bibliquest for a list of known typos in the source. These issues have been reported upstream.

Issues related to frontends



Personal tools