[bt-devel] [ bibletime-Beta testing reports-1225676 ] Comma problem in LD mods

[SourceForge.net]

Beta testing reports item #1225676, was opened at 2005-06-22 19:09
Message generated for change (Settings changed) made by mgruner
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=521207&aid=1225676&group_id=954

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Deleted
Resolution: Accepted
Priority: 6
Private: No
Submitted By: Gregory Scott Hellings (hellings)
Assigned to: Joachim Ansorg (joachim)
Summary: Comma problem in LD mods

Initial Comment:
Some Dictionary/Lexicon entries which contain a comma
in the entry key do not display data when selected,
even if the data has been included in the file.  An
example would be the module AmTract (American Tract
Society Bible Dictionary).  Many entries containing
commas ("Arimathea, or Ramah", "Atonement, Day of",
"Avim, of Avites", "Bamah, plural Bamoth", etc) do
display properly, but at least one ("Ashtoreth, plural
Ash'taroth") does not display when selected.  The
module does contain data for that which will display in
gnomesword2.

The bug is current as of 1.5rc2 and the most current
CVS build as of 18:00 GMT June 22.

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2005-07-19 17:21

Message:
Logged In: YES 
user_id=169722

Closing this now. Should be reported to crosswire.org/bugs
instead.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-06-29 22:51

Message:
Logged In: NO 

Hi,
it's not the comma, but the apostrophe.

The AmTract module is not encoded in UTF-8 but contains
non-latin1 chars in the key names (afaik) And it's not
unicode, either.

I think this is a module problem. Sword has no good handling
of non-latin1 keys in lexicons, at least frontends don't
know what to do :(

If that makes sense let me know so we can close this report.

Joachim

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2005-06-28 18:25

Message:
Logged In: YES 
user_id=169722

We should fix this for 1.5, if it is indeed a frontend bug. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=521207&aid=1225676&group_id=954