Thanks for finding this. There are, if you will, two issues, so I'll
issue a pair of updates, one to pub and one to experimental.
The first issue is versification, though the problem in Mal 4:6 isn't
the result of this. Aleppo /should/ have MT versification now that we
can support it.
The se
I opened Aleppo in the SWORD Project for Windows, to Malachi 4:6. It
says, Chapter 4 at the top, then has a 1, for verse 1, followed by Mal
3:19-24, with (Malachi 3:19), etc. with each verse. Then immediately
after that it has a 6, for a verse number (no 2-5 in between), followed
by multiple
Data taken from the Masoretic text is available in the
bibledit-x.x.tar.gz package, in directory templates. It's a file called
masoretic-paragraphs. Teus.
On Sat, 2009-11-07 at 18:02 +0100, Peter von Kaehne wrote:
>
> It appears that the Masoretic text has some sort of paragraphing and
> section
DM Smith writes:
> This seems to say that Aleppo needs to have a different versification.
Perhaps, but perhaps not. This came to attention via a Xiphos bug
report, where the reporter said, "...displays Genesis 1:1 and a lot more
text."
If it's repeating Gen1.1 then of course something deeper is
> On Sat, Nov 7, 2009 at 2:05 PM, Chris Little
> wrote:
>
> > We have many many Bibles that lack any kind of paragraphing markup.
It appears that the Masoretic text has some sort of paragraphing and
sectioning. I would consider that such a paragraphing overlayed is the best way
forward, rath
On Nov 7, 2009, at 10:02 AM, Karl Kleinpaste wrote:
diatheke -b Aleppo -k Mal4:6
This seems to say that Aleppo needs to have a different versification.
Malachi 4:6 is the last verse in the KJV versification. The various
module importers (osis2mod, imp2mod, ...), on hitting a verse that
t
diatheke -b Aleppo -k Mal4:6
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
On Sat, 7 Nov 2009, Jonathan Morgan wrote:
>
> It would be preferable not to bump all version numbers and make all modules
> be re-downloaded (in frontends that support module updating) just for
> changes which will not make any difference to current frontends anyway.
This is another issue altoget
On Fri, 6 Nov 2009, Troy A. Griffitts wrote:
> Yeah, Eeli, I would guess Matthew is correct about your changes breaking
> binary compat, though I HOPE we haven't broken binary compat since 1.6.0.
>
As I wrote, I didn't find any indicator in the KDE document that adding
a static member function wo
On Sat, Nov 7, 2009 at 2:05 PM, Chris Little wrote:
> We have many many Bibles that lack any kind of paragraphing markup. These
> will tend to be rendered as a single big block of text per chapter, which is
> rather ugly.
>
> Some front ends offer a verse-per-line option where every verse gets it
Some thoughts arising, relating to what is essentially a good idea.
Prior to the publishing of the first Cambridge Paragraph Bible (based on the
KJV), was it not the case that all printed editions of the KJV were
published in what we now call VPL format, but with a pilcrow (ΒΆ) included in
the tex
Why not offer all the options below for the user to choose either per module
or globally. For modules where there is a .conf entry Feature=Paragraphs
then module specific paragraph and poetry display could be enabled/offered.
Where this is not present, users could have the choice of either vpl or
12 matches
Mail list logo
