Proposed definitions muddled - partial fix of issue 15

[GoogleCodeExporter]

This is a follow-up to the second part of issue 15:

"The other thing that the screen shot shows is that questions 1 & 2 for the 
proposed definition are identical. This is also true for other proposed 
definitions.

My guess is that one of these questions should read:
Can you think of a relationship that does not match "father", but is not called 
n̄_tɔ̄ɔ?"

I went to see if the questions had also been updated in the new release version 
(SILKin 1.0) of the Claire MQL file. However, the entry for has completely 
disappeared and the data is now scrambled in the proposed definitions.

In the snapshot included the drop-down box for suggestions shows '11. 
n̄_tɔ̄ɔ - Proposed definition. But the actual definition visible is for 
n̄_yāa. The data that follows is then incorrect, talking about a divorcée 
or wife when is should actually be 'husband'. Meanwhile, n̄_pūōhɔ̰, 
which is the actual term for wife is now suggesting 'husband'. I haven't 
checked in detail the other propositions.

The drop-down list has 14 proposed definitions, but only 13 are available in 
the details box. I guess the loss of 'father' has meant the others somehow got 
muddled.

Original issue reported on code.google.com by idani_na...@yahoo.co.uk on 21 Jan 2012 at 5:13

Attachments:

• [drop-down mismatch 1.tiff](https://storage.googleapis.com/google-code-attachments/silkin/issue-17/comment-0/drop-down mismatch 1.tiff)

[GoogleCodeExporter]

I suspect the problem was caused when an older, outdated version of 
Silk-status.xsl was used. I've sent test materials (including the latest XSL) 
and my test results to the originator to review.

PS -- The latest XSL file can be downloaded by itself from the "Source" area. 
It is also included in the SILKin 1.0 ZIP folder.

Original comment by garymorr...@verizon.net on 2 Feb 2012 at 9:46

• Changed state: Started

[garymorris2245]

This problem was solved by using the correct "Silk-sattus.xsl" file.

[garymorris2245]

Correction: This problem was solved by using the correct "Silk-status.xsl" file.