Greg,
This is a valuable thing to be working on. I wish you good success.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-Validation-tp2271489p2275178.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
On Tue, Jun 29, 2010 at 8:39 PM, troypulk wrote:
> The error lies in the mod2osis and how it renders the .xml
Actually this is not the case. Chris Little and I got to the bottom
of this over IRC today and it was actually a problem with how the
older versions of osis2mod stored the new module as
The error lies in the mod2osis and how it renders the .xml
I've modified the mod2osis to reproduce a valid osis.xml using the EMTV bible
but when I use it for the KJV I get the following:
kjv.xml:33566: parser error : Opening and ending tag mismatch: chapter line
33544 and osisText
OSIS and import experts,
So I'm working on the elusive Holy Grail of dumping out valid OSIS
from the engine into an XML file of the module. What I am currently
getting from the engine has two parts that fail to validate as OSIS
when I'm working with the KJV module. Namely, those Psalms that have
omitted from the scope? This
knowledge would be helpful when module testing.
Thanks again.
John Duffy
-Original Message-
From: Chris Little [mailto:chris...@crosswire.org]
Sent: 03 November 2009 05:51
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Osis valid
DM Smith wrote:
John,
allows as a child and this element can contain any
content. My guess is that it was provided as a way to maintain the
Dublin Core header elements from a TEI document. Perhaps Chris can comment.
In Him,
DM
All of the Dublin Core header elements are represented in (the
Here is the valid version of your header. Comments follow.
http://www.bibletechnologies.net/2003/OSIS/namespace";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
http://www.bibletechnologies.net/osisCore.2.1
Owens [mailto:dhow...@pmbx.net]
Sent: 02 November 2009 15:12
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Osis validation problems on header
Peter is right. Whatever you add in the header is useful mainly for
yourself. That kind of information usually goes in the co
John,
allows as a child and this element can contain any
content. My guess is that it was provided as a way to maintain the
Dublin Core header elements from a TEI document. Perhaps Chris can comment.
In Him,
DM
On 11/02/2009 09:08 AM, johndu...@cgcf.net wrote:
Hi,
I've got the whole of the
again, for
general use of the osis file apart from producing Sword modules?
John Duffy
-Original Message-
From: Peter von Kaehne [mailto:ref...@gmx.net]
Sent: 02 November 2009 14:56
To: johndu...@cgcf.net; SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Osis
I can add that jEdit has a nice validator plugin that I usually use.
Notepad++ can only validate to a certain length in your document.
Daniel
David Haslam wrote:
Have you tried validating it with http://xml-copy-editor.sourceforge.net/
XML Copy Editor , instead of with Notepad++ with the XML
rg
Betreff: [sword-devel] Osis validation problems on header
Hi,
I've got the whole of the Bible to validate, but have problems with the
header.
The basic header which is output from usfm2osis.pl allows the whole Bible
to
validate (using Notepad++ and a copy of the Osis schema s
Have you tried validating it with http://xml-copy-editor.sourceforge.net/
XML Copy Editor , instead of with Notepad++ with the XML Tools plugin?
It's generally a good idea, just in case there is a subtle bug in the
plugin.
- David
johnduffy-2 wrote:
>
> Hi,
>
> I've got the whole of the Bib
- Original-Nachricht
> Datum: Mon, 2 Nov 2009 14:08:12 -
> Von: johndu...@cgcf.net
> An: sword-devel@crosswire.org
> Betreff: [sword-devel] Osis validation problems on header
> Hi,
>
> I've got the whole of the Bible to validate, but have problems with the
>
Hi,
I've got the whole of the Bible to validate, but have problems with the
header.
The basic header which is output from usfm2osis.pl allows the whole Bible to
validate (using Notepad++ and a copy of the Osis schema saved as a local
file).
http://www.bibletechnologies.net/2003/OSIS/namespac
Chris,
Thank you, that makes sense. I was using xmllint, and I will have a
look at the website you mentioned. xmllint doesn't give line numbers
after 63555 or something, so I finally figured out how to validate with
jEdit to find out where the errors were. There was no problem with the
foreign
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
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',
> attribut
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 '{http://www.w3.org/XML/1998/n
19 matches
Mail list logo
