<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Robin,<br>
<br>
I have moved your "bugs" from Sword to either BibleCS or Modules, if
they pertained to those. Generally anything that deals with color,
scrollbars, popups and other graphical elements belongs with BibleCS.
BibleCS is also responsible for rendering the text once it is gotten
from from the Sword API. When it renders badly, it could be a problem
in the encoding of the module (for example, the KJV NT encoding is
very, very bad) or it could be in that the Sword API which gets the
text from the module and converts it (aka filters) to what is requested
has a bug or the problem is in the GUI.<br>
<br>
There are a few that I left as it was not obvious to me where they
belonged. Here is what remains and my thought behind each:<br>
<br>
API-31 On Dictionary Lookup "0" appears in front of Greek number on
StrongsGreek window<br>
I think that this can be moved to modules or closed as a duplicate.
We have already discussed that the better form is to have a G or H
preceding the number and for the Greek and Hebrew Strongs to be merged
into one. There is a feature request already in Modules for this.<br>
<br>
API-33 In the KJV John 1:1 is the same as John 1:0 (Not sure this is a
bug)<br>
According to prior threads, 0 is used to lookup intros. What should
happen if there is no intro? My guess is that the module is encoded to
return the first verse, instead of nothing. If so this would move to
"Modules".<br>
<br>
API-41 With HebModern and Transliteration set to Basic Latin only verse
numbers appear in the window<br>
Don't know where transliteration is done. So I left it alone. It
raises an interesting point to me: If a rtl is transliterated to a ltr,
then the direction needs to be changed.<br>
<br>
API-44 The word "CAESAR" is not found in Webster's Dictionary since
"AE" is considered one letter in Webster's<br>
I think this is both a API and a module problem. AE (like OE) is
often a single letter. Problem is that people don't see it that way.
This is a more general issue in how to represent searching for things
that are not represented as ascii. For example, often in German a o or
u with an umlaut is rendered as oe or ue respectively and one could
reasonably expect to use either in a search to find the other.<br>
<br>
API-45 Add Bible Atlas to Modules so a place will link to a map<br>
Is this a new feature request?<br>
<br>
API-54 Josephus seems to load very slowly compared with MHC, Pilgrim,
GerAugustinus<br>
I was not sure if this was a problem with rendering (i.e. BibleCS)
or with getting the material (i.e. SwordAPI) or with the module
representation. Performance problems are often a combination problem.<br>
<br>
<br>
DM Smith wrote:
<blockquote cite="mid4289134A.1020604@yahoo.com" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
Robin,<br>
<br>
To move an issue in Jira, open the issue and on the left will be a
"move" link. You can use it to move the issue. While it is pretty easy
to use, it does not solve the classification problem, which ones to
move.<br>
<br>
DM<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:RLRANDALLX@aol.com">RLRANDALLX@aol.com</a>
wrote:
<blockquote cite="mid103.617a8bb9.2fba68d2@aol.com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.2627" name="GENERATOR">
<font id="role_document" color="#000000" face="Arial" size="2">
<div>
<div>
<div>In a message dated 5/16/2005 8:37:04 A.M. Pacific Daylight
Time,
<a class="moz-txt-link-abbreviated"
href="mailto:sword-devel-request@crosswire.org">sword-devel-request@crosswire.org</a>
writes:</div>
<blockquote
style="border-left: 2px solid blue; padding-left: 5px; margin-left: 5px;"><font
style="background-color: transparent;" color="#000000" face="Arial"
size="2"><br>
Please don't get me wrong, I so appreciate the reports. Thank you
for <br>
all the time you've spent testing and making us aware of where we fall <br>
short.<br>
<br>
</font></blockquote>
</div>
Troy,</div>
<div> </div>
<div>There must be a faster way to re-categorize the bugs in Jira.
I
need a Jira guru who can change the SWORD bug list into XML, make the
necessary changes (SWORD -> BibleCS, API ->BCS, etc) and add it
to the BibleCS tree. If you want me to duplicate my effort, at least
give me a list of which ones are clearly Windows related and I can
reenter them. The Jira guru will have to delete the reports from the
SWORD list or at least close them.</div>
<div> </div>
<div>In His Grace,</div>
<div>Robin</div>
<div> </div>
<div><font family="SANSSERIF" ptsize="10" face="Arial" lang="0"
size="2">E-mail: </font><font family="SANSSERIF" ptsize="10"
color="#ff0000" face="Arial" lang="0" size="2"><a
class="moz-txt-link-abbreviated" href="mailto:RLRandallX@aol.com">RLRandallX@aol.com</a></font></div>
</font>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated"
href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext"
href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
</body>
</html>