Hi Greg,<br><br>While I could implement such a system, I struggle to see that it's high enough priority to bother. As a generalisation I'm not very keen on working on configurability and special options, because I strongly suspect that most people don't use them (I certainly don't if I can avoid it), and I know of problems which affect every user rather than a small sub-set and so are probably more important. [which is not to ignore the problem and its solution, just to minimise it :) ].<br>
<br>Jon<br><br><div class="gmail_quote">On Mon, Sep 20, 2010 at 12:40 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: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I was suggesting that in your application's settings you could provide<br>
a "customize book abbreviations" mechanism to the user, so they<br>
wouldn't have to locate the files and manually edit them.<br>
<br>
I don't see a problem with the 2 letter ones, as long as they are<br>
clearly obvious as to what they are. Philippians and Philemon, for<br>
example, I don't think ought to be given default 2 letter<br>
abbreviations. While "Ph" usually means Philippians and "Phil" means<br>
Philemon, usually don't remember Philippian's existence when I'm<br>
quickly abbreviating Philemon as "Ph".<br>
<br>
Thus, if you allow the user to edit the abbreviations through the<br>
application, then they can select "P" to mean Philemon if they use<br>
that book frequently or "N" to be Nehemiah. It could also solve this<br>
user's problem directly by allowing him to provide his own set of<br>
2-character abbreviations.<br>
<font color="#888888"><br>
--Greg<br>
</font><div><div></div><div class="h5"><br>
On Sun, Sep 19, 2010 at 9:27 AM, Jonathan Morgan <<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a>> wrote:<br>
> They are plain text files, so it is certainly possible to edit them.<br>
> However, anything that is editable will probably not be edited by very many<br>
> people, so I think it is important to get the defaults "right". The<br>
> questions are more "Does anyone think that these kind of two character<br>
> abbreviations make sense to be included by default?" and "Can anyone see any<br>
> major problems with using these kind of two character abbreviations?"<br>
><br>
> BTW, the standard English locale seems to already have some one letter<br>
> abbreviations, such as "N" for "Numbers" and "P" for "Psalms".<br>
><br>
> Jon<br>
><br>
> On Mon, Sep 20, 2010 at 12:22 AM, Greg Hellings <<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Book abbreviations are part of the translations of SWORD, are they<br>
>> not? If they are, it should be relatively easy to allow users to edit<br>
>> and add them to their heart's content by providing a programmatic<br>
>> method to allow them to edit the localization files. That would allow<br>
>> the user to set their own two or even one character abbreviations if<br>
>> they wanted.<br>
>><br>
>> Of course, I could be wildly mistaken in that.<br>
>><br>
>> --Greg<br>
>><br>
>> On Sun, Sep 19, 2010 at 9:05 AM, Jonathan Morgan <<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a>><br>
>> wrote:<br>
>> > Hi all,<br>
>> ><br>
>> > We have received a request that all books have 2 letter abbreviations,<br>
>> > like<br>
>> > Luke does (Lk). Full text below:<br>
>> ><br>
>> > "Sometimes I do a lot of searches, and it would also be faster if the<br>
>> > abbreviations for books were reduced to 2 consonants, like rv for<br>
>> > Revelation<br>
>> > or rm for Romans, rather than rom. Most are only two, like like for<br>
>> > Luke,<br>
>> > but for some reason others are not."<br>
>> ><br>
>> > I can't think off hand of any problems with this other than the<br>
>> > increased<br>
>> > potential for collisions and multiple abbreviations being used for the<br>
>> > same<br>
>> > book name. What do others think. Is this a good idea or a bad idea?<br>
>> ><br>
>> > Jon<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" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> > Instructions to unsubscribe/change your settings at above page<br>
>> ><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" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> Instructions to unsubscribe/change your settings at above page<br>
><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" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
><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" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>