The xulsword front-end has been entirely refactored using React, Electron
and NodeJS. It is available for Windows and Linux on GitHub:
https://github.com/JohnAustinDev/xulsword. MAC is coming.
There is no longer any XulRunner dependency (XulRunner went the way of the
dodo years ago which stopped x
I'm updating old modules in IBT's repository to use CrossWire best
practice OSIS, using usfm2osis.py. So these OSIS files are CrossWire
standard, but the corner cases are revealing some bugs to fix. I've
reported these on Jira, along with patches, but mention them here in
case there is discussi
T, KHKDICT, TBNDICT, TVNDICT, etc.
I suggest that you make contact with the xulsword developer, John Austin.
xulsword is hosted at https://github.com/JohnAustinDev/xulsword
John also uses this mailing list occasionally.
Best regards,
David
--
View this message in context:
http://sword-dev
that might either be interfering with the SVN command or helping
the web browser?
Troy
On November 5, 2015 11:27:44 PM MST, John Austin http://gpl.programs.info>@gmail.com> wrote:
Something has changed so that for the past week now, the CrossWire
subversion server has been unreachable fr
Something has changed so that for the past week now, the CrossWire
subversion server has been unreachable from Central Asia.
This:
svn checkout http://crosswire.org/svn/sword/trunk ./
Only returns this (after a time-out wait):
svn: E000110: Error running context: Connection timed out
Access to
Peter is right. Looking toward the bigger and brighter future, the
module name should be an internal code to represent a particular text
from a particular publisher. By "publisher" I mean whoever actually
created the module, not the copyright holder. If another publisher wants
to issue the "sam
On 08/27/2015 02:33 AM, Kahunapule Michael Johnson wrote:
If I use the new versifications to create Bibles, using the updated
Sword library and osis2mod that includes these versifications, will
those modules work properly with existing older Sword applications using
older versions of the Sword li
IBT's repository has dozens of SWORD Bible modules, and they all need to
be rebuilt for SWORD 1.7+ using OSIS module best practices (as outlined
in the extremely useful CrossWire wiki). Below are some conceivably
controversial issues. We hope to achieve excellent module functionality
with the v
This sounds great! Hopefully this will also result in adding support for
compressing RawCom4 commentaries? Currently this is not possible, but
would sure be great to have. Thanks Chris!
-John
On 03/18/2014 12:43 PM, Chris Little wrote:
We've got quite a few classes in Sword that essentially d
gram. When the
change is a work-around for something that shouldn't be in module, I
think we should avoid that. For example, the NET Bible has some bugs
that should be fixed. But instead we have some special code that is
essentially: if module is NET then fix such-and-so when it occurs.
Tog
ess another question is: are links
within Bible texts allowable practice? If so, everyone benefits from a
filter. But if not, what other approach is there?
John
Troy
On 09/25/2013 06:22 AM, John Austin wrote:
I've read through the current SWORD osis option filters, to see if
ther
I've read through the current SWORD osis option filters, to see if there
might be a way to do textual references to external works which can be
filtered with existing filters. There appears to be no way to do this using
existing filters. (?)
I am open to changing the way IBT's OSIS modules are enc
Should a dictionary/glossary link filter be added to SWORD? These links
are a perfect way to allow instant access to maps, pictures, tables, and
to explain terms which are found in the text. But sometimes users want
to turn these links off, so a filter is needed.
Such a filter is already avail
of the empty method which John
pointed out.
I didn't evaluate the logic of the actual implementation. I am going
off the assumption that it worked :) If we have any troubles with it
(John could you test your use case), then we can change the
implementation to use Jeff's suggestion.
Tr
I've been testing the latest SWORD code for some time now, with
xulsword, on both Windows and Linux, and it's working great. But I did
just discover that Lucene searches in some non-versekey modules fail
because utilstr.cpp's wcharToUTF8() has not yet been coded. It's got
"TODO: finish this log
a second
Synodal is the right answer in the end. Although this v11n may be used
by more than "Protestants", so perhaps Synodal2 would be more correct?
Actually I believe that this is exactly the approach that Paratext
offers- different Synodal verse
nswer in the end. Although this v11n may be used
by more than "Protestants", so perhaps Synodal2 would be more correct?
Actually I believe that this is exactly the approach that Paratext
offers- different Synodal verse systems to choose from.
John
2013/5/13 John Austin mailto:gpl.pr
On 05/13/2013 05:34 PM, Костя Маслюк wrote:
No need to introduce new functions because last chapter would be always
calculated via getChapterMax().
I think that getChapterMax returns the maximum chapter in the verse
system. But we still need something like lastChapterPresent to return
the m
On 05/13/2013 10:30 AM, Troy A. Griffitts wrote:
We have the first part already in the API:
SWModule::hasEntry(const SWKey *)
What sort of use cases do we have to build further API calls on this?
vector getBooksPresent()
???
Yes- or even just:
bool isBookPresent(aBook)
and there also pro
On 05/12/2013 02:19 PM, David Haslam wrote:
Thanks friends.
I wasn't trying to muddy the waters at all, but I myself had wondered
whatever had happened after the detailed discussion about "scope" in .conf
files.
Yes- The Scope param, if properly implemented, can solve many problems.
I would
On Mon, Apr 15, 2013 at 12:38 AM, Peter von Kaehne wrote:
> On Sun, 2013-04-14 at 18:19 +0200, Matěj Cepl wrote:
> > What
> > should be the SEMANTIC name of the suggested new element?
>
> Please read my post and John's reply.
>
> Most of the occasions where the element is in use it would be suff
On 04/13/2013 05:35 PM, Peter von Kaehne wrote:
Can I try and summarise what I think is going on here?
Basis of problem:
1) CrossWire has a whitespace/title/poetry problem which has been
discussed at nauseam for many years. But it has neither been thoroughly
resolved nor even isolated. Various
On 04/14/2013 04:39 AM, Matěj Cepl wrote:
On 13/04/13 03:54, John Austin wrote:
It says right on the tag: "indent". So anyone at anytime, who knows some
English, will know exactly what to do with this tag in any situation. It
is ideal really. Please note that this would NOT be the c
On 04/13/2013 03:06 PM, Chris Little wrote:
On 4/12/2013 9:42 PM, John Austin wrote:
I still can't see the argument for requiring that everyone call these
questionable instances paragraphs, and require that they must always be
marked up as such. Why not give the publisher the opti
On 04/13/2013 03:06 PM, Chris Little wrote:
On 4/12/2013 9:42 PM, John Austin wrote:
I still can't see the argument for requiring that everyone call these
questionable instances paragraphs, and require that they must always be
marked up as such. Why not give the publisher the opti
indent, then the text can
be encoded true to the translator's wishes on a case by case basis. This
will in turn improve comprehension of Sword texts in other languages.
This will save all the translators' content for future generations. I
think it would work out great.
John
Jo
On 04/13/2013 09:24 AM, Chris Little wrote:
On 4/12/2013 11:18 AM, John Austin wrote:
On 04/12/2013 07:45 PM, Chris Little wrote:
I've worked with many, many SFM texts, and they often do not follow SFM
rules or play nice in a variety of ways. All of this greatly
complicates
an al
On 04/13/2013 09:24 AM, Chris Little wrote:
On 4/12/2013 3:31 AM, Peter von Kaehne wrote:
Having said this, I think if there is a large number of existing modules
which get insufficiently rendered and if the patch required is small,
then I would suggest a two pronged approach:
1) accept the pa
On 04/13/2013 09:24 AM, Chris Little wrote:
On 4/12/2013 6:58 AM, Greg Hellings wrote:
On Fri, Apr 12, 2013 at 6:57 AM, John Austin
mailto:gpl.programs.i...@gmail.com>> wrote:
You didn't address my main point: Content providers should be given
a way to have final contr
On 04/13/2013 07:34 AM, Greg Hellings wrote:
On Fri, Apr 12, 2013 at 4:37 PM, Matěj Cepl mailto:mc...@redhat.com>> wrote:
My point was that documents are more valuable and more difficult to
change than programs. So we should orient on perfecting documents
and change programs if
On 04/13/2013 02:35 AM, Matěj Cepl wrote:
I am sorry, if I am too harsh, but it seems that the SWORD project is
already slipping on this dangerous slippery path towards making its
products useless for its intended purpose (long time record of the
Biblical texts for any possible purpose), so I wan
On 04/12/2013 07:45 PM, Chris Little wrote:
On 4/12/2013 4:57 AM, John Austin wrote:
You didn't address my main point: Content providers should be given a
way to have final control over how their formatted texts appear, and one
which is simple and reliable. I'll comment below, b
On 04/12/2013 03:26 PM, Chris Little wrote:
Executive summary:
I don't have a problem with making it clear how to encode indented
paragraphs and line breaks and improving support for diverse paragraph
types.
I do have problems with the specific syntax and the rationale described
below.
Sword should support basic indents and line breaks. Content providers
should be able to control the formatting of their texts and should not
be required to assign their content to artificial ... or other
containers to do so. Although these containers might be useful, the text
of some translatio
I'll do that. I meant to post this to jsword-devel rather than
sword-devel. So I'll post there...
John
On 10/29/2012 03:48 PM, David Haslam wrote:
John,
Has this been reported through http://www.crosswire.org/tracker/browse/JS ?
If not already done, it would be sensible to create an issue the
A patch for JSword is attached. The Verse class was not maintaining
its own versification value and so it was impossible for Verse to
operate properly in some circumstances. This ultimately led to
unhandled exceptions when reading certain passages from non-default
versified Bibles such as IBT's UZV
The xulSword program used primarily in Russia and the CIS has been
relying on Sword's own built in v11n capability since shortly after
1.6.1 was released. From that time a number of IBT texts have already
been released which use the "Synodal" verse system, including Russian
modules, Kazakh, Crimean
Xulsword (pronounced zool-sword) is now available for download and
collaboration at:
http://code.google.com/p/xulsword/
Xulsword is a Bible reading and study tool which is easy and fun to
use, yet very powerful at the same time. The marriage of Xulrunner
with SWORD provides the best of both world
go about applying to have this canon added to the list?
Localization is a separate issue since there are many different
languages in Central Asia alone. However, most translations in this part
of the world do use the Russian verse system, so it might be good to add
native sup
39 matches
Mail list logo
