Gloss of Definitions in XSL File is Inaccurate

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Click on a Proposed Definition after "Act on Suggestions."
2.Read the gloss of any definition that is multi-literal.

What is the expected output? What do you see instead?
Expected: an English statement of the chain of relations from Ego to Alter.
Seen: gloss that seems to include both base definitions and "expanded 
definitions"

What version of the product are you using? On what operating system?
Candidate for Release 1.0.

Please provide any additional information below.
Gary Simons and Gary Morris need to collaborate on solution. Issue is posted 
here so you all know it is being addressed. (Gary: see my prior email with 
suggested resolutions. I am ready to generate the glosses for you if desired.)

Original issue reported on code.google.com by garymorr...@verizon.net on 12 Oct 2011 at 7:28

[GoogleCodeExporter]

Original comment by garymorr...@verizon.net on 12 Oct 2011 at 7:29

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Gary M has added computed glosses to the SILK file format for suggestions 
(issues). As soon as Gary S has a chance to incorporate them into his XSL code, 
they should display as computed. Ergo, future complaints s/b addressed to Gary 
M.

Original comment by garymorr...@verizon.net on 21 Oct 2011 at 3:11

• Changed state: Started

[GoogleCodeExporter]

Update of XSL file to be done by Gary Simons.

Original comment by garymorr...@verizon.net on 4 Nov 2011 at 6:28

[GoogleCodeExporter]

Original comment by garymorr...@verizon.net on 5 Dec 2011 at 12:13

• Changed state: Verified