On Wed, Jan 06, 2016 at 09:07:48AM -0800, David Haslam wrote:
> As I continue to evaluate the efficacy of Aydeth's u2o.py script, this
> subject surfaced in my thinking.
>
> The \sr marker is described in the USFM Reference:
>
> Section reference range.
> · The text reference range listed under
Got it. Thanks! I have started
converting the 1965 Japanese Sinkaiyaku New Testament. It should
be converted and available on the eBible.org beta repository
within 12 hours if the Good Lord is willing and everything works
right.
On 01/06/2016 07:12 AM
On 01/06/2016 07:07 AM, David Haslam
wrote:
As I continue to evaluate the efficacy of Aydeth's u2o.py script, this
subject surfaced in my thinking.
The \sr marker is described in the USFM Reference:
Section reference range.
· The text reference range listed under
Both the \fr and \xo fields serve the
same purposes:
Provides a human-readable visual indication of where the
note came from, especially in media like printed pages and
PDFs.
Provides a back-link to the main text where appropriate,
The Sword Project has done some pretty
awesome things in open source Bible study software over the years.
Taking more than 12 years to release a NASB module in any form is
not one of them.
1) Yeah, it is a duplication of effort, but I have a scripted
On 2016-01-06, 22:04 GMT, Troy A. Griffitts wrote:
> I hesitate to even respond to this thread, as none of this
> kicks the can down the road, but...
I agree. Besides, I really do not believe Lockman Foundation
expects anything at this point. They would have to have
supernatural gift of patienc
I hesitate to even respond to this thread, as none of this kicks the can down
the road, but... I believe some of the issue has to do with typical open source
volunteer problems. Specifically, in this case, none of the pumpkin holders was
satisfied to build on their predecessors' code. I original
On 2016-01-06, 18:53 GMT, Troy A. Griffitts wrote:
> This is a commercial module to be sold by Lockman. That is
> a different scenario from other modules. For this module,
> I have reasonably asked:
I didn’t like Karl’s tone last time the flamewar went around,
but I have to admit he is right.
Yet another subject arising from working on a copy of u2o.py
Aydeth treated these two markers differently.
\fr is the footnote "origin" reference.
· This is the chapter and verse(s) that note refers to.
\xo is · the cross reference "origin" reference.
· This is the chapter and verse(s) that t
On Jan 6, 2016 12:53 PM, "Troy A. Griffitts" wrote:
>
> I don't want to fight about this yet again.
>
> This is a commercial module to be sold by Lockman. That is a different
> scenario from other modules. For this module, I have reasonably asked:
>
> 1) That we have a scripted, reproducible wa
I don't want to fight about this yet again.
This is a commercial module to be sold by Lockman. That is a different
scenario from other modules. For this module, I have reasonably asked:
1) That we have a scripted, reproducible way to transform their data
from their pristine source to a module.
I agree
> Gesendet: Mittwoch, 06. Januar 2016 um 18:20 Uhr
> Von: "David Haslam"
> An: sword-devel@crosswire.org
> Betreff: Re: [sword-devel] SFM to OSIS handling of the \sr marker?
>
> Addendum: The same applies to the major section range marker \mr
>
> As I continue to work on the Welsh Beibl
Addendum: The same applies to the major section range marker \mr
As I continue to work on the Welsh Beibl (to replace our NT & Psalms
module),
I will change my working copy of u2o.py
such that it will no longer convert either \mr or \sr to
...
This will affect 21 such headings in total, all of
On 01/06/2016 10:56 AM, Greg Hellings wrote:
> but no one has told me what those issues are
It comes down to this:
We need to look for the way to say Yes, and stop coughing up any and all
possible, weak, ham-handed excuses to say No.
A long time ago -- late '08 -- I flamed at length here about Get
> Von: "David Haslam"
> Does anyone agree?
s/agree/disagree/ more like...
No, I do not disagree.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your set
As I continue to evaluate the efficacy of Aydeth's u2o.py script, this
subject surfaced in my thinking.
The \sr marker is described in the USFM Reference:
Section reference range.
· The text reference range listed under a section heading.
· \sr is not equivalent to \r which is used for marking
> Thanks for the information.
>
> Is there a suitable online source?
1. Informations about bibliogrphy
https://nirc.nanzan-u.ac.jp/nfile/4128
Efforts in Japanese Bible Translation Since 1965
by Bernardin SCHNEIDER, OFM
Shinkaiyaku seisho (New Japanese Bible)
Organized and sponsored by the Lockma
Greg already has the aforesaid "David" in the NASB module testing loop. :)
"David" got to see the bugs before the module is released.
Notwithstanding, it's "a year and a day" since my last email to Greg on the
NASB.
Isn't there a rule about that?
David
--
View this message in context:
htt
Title: signature
For what it is worth, I already have
NASB source in USFM and OSIS, and have even generated a Sword
module for it the same way as all of the open access Bibles. I
just haven't posted it because of permission issues, but if you
have permission, then
They are still in exact the same status they were handed to me. I
haven't touched the lexica at all, I believe. They have vaguely been
said to have "issues", but no one has told me what those issues are,
and I haven't bothered to comb through for the issues they might have.
--Greg
On Wed, Jan 6,
On 01/06/2016 10:22 AM, Peter Von Kaehne wrote:
> I much rather would deal on the support line with complaints about NASB not
> working well on whatever than it still not available.
I could try to express how much in agreement I am with this sentence but
I cannot succeed.
Make it available, watch
Guys, I like perfect modules. But sometimes cutting corners and saying "This is good enough" (e.g. after 12 years of waiting and being told for half of these it is just around the corner) is probably appropriate.
It is easy to re-issue a module. We simply bump the version number... FWIW, Davi
I also have in my mind that the Hebrew and Greek lexicons Lockman includes with
the NASB still had some processing to complete, is that right?
On January 6, 2016 7:55:57 AM MST, Greg Hellings
wrote:
>The software requirement was JSword support - I forget which feature
>it was that was needed, b
That makes little sense. Many a time only attractive modules available have
changed the glacial speed by which some frontends improve. I much rather would
deal on the support line with complaints about NASB not working well on
whatever than it still not available.
Peter
> Von: "Greg Hellings"
On 01/06/2016 09:26 AM, David Haslam wrote:
> You mentioned MDB - that's certainly the MS Access file extension.
On Linux systems, "mdbtools" packages (main plus -devel, -lib, and -gui)
are available. The viewer tool is gmdb2 in mdbtools-gui.
Also, https://sourceforge.net/projects/mdbtools/.
_
The software requirement was JSword support - I forget which feature
it was that was needed, but Troy didn't want to proceed until
JSword/BibleDestktop fully supported the features.
--Greg
On Wed, Jan 6, 2016 at 8:53 AM, Karl Kleinpaste wrote:
> NASB has been a decade-plus in progress.
>
> Last
NASB has been a decade-plus in progress.
Last I knew or remembered, Greg's markup had gotten quite solid and, I
believe, finalized. There was something going on about necessary engine
support percolating out to one or more of the frontends before NASB
would be considered for release. Where do we
Thanks for the information.
Is there a suitable online source?
Please provide the link. Thanks.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/japanese-sinkaiyaku-bible-new-testament-1965-is-now-in-the-public-domain-tp4655598p4655600.html
Sent from the SWORD De
Hi DM,
You mentioned MDB - that's certainly the MS Access file extension.
For those who don't have Access installed, and if you only want to
read/view/export data, this is a useful tool.
http://www.alexnolan.net/software/mdb_viewer_plus.htm
I've used it successfully many times.
David
--
Vie
29 matches
Mail list logo
