How do front-ends know not to double/triple/quadruple...a verse range? Diatheke
fails at that right now and I would like to fix this.
Peter
Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
___
sword-devel mailing list: swor
Dear All,
This is to announce that we have just now uploaded UrduGeoDeva.
This is is an updated version of UrduGeoDeva.
Many thanks to update for the hard work.
yours
The Module Team
P.S.: This email is sent automatically on upload of a new/updated module
___
Description shouldn’t have RTF. Also, "Public Domain. Copy freely.” doesn’t
belong in the description, but rather elsewhere, e.g. Distribution license.
> On May 21, 2017, at 11:03 AM, David Haslam wrote:
>
> Hi Peter,
>
> The last line of the Description has a typo.
>
> \paryPublic Domain. C
*Headings* is too broad an object type to cope with what modules may actually
contain at the start of each chapter.
SWORD needs to distinguish between *Chapter Titles* and *Chapter
Descriptions*.
In printed Bibles, *Chapter Titles* are normally bold text and typically
without italics.
SWORD alway
Do any front-ends have an optional capability to display the localised
*Description* text and *About* text if present in a module .conf file?
e.g. As in the three recently released Danish modules, each of which also
has:
Description_da=
About_da=
as well as the normal unsuffixed keys.
Hi Peter,
The last line of the Description has a typo.
\paryPublic Domain. Copy freely.
The letter "y" is spurious.
NB. When reading your latest conf files in Notepad++, it doesn't help that
you have no space between the RTF tag *\par* and the next word of text.
Should any line just happen to
Testament titles do not show up as OSIS fragments using the *title* element
in the output of *mod2imp*.
I think that explains why I missed it.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Module-upload-DaNT1819-tp4657189p4657201.html
Sent from the SWORD Dev mai
So, I did a little experimenting this weekend and found that the ICU
RegEx engine is actually really capable.
o It's fast.
o It supports {n,m} characters instead of bytes
o It even works (though a little slow) with lookaheads and lookbacks,
e.g., for words in any order: (?=.*God)(?=.*world)(?
Dear all,
I have published the Danish Bibles using NRSV versification as it seems
this has the least problems of all I tried - but there are at least 100
verses out of sync still in the OT. I am not too happy about that.
I do not want to add for 3 texts a new versification, but it would be
good
