<div class="gmail_quote">On Thu, Jan 20, 2011 at 11:31 AM, Greg Hellings <span dir="ltr"><<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Jan 19, 2011 at 4:41 PM, Ben Morgan <<a href="mailto:benpmorgan@gmail.com">benpmorgan@gmail.com</a>> wrote:<br>
> What I've used in BPBible in a few places is Name - Description (i.e. ESV -<br>
> English Standard Version). The abbreviation at the start (hopefully) means<br>
> that if the rest is cut of it shouldn't matter too much.<br>
<br>
</div>I think this is a good pattern, though I might have switched their<br>
order myself, or only given the abbreviation if the two Descriptions<br>
are identical. I was thinking of a precedence like:<br>
1) Description, if present<br>
1.1) If Description is not unique, combine with one of the below<br>
2) Abbreviation, otherwise<br>
3) Name, otherwise<br>
<br>
I know that Description is listed as a "Required" element, but if it<br>
were absent, having fallbacks is a good idea.<br></blockquote><div>I think putting abbreviation first always is nice because it is easier to scan for (i.e. ESV is much more recognizable than English Standard Version). Putting the Abbreviation on the front makes it possible to scan through a list for it, whereas if the description was first and the abbreviation at the end it would be much more difficult. <br>
</div><div><br clear="all">God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>Multitudes, multitudes,<br> in the valley of decision!<br>For the day of the LORD is near<br>
in the valley of decision.<br><br>Giôên 3:14 (ESV) <br></div></div><br>