Jfyi, somebody is working on a script that aims to export mediawiki markup to OSIS in order to provide easy snapshots of German community Bible translation <a href="http://www.offene-bibel.de">www.offene-bibel.de</a>. This might be something in the way that Peter was imagining. Our translation does use a few custom tags e.g. for parallel verses or hebrew text though. For all who know some German: <br>
<a href="http://www.offene-bibel.de/news/ofbi-bibelmodul_inoffizieller_vorabversion">http://www.offene-bibel.de/news/ofbi-bibelmodul_inoffizieller_vorabversion</a><br><a href="http://www.offene-bibel.de/forum/osis_konverter">http://www.offene-bibel.de/forum/osis_konverter</a><br>
<br>Would it be worthwhile to pursue this approach and make it applicable to module making in general? <br><br>Ben<br><br><div class="gmail_quote">2011/8/15 Peter von Kaehne <span dir="ltr"><<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I think the route of a MS Word/OOo -> module is so fraught with difficulties that it is simply pointless to think one can automatise it.<br>
<br>
What i can see and many people seem to cope just fine with is using some simple markup used in fora software, wikis and blogs. People then can be told - these are the 20 codes we support and please get going.<br>
<br>
This is largely semantic markup, but is also easily understood.<br>
<br>
Peter<br>
-------- Original-Nachricht --------<br>
> Datum: Mon, 15 Aug 2011 21:55:03 +1000<br>
> Von: Jonathan Morgan <<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a>><br>
> An: "SWORD Developers\' Collaboration Forum" <<a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>><br>
> Betreff: Re: [sword-devel] Logos Personal Book Builder<br>
<div><div></div><div class="h5"><br>
> Hi Greg,<br>
><br>
> On Mon, Aug 15, 2011 at 4:45 AM, Greg Hellings<br>
> <<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>>wrote:<br>
><br>
> > I have pursued the avenue of docx -> Bible conversion in the past and,<br>
> > allow me to state unequivocally, it is incredibly complex. The sheer<br>
> > number of ways to mark up the same item and material makes any sort of<br>
> > attempt at such a conversion almost impossible to conceive. I never<br>
> > completed the project (my apologies to David for that), but I did get<br>
> > so far as to have the base text working in SWORD. However, headings<br>
> > were in the wrong places, foot notes were acknowledged but not<br>
> > present, and many other things were very wrong with the results I<br>
> > produced. Not to mention that the parsing was highly dependent upon<br>
> > that one text and the manner in which its editor had elected to markup<br>
> > his works. I have since come into possession of better tools which<br>
> > would make some parts of the process easier, but by no means would it<br>
> > be simple.<br>
> ><br>
><br>
> I'm not surprised. I don't know how long it took Logos to develop their<br>
> PBB<br>
> and how many programmers were involved, but I do know it was originally<br>
> tentatively planned for 2010. As you say, I think a big part of the<br>
> problem<br>
> is the number of ways a thing can be represented as (plus the general<br>
> problem of trying to map from presentation to meaning - it's also possible<br>
> that Logos has a more presentational format than you are targetting). I<br>
> think Logos handles things like verses using pre-defined styles, but I've<br>
> only played with it, not read the documentation.<br>
><br>
><br>
> > Producing a general book might have better results, but it would still<br>
> > be a monumental undertaking for anyone who wanted to tackle it. I am<br>
> > up to my ears right now in other projects or I might consider it.<br>
> > Also, I lack any sort of source texts which would make it worthwhile<br>
> > for myself to undertake the project.<br>
> ><br>
><br>
> Indeed.<br>
><br>
> Jon<br>
><br>
><br>
> ><br>
> > --Greg<br>
> ><br>
> > On Sun, Aug 14, 2011 at 9:43 AM, Benjamin Misja <<a href="mailto:alvanx@googlemail.com">alvanx@googlemail.com</a>><br>
> > wrote:<br>
> > > Hi,<br>
> > ><br>
> > > The new PBB feature sounds exciting and I will definitely see if I can<br>
> > > integrate some papers and additional bible translations into my Logos<br>
> > library.<br>
> > ><br>
> > > I would think that having a comparable feature for making SWORD<br>
> modules<br>
> > would<br>
> > > give a huge boost to both the available amount of books and community<br>
> > > participation. I think SWORD should make tools like this available to<br>
> the<br>
> > > community at any cost. It would take making modules out of the hands<br>
> of<br>
> > those<br>
> > > who know at least regular expressions and some programming language<br>
> and<br>
> > put it<br>
> > > into the hands of anybody who would want to make a module. I know I'd<br>
> be<br>
> > > making a lot of them if only I could! It would make SWORD so much<br>
> cooler<br>
> > and<br>
> > > more dynamic. ;-)<br>
> > ><br>
> > > Just my humble opinion,<br>
> > ><br>
> > > Ben<br>
> > ><br>
> > ><br>
> > > Am Sonntag, 14. August 2011, 23:28:39 schrieb Jonathan Morgan:<br>
> > >> I don't usually comment on competing products, but I thought the new<br>
> > >> (long-expected) Logos Personal Book Builder was worth commenting on.<br>
> > You<br>
> > >> can find a post about it at<br>
> > >><br>
> <a href="http://blog.logos.com/2011/08/personal-book-builder-the-inside-scoop/" target="_blank">http://blog.logos.com/2011/08/personal-book-builder-the-inside-scoop/</a>.<br>
> > The<br>
> > >> main difference from most software is the fact that books are built<br>
> by<br>
> > >> importing a docx file rather than entering any text into an editor,<br>
> > which<br>
> > >> hopefully means minimal work to make it happen. The created books<br>
> can<br>
> > then<br>
> > >> just be shared as you wish, even through the main Logos servers.<br>
> > >><br>
> > >> I personally do not intend to do anything about this, but I thought<br>
> it<br>
> > worth<br>
> > >> mentioning to see what others thought of the idea. Certainly<br>
> > difficulties<br>
> > >> converting the text into a usable form seem to crop up quite a bit<br>
> for<br>
> > >> SWORD, and we have no knowledge of how many people just give up<br>
> without<br>
> > >> asking (I know there is a project to work with OpenOffice to create<br>
> > >> Genbooks, but I have never used it and so do not know how capable and<br>
> > how<br>
> > >> automatic it is).<br>
> > >><br>
> > >> Thoughts?<br>
> > >><br>
> > >> Jon<br>
> > ><br>
> > > _______________________________________________<br>
> > > sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> > > <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> > > Instructions to unsubscribe/change your settings at above page<br>
> > ><br>
> ><br>
> > _______________________________________________<br>
> > sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> > <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> > Instructions to unsubscribe/change your settings at above page<br>
> ><br>
<br>
</div></div><font color="#888888">--<br>
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!<br>
Jetzt informieren: <a href="http://www.gmx.net/de/go/freephone" target="_blank">http://www.gmx.net/de/go/freephone</a><br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</div></div></blockquote></div><br>