So the latest SVN version of osis2mod (Rev: 2197, anyway) solved my
problems with section headings and verse numbers. (Yay!) But I failed
to notice what it was doing with my chapter titles: Chapter 11 was
getting as its title "Chapter 12", and so on. I added a chapter title
to Chapter 2, and Chapte
Hi,
On Tue, Dec 2, 2008 at 10:16 AM, Ben Morgan <[EMAIL PROTECTED]> wrote:
> In case you hadn't noticed, GoBible has the dagger link at the bottom, and
> is missing its graphic, as is Alkitab.
First, thank you for the inclusion of Alkitab in Crosswire web site,
it is very appreciated..
And if y
On Tue, Dec 2, 2008 at 2:05 PM, Peter von Kaehne <[EMAIL PROTECTED]> wrote:
> OK, now the frontpage is _really_ unwieldy ;-)
>
Looks much better, thank you.
I have listened to the various comments and have re-incorporated all
> sword applications but for the truly and irredeemably dead ones.
OK, now the frontpage is _really_ unwieldy ;-)
I have listened to the various comments and have re-incorporated all
sword applications but for the truly and irredeemably dead ones. I will
find a solution for the Palm ones. I do think BpBible should stay in.
Maybe we can convince them to upgrad
On Sun, Nov 30, 2008 at 12:00 AM, Chris Little <[EMAIL PROTECTED]> wrote:
> The other (very good) possibility is a problem with the importer. DM
> just did a rather radical update to osis2mod (and by "just", I mean
> since 1.5.11). So my first question would be: are you using osis2mod
> from 1.5.11
On Tue, Dec 2, 2008 at 6:52 AM, Peter von Kaehne <[EMAIL PROTECTED]> wrote:
> > I would agree with DM that in-development stuff shouldn't be on the
> > front page yet. If the developers don't feel their work is up to version
> > 1.0 status, I don't think we should be directing traffic there yet.
>
There are two main determinants for choice of programme - platform and
translations. My suggestion is that I somehow incorporate the number of
languages a particular programmme is translated in. Not sure.
Peter
___
sword-devel mailing list: sword-devel@
OK, I can't remember all my arguments for keeping the infamous
"Pre-verse hack", but generally, the logic goes something like this:
module content is displayed in many different contexts: the obvious
contextual display, search results, popup verse lists for x-ref,
references, etc. parallel disp
I like this idea. It is great to programmatically tag the text with the
importer. I would suggest something more general like:
Great idea Chris.
Chris Little wrote:
> I just filed an improvement task in the bugtracker for this
> (http://www.crosswire.org/bugs/browse/API-104), but thought I
Peter von Kaehne wrote:
>
>> Troy might have a better feel for the current state of Linux on
>> handhelds (QPE/Linux on iPaq). I don't know whether it was necessarily
>> time to remove these yet.
>>
>
> To be honest i always thought this was a hobbyists field - no Linux PDA
> ever made it, Z
> Thanks for suggesting this. I thought everyones' heart was set on
> Diatheke, I could not bring up the courage to suggest this ;-)
So, are we planning to have any visibility of a command-line tool?
> I agree with logos. But we might not have any for some applications.
> Will look.
I think some
I just wanted to send out a quick note to let you all know how much I
truly appreciate you guys. I realize we all don't agree on everything,
and sometimes don't get along well with each other, but with the
semi-private apologies I've seen and the way everyone is truly committed
to living toget
Am 01.12.2008 um 21:30 schrieb Daniel Glassey:
> 2008/12/1 Eeli Kaikkonen <[EMAIL PROTECTED]>:
>> On Mon, 1 Dec 2008, Matthew Talbert wrote:
>>
>>> Also, perhaps a demonstration of where all they can get help. The
>>> manual, mailing list, irc.
>>
>> I'm not in a position to tell you what to do,
Hi Daniel,
are you still the maintainer of the libsword and bibletime packages in Debian?
mg
On Monday 01 December 2008 21:30:03 Daniel Glassey wrote:
> 2008/12/1 Eeli Kaikkonen <[EMAIL PROTECTED]>:
> > On Mon, 1 Dec 2008, Matthew Talbert wrote:
> >> Also, perhaps a demonstration of where all th
2008/12/1 Eeli Kaikkonen <[EMAIL PROTECTED]>:
> On Mon, 1 Dec 2008, Matthew Talbert wrote:
>
>> Also, perhaps a demonstration of where all they can get help. The
>> manual, mailing list, irc.
>
> I'm not in a position to tell you what to do, but the topic is
> interesting and useful for other softw
Chris Little wrote:
> Just some quick notes:
>
> *please* dump the whole Diatheke section. As a CLI, it's fine, but it's
> really part of the library/utilities distribution. The ActiveX control,
> PQA, and CGI stuff are all way out of date.
Thanks for suggesting this. I thought everyones' heart
Just some quick notes:
*please* dump the whole Diatheke section. As a CLI, it's fine, but it's
really part of the library/utilities distribution. The ActiveX control,
PQA, and CGI stuff are all way out of date.
Looking through the list as a whole, I find the screenshots very
underwhelming. Som
I just filed an improvement task in the bugtracker for this
(http://www.crosswire.org/bugs/browse/API-104), but thought I would also
propose/mention it on the list. I'm proposing that we tag modules,
within the module itself, with the revision of osis2mod that was used to
create them. This shou
DM Smith wrote:
> I think Chris's caveat is correct. The latest version in SVN does have
> one reported bug and may have more. But please see if it works with
> your module!
I should mention, people can assist in testing the new osis2mod even if
they don't have texts to import and don't hav
Great start.
Couple of thoughts:
The page has always been a bit terse. I think a very short introduction
would be in order.
I suggest listing the front-ends first and the "projects" second. Or
moving the projects (aka development entirely to the wiki). Several of
us postulate that this page is
Hi,
Following previous discussions on the list I have started reworking the front
page of the project. I have no ambitions as a web designer, but simply wanted
to update the page, remove dead links (micros, diatheke CGI, BibleStudy) and
add links to active projects which compile on the current
On Dec 1, 2008, at 9:21 AM, Chris Little wrote:
>
>
> David Haslam wrote:
>> I just wonder if all these "bugs" would be solved if we were not
>> using an
>> Windows osis2mod build as old as June 2008.
>
> The June 2008 build of osis2mod corresponds to the Sword 1.5.11
> release.
> I know that
David Haslam wrote:
> I just wonder if all these "bugs" would be solved if we were not using an
> Windows osis2mod build as old as June 2008.
The June 2008 build of osis2mod corresponds to the Sword 1.5.11 release.
I know that DM wants us to test and use the more recent SVN version, but
given
Hello,
the perl script version 1.1 handles the apocrypha book numbers wrong
here is the revised script that does the job now
http://zefania-sharp.svn.sourceforge.net/viewvc/zefania-sharp/trunk/utils/perl/zef2osis.pl?view=log
have fun
wolfgang
http://zefania.blogspot.com
2008/11/30 Peter vo
Adrian/David (and others):
Most of these warnings are gone with with the latest build of
osis2mod. When you run it, it will say:
You are running osis2mod: $Rev: 2197
If you are running an earlier version, please upgrade.
A bit of history.
There are some notions of well-formed.
1) Well-formed XM
The warning messages are just that: warning messages, not errors.
And they indicate what they say literally: that the specified VERSE is
not well-formed. OSIS doesn't require that verses be well-formed. If it
did, there would be no milestone version of the verse element. But Sword
will work bes
Hi Adrian,
I too found loads of warnings and some errors when I tried to use the Win32
build of osis2mod.
I was making an attempt in converting the Tedim Bible (from Myanmar Bibles)
to make a Sword module.
The list of outputs is too long to include here.
Using http://xml-copy-editor.sourceforge
Everyone interested in the wider scene should read this article in
Christianity Today. (Nov 6, 2008).
http://www.christianitytoday.com/ct/article_print.html?id=61403
http://www.christianitytoday.com/ct/article_print.html?id=61403
-- David
btw. Zondervan is part of the HarperCollins group, whi
Whoever addresses this issue should also give attention to why the ALEPH for
[the acrostic poem] Psalm 119 is not treated in the same manner as the
remaining Hebrew letter stanza headings BETH to TAU.
"Aleph" is treated as the Psalm title, rather than as the first stanza
heading for a Psalm that
29 matches
Mail list logo
