[sword-devel] Held emails being released

2017-05-27 Thread DM Smith
Apparently old emails that have been held by mailman as potential spam needing 
moderation are being released. 
___
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


Re: [sword-devel] ERV issues in And Bible

2017-05-27 Thread Martin Denham
Regarding the original issue in And Bible - I released a work-around in the
last release so now ERV displays fine in And Bible.

Martin

On 15 March 2017 at 15:25, Karl Kleinpaste  wrote:

> On 03/15/2017 10:16 AM, Martin Denham wrote:
>
> The bullet points are on empty lines, but I don't have the latest Xiphos
> so maybe this does not happen with the latest version.
>
> Bullet points look normal in 4.0.4, both Linux and Windows.
>
> ___
> 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
>
___
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

[sword-devel] PocketSword on IOS

2017-05-27 Thread Leslie Craig
Hi Nic,


There seems to be a problem on the app which means that Strongs searches do not 
work and the app crashes.

I have only noticed this recently. I was showing a teen Bible group how to 
study using the PocketSword app and it was a bit embarrassing!

Warmly 

Leslie 

___
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


[sword-devel] questions concerning xml markup osis

2017-05-27 Thread Parks

Hi,
Working with the osis xml KJV file.

I was hoping someone could help me to understand:

1) milestone types.
I see in the Old Testament: x-extra-p, x-p with a marker value of 
paragraph.
	In the New Testament all the milestones are type x-strongsMarkup 
with data information so I assume these have nothing to do with 
translations but simply markers that helped contributers to keep 
track of the work. So Basically if someone could help with the Old 
Testament milestone types?


2) Seg markers.
	Most appear to be being used without any attributes (mostly around 
the divinename elements), but I am seeing some with something like 
. I am assuming these are 
marking added text - BUT, I am also seeing type="added">. Is there some difference between these tags? 
 seems to be used mostly in the Old Testament, but the 
New Testament is making use of both seg and transchange.


Thank you for any help,
Michael Parks



-
This message has been scanned for viruses. [No Virus Found]
Checked by AVG - www.avg.com
Version: 2016.0.7227 / Virus Database: 4568/12204 - Release Date: 05/10/16


___
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


Re: [sword-devel] OSISqToTick=false

2017-05-27 Thread Michael Johnson
Thank you for the correction, Troy. :-)
I would not and do not use the OSIS "feature" to generate quotation punctuation 
from the  marker, either. Nor do I know any Bible translators who would. And 
I know many Bible translators. That is why every OSIS file I generate uses  as the only  marker, and then only to mark direct 
quotations of Jesus Christ. This is what I translate the USFM \wj to. Because 
\wj markup starts and stops with every verse, while quotations often span 
multiple verses, this is not an exact
equivalent, but it works well enough only because punctuation isn't being 
generated from the  marker.

I'm pretty sure that there is no such thing as a programmer on this planet who 
could correctly generate punctuation for every language and style from «» 
markup. Nobody has that much knowledge of that many languages. Thus OSISqToTick 
should not only default to false, SWORD should probably just issue a warning 
and ignore the setting if it is set to anything else.

On 05/24/2017 04:43 PM, Troy A. Griffitts wrote:
> correction:
>
> -  it should be used in place of the language quotation marker.
>
> + it shouldn't be used in place of the language quotation marker.
> + though, of course that is what  is for; however, I
> wouldn't use it.
>
>
> On 05/24/2017 07:32 PM, Troy A. Griffitts wrote:
>> I am not sure who decided that OSISqToTick is deprecated.
>>
>> As a matter of principle, I don't think  should ever produce
>> punctuation marks and I would always set it to false in a module I produce.
>>
>> The idea is that, conceptually, no other punctuation mark in a module is
>> produced from a tag.  Marking quotations for a language (even English)
>> varies dramatically and is not always at the start and end of a quotation.
>>
>> Let the author use punctuation however they expect the punctuation for
>> the language to appear (just like question mark, exclamation mark,
>> etc.).  Tags are there not to add actual content to the text, but merely
>> meta information.   might be added to specify 'who' was speaking, but
>> it should be used in place of the language quotation marker.
>>
>> Troy
>>
>>
>>
>> On 05/24/2017 06:24 PM, DM Smith wrote:
>>> Your advice is appropriate for OSIS modules that are properly marked up.
>>>
>>> It is deprecated because the SWORD engine now uses the marker attribute on 
>>> the q element to display the quotation mark. If that is not present, the 
>>> SWORD engine will generate a quotation mark.
>>>
>>> A module that marks up the words of Christ, that doesn’t want quotation 
>>> marks, must either use marker=“” or OSISqToTick to suppress the generation 
>>> of quotation marks.
>>>
>>>
 On May 24, 2017, at 9:20 AM, David Haslam  wrote:

 The configuration key *OSISqToTick* is deprecated.

 Whenever the modules team updates a module, please ensure that such a key 
 is
 removed if previously present.

 I imagine a check for this could be readily included in the automation
 script.

 Best regards,

 David



 --
 View this message in context: 
 http://sword-dev.350566.n4.nabble.com/OSISqToTick-false-tp4657248.html
 Sent from the SWORD Dev mailing list archive at Nabble.com.

 ___
 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
>>> ___
>>> 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
>> ___
>> 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
>
> ___
> 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


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule



___
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

Re: [sword-devel] anniversaries

2017-05-27 Thread Michael Johnson
On 01/09/2017 03:56 PM, Karl Kleinpaste wrote:
> On 01/09/2017 08:47 PM, Kahunapule Michael Johnson wrote:
>> I'm pretty sure the Lockman Foundation is not actually interested in 
>> releasing the NASB on Sword.
>
> You misunderstand. There has been a Lockman-sanctioned NASB in progress since 
> 2004.
>

Seriously? What is the delay? Is nobody actually working on it? I have 
Lockman-supplied NASB 1995 source (for the posting on InScript.org), and can 
generate a Sword module in a matter of minutes if we have permission to post 
it. Normally, I just send modules to the eBible.org repository, but I'm 
guessing that one would have to be in Crosswire main, which is totally fine by 
me. Is anyone interested?

-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
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

Re: [sword-devel] ERV issues in And Bible

2017-05-27 Thread Michael Johnson
Note: those preverse milestones and their sID values are generated with 
osis2mod. I have no control over them. It seems clear that osis2mod is the 
problem, here.


On 03/08/2017 12:20 PM, David Haslam wrote:
> Here's the *mod2imp* portion for Psalm 3:8 and the next verse.
>
> $$$Psalms 3:8
>  sID="gen11939"/>  subType="x-preverse" eID="pv6991"/>LORD, the victory osisID="Ps.3.8!note.1" osisRef="Ps.3.8" placement="foot" type="translation">
> 3:8 victory
> Or “salvation.” is yours!  level="2" sID="gen11941"/>You are so good to your people.  level="2"/>Selah type="selah"/> * subType="x-preverse" sID="pv6992"/>* eID="Ps.3.seID.14187"/>
> $$$Psalms 4:0
>  
> $$$Psalms 4:1
> ** canonical="true" type="psalm">To the director^: With stringed instruments. A
> song of David.^ 
> God, you showed
> that I was innocent.  sID="gen11946"/>You gave me relief from all my troubles.  level="2"/> sID="gen11948"/>So listen to me now when I call to you for help.  eID="gen11948" level="1"/>Be kind to me and
> hear my prayer. 
>
> I have bolded the duplicated elements.
>
> David
>
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656934.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> 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


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
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

Re: [sword-devel] ERV issues in And Bible

2017-05-27 Thread Michael Johnson
You can see the source OSIS XML file at 
https://ebible.org/Scriptures/engerv_osis.zip if you like. All of the OSIS 
source files for Sword modules in the eBible.org repository are in that 
directory.

I'm referring this one to whoever the current pumpkin holder for osis2mod is 
for comment and/or further action, and waiting for a response before doing 
anything else. In the mean time, I just rebuilt engerv2006eb using osis2mod Rev 
3401 just to make sure we aren't dealing with an older and possibly already 
corrected problem. If I need to rebuild the eBible.org repository with a 
corrected version of osis2mod, please let me know.


On 03/08/2017 12:13 PM, David Haslam wrote:
> Dear Michael,
>
> I don't have access to your OSIS XML file, or if I do, I've not yet gone
> looking for it.
> I was merely going by what I saw in the output from *mod2imp*, which
> includes numerous OSIS snippets.
>
> I've never before come across duplication of internal items when a module
> content is exported using this Sword utility. It's supposed to be lossless
> (unlike what's on record for *mod2osis*).
>
> In theory, a round trip module rebuild ought to be feasible:
>
> module => *mod2imp* => IMP file => *imp2vs* => module
>
> I rather suspect therefore that the problem may be caused by *osis2mod* when
> you built the module.
>
> It being documented in the wiki, we know that *osis2mod* performs a
> transformation of its input.
> See https://crosswire.org/wiki/Osis2mod#Transformations
>
> That's where the milestone div elements are made, if they don't already
> exist.
> I was unaware that osis2mod inserts *type="x-milestone"* as well.
> That's not mentioned in the wiki page.
>
> *osis2mod* expects an input file that meets OSIS 2.1.1 or possibly the
> latest CrossWire updated schema.
>
> Neither of these schema allow for the milestone form of the *div* element.
>
> I've therefore started a discussion about this in the talk page:
>
> https://crosswire.org/wiki/Talk:OSIS_211_CR#A_milestone_form_of_the_div_element_.3F
>
> As far as I know, there's been next to no discussion of this before between
> the API developers.
> We do use the milestone form internally, but don't expect it as part of the
> XML input.
>
> With *And Bible* being a *JSword* app., one needs to understand that JSword
> does an XSLT on the internal OSIS XML of a module. What this might do if it
> encounters an orphaned/duplicated milestone *div* element is anyone's guess.
>
> Does any other module show signs of duplicated div elements when analysed
> using *mod2imp* ?
> I think we ought to have noticed this before, but it does require more
> researching.
>
> I've not yet looked at any other modules from *eBible.org* for this
> phenomenon.
>
> Martin reported that Psalm 2:12 was an example location of the issue, so
> that's the place I examined in detail.
>
> His other example Psalm 3:8 has exactly the same sort of triple occurrence,
> this time for *ID="pv6992"* where the previous letter is either "s" or "e",
> there being 2 of the former and 1 of the latter.
>
> Martin added that there are many more, and I counted a total of 503
> instances.
>
> It should be feasible to systematically remove one of the duplicates from
> every such location and rebuild the module using *imp2vs* to see whether
> this gives one that no longer crashes *And Bible* or other JSword apps.
>
> Once we learn which of the pair of sID elements is the delinquent one, we
> might then try and find out where these are coming from, and whether your
> copy of *osis2mod* is the culprit.
>
> Best regards,
>
> David
>
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656933.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> 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


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
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

Re: [sword-devel] Is the eBible repo down?

2017-05-27 Thread David Haslam
Latest update: The *eBible.org* repo is now working again.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Is-the-eBible-repo-down-tp4657261p4657269.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
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


Re: [sword-devel] Headings, titles and chapter descriptions

2017-05-27 Thread DM Smith
JSword uses CSS for the distinction. It also treats generated titles as 
distinct from what the module provides. 

In Him,
DM 

> On May 27, 2017, at 12:09 PM, David Haslam  wrote:
> 
> Hi Dominique,
> 
> The problem is that SWORD doesn't.
> 
> It treats chapter descriptions as titles and therefore as headers, but they
> are neither.
> 
> This is because *usfm2osis* converts chapter descriptions to title elements,
> even though they are simply not ordinary titles.
> 
> Aside: *ParaTExt* uses stylesheets for its formated view of USFM files. I
> presume it displays chapter descriptions right.
> cf. The open source program *Bibledit* also has a formated view, but AFAIK,
> it doesn't apply italics to chapter descriptions.
> 
> I am told that *Bible Desktop* (based on JSword) has several different
> styles for multi-level titles, yet even this is not the solution for the
> issue here.
> 
> David
> 
> 
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/Headings-titles-and-chapter-descriptions-tp4657204p4657262.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> 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

___
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


Re: [sword-devel] Headings, titles and chapter descriptions

2017-05-27 Thread David Haslam
Introductions have been mentioned.

For comparison, Aydeths' u2o.py (which we generally don't use) contains
these lines:

# # chapter cd tags # #
# the osis user manual says cd titles should be in an introduction div.
r'\cd': (u'\ufdd0',
 u'\ufdd0'),

Aside: Unicode character \ufdd0 is part of his algorithm and gets replaced
later.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Headings-titles-and-chapter-descriptions-tp4657204p4657267.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
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


Re: [sword-devel] Headings, titles and chapter descriptions

2017-05-27 Thread David Haslam
Thanks Troy,

Just so you all know, it's the content of the following USFM tag.

\cd text

What the Python script *usfm2osis.py* does is to convert this to: 

1 Ko e fakatupu ʻoe langi mo māmani, 3 ʻOe
maama, 6 Mo e ʻatā, 9 Mo e mavahe ʻoe fonua mei he ngaahi vai, 11 Mo e
ngaohi ia ke fua, 14 ʻAe laʻā, mo e māhina, mo e ngaahi fetuʻu, 20 ʻAe ika,
mo e fanga manupuna, 24 ʻAe fanga manu kehekehe, 26 Ko e tangata ʻi he tatau
ʻoe ʻOtua. 29 Ko e tuʻutuʻuni foki ʻoe meʻakai.

(this example is from the Genesis 1 in the *Tongan RWV* module)

As this is a standard feature of ParaTExt/Bibledit produced USFM files, it
should not be up to the individual module submitter to provide a special CSS
file for rendering these elements suitably/correctly.

We need to distinguish these items from ordinary title elements.

As things stand, the type attribute is simply ignored, especially with it
being a user-defined one with the x-prefix.

Best regards,

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Headings-titles-and-chapter-descriptions-tp4657204p4657266.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
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

Re: [sword-devel] Is the eBible repo down?

2017-05-27 Thread David Haslam
It was down for a few hours, but though the server is now up again, he thinks
there's another problem.

David

PS. You'd get a faster response by alerting Michael directly.



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Is-the-eBible-repo-down-tp4657261p4657265.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
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


Re: [sword-devel] Headings, titles and chapter descriptions

2017-05-27 Thread Troy A. Griffitts
Hi David. I'm a little confused by your reply. When you say "SWORD doesn't," 
what do you mean?

If usfm2osis does something odd converting chapter 'descriptions' (I'd like a 
definition of a chapter description. Is this a chapter intro?) to OSIS titles 
then the owner of usfm2osis needs to improve the tool. I haven't kept up with 
all the tools floating around to convert usfm to OSIS or which ones are 
maintained/used/recommended by us.

Just to be sure there is no misunderstanding, SWORD XHTML RenderFilters do 
cater for CSS.

Troy

On May 27, 2017 9:09:52 AM MST, David Haslam  wrote:
>Hi Dominique,
>
>The problem is that SWORD doesn't.
>
>It treats chapter descriptions as titles and therefore as headers, but
>they
>are neither.
>
>This is because *usfm2osis* converts chapter descriptions to title
>elements,
>even though they are simply not ordinary titles.
>
>Aside: *ParaTExt* uses stylesheets for its formated view of USFM files.
>I
>presume it displays chapter descriptions right.
>cf. The open source program *Bibledit* also has a formated view, but
>AFAIK,
>it doesn't apply italics to chapter descriptions.
>
>I am told that *Bible Desktop* (based on JSword) has several different
>styles for multi-level titles, yet even this is not the solution for
>the
>issue here.
>
>David
>
>
>
>
>
>
>
>--
>View this message in context:
>http://sword-dev.350566.n4.nabble.com/Headings-titles-and-chapter-descriptions-tp4657204p4657262.html
>Sent from the SWORD Dev mailing list archive at Nabble.com.
>
>___
>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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
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

Re: [sword-devel] Is the eBible repo down?

2017-05-27 Thread David Haslam
Yes - I can't get at any eBible modules from PocketSword either.

Have alerted Kahunapule MPJ via Messenger.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Is-the-eBible-repo-down-tp4657261p4657263.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
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


Re: [sword-devel] Headings, titles and chapter descriptions

2017-05-27 Thread David Haslam
Hi Dominique,

The problem is that SWORD doesn't.

It treats chapter descriptions as titles and therefore as headers, but they
are neither.

This is because *usfm2osis* converts chapter descriptions to title elements,
even though they are simply not ordinary titles.

Aside: *ParaTExt* uses stylesheets for its formated view of USFM files. I
presume it displays chapter descriptions right.
cf. The open source program *Bibledit* also has a formated view, but AFAIK,
it doesn't apply italics to chapter descriptions.

I am told that *Bible Desktop* (based on JSword) has several different
styles for multi-level titles, yet even this is not the solution for the
issue here.

David







--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Headings-titles-and-chapter-descriptions-tp4657204p4657262.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
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


[sword-devel] Is the eBible repo down?

2017-05-27 Thread Martin Denham
I seem to be having problems accessing the eBible repo.  However I seem to
be having problems accessing one or 2 things atm.

Regards
Martin
___
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