Yes, thank you for the suggestions all.
Peter, your instincts are correct - it was a pathing problem.
Cheers
~A
On Thu, Aug 2, 2012 at 1:49 PM, DM Smith wrote:
> Try creating a "raw" module and open the data files with a text editor to see
> if they have what you expect. The -d 2 flag is usefu
Try creating a "raw" module and open the data files with a text editor to see
if they have what you expect. The -d 2 flag is useful in understanding the data
file.
I agree w/ Peter et al, it is almost always a conf or a file permission problem.
In Him,
DM
On Aug 2, 2012, at 10:29 AM, An
I haven't had a chance to explore Peter's recommendations yet, but I
know it isn't file permissions. I have a script that auto-magically
corrects them as part of the same process that runs osis2mod.
Both suggestions make me think the problem is below the client
application, which is consistent wi
... or maybe file permissions on the module or conf file?
On 08/02/2012 12:35 PM, Peter von Kaehne wrote:
Usually path or driver errors.
Wrong path to module or mismatch between driver and conf entry re driver.
Peter
On 02/08/12 15:29, Andrew Thule wrote:
I'm working on a 'commentary' for
Usually path or driver errors.
Wrong path to module or mismatch between driver and conf entry re driver.
Peter
On 02/08/12 15:29, Andrew Thule wrote:
> I'm working on a 'commentary' for the first time and having some trouble.
>
> I very much like the module OTPassages. Chris has given me an IMP
I'm working on a 'commentary' for the first time and having some trouble.
I very much like the module OTPassages. Chris has given me an IMP file
of the module OTPassages (quoted in the NT) which I have converted to
OSIS, xmllintetd and run through osis2mod all without problems. When
I use osis2mo
