sillsdev / silkin

Kinship Analysis software for field workers in Anthropology and Bible translation
http://www.sil.org/resources/software_fonts/silkin
4 stars 1 forks source link

Next attemp has also failed #12

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. As I hadn't got very far with the new Claire Mbelime silk. file I created, I 
decided to start again, this time calling it Claire MQL. I made sure I used 
underscores between words for the terms of reference and where I had multiple 
references, separated them with a coma and space (as instructed in Nairobi!)
2. I saved the data regularly. Having entered a total of 10 alters and details 
in relation to one Ego, I quit (it was lunch time!)
3. When I went to open the file to add more terms by changing the Ego. But 
alas, a pop-up message popped up and I'm stuck again. 

A screen shot of the message is attached, together with the .silk file 
concerned. I'd hate to have to start this a third time...

I'm also puzzled by the file format that claims to be 'document' and is blank 
in finder; this differs from the Adam-and-Eve silk file that claims to be a 
simple text file and has a different icon (see screen shot attached)

Original issue reported on code.google.com by idani_na...@yahoo.co.uk on 26 Oct 2011 at 11:01

Attachments:

GoogleCodeExporter commented 8 years ago
This turns out to be similar to Issue #10.  Although I am sure you were very 
careful, when you entered the kin term that #0 calls #7, you entered 
"n̄_nān̄kɛ, n̄_nīi_yɛ̄n̄tɔ̄ɔ_ bīikɛ".  Although it is tough to 
see, there is a space after the last underscore. The embedded blank stopped 
SILKin from reading this SILK file.

As before, the real problem is that I was not catching illegal terms until too 
late. The fix for Issue #10 (complain while you are still entering terms) 
corrects this one, too.

In my tests, making this entry causes an immediate complaint. Of course, it is 
<i>still</i> hard to see the blank in some font faces and sizes. But at least 
SILKin will now hound you until you fix it.

Original comment by garymorr...@verizon.net on 3 Nov 2011 at 7:06

GoogleCodeExporter commented 8 years ago
Concerning the way the Finder displays a SILK file: The file extension ".silk" 
is not registered with Apple, so the Finder cannot just "look it up" in a 
database. If the Finder recognizes the application that last touched the file 
(e.g. SimpleText) it may suggest that this is what type of document it is.

This does not reflect a flaw in the SILK file.

Original comment by garymorr...@verizon.net on 3 Nov 2011 at 7:10

GoogleCodeExporter commented 8 years ago
Issue 12 solved

Original comment by idani_na...@yahoo.co.uk on 5 Nov 2011 at 8:06

GoogleCodeExporter commented 8 years ago

Original comment by garymorr...@verizon.net on 5 Nov 2011 at 9:34