__TITLE:__ Doesn't work with 2.0.1
Sogudi 0.4.6 does not work with Safari 2.0.1 on 10.4.2 for some users. %%%
Sogudi 0.4.6 does not work with Safari 2.0.2 on 10.4.3 for some users. %%%
Sogudi 0.4.6 does not work with Safari 2.0.4 on 10.4.8 for some users.
2005-08-31 16:45:27.417 Safari! Sogudi may not work with this version of Safari.
2005-08-31 16:45:27.417 Safari! Sogudi will attempt a generic approach.
2005-08-31 16:45:27.418 Safari! Please notify sogudi»kitzkikz of result
From console.log on 2.0.4/10.4.8/Intel/German (added by bert»freudenbergs):
From console.log on 2.0.4/10.4.8/Intel/German:
2006-10-05 11:11:52.570 Safari! *** -![NSBundle load]: Error loading code
for bundle /Users/name/Library/!InputManagers/Sogudi/Sogudi.bundle, error code 2
(link edit error code 0, error number 0 ())
;4-Sep-2005: After installing OS X 10.4.2 and Safari 2.0.1 (412.5), I verified that Sogudi 0.4.6 does indeed work correctly and there was nothing logged to the console.log. At this point, I'm not sure why you are getting the above behavior. That is the expected message when a version of Safari is found that Sogudi can not work with. Perhaps you are using a different version than what I downloaded from Apple last night. If you haven't already, please email me so I can troubleshoot your situation more directly (sogudi»kitzkikz).
;3-Nov-2005: About half a dozen people have emailed that they are experiencing this problem and now it seems to have spread to the new OS X 10.4.3 and Safari 2.0.2 (416.12). I upgraded my system to these versions and Sogudi 0.4.6 still works just fine. My current plan is to create a special debug version of Sogudi that will put out a lot more detailed information and send this to the users that are experiencing the problem. Unfortunately, my dev hard drive (the one with all my Sogudi code on it) has been crashing. I have a backup, of course, but no reliable hard drive to restore to. I can't afford to buy a new external hard drive right now, but possibly in a few weeks when I get my next paycheck.
None - still troubleshooting.