[sword-devel] Questions about usfm2osis.pl

johnduffy at cgcf.net johnduffy at cgcf.net
Thu Oct 29 02:58:17 MST 2009

Hi Chris,

Thanks for updating w.r.t. the BOM.  I've downloaded that and will use it
from now on.  By the way, I've just checked and that didn't change the
normal usage.  But with only one book it did not have the BOM character but
still didn't recognise the book (GEN):
<div type="book" osisID="UnknownUSFMBook">
<title type="main">GEINEASAS</title>

The version of Cygwin I've just downloaded is 1.5.25
The version of Perl I've downloaded with it is and is
I'm using Windows XP Pro (with all latest updates & SPs)

Previous to that, I'd just been using USFM2osis.pl on its own, without an
installation of Perl, running it from the Windows cmd.exe.  

I've been looking at how to get Perl scripts to run, and since I'm new to
Perl and Cygwin, I haven't got it to work yet - that is, I'm still working
out how to call the script properly using bash.  I'll keep plugging away at
this and let you know how I get on.

John Duffy

-----Original Message-----
From: Chris Little [mailto:chrislit at crosswire.org] 
Sent: 29 October 2009 00:16
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Questions about usfm2osis.pl

Chris Little wrote:
> DM is exactly right here.
> DM Smith wrote:
>> On Oct 28, 2009, at 12:04 PM, <johnduffy at cgcf.net> wrote:
>>> Hi Daniel,
>>> Yes, it works even using a relative path if only one file is 
>>> specified but not the *.sfm.
>> Expansion of * is something that the os needs to do. I don't know if 
>> or how Windows does it.
> I use usfm2osis.pl on Win32 most of the time and it works fine, but I 
> run it in bash, which is doing wildcard expansion. I'd never considered 
> the need to do this, but it should be easy enough to add this for use in 
>  the Windows command shell.
> On the other hand, I can heartily recommend the option of installing 
> Cygwin, which will provide you both bash and perl.

I've done some testing now, and can't recreate the problem on my system. 
I'm using 64-bit Windows 7 with bash & perl via Cygwin.

I get identical behavior (correct behavior, with expanded wildcards) 
whether using bash or the Windows command shell (cmd.exe). In both 
cases, I'm using mainline perl (5.10.0-5) from Cygwin.

Which version of Windows are you using? Which version of Perl (and from 
what source)? And are you using any shell other than cmd.exe?

I'm willing to work on a solution if this is caused by earlier versions 
of Windows, but if the failure to expand is caused by a non-mainline 
version of Perl (e.g. ActiveState), I'm more inclined to simply declare 
those versions unsupported.

The latest usfm2osis.pl 
(http://www.crosswire.org/ftpmirror/pub/sword/utils/perl/) fixes the 
problem with handling the BOM.


sword-devel mailing list: sword-devel at crosswire.org
Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list