Closed GoogleCodeExporter closed 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
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
Issue 12 solved
Original comment by idani_na...@yahoo.co.uk
on 5 Nov 2011 at 8:06
Original comment by garymorr...@verizon.net
on 5 Nov 2011 at 9:34
Original issue reported on code.google.com by
idani_na...@yahoo.co.uk
on 26 Oct 2011 at 11:01Attachments: