<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
This is a great idea. Rather than emailing source to modules at
crosswire dot org, one could upload it via a web service. We could have
stages of validation (xmllint) and construction (osis2mod). Such a
service could evaluate the quality of the submission.<br>
<br>
In Him,<br>
DM<br>
<br>
On 04/05/2010 12:01 PM, Weston Ruter wrote:
<blockquote
cite="mid:w2sfb8299e11004050901h185c5ac0oae99974d224e8f97@mail.gmail.com"
type="cite">Why not turn osis2mod into a web service? Then it wouldn't
matter how it is implemented since it would be abstracted away by the
web service interface. It could use the best XML libraries available
today and written in the programming language of choice, both of which
would make maintenance and the addition of new features much easier. <br>
<br>
Weston<br>
<br>
<div class="gmail_quote">On Mon, Apr 5, 2010 at 5:55 AM, Manfred
Bergmann <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:manfred.bergmann@me.com">manfred.bergmann@me.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi
DM.<br>
<br>
Am 05.04.2010 um 13:21 schrieb DM Smith:<br>
<div class="im"><br>
> Regarding using a "real" parser, it is a good idea. But we don't
want SWORD to be dependant on an external parser.<br>
<br>
</div>
What's the reason for that?<br>
I could understand if it would mean for the user to install certain
libraries manually but when the sources can be integrated into the
project and has the appropriate licence then why not?<br>
<font color="#888888"><br>
<br>
Manfred<br>
</font>
<div>
<div class="h5"><br>
><br>
> On 02/04/2010 05:31 AM, John Zaitseff wrote:<br>
>> Dear SWORD developers,<br>
>><br>
>> Firstly, thanks for developing the SWORD library! I have been
using<br>
>> this library, in conjunction with the BibleTime front-end, for
many<br>
>> years.<br>
>><br>
>> I have recently started to develop some OSIS documents of my
own.<br>
>> In doing so, I found that the XML parser in osis2mod is
somewhat<br>
>> fragile---something that you are, no doubt, aware of.<br>
>><br>
>> In particular, osis2mod does not handle XML comments at all,
nor<br>
>> does it correctly parse the <header> element. Being
able to handle<br>
>> XML comments is, I think, quite important---I like to document
the<br>
>> SVN revision ID, for example, in an XML comment.<br>
>><br>
>> Furthermore, the osis2mod XML parser looks for the first
<div> in<br>
>> the document, no matter where that occurs. In particular, if
the<br>
>> OSIS document includes a <revisionDesc> tag in the
header, it will<br>
>> have <p> tags as well---which will be translated by
transformBSP()<br>
>> into <div> tags---and get used as the starting point for
the<br>
>> document!<br>
>><br>
>> For this reason, I have generated a quick patch that will solve<br>
>> these particular problems. Could you please apply it to the
SVN<br>
>> head for utilities/osis2mod.cpp. Comments are handled similar
to<br>
>> spaces: they are skipped. And handleToken() now looks for the
first<br>
>> <div> after the </revision> end tag.<br>
>><br>
>> In general, I think that (perhaps eventually) the proper way to<br>
>> parse XML is to use a library like libxml---which is designed<br>
>> specifically for this purpose.<br>
>><br>
>> Yours truly,<br>
>><br>
>> John Zaitseff<br>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>