<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jon,<div>I mean that for any given reference, it is parsed by one notation or the other, not both. If the input is provided by an end user via the keyboard, it would use the user's stated preference. When formatting references for output, it would also be used. But for all references coming from a module, it would use the current notation. Of course, we could have a conf entry in a module that would provide the punctuation. But I don't think that is necessary, as in OSIS there is a fixed notation using periods and ThML can use OSIS refs.</div><div><br></div><div>That way it is unambiguous.</div><div><br></div><div>In His Service,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br><div><div>On Nov 2, 2010, at 2:54 AM, Jonathan Morgan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Are you suggesting that we support making the choice of reference system an option (e.g. by default we support "Genesis 3:12, 15, 19", but you can configure it so that it supports "Genesis 3, 12. 15. 19"), or that we try to make the parser handle both reference systems simultaneously? The latter could be tricky, and I don't think that every reference would be unambiguous (for example, in a ThML module "Genesis 3,4" might be a valid reference for "Genesis 3 - 4" in a daily reading planner, but Genesis 3:4 in the other reference system. I couldn't see any reading planners encoded like that though).<br>
<br>Jon<br><br><div class="gmail_quote">On Tue, Nov 2, 2010 at 1:26 PM, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex; position: static; z-index: auto; ">
I don't think that this would be too hard to implement in the SWORD engine. The trick would be to note the difference between user supplied punctuation and that coming from modules. And generated references could use them too. This is similar to the standard internationalization of decimal numbers. Essentially it could be driven by a small array of separators.<br>
<br>
In Him,<br>
<font color="#888888"> DM<br>
</font><div><div></div><div class="h5"><br>
On Nov 1, 2010, at 6:40 PM, Matthew Talbert wrote:<br>
<br>
> See request at <a href="http://www.crosswire.org/forums/mvnforum/viewthread_thread,979" target="_blank">http://www.crosswire.org/forums/mvnforum/viewthread_thread,979</a><br>
><br>
> I thought it might be of interest after our recent discussions about<br>
> reference parsing.<br>
><br>
> Matthew</div></div></blockquote></div></blockquote></div></div></body></html>