Kahunapule Michael Johnson writes:
> Chronic or excessive bugs, or bugs that are serious but don't get
> fixed are a major problem.
> Designed-in bugs that don't get fixed are show-stopper problems.
I would be interested in -- entertained by -- even one example of any
Sword program or library who
"Troy A. Griffitts" writes:
> Yes. If you compile xiphos against sword svn, it should be fixed.
Yeah. Matěj, as a first effort, you need to upgrade to 3.1.5, just on
general principles, because a great deal has been done since 3.1.4.
Beyond that, building your own Sword library from SVN is beco
"Troy A. Griffitts" writes:
> Karl, I tried it on the new KJV and got stuff out from RenderText.
Yes, I confirm that the update makes KJV 2.4 display Psalm headings.
Thanx.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.or
Daniel Owens writes:
> But BibleTime, Xiphos, and BibleCS simply do not display the text of
> Canonical psalm titles. That is a severe bug.
Xiphos obtains headings using the canonical reference
mod.getEntryAttributes()["Heading"]["Preverse"]["0"] as passed through
mod.RenderText(). Period.
Troy
DM Smith writes:
> I'm not sure you're wanting a reply or just wanting to rip on OSIS as
> a "standard."
Not at all. Consider: I have a long history in IP communications, whose
RFCs are The Definition Of Interoperability. The idea of ambiguity in
such a field is virtually anathema. In the long
DM Smith writes:
> There is ambiguity about a title that is before the first verse in a chapter.
> Titles for sections should be within a section div. This solves the
> ambiguity problem for titles before the first verse.
Shouldn't The Standard have eliminated the ambiguity in the first place,
r
>> There are several versions of osis2mod about which produce different results.
> Revision 2358, 28 April 2009: The x-preverse div was added.
...
> Revision 2519, 4 June 2010: The x-preverse div was commented out.
...
> Revision 2668, 12 Nov 2011: The x-preverse div was put back in.
> Where does
We get somewhat routine inquiries about whether Xiphos can be made
available for Macs. At this time, we have no developer with a Mac so as
to do the packaging necessary. That said, it is perfectly possible to
build Xiphos for Macs:
http://surgut.wordpress.com/2009/12/27/xiphos-on-mac-os/
But wh
"Steven P. Ulrick" writes:
> When I attempt to build Xiphos from SVN, I get the following error if I
> use the included "waf":
> File "/usr/bin/xml2po", line 191, in
> main(sys.argv[1:])
> File "/usr/bin/xml2po", line 88, in main
> from xml2po import Main
> ImportError: No module name
David Haslam writes:
> I had McCheyne installed as a Daily Devotional module (when I was using
> Xiphos v3.1.4)
> In Xiphos 3.1.5 for Windows this is not visible anywhere!
If it's not visible in the sidebar module list or the mod.mgr, then you
don't have it installed. There is nothing about modu
Karl Kleinpaste writes:
> Building against latest Sword SVN is straightforward.
> Building against not-the-latest requires that you add
> -DNO_SWORD_SET_RENDER_NOTE_NUMBERS=1.
Unfortunately, I am a bit of a dummy. I had a glitch in the build
necessities for prior-to-yesterday's S
After entirely too long a delay, we have finally released Xiphos 3.1.5.
Windows users can get the installer immediately:
http://sourceforge.net/projects/gnomesword/files/Xiphos/3.1.5/xiphos-3.1.5-win32.exe/download
Or get the source tarball:
http://sourceforge.net/projects/gnomesword/files/Xiphos/
I just committed an updated patch to accomplish this, with Troy's OK.
He didn't like abusing RenderText() (and he was right), so it is
implemented as a trivial setRenderNoteNumbers(bool) in each of the 7
*htmlhref and *xhtml filters.
___
sword-devel mail
Daniel Owens writes:
> It is an enhancement for the sake of the user experience.
!! _*/THERE/*_ !!
Far too often we forget this axiom, maxim, principle.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/
"Troy A. Griffitts" writes:
> Again, I am not arguing against displaying publisher provided labels.
> I am arguing against forcing all frontends to display publisher
> provided labels.
If I were an author/publisher, I would walk away from Sword on that
basis alone. I'm not kidding one iota.
I (
Greg Hellings writes:
> You are using Lockman and the NASB as your example because of its
> prevalence all over the web.
[a] There is indeed an irritating difference between print publication
and electronic publication in footnote standards. I argued a bit some
years ago with bible.org people ov
Attached is an updated patch to do this as suggested by Greg. It makes
RenderText() take another default-value argument. No change to old
behavior, unless you explicitly provide that (4th) parameter as "true".
The patch sets a field in SWModule, which is then pulled into the
filters' user data s
"scribe...@gmail.com" writes:
> My thought on this is similar to strongs. Don't show the numbers. They
> are left overs from the era of print-only.
I disagree about that. Footnote/xref markers are obligatory in a very
large variety of publications, regardless of print or electronic form,
exactly
To date, we have DM in support of n=X content in *n/*x, as well as Brian
noting that consistency should be supported in that note numbers provide
the common language of note reference.
No one has suggested that such an update is a bad idea, though Troy
wondered aloud the other night in #xiphos abo
When I got home late last evening, I found that Troy and Greg had had a
conversation about this in #xiphos. Troy theorized and Greg confirmed
that Xiphos must be calling RenderText() too often; I hadn't noticed
this -- it happens in a "bridge" routine in Xiphos' backend by which to
call the engine
Quite a while ago, Xiphos gained the capability to post-process the
*n/*x that come out of the engine so as to add the n=X identifiers that
emanate out of OSIS and ThML markup. This is a fine and welcome idea,
but we have run into a problem.
Some modules have single-section content that is really
David Haslam writes:
> Is there an example module that uses *other lemmas*?
> I'd like to study how the filter *OSISLemma* works in practice for
> some of the front-ends.
TischMorph and 2TGreek use ThMLLemma.
You will find differences in provided lemmas in these 5 verses, as will
be seen by sele
Greg Hellings writes:
> Xiphos does not support it, either.
Xiphos will, within a month or so after we get 3.1.5 out the door.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to
Nic Carter writes:
> Are people able to make a brief comment about what the different
> front-ends can do and I can pass this info on to him?
Xiphos has text-to-speech; it requires that Festival be installed. See
Xiphos' Read Aloud option on the View menu, which will induce reading of
verses as
It would be mildly more helpful if:
[1] We had version stamps on all modules, and
[2] InstallSize was provided in *.conf.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubs
Brian J Dumont writes:
> You could sort of make one in Xiphos, but it was so ugly as to be
> totally unusable.
Considering that Xiphos really doesn't care what the engine feeds it,
the entirety of whether tables work in Xiphos is bound up in whether
OSIS->HTML filtration is sufficiently precise.
Greg Hellings writes:
> When Xiphos 3.1.5 is released the same will be true in it (display in
> Xiphos <= 3.1.4 is no different from opening a page in Firefox unless
> the user has compiled against GTKHTML or is using the Windows build).
Well, no.
Xiphos' main_url_handler() notices special sword
Aaron Christianson writes:
> If you don't know the Hebrew or Greek alphabets, it is possible that
> the Strong's transliterations will be more helpful to you (though
> those may also be in the 'real' versions, come to think of it).
As StrongsRealGreek's "about" observes:
Technical format rende
The "Real" versions in the Xiphos repository use real Hebrew and Greek;
the regular modules in the CrossWire repository use transliteration.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Ins
No, mid-verse headings are not handled at all well in Sword. Frankly,
the idea of a (modern) editor choosing to insert a heading at such an
exact point is absurd. We're lucky to get reasonable paragraph
boundaries most of the time at our already-artificial verse boundaries,
and section headings a
"Troy A. Griffitts" writes:
> This script removes all \r's from your file
You sure do like to work awfully hard.
sed -i -e 's/\r$//' foo.txt
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
i suppose it was intended to refer to the per-category, per-language
collapsing of lists so that they are not seen.
if it bothers you, change it. i don't care.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/lis
Chris Little writes:
> I just checked two print editions of Strong's, from different dates &
> publishers. Both have the correct 2992, so I think it's safe to
> correct. It's at least reasonable to assume your print edition is from the
> same publisher as these texts' print source, though.
FWIW,
Martin Denham writes:
> The user has suggested another possible OCR error. The error report makes
> sense but the Sword Strongs module appears to contain the same as other
> Strongs I have checked on the internet. Here is the users's report:
> 3532 Nikolaos nik-ol'-ah-os from 3534 and *2994*; v
FYI, StrongsRealGreek in the Xiphos repo has been updated, version
1.4-110905, to reflect this fix (3156, ref 3164 => 3161) as well as a
similar, previously reported glitch in 5043 (ref 5098 => 5088).
___
sword-devel mailing list: sword-devel@crosswire.o
It's an OCR error.
I just checked my real (print) Strong's. The entry for 3156 notes being
a shorter form of *3161* (as suggested), not 3164.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
If you peek at the "About" information for StrongsRealHebrew, you'll
find that it's taken from Jens Grebner's version, auto-edited with a
script to produce the ThML content comprising the module. If you wish
to work from this base, use that source directly; any update from there
is what I would re
David Haslam writes:
> btw. Two of the French Bibles with av11n do not display a file size
There is (supposed to be) a nightly script which updates the content of
all *.conf for valid InstallSize. If these are recent updates (i.e.
today) they will be corrected tomorrow.
I added a comment to the bug. It's a problem that's been mentioned
before.
The problem is the encoding of side-by-side xrefs as:
..., ...
where the comma is stand-alone, outside the constraint of either of the 2 notes.
___
sword-devel mailing list: swo
Greg Hellings writes:
> What does keeping htmlhref the way it is gain?
The wisdom of caution.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings
A Xiphos bug report...
https://sourceforge.net/tracker/?func=detail&aid=3291274&group_id=5528&atid=105528
...observes that searching for "[est]" in FreJND, without specifying
regular expression, causes Xiphos to crash.
He's right:
#0 0x003adac74749 in lucene_tcslwr(wchar_t*) () from
/us
David Haslam writes:
> Has anyone else looked at the behaviour of the up/down navigation controls in
> Xiphos when the current module is a Bible with non-KJV book order?
Sure. It doesn't work.
Xiphos is still pending av11n (non-KJV) support. Sorry. We're
currently entering the final stages of
""ref...@gmx.net"" writes:
> Arabic and Chinese don't have small caps
So how does content get rendered in those languages?
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to un
We had a bug report against Xiphos, that changing the base font size
when displaying RNKJV causes all text to resize _except_ divine names.
That is, module markup contains e.g. Yahushua
all over the place. What comes out of the engine for this includes its
own font size specification, without rega
Jonathan Marsden writes:
> Is Xiphos going to be able to switch away from xulrunner
Long in progress and coming along.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubsc
Mike Hart writes:
> I'm working on importing the Catholic Public Domain Bible.
There is already a CPDV module, in the Crosswire Experimental repository.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/s
Greg Hellings writes:
> Perhaps for you. Some people don't like to put together pipes of that size
One uses the weapons with which one is familiar. Between a one-line
pipeline -vs- constructing a python program including several imports,
knowledge of needed Sword methods (one of which you couldn
Karl Kleinpaste writes:
> $ mod2imp KJV | grep '^\$' | tr -d '$' | grep : | head -2 | while read key ;
> do read -u 17 line ; echo '$$$'"$key" "$line" ; done > text.vpl
Oops, remove the &q
python is too big a weapon for this.
given: a. text.orig containing verse reference-less text.
b. you're using bash.
$ exec 17 text.vpl
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Angel Candelaria writes:
> For some reason that didn't work
$ cat text.vpl
gen 1:1 in the beginning god created the heavens and the earth.
john 3:16 for god so loved the world that he gave his only begotten son...
$ sed -e 's/^\(.\+ [0-9]\+:[0-9]\+\) /\$\$\$\1\n/' < text.vpl > text.imp
$ cat text
Angel Candelaria writes:
> Is there a way I can add the required imp markup (I mean, the $$$
> before each verse and sections) in an automated way
sed -e 's/^\(.\+ [0-9]\+:[0-9]\+\) /\$\$\$\1\n/' < text.vpl > text.imp
___
sword-devel mailing list: swor
Matej Cepl writes:
> Hi, when trying to build the last checkout of xiphos SVN on Fedora 15, I
We're late, and we know it, but it's being worked on. Eliminating
xulrunner in favor of webkit once and for all, and dealing with F15's
new GTK3 weirdnesses are driving us right now.
Soon.
___
Mike Hart writes:
> Perhaps if the section were renamed something less offensive it might
> contain more works. Sectarian? or Unorthodox?
The conf directive is in fact...
Category=Cults / Unorthodox / Questionable Material
...as can be seen by actually looking at the *.conf for JST and Dia
There is a new note in forums that bible.org cannot be refreshed.
Manually testing, the user is right:
Name (ftp.bible.org:karl): anonymous
331 User anonymous OK. Password required
Password:
530 Login authentication failed
Login failed.
Neither "anonymous" nor "ftp" can authenticate to
DM Smith writes:
> Look for the element.
> You'll find it at a minimum in the Psalms.
Although there are such headings, notably in Psalms, they do not come
out of the engine in any obvious way.
Psalm 4:1 contains
To the chief Musician on Neginoth, A
Psalm of David.
But Xiphos, for one, expects
Bryan Fordham writes:
> Do you know if there's been any effort to create a module for Calvin's
> commentaries? Just installed PocketSword, and would love to have
> Calvin's stuff on there.
You simply have not looked.
See the CrossWire Beta repository, known as "CrossWire 2" in PocketSword.
_
To expand on Matthew a bit...
It is an extraordinarily Windows-centric view, that we should try to do
something _for one user_ during software installation _for the machine_.
Let the application figure out user-specific stuff when the user runs it.
In Linux, Xiphos (or BibleTime, or anything els
Karl Kleinpaste writes:
> The difference, it seems, is just whether there is non-empty content
> between .
Amend, RSThcsK also lacks a comma separating the individual
clauses.
___
sword-devel mailing list: sword-devel@crosswire.or
Checking on the state of these modules, the first one I tried in Xiphos
was RSThcsK. Xiphos crashed on it when I moused over an xref. I was in
Gen 4:3 when it happened.
Footnotes in RSThcsK are encoded e.g.:
Compare to NASBnew, where a Gen 4:2 xref is encoded:
Luke 11:50,
51
The differe
ESV Isaiah 1:10a
10 Hear the word of the LORD,
you rulers of *xy, *xz Sodom!
"*x_" are Xiphos' xrefs. The comma separating these two is not properly
encoded as being part of the xref itself; if one turns off xrefs, the
comma remains, creating a very odd, very wrong bit of punctuation.
A simpl
BTW, belated thanx to Nic for pointing that out for us.
I have to note that the Strong's content isn't zero-prefixed so as to
generate exactly-5-digits entries, either. Gen 1:1...
| In the beginning God created the
| heaven and the
| earth.
It's just an arbitrary, single, leading zero on all en
"Peter von Kaehne" writes:
>> Was his name Walther?
> yes, I think so.
"Oops."
Please contact him again and let him know that the problem is
understood, and is in fact pretty minor.
I wish lemma searches would automatically prepend '0' without making the
user worry about it.
_
"Peter von Kaehne" writes:
> I hope that was not the same publisher I waxed lyrically to about the
> joys of our software and how they could try it out on the KJV
> This very morning.
Was his name Walther?
___
sword-devel mailing list: sword-devel@
Someone came into #xiphos this morning to ask a few questions, one of
which was how to search for a Hebrew Strong's reference. His example is
H5062, "smite."
We can't get any search results from KJV for Hebrew at all.
I'm now experimenting with sword/examples/cmdline/search, having changed
char
Ben Morgan writes:
> When this last came up was when it was decided to put the Abbreviation field
> in the .conf files, but I don't know that
> a) it was done in any of the conf files
> b) any frontend authors added support for it
> If a) happens, b) is likely to follow.
[1010] [12:00 AM] awol:I
Actually, there's a module with an even longer Description. "Practice" has:
The Practice of the Presence of God: The Best Rule of Holy Life by Brother
Lawrence (Nicholas Herman, 1605-1691)
Gosh, that's annoyingly long.
Greg Hellings writes:
> One of my modules is [CONNOT] which is a decent ab
Greg Hellings writes:
> Description is overkill and probably not fit for display in a module
> selection widget - a description for the module would go something
> like:
> "Dr. Doe's classic commentary on the book of Galatians from 1977.
> Widely praised for its scholarliness and ecumenical appeal
Summarizing...
a. The regex is a horror.
b. The manual's definition is inconsistent, re: multiples.
c. The () -vs- [] syntax is wrong.
d. Whitespace isn't allowed at all.
e. Ignoring [d], there is a transform to something that ought to work,
but it's not known whether it actually does work.
So.
DM Smith writes:
> The problem with spaces in an osisRef is that a space is defined as the
> separator between one reference and another.
> E.g. osisRef="Rom.1.1 Rom.2.1-Rom.3.1"
Then I would like to think that either URL-standard '+' or hex-encoded
"%20" would work in place of a real space.
___
Matthew Talbert writes:
> Am I understanding this correctly that you have keys with spaces, and
> you put in NBSP and that all works in Xiphos? I thought that neither
> normal spaces nor NBSP would actually work.
I don't know how he edited it, but the import file has plain spaces, and
they work f
Peter von Kaehne writes:
> I have submitted to Karl for Xiphos a commentary for the Westminster
> Confession by Robert Shaw.
Now available there.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-de
David Instone-Brewer writes:
> BTW the Strongs Greek v.1.4 still lists 5054 (teknwn) as derived from
> 5098. This should be derived from "5088". This is in error in all
> online versions of Strongs
The point is valid but the bogus xref is in 5043, not (double typo) 5054.
___
Chris Little writes:
> I really wouldn't say that the collective output of people producing
> content in ThML for the Xiphos repository has any chance of countering the
> trend of OSIS/TEI content produced for CrossWire (numerically speaking).
It is not and never was any kind of competition. It
"Peter von Kaehne" writes:
> I would much rather we produced good modules and filed endless numbers of
> bug reports against any application and the library for non-compliance if
> things which should work do not work, instead of targetting the oddities
> and non-compliant aspects of each applicat
Greg Hellings writes:
> 2) I can provide an external CSS stylesheet along with my module.
> Then I could still use OSIS and, assuming well-defined use of HTML+CSS
> classes being produced from OSIS by the engine, I could style the
> module the way I desired. This would not require terribly much w
Chris Little writes:
> ThML's fading value in other genre notwithstanding, it has almost
> always been useless for Bibles.
I have generated 44 ThML Bible modules. They look quite good. My spin
of NET/NETnote is a heckuva lot better than bible.org's own -- far more
featureful, and more true to e
It is nothing more than a module markup flaw, and has presumably been
there since the dawn of time, considering that ASV is an ancient GBF
module.
As seen coming out of the engine, this is what Xiphos is given to work
with. Notice the opening , 3 lines down, which is not closed. Bear
in mind tha
DM Smith writes:
> InstallSize is also fairly recent and not all confs have it.
All 3 CrossWire repos (regular, beta, experimental) and the Xiphos repo
have InstallSize support.
Whether other publishers put it to use is an unknown.
For CrossWire repos, it's a nightly cron-driven script. All *.
Jonathan Morgan writes:
> I tend to dislike software that forces me to search in certain ways:
> whether it's "You must select the language before we show you what's
> available" or "You must select the type of book" or "You must select
> the publisher's repository", there will be some times when
On the one hand, I appreciate a desire for a combined all-repos view of
what's available. It would be useful in some ways. On the other hand,
I find it problematic for several reasons.
- It depends on finding all repos operating. Like it or not, repos go
away for short or long periods, and the
Matthew Talbert writes:
> Perhaps this isn't any better, but you can see the entire list here:
> http://ftp.xiphos.org/sword/zip/ Of course, it doesn't use very
> descriptive names, but it slightly more user friendly than opening the
> tar.gz.
Well, again, I don't want a _human_ cracking open mod
"Troy A. Griffitts" writes:
> I don't consider End Users Publishing and Publishing End Users the
> same thing :)
Well... I suppose I consider them alternate cases of the same
underlying technical capability: "I've got content that you can get."
> I believe your idea was for allowing users to pu
"Troy A. Griffitts" writes:
> Matthew Talbert had a great suggestion on IRC last night to simply add
> a 'prep for publishing' (or in his words simply "publish") option to
> the InstallMgr interface...
It's great, but funny, to see all the sudden interest in publishing
users' content. I've talke
Jonathan Morgan writes:
>> You can access http://ftp.xiphos.org/sword/mods.d.tar.gz, crack it open,
>> and see what's available. Just two assumptions:
>> - the zip subdir is at the same level as mods.d
>> - xyz.conf has a corresponding xyz.zip.
> Agreed. I can and have. I don't expect my avera
Jonathan Morgan writes:
> 2. Offering a list of downloads at CrossWire tends to suggest that
> they are the *only* books available. While I can download zip files
> from Xiphos FTP directly (for example), it's not easy to find out
> about
...
> BPBible relies on zip installation at present. I th
"Troy A. Griffitts" writes:
> Today I tried refreshing the Bible.org remote site in our list of
> repositories and the refresh process just hangs using CURL-enabled SWORD
> Can anyone else successfully run:
> sword/utilities/installmgr -sc
> sword/utilities/installmgr -ri Bible.org
You meant just
"Troy A. Griffitts" writes:
> does it happen when creating non-compressed modules (ModDrv=RawText)?
I have never seen this happen, in any of the ~40 RawText Bible modules
I've produced. (I've never bothered to generate compressed modules.)
I've reported problems with compressed lexdict modules
Matthew Talbert writes:
> more timely releases would make that job much easier all around
Amen, yea verily, and rah-rah-rah.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to u
The intent had been to release X3.1.4 when S1.6.2 came out. But we had
gotten done all that was needed, with more time to spare than we could
use. I'm sure that package builders will be aware of the release of
S1.6.2.
___
sword-devel mailing list: swor
David Haslam writes:
> Is this entry just FIO to advise prior to download, or does it make a real
> difference to module behaviour?
It is purely advisory to the user, if the application shows it to him.
It lets the user know whether he will spend a long time downloading, or
occupy a lot of disc,
David Haslam writes:
> When I view using Xiphos 3.1.3, Song of Solomon (any chapter) and Isaiah 1,
> for module NETfree, all the text appears bold.
An engine error, recently fixed by Troy, a tag open/close mismatch. Not
happening in current SVN Sword.
___
David Haslam writes:
> For a compressed Bible module, is this just the sum total of the file-sizes
> for the following files?
> nt.bzs, nt.bzv, nt.bzz, ot.bzs, ot.bzv, ot.bzz
> or is it something else?
As done for Xiphos and all CrossWire repos, it is a blunt total of file
sizes for all files in
We were overdue for a release. Lots of new features, mostly display-
related, some navigation-related, tooltips everywhere, sword:// handling
in Linux, many other things. See the SourceForge files area. Package
builders should be doing their thing soon.
_
troypulk writes:
> Is there a fix? and is anybody else getting this error?
In -r2560, I do not see this error in Fedora13. I have these ICU packages:
libicu-4.2.1-8.fc13.x86_64.rpm
libicu-devel-4.2.1-8.fc13.x86_64.rpm
___
sword-devel mailing list: sw
In the Xiphos repo, I've just placed a new module ACDCref, which is an
update to the ACDC module present in CrossWire Beta repo.
This module makes just one change: It wraps all verse references in
attributes, rendering them clickable. That's all. It's not
perfect, but it's a good step forward.
Jaak Ristioja writes:
> Why not branch?
Because branching is a whole new world of pain, for something as
straightforward as a workaround patch for a curl library bug. It's a
one-line patch, for pity's sake.
> Since there has probably been no announcement from Sword that distros
> should patch,
David Haslam writes:
> Well that's going to be the case anyway. Each SWORD (or JSword)
> front-end application would need to implement a media player
No, not at all.
If the resulting HTML returned by the filters is any sort of typical
"passagestudy.jsp?action=playMultiMedia" link, then Xiphos w
Karl Kleinpaste writes:
> the application probably has to hack the filter output to spackle in a
> standard miniature image to indicate it, to go along with the intended
> pseudo-picture actually-audio reference
It occurs to me as well that simply adding a standard "there'
Chris Little writes:
> If you mean to embed the audio in-line, I would recommend using the
> element. There's nothing specifically image-oriented about the
> element, aside from implications made by its name.
Yes, there is: The XXXhtmlhref filters wrap the resulting HTML
element in for the sak
Matthew Talbert writes:
>> I thought of that. But images have a separate tag (figure, I think)
OSIS , ThML .
>> a generic does not exist, does it?
Only in ThML, I'm pretty sure.
> I do think you would be better off splitting it into per-verse files.
Ow.
31,102 verses in KJV. At the very le
501 - 600 of 1158 matches
Mail list logo
