On Mon, Oct 5, 2009 at 2:16 PM, Chris Little <chris...@crosswire.org> wrote:
> mod2imp was designed and intended to output the contents of a module as it > is represented within that module, without any processing, irrespective of > markup, encoding, or OS. > To that effect, I have found other utilities to be very helpful in format conversion, It probably won't help with imp format, but when an OSIS document is in an encoding other than UTF-8 I used the xsltproc utility and wrote the simplest of XSLT sheets that just copied the contents across to output and asked it to output UTF-8 encoding. I'm fairly sure you can find other utilities to do that with plain text files if you need them. Simply piping the output of mod2imp through one of those would probably accomplish your goals. --Greg > --Chris > > David Haslam wrote: > >> Is there a reason why the text encoding for the output of the Sword (1.6) >> Windows utility MOD2IMP is not Unicode? >> >> I just tried >> mod2imp FreCrl >FreCrl.imp.txt >> >> and found the text file was encoded as Windows 1252: Western European. >> >> It would be much more sensible for the output to be encoded as UTF-8. >> >> btw. Does the *nix version behave the same way? >> >> David Haslam >> >> >> > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
