Good point.<br>
<br>
I was thinking more of the original import file, rather than the master
source. I was guessing that Lynn needs a copy of an importable
file to use as demonstrations for the importer how-to that he's
creating. In that case, the exporter should have all the required
mark-up that he would need, I would think.<br>
<br>
--Greg<br><br><div><span class="gmail_quote">On 2/4/06, <b class="gmail_sendername">DM Smith</b> <<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greg Hellings wrote:<br>> Lynn,<br>><br>> Getting a copy of the "original" source should be close to possible<br>> using the exporter programs.<br>I don't think that the content of a module is necessarily from original
<br>source. In some cases it is derived from a secondary source.<br><br>And if it is from the original source, it is not necessarily true that<br>an export will be even close to the original.<br><br>In the case of OSIS Bibles, the osis2mod importer is lossy. It does not
<br>keep everything that is in the original file. It is faithful with the<br>biblical text, but not with some of the extras.<br><br>I don't know about the other importers.<br><br>_______________________________________________
<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel
</a><br>Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br>