It was pointed out to me that emptyvss isn't included in any of the
project files (either the Windows project files or the Make system) so
it won't be built by default. However, you should be able to add it into
the Make system fairly easily.
emptyvss is quite useful if you're testing modules,
SonWon wrote:
where do I find the options for mod2zmod? I tried here,
/www.crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/idx.jsp
I am wondering if it builds an index that points directly to the chapter?
As with all of our utilities, you can get the command line syntax by
running the
Kamal Abou Mikhael wrote:
To Whom it May Concern:
Genesis 18:25 only has the first three words of the verse.
Thank you for spotting this. The problem affected every verse that
crossed a page boundary in the Word files. I corrected the problem and
have posted an updated module.
By the way,
There's also BPBible, which has a portability as a conscious design
feature. See: http://bpbible.com/support/bpbible_portable
And, yes, this is all summarized in the FAQ:
Joachim Ansorg wrote:
Hi,
I just wanted to upload a fixed version of the GerLuth1545lh module I did
some
time ago.
I noticed there are updated version in the beta area now. Who did update
these?
What is the current status of those?
Joachim
Hi Joachim,
I just updated GerLut1545lh
Manfred Bergmann wrote:
Hi Joachim.
I just had a quick look. I opened the text on OpenOffice and exported
to LaTeX and xhtml which both look promissing to do further
conversion. Probably xhtml is better because it is valid XML.
Versenumbers are marked in both xhtml and LaTeX (kind
Thanks; it's all fixed now.
The problem was that the oe-lig was encoded as #156;, which will
appear fine in HTML-based frontends (but can't be searched) and will
disappear from view in BibleCS.
--Chris
David Haslam wrote:
In the module called FreBBB, all French words that should contain the
Karl Kleinpaste wrote:
Both of these modules' .conf contain
GlobalOptionFilter=OSISMorph
yet neither actually contains morph content.
Thanks for catching this. They actually do contain some basic morphology
content, but it wasn't encoded correctly. I corrected this and a number
of other
David Haslam wrote:
There was a very similar bug in the ISV module, the ItaDio module, the
ItaRive module. Probably several other modules too.
This *sounds* like its an old bug in an importer or in the drivers that
is being exposed because the bug has been fixed. If that's the case,
these
fred smith wrote:
As for the suggestion of replacing the OS, I intend to investigate that
but do not plan to leap into it without first verifying it is a good idea.
I want to be sure that any replacement will work with all the builtin
hardware, including the webcam, but most espcailly all
David Haslam wrote:
Has anyone in Crosswire ever thought about distributing these Indonesian
translations?
Bahasa Indonesia Seharihari
Terjemahan Baru
Terjemahan Lama
These are all available at CCEL, and they state the files were automatically
converted from data files supplied by the
Karl Kleinpaste wrote:
DM Smith [EMAIL PROTECTED] writes:
We have a wiki page regarding Eee PC running Linux.
The downside of that page's recommendation to use the standard Debian
repos is that the version of GnomeSword present there is chronically way
out of date. domcox' builds are
I think DM is planning to do some other work on osis2mod, so we can hope
he spots this bug in the course of doing that. The bug could possibly be
in the library itself.
I would suggest building the module correctly the first time. Fixing
this bug /should/ be a priority. How soon a priority
DM Smith wrote:
I think we can use JSword to test if this is a library bug or a module
bug. Can you point me to a module that exhibits the problem and a
reference in that module?
If it is a module bug, then it can be fixed in osis2mod.
-- DM
Excellent idea. The mir_BL_1988 module
Peter von Kaehne wrote:
Dear Chris,
Thanks for putting the AraSVD with vowels already up in Beta.
One remark - could you please put it up as an extra module and not
simply as an updated/improved version of the old module we had?
We can do that, but...
2 reasons:
1) Not everyone
Peter von Kaehne wrote:
2) The old version is public domain - this one is more restricted. A
public domain version has significant advantages for third party
distributers.
Which sorts of 3rd party distributers do you mean?
I think 3rd parties who are taking our content on CD (for example) to
Diatheke uses the API, which inherently understands linked verses. It's
not even possible for a Sword app to not return a value for a linked
verse if it exists because there's no difference from the data stored
for the primary verse.
Besides, I've seen the linking bug myself. I've got a couple
If you think it would help your efforts (which we certainly appreciate),
you could mention that WBTI gave us permission to distribute 40 Bibles
(38 NTs, a full Bible, and an NT+Psalms), primarily in languages of
Mexico Guatemala. There may be more, but that's the first batch. Those
will show
DM Smith wrote:
I'm wondering whether it is encoded sufficiently. I see how the module
is marked, but it doesn't seem that it maps well to the definition of
ruby. I'm not sure of the OSIS semantic that is being used.
For those who haven't looked at the markup, the first ruby annotated
word
DM Smith wrote:
Should SWORD directly render the gloss attribute? Or should it treat it
the same way as it does a lemma or a morph? And would it be a good time
to add xlit also?
Gloss is handled fairly similarly to lemma and morph. The render filter
should do something to render the
Daniel Owens wrote:
I am working on usfm2osis.pl still, and I am trying to validate the
output. The foreign element is giving me problems.
vbu26.out.xml:65535: element foreign: Schemas validity error : Element
'{http://www.bibletechnologies.net/2003/OSIS/namespace}foreign',
attribute
I found a nice little RFC 4646 language tag validator (and parser):
http://schneegans.de/lv/
--Chris
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your
Sebastien Koechlin wrote:
On Tue, Jul 01, 2008 at 02:07:09PM -0400, DM Smith wrote:
There has been an on-going debate as to whether one should have verses be
containers. To me it seems that sides are taken depending on ones role.
Software developers, using the SWORD engine, nearly always
Daniel Owens wrote:
Chris, why do you recommend SFMToOSIS over usfm2osis.pl?
If usfm2osis.pl gives you better results, then by all means, use it. But
SFMToOSIS was developed in close collaboration with a couple of
different Bible societies using the defined mapping between USFM and OSIS.
The set of 43 WBTI Bibles have been updated. The update affects the
.conf files only--don't expect any change in function or appearance
within the content. Indeed, the only change may be to the LCSH line.
Two modules have been renamed:
sco_BL_1986 became cso_BL_1986
xmt_BL_1983 became
Sebastien Koechlin wrote:
On Tue, Jul 01, 2008 at 02:07:09PM -0400, DM Smith wrote:
There has been an on-going debate as to whether one should have verses be
containers. To me it seems that sides are taken depending on ones role.
Software developers, using the SWORD engine, nearly always fall
DM Smith wrote:
Chris Little wrote:
It looks like I've finally found _one_ thing OSIS can't encode, related
to this. OSIS is unable to encode a paragraph that spans consecutive
books (because p/ can't contain div/).
There is actually a case in which this is needed, across the
1Kings
They all use TEI. If you use the HTMLHREF filters, then an early version
of TEIHTMLHREF is available. If you use the plain HTML filters, it still
hasn't been written. (Does anyone still use the plain HTML filters?)
--Chris
Manfred Bergmann wrote:
Hmm. The crash was for NASLex not for
Adrian Korten wrote:
Good day,
I'm a newbie with OSIS. Could someone say why you would prefer one over
the other? Or how this relates to how Crosswire handles the files?
ak
My interpretation of this question (in contrast to the existing
responses) was that it was not a question of why
** ThML is xml, but is layered upon HTML. It does not separate
presentation from content. Cross-references are ad-hoc.
ThML is also still (I think) used by the greatest percentage of our
modules (though that may be changed in the future).
Separating presentation from content is a nice
Karl Kleinpaste wrote:
Jonathan Morgan [EMAIL PROTECTED] writes:
ThML is also still (I think) used by the greatest percentage of our
modules (though that may be changed in the future).
...
Will GBF continue to be supported? I seem to remember that Chris
reported lack of GBF support as a
DM Smith wrote:
Of the current ThML module, there are 106 glossaries. (These probably would
be best to be encoded in TEI.) If we ignore these, since most people find
them useless and ignore them and because most front-ends can't do anything
useful with them, the number of ThML modules
Karl Kleinpaste wrote:
David Haslam [EMAIL PROTECTED] writes:
There are needed some improvements in punctuation -
eg. sometimes there's no space after a full-stop in the jvn module.
That might be legitimate in those languages; I wouldn't know. But the
modules' *.conf mention that one
David Haslam wrote:
Can anyone shed light on the following?
The SWORD module Ukrainian is the whole Bible of 66 books, as derived from
the CCEL file (ThML format).
No Sword Bible has ever been based on CCEL content. The TextSource line
in the module's .conf file will, more often than not,
David Haslam wrote:
Although the country code for the Ukraine is ua, CCEL had used the two
letter acronym uk for this module.
Strange but true.
uk is the ISO 639-1 code for Ukrainian (the language).
--Chris
___
sword-devel mailing list:
There's no regression. Most of these issues have never been features.
Karl Kleinpaste wrote:
I am experimenting with the just-released 1.5.11 Windows UI. It seems
to have problems with some modules with images.
- GnomeSword (manual module) displays no images, but there are
scrollbars that
jonathon wrote:
All:
I've just been asked about the copyright status of the following
resources created by _The Sword Project_
* Hebrew to Greek Dictionary of Septuagint Words
* Greek to Hebrew Dictionary of Septuagint Words
a) What is the copyright status of those resources;
It
You might also take a look at
http://www.crosswire.org/~chrislit/osis/BibleBookNames.html
--Chris
Wolfgang Schultz wrote:
Hi all,
i need for my data base with bible references some input. ;-)
http://code.google.com/p/truesharpswordapi/source/browse/trunk/usefullFiles/bnames.xml
My
I happened upon another review of free Bible software that I haven't
seen mentioned here before. Overall it is quite positive. And unlike
other reviews I've seen, it gives a brief examination of not just
BibleCS, but The Bible Tool too (in addition to a few pieces of
software/webpages not made
The About field actually has to be RTF (\u?-style). State your case
to Troy if you want this to change, but it doesn't make much sense to me
that we should want to include RTF markup and UTF-8 character encoding
(which isn't permitted in RTF) in the same field.
--Chris
DM Smith wrote:
I suppose we'll have to get Troy to clarify our position.
DM Smith wrote:
I may have misunderstood, but I understood that Troy already spoke on
this saying that SWORD allowed UTF-8 in RTF as an extension (I think
this was also stated on the old Module Making page) and that the
encoding
Manfred Bergmann wrote:
http://www.bible-researcher.com/luthercomma.jpg
I would say even in this ancient german the u is a u and not a v
be it at the beginning of a word or within.
Compare line 1, word 4, und vnd with line 5, word 10, vor vor. The
same character v appears at the
Karl Kleinpaste wrote:
There are a bunch of things that seem peculiar about content at
upper-level keys.
First, why is there a single top-level key /Jub? If there is no
actual division at that level, why does that level exist?
Standard references to the book of Jubilees will appear as Jub
Peter von Kaehne wrote:
It appears there's no ISO 639-3 code for Fnhd. I'll draw up a change
request to see if we can get a new code. If not, we should add a subtag
to the language of GerLut1545 to separate it from the real Nhd. material.
Not sure whether I like this. Luther and his
Peter von Kaehne wrote:
DM Smith wrote:
I have curiosity questions. Is it that it is actually the letter 'V'
or is it the letter 'U', but the glyph is looks like the letter 'V'?
I think the glyphs are used interchangably - a V shape is often used for
an u in the begin of a word, but
Eeli Kaikkonen wrote:
On Mon, 16 Jun 2008, Chris Little wrote:
AquinasSummaTheologica is a recent submission from Pedro Giffuni, based
on CCEL's (ca. 2002) OSIS 1.1 edition, converted to OSIS 2.1.1.
Just a quick thought: AquinaSummaTheologica is an awfully long name for
a module. I think
I'm redoing Barnes at the moment. There's no need to test the current
beta until a new version is posted.
--Chris
Peter von Kaehne wrote:
I tried to open Barnes in BD on Gen1:1 - the result was the computer
crashed. The processor load went up and the computer rapidly heated up
while the
Manfred Bergmann wrote:
Am 17.06.2008 um 22:05 schrieb Peter von Kaehne:
Manfred Bergmann wrote:
Well, if this text is supposed to be so then I guess no one can read
it any more nowadays.
Oh, I read it fine:-)
Well, it takes some effort. :)
This module is more for linguists I guess.
I guess your suggestion is that the material from Greek Daniel should be
removed from the text.
We don't do manual edits to text or manual versification changes.
Whatever is in the source goes into the module. The only exception is
those books that are not part of the 66-book canon, which
did you update?
Peter von Kaehne wrote:
Also a problem in BD - Matth 5 and 6 are not appearing red, nor anything
in Acts 1
Peter
Peter von Kaehne wrote:
I have a problem in GS, not tried yet BibleCS.
problems I found are also e.g. in Matt chapter 6 not red but for verse 1
Also Acts 1
Please take a look at the two Summa Theologica modules I've just
uploaded. I would like an opinion on which seems to be a better module
(and should be moved towards the public repository).
SummaTheologica is quite an old module (from 2003) and was previously
available in the beta repository as
If you would like to help with this, you can download the source
document in Zefania XML, make the corrections, and submit it to them and
to [EMAIL PROTECTED]
http://sourceforge.net/project/showfiles.php?group_id=89078package_id=93533release_id=339281
--Chris
Peter von Kaehne wrote:
This
The LXXM DRCgb modules are TreeKey-based Bibles. Troy committed some
basic VerseTreeKey code yesterday, so I put the two existing
VerseTreeKey Bibles in beta with the correct KeyType value to trigger
the new code. The modules themselves are fine, but the code is still
preliminary.
These
David Haslam wrote:
a. Words in italic type have been added for clarity. They are not found in
the original Greek.
This is transChange type=added/.
d. Words in oblique type in the New Testament are quoted from the Old
Testament.
This is seg type=otPassage/.
CSS supports both italic and
The markup is correct, but there is a rendering error in BibleCS. I see
two segments of red-letter text in Acts 1: vv. 4 7, but it should be
vv. 4-5 7-8.
I'll try it with milestoned q/ elements instead, to see if it
simplifies processing.
--Chris
Peter von Kaehne wrote:
The newly to beta
Daniel Glassey wrote:
2008/6/13 Chris Little [EMAIL PROTECTED]:
Peter von Kaehne wrote:
problems I could identify are
a) with RtoL - Persian is now RtoL but unligated
Can you try another program, such as notepad or wordpad, to see if they
show the same behavior. It's possible
Here you go:
http://www.crosswire.org/sword/modules/ModInfo.jsp?modName=ABUbeta=true
I wasn't really convinced that this was a unique Bible, but did find
some passages that I couldn't find in identical form elsewhere. (Just
the same, I'm not sure that there's much value in yet another 19th to
There's an update (version 1.3) to usfm2osis.pl:
http://www.crosswire.org/ftpmirror/pub/sword/utils/perl/usfm2osis.pl
I would recommend SFMToOSIS over usfm2osis.pl, but since our util is so
much easier to actually use, I thought it would be good to update it
nonetheless. The update (in
Peter von Kaehne wrote:
problems I could identify are
a) with RtoL - Persian is now RtoL but unligated
Can you try another program, such as notepad or wordpad, to see if they
show the same behavior. It's possible that Uniscribe isn't functioning
under Wine.
Does Arabic work correctly in
Unfortunately the sword module RSS feeds appear not to be working, so
I'll identify some new releases from the last few days here.
Brian's latest update to the Book of Concord is up in beta.
There are 4 new Japanese Bibles in testing. They include ruby annotation
in the gloss attribute of
I think BibleCS 1.5.11 is in a more or less final state. There remain a
few known bugs, but at this point it would be better to just release it
rather than continue providing nothing over 1.5.9.
--Chris
Peter von Kaehne wrote:
Hi, everyone is gearing up for a major release across board (all
Peter von Kaehne wrote:
Chris Little wrote:
I think © ... 1994 makes it pretty clear.
Not by necessity. Sometimes very modern stuff is freely available.
Your previous email made a comment about not being able to ascertain the
copyright status. The copyright status is clear.
How
Burmese/Myanmar has been in Unicode since 3.0, but it got a major
overhaul in version 5.1, which just came out a couple months ago. (And
apparently there are still felt to be some shortcomings in the new
encoding model.)
The Burmese Bible we have most likely uses the Unicode 3.0 model, while
Karl Kleinpaste wrote:
Chris Little [EMAIL PROTECTED] writes:
The suggested best course of action for today is to use the Eclipse SWT
framework since it will use pango on linux uniscribe on windows.
GS already uses pango, and has the same mistakes (relative to WorldPad)
as seen in BT
DM Smith wrote:
On Jun 6, 2008, at 7:13 PM, Ben Morgan wrote:
Just a question - do you think that the GUI controls, such as text
boxes and lists and what not (everything but the actual text of the
module), should be able to have a different font from the actual
text? Currently under
Daniel Glassey wrote:
2008/6/6 Karl Kleinpaste [EMAIL PROTECTED]:
Activity of the last couple weeks, at ftp.kleinpaste.org in /pub/sword:
3. EarlyFathers, from public domain content, distributed as freeware in
WinHelp format; a monstrous genbook collection (37 volumes when in
print) of
DM Smith wrote:
Chris/Troy,
Can we please actually add this to the conf's. I think it becomes
important for larger modules, so perhaps, we say that the default for
the entry is 2M? (or whatever would be about 15 minutes on dialup) I
don't see any reason that it needs to be highly
DM Smith wrote:
On Jun 7, 2008, at 12:05 AM, jonathon wrote:
On Fri, Jun 6, 2008 at 8:34 PM, DM Smith wrote:
(Such as ISO-639 for languages). I'm not sure that even if such a
notion existed whether we could make it understandable to users.)
What about using ISO 15924?
Daniel Owens wrote:
I will watch that page, but thanks for helping me with the syntax. I
will see how it goes with the Perl script and decide what to do next. I
expect to need to transform a few USFM Bibles in the next year or so.
Where do I find USFMToOSIS? Google didn't list any hits.
New in beta is a complete re-do of the WebstersDict module, now called
Webster1913. This is mostly intended for developers and module makers.
Nothing is necessarily final. I'm open to suggestions about anything.
The module uses TEI, so expect no decoration or extremely poor/incorrect
Peter von Kaehne wrote:
I just had a look at the beta module section on the server. There are
many modules now in there for over a year or so.
What exactly is keeping them back to join the ordinary repositories?
Many modules are simply waiting for a version of BibleCS 1.5.9 to be
Ben Morgan wrote:
I've just released BPBible 0.3, which adds many more features.
It also has a new website, with forums and screenshots at http://bpbible.com
Congrats on a new release. It looks nice.
BPBible also uses a new locale, which gives nicer references than the
traditional ones
I
I'm currently working on a recommended process for converting (U)SFM to
OSIS. So keep an eye on
http://www.crosswire.org/wiki/index.php/Converting_SFM_Bibles_to_OSIS in
the coming days. Truthfully, I don't think I can recommend using
usfm2osis.pl. I think Snowfall Software's USFMToOSIS will
Glen Pfeiffer wrote:
jonathon wrote:
Well, a verse, presuming non-commercial usage would be fair
use.
But what we're really talking about is I am breaking to law if
I copy and paste EVERY verse from e-Sword to wordpad on the
same computer. And that's definitely copyright infringement.
Just send to [EMAIL PROTECTED] (My mention of the other was in
error, and it should bounce back to you.)
But you should submit it again, because I haven't received anything from
you in roughly a year.
--Chris
Brian J. Dumont wrote:
Hi all,
What is the correct way to submit module
JECompton wrote:
Well I've spent some time becoming more familiar with the community and
the SWORD api. Reading the to-do list on the crosswire website confirmed
my decision to commit to helping in what ways I can. The api overview
reminded me of how weak my C++ knowledge is. I will continue
There's a very insignificant update to the utils again. (Only the
compiled sword utils. And all of the DLLs are still up to date.)
This includes ICU 4.0 d02 code. (Draft 2 of 3 scheduled.) The next draft
of 4.0 is coming in a couple weeks, and the final will be in about a
month. So, unless you
CrossWire does not condone or support the use of scraper scripts. Their
use is abusive to content hosts because of the traffic it causes. And in
no way is their use with copyrighted texts anything but illegal--this
isn't fair use. It's copyright violation.
If you are still intent on breaking
John H. wrote:
Not breaking the law. As it has been made clear on this list, none of
you guys are lawyers, and as a lawyer myself, I am not quite sure where
the idea came from on here that if you download a bible it is any more
illegal than using miro for youtube, or cbs.com. This has
jonathon wrote:
On Sat, May 31, 2008 at 2:41 PM, John H. wrote:
You're also saying that having a legal electronic license of a translation
of the bible, for use in esword, otherwise, means that I am breaking the law
if I copy and paste a verse from esword to wordpad on the same computer.
John H. wrote:
On Sat, 2008-05-31 at 15:14 -0700, Chris Little wrote:
jonathon wrote:
On Sat, May 31, 2008 at 2:41 PM, John H. wrote:
You're also saying that having a legal electronic license of a
translation of the bible, for use in esword, otherwise, means that I am
breaking
John H. wrote:
Chris, this is interesting coming from you, the same person who referred
to me as both hitler and I just found out while I wasn't even in the
channel on irc that you said I had mental problem. I think you're not
in any place to say what is and is not christian. Yet you
Sounds great. I'm willing to bet that none of the frontends can render
the Myanmar script correctly, but the existence of such content would
help to underscore the importance of improving Unicode complex script
support across the board (via integration of ICU, Graphite, etc.).
--Chris
David
for Unicode 5.1, so if you are
using utilities that perform normalization, make sure to grab the new
utilities.
--Chris
Chris Little wrote:
The utilities are updated once again, this time to 1.5.11 final:
http://crosswire.org/ftpmirror/pub/sword/utils/win32/
There are individual zips for each
Bear in mind that this is the work of an individual, with a fairly
specific purpose in mind. And the page is also a bit out of date and
fairly inaccurate with respect to OSIS.
The fact that Paratext figures into the evaluation makes fairly clear
that this is a discussion specifically intended
The utilities are updated once again, this time to 1.5.11 final:
http://crosswire.org/ftpmirror/pub/sword/utils/win32/
There are individual zips for each utility as well as an
allutilities.zip with everything in a big bundle. They need icudt38.dll.
Separately, but in the same location, I've
Daniel Owens wrote:
Like I said, for what it's worth... Perhaps Lexique will give you some
food for thought. It's a nice program for producing a nicely typeset
dictionary quickly and with minimal expertise. I might create Perl
scripts to go between TEI and their format if I ever have the
http://crosswire.org/ftpmirror/pub/sword/utils/win32/
There are individual zips for each utility as well as an
allutilities.zip with everything in a big bundle. They need icudt38.dll.
--Chris
___
sword-devel mailing list: sword-devel@crosswire.org
BibleCS InstallManager:
http://crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/alpha/BibleCS-1.5.11RC1.zip
Also requires icudt38.dll if you don't have it:
http://crosswire.org/ftpmirror/pub/sword/utils/win32/icudt38.zip
___
sword-devel mailing
Diaspora is no longer under development or supported. We no longer
distribute Diaspora, either. And anyone who IS distributing Diaspora is
probably doing so in violation of the license, because they aren't
including or offering the source.
Source is still available via SVN, but requires BCB to
DM Smith wrote:
On May 12, 2008, at 7:10 PM, Chris Little wrote:
Our plans are to use TEI for dictionary encoding from here forth.
Chris has started a wiki for how to encode a TEI dictionary. See:
http://www.crosswire.org/wiki/index.php/TEI_Dictionaries
In Sword's svn you can find
The original private protocol syntax for Sword (which is what is
implemented in BibleCS) is:
sword://{module}/{key(list)}
Our test page is: http://www.crosswire.org/~chrislit/testlinks.html
BibleCS configures the private protocol handler in Windows when it
loads. There's also a Libronix-style
Karl Kleinpaste wrote:
(As it happens, GnomeSword understands sword:// and bible://
equivalently, but I suspect we should do away with the latter.)
I had thought that BibleCS handled bible:// too, but when I checked
earlier, it didn't.
I'm open to adding bible://. It's certainly an easy
DM Smith wrote:
Chris Little wrote:
I think simply
sword://Josephus/The War of the Jews/Book 1/Chapter 2/Section 3
should work, or
sword://Josephus/The%20War%20of%20the%20Jews/Book%201/Chapter%202/Section%203
encoded as an URL.
This does not answer the osisID question. If one had
Manfred Bergmann wrote:
MacSword uses the following schema for URLs:
sword://[FilterOption[[EMAIL PROTECTED]ModuleShortName/Key|KeyRange
This is how I found it.
I'm open to implement a standard if this has been besided.
What would you think of putting filter options in the query segment
Our plans are to use TEI for dictionary encoding from here forth. At the
moment we have some support for both P4 and P5 conversion to RTF (used
by BibleCS), plain, and HTMLHREF (used by GnomeSword, BPBible?,
others?). So...
Issue 1:
Which filters remain necessary before we can declare that
There's a database problem (again). News the news feed are down,
though the forums are still up.
--Chris
Greg Hellings wrote:
My RSS feed reader (Mail 3.2 for Leopard), complains that the Sword
RSS feed isn't active. Has the URL changed of late and I missed the
notification, or is
BosworthToller has an error, either due to encoding or to an import
error, which causes it to loop on the entry for 1. Any frontend or
utility that iterates through all keys should hang at the same point.
--Chris
Karl Kleinpaste wrote:
I have found that indexing is not working on some
Steven P. Ulrick wrote:
I will be more than glad to test the BosworthToller module if you can
help me with the following:
1. If I really do need Sword 1.5.11 to use this module, how do I get if
if the most recent version in SVN is 1.5.10?
BosworthToller does require 1.5.11 in that it
DM Smith wrote:
On May 7, 2008, at 1:42 AM, Ben Morgan wrote:
Hi,
Just a few questions about unicode things.
Are VerseKeys and TKs UTF-8?
I'm not sure how to answer the question with respect to VerseKeys.
They're not tied to specific modules, and whether they are UTF-8 or not
depends
701 - 800 of 1869 matches
Mail list logo