Re: [sword-devel] OSIS supported added to osisxhtml and osislatex

Aside: What is the touch screen equivalent of "mouse hover" ? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-abbr-supported-added-to-osisxhtml-and-osislatex-tp4655248p4655249.html Sent from the SWORD Dev mailing list archive at Nabble.com.

[sword-devel] OSIS supported added to osisxhtml and osislatex

is a tag which somehow has escaped notice for too long. As the tag has a direct html equivalent - just a differently named attribute - it was easy to implement. It is visible in Xiphos, if you compile it with libsword from svn head. WLC Obad.1.1 footnote 2 (and many other similar places) -

[sword-devel] Adding a conf entry (C++)

What am I doing wrong here? SWConfig *config = new SWConfig(modFile.c_str()); ["InstallTime"] = ctime(0); config->Save(); On compiling I get an error error: invalid types 'sword::SWConfig*[const char [12]]' for array subscript I did think that this was the code

Re: [sword-devel] OSIS supported added to osisxhtml and osislatex

Don't know but, as i said it is easily overriden. Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 10:08, David Haslam wrote: > > Aside: What is the touch screen equivalent of "mouse hover" ? > > David > > > > -- > View this message in context: >

[sword-devel] GlobalOptionFilters in Conf files.

I'm updating SPARVG to the 2015 text, and making a few corrections (moving the directives in psalms to their proper place prior to verse 1. and a single opening question mark into the redletter zone in matthew 16.) I'm working on the conf file now.The RVG module on crosswire has

Re: [sword-devel] osis2mod default versification

The utility imp2vs also provides for a -v flag. The default is KJV. The copy of imp2vs.exe installed along with Xiphos 4.0.3 is still Rev 2234. Defaults in SWORD utilities should remain consistent. David -- View this message in context:

Re: [sword-devel] osis2mod default versification

There are a few more changes that can be documented, such as the change of the flags regarding compression and the addition of other compression methodologies. Both SWORD and JSword properly support these. — DM > On Sep 5, 2015, at 3:22 PM, David Haslam wrote: > > All

Re: [sword-devel] GlobalOptionFilters in Conf files.

It probably shouldn't matter. And anyway, it's typically not expected that section or chapter headings would include words of Jesus. Even if this were the case, I can't see how it would cause a problem. I've never come across red letter markup within a title. Best regards, David -- View this

Re: [sword-devel] osis2mod default versification

Looking at the code, it has not changed. — DM > On Sep 5, 2015, at 5:08 PM, DM Smith wrote: > > It shouldn’t have changed!!! > — DM > >> On Sep 5, 2015, at 2:37 PM, David Haslam wrote: >> >> The de facto observation that recent builds of

Re: [sword-devel] osis2mod default versification

The de facto observation that recent builds of osis2mod make NRSV the default v11n raises several questions: When was this change sneaked in? Was there a formal agreement among developers? Was there any announcement? Why was this not mentioned on the Developers' wiki? Which other SWORD

Re: [sword-devel] osis2mod default versification

There have been changes to the osis2md syntax help in other respects. I just compared the help out put for versions 3177 and 3314. Below is the diff file. diff C:/Users/David/AppData/Roaming/Sword/Help/osis2mod.xiphos.help.txt

Re: [sword-devel] osis2mod default versification

The lack of documentation agreement on what the default versification is doesn't surprise me, but it should be fixed. It also doesn't affect me, because I never call osis2mod without specifying the versification to use, so I never use the default. This is a

Re: [sword-devel] osis2mod default versification

In modern Bible Translation (Wycliffe/SIL) circles, "default" versification in the translation programs (ParaTExt, SIL Translation Editor, and Teus' BiblEdit) is 'English' which is (as far as I know) the same versification as what Sword calls NRSV, so this change should be considered. It will

Re: [sword-devel] osis2mod default versification

All significant changes for osis2mod should be documented! Here's where past changes are listed. http://www.crosswire.org/wiki/Osis2mod#History_of_Changes Changing a default setting is one of the worst things a programmer can do! It would be better to have removed the default and made the

Re: [sword-devel] osis2mod default versification

It shouldn’t have changed!!! — DM > On Sep 5, 2015, at 2:37 PM, David Haslam wrote: > > The de facto observation that recent builds of osis2mod make NRSV the default > v11n raises several questions: > > When was this change sneaked in? > > Was there a formal agreement

Re: [sword-devel] osis2mod default versification

It is documented. It is the KJV. — DM > On Sep 5, 2015, at 4:33 PM, Kahunapule Michael Johnson > wrote: > > The lack of documentation agreement on what the default versification is > doesn't surprise me, but it should be fixed. > It also doesn't affect me, because I

Re: [sword-devel] osis2mod default versification

Osis2mod handles mid-verse section titles properly. The problem is elsewhere. They work just fine in Bible Desktop and other JSword applications. Regarding more v11n, this has nothing to do with osis2mod. osis2mod merely knows what SWORD makes available and allows that. — DM > On Sep 5, 2015,

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

I just tried a build with midverse section titles turned on with Xiphos, and lo and behold, it worked! Someone fixed something or my memory was faulty or both. Verified with kkl2015eb, Acts 9:19. (This is the newest Bible in the collection.) If you don't

Re: [sword-devel] osis2mod default versification

I think there is a misunderstanding. When i said NRSV is the default, thrn i meant simply that the bulk of all translations i load up are NRSV and i tend not to even consider KJV, unless forced to. It is quite clear that none of the tools havr changed, also the engine has not changed, nor is

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

Should I re-enable section titles (including mid-verse section titles) in the OSIS I feed to osis2mod? I recall discussions about things not working right, but don't recall the details of what failed how in which front ends. On 09/05/2015 11:22 AM,

Re: [sword-devel] osis2mod default versification

Re versifications, the need for any v11n needs to be established and well documented. Once in use we can not easily withdraw any v11n, so introduction happens careful, but nothing should stop you making a good case for specific new v11n(s). Domcox has just now produced two new v11ns which

Re: [sword-devel] osis2mod default versification

On 09/05/2015 02:23 PM, Peter von Kaehne wrote: Re versifications, the need for any v11n needs to be established and well documented. Once in use we can not easily withdraw any v11n, so introduction happens careful, but nothing should stop you making a good case

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

Yes Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 11:44 pm, Kahunapule Michael Johnson wrote: > > Should I re-enable section titles (including mid-verse section titles) in the > OSIS I feed to osis2mod? I recall discussions about things not working