[sword-devel] Using Perl script usfm2osos.pl in Windows?

David Haslam dfhmch at googlemail.com
Mon Apr 11 11:11:34 MST 2011

My expectations are simple enough...

I'd like to be able to use usfm2osis.pl with Windows filespec wildcards.
e.g. *.SFM, as the last command line parameter ("like it says on the tin").

usfm2osis.pl -- USFM 2.2 to OSIS 2.1.1 converter version 1.7.2
Revision $Rev$ ($Date$)
Syntax: usfm2osis.pl  [-o OSIS-file] [-e USFM encoding] [-t module type] 
- Arguments in braces < > are required. Arguments in brackets [ ] are
- The osisWork is a short name with no spaces which will identify your
- If no -o option is specified for the output filename, the default output
file is: 
- Supported encodings include:
	7bit-jis, AdobeStandardEncoding, AdobeSymbol, AdobeZdingbat, ascii,
ascii-ctrl, big5-eten, big5-hkscs, cp1006, cp1026, cp1047, cp1250, cp1251,
cp1252, cp1253, cp1254, cp1255, cp1256, cp1257, cp1258, cp37, cp424, cp437,
cp500, cp737, cp775, cp850, cp852, cp855, cp856, cp857, cp858, cp860, cp861,
cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp875, cp932, cp936, cp949,
cp950, dingbats, euc-cn, euc-jp, euc-kr, gb12345-raw, gb2312-raw, gsm0338,
hp-roman8, hz, iso-2022-jp, iso-2022-jp-1, iso-2022-kr, iso-8859-1,
iso-8859-10, iso-8859-11, iso-8859-13, iso-8859-14, iso-8859-15,
iso-8859-16, iso-8859-2, iso-8859-3, iso-8859-4, iso-8859-5, iso-8859-6,
iso-8859-7, iso-8859-8, iso-8859-9, iso-ir-165, jis0201-raw, jis0208-raw,
jis0212-raw, johab, koi8-f, koi8-r, koi8-u, ksc5601-raw, MacArabic,
MacCentralEurRoman, MacChineseSimp, MacChineseTrad, MacCroatian,
MacCyrillic, MacDingbats, MacFarsi, MacGreek, MacHebrew, MacIcelandic,
MacJapanese, MacKorean, MacRoman, MacRomanian, MacRumanian, MacSami,
MacSymbol, MacThai, MacTurkish, MacUkrainian, MIME-B, MIME-Header,
MIME-Header-ISO_2022_JP, MIME-Q, nextstep, null, posix-bc, shiftjis, symbol,
UCS-2BE, UCS-2LE, UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE, UTF-32LE,
UTF-7, utf-8-strict, utf8, viscii
- If the encoding is omitted, utf8 is the default value.
- The script can currently produce valid OSIS for usfm bibles and nearly
valid OSIS for usfm commentaries. To set the module type use '-t' with
either 'bible' or 'comment'. On ommision 'bible' is assumed.
- USFM filenames with the SFM extension can be accessed using a wildcard: 
As an example, if you want to generate the osisWork  and your USFM files are
encoded in utf8, located in the /Bible folder relative to this script with
the file extension SFM, enter:
	perl usfm2osis.pl bible Bible/*.SFM

Is that not something that a good Perl programmer can add fairly simply?


View this message in context: http://sword-dev.350566.n4.nabble.com/Re-Using-Perl-script-usfm2osos-pl-in-Windows-tp3441964p3442709.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

More information about the sword-devel mailing list