<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 2, 2016, at 7:21 PM, Kahunapule Michael Johnson <<a href="mailto:Kahunapule@ebible.org" class="">Kahunapule@eBible.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;" class="">Also, one word of caution: There is no proper way to do a one-to-one, lossless, round tripable correspondence between USFM to OSIS.</span></div></blockquote></div><br class=""><div class="">Thank you for your help, I'm finding your emails most helpful.</div><div class=""><br class=""></div><div class="">Because I'm doing this with the USFM to OSIS converter in mind, I am not attempting to do a lossless, round-tripabble conversion. In fact, once I have it parsed into code datastructures, it's not a goal to have it be possible to reverse the process losslessly, at least not at this point.</div></body></html>