I'm looking to convert some HTML docs to work with Sword. It would help me a
lot to have a concise working example of one of the intermediate forms (ThML
or OSIS) that's not organised as a Bible or Commentary, just a plain ol'
document.
Cheers; Leon
Try http://www.ccel.org/osis/xml/, lot's of valid OSIS documents there.
I don't know if they can be imported with osis2gbs, but you can easely
try that yourself
For more info about OSIS see
http://www.bibletechnologies.net/OSISinformation/Presentations.dsp
Greetz,
Simon
-Oorspronkelijk beri
Title: Bericht
Hello,
I am currently
working on a project (together with another guy) to include a Bible in a
postnuke site.
First I started
working on this project by my self and used a script that created sql files from
the sword modules. Now with the new guy the module can use the RAW t
While looking through some sources to improve the docs, I noticed something
that might be a possible bug in FileMgr.
It looks like
FileDesc *open (const char *path, int mode, int perms = S_IREAD | S_IWRITE,
bool tryDowngrade = false);
will add the newly created file to the internal list of f
Another small thing I noticed: If somebody uses FileMgr to open a file, and
then deletes the FileDesc object, the FileMgr will still have a pointer to it
in its list. ~FileDesc() should probably tell its parent about it, or be made
private instead, to avoid possible program crashes.
Martin
Am
Sorry, I read the sourcecode wrong.
Please ignore this.
Martin
Am Montag, 3. März 2003 17:16 schrieb Martin Gruner:
> While looking through some sources to improve the docs, I noticed something
> that might be a possible bug in FileMgr.
>
> It looks like
>
> FileDesc *open (const char *path, in
On Mon, 3 Mar 2003, Eduard Wustenveld wrote:
> Just wanted to let you all know that Sword can almost be used in a
> Postnuke/PHP environment, when the postnuke module is finished we will be
> working on a stand-alone module for all websites that want to use a Bible.
> So the API of Sword is not us
Hi,
Maybe it would be nice to convert all markup in all modules to OSIS. I
didn't look in the sourcecode, but I am sure that supporting just 1
format for markup requires much less code...
Currently I am writing a PHP script that replaces all markuptags with
their equivalant OSIS-markup tag.
I h
If you are importing the Sword module into a database, why not simply
use mod2osis, and import the OSIS file? That is much easier. I use that
method, and works very well, only problem is that mod2osis doesn't
export all markuptags..
Currently I am converting all modules to valid OSIS (including al
Sword is not used in this project. Only the text files from Sword are
converted.
Martin
Am Montag, 3. März 2003 10:27 schrieb Eduard Wustenveld:
> Hello,
>
> I am currently working on a project (together with another guy) to include
> a Bible in a postnuke site.
> First I started working on this
I have one page of the Sword Web interface proposal up. I was hoping to
have several mock pages together by now, but I don't have them together yet.
I figured I might as well share this one, because if everyone hates it, I
can change gears before getting too far along. :)
What you see here http:/
On Mon, 3 Mar 2003, Simon wrote:
> Maybe it would be nice to convert all markup in all modules to OSIS. I
> didn't look in the sourcecode, but I am sure that supporting just 1
> format for markup requires much less code...
True, it requires less code, but the code has already been written. Troy
>> Maybe it would be nice to convert all markup in all modules to OSIS.
I
>> didn't look in the sourcecode, but I am sure that supporting just 1
>> format for markup requires much less code...
>True, it requires less code, but the code has already been written.
Troy
>also doesn't want to remove
On Mon, 3 Mar 2003, Simon wrote:
> Well, why not keep the main code and the import/export code strictly
> separate? By doing so the number of possible bugs in the maincode will
> reduce. I know programmers don't like that way of arguing (in my job as
> Software Architect I face that problem day-by
> Well, why not keep the main code and the import/export code strictly
> separate? By doing so the number of possible bugs in the maincode will
> reduce. I know programmers don't like that way of arguing (in my job
> as Software Architect I face that problem day-by-day), but if done
> that way,
On Mon, 3 Mar 2003, Simon wrote:
> Ah, any idea when the OSIS Presentation module will be finished?
I don't believe it is even started yet, but I presume it is still planned.
--Chris
___
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire
>> Ah, any idea when the OSIS Presentation module will be finished?
>I don't believe it is even started yet, but I presume it is still
planned.
Uhm, not so nice. I am currently writing a script to convert Calvins
Commentaries (from ccel.org) into an easy-to-import OSIS-format (at CCEL
the files a
Hi all,
I'm the "other guy" who's helping Eduard out with the
PostNuke/Sword/Bible module. We're calling it
"pnBible". I wrote the part that imports the raw
Sword modules into the database.
Thanks for all your comments! I was asking about the
formats of the vss, chs, and bks files back around
Don,
As always, your web interface looks awesome! It did look and resize
well on Linux/Netscape 7.02. I'm excited to hear others comments on it.
-Troy.
Don A. Elbourne Jr. wrote:
I have one page of the Sword Web interface proposal up. I was hoping to
have several mock pages together by no
It look really nice, but isn't to much of the space spend with the
menus?
Maybe as alternative idea something like http://www.scripture.nl/
Greetz,
Simon
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Troy A. Griffitts
Verzonden: maandag 3 maart 2003 23
> It look really nice, but isn't to much of the space spend with the
> menus?
I agree, looks great! But how about implementing a feature to collapse the
menu of the different texts so it would be a bit smaller? It's somewhat
annoying to have only 30 lines of content with a menu extending 75 line
One possible idea for collapsing is to arrange the versions as submenus
under languages (so that the versions for only one language show at once)...
Another idea is to use a pulldown menu... or a combination of the two,
etc... It all depends on many factors as to what method works best...
Dave
22 matches
Mail list logo
