NateM Posted May 5, 2006 at 01:39 PM Report Share Posted May 5, 2006 at 01:39 PM Hello all, I've been an avid user of adsotrans since I first found out about it, (a whopping 2 weeks ago). However, last night Firefox did an automatic update and now adsotrans seems to be broken. I can still activate it and it will pop up with definitions of the words, but the characters themselves no longer show up in that little pop-up, (they are fine on the page itself, however). Perhaps the update messed up the encoding for the plug-ins, somehow? Anyone got a good quick-fix for this? Quote Link to comment Share on other sites More sharing options...
mandarinstudent Posted May 5, 2006 at 11:53 PM Report Share Posted May 5, 2006 at 11:53 PM Im having the same problem, except it is with the adsotrans "greasemonkey" plugin that I found on this forum. After the Firefox auto-update the window pops up when I click the characters, but in the window is mostly ???????Anyone know how to fix this? Quote Link to comment Share on other sites More sharing options...
sui.generis Posted May 6, 2006 at 01:24 AM Report Share Posted May 6, 2006 at 01:24 AM I thought that I was doing something wrong, but now that I think of it, the first time firefox auto-updated to 1.5.0.1, it broke my 同文堂 plugin, and that didn't start working again until a newer version of the plugin was released. Instead of characters, mostly ??'s (and a few other random characters) show up. Some of them still have the appropriate pop-ups with definition and pronunication, but some of them don't. Quote Link to comment Share on other sites More sharing options...
NateM Posted May 6, 2006 at 03:13 AM Author Report Share Posted May 6, 2006 at 03:13 AM Yup, that's what I'm getting too. I wonder if the updates are reverting the encoding for the plug-ins back to a Western European setting somehow. I don't really know how to check that, though. Quote Link to comment Share on other sites More sharing options...
trevelyan Posted May 6, 2006 at 09:34 AM Report Share Posted May 6, 2006 at 09:34 AM Sorry guys. This looks like an encoding issue. Was fixing some issues with pinyin generation for numbers and implementing a few new features. Must have screwed it up sometime. Will get on it now. Quote Link to comment Share on other sites More sharing options...
trevelyan Posted May 6, 2006 at 10:24 AM Report Share Posted May 6, 2006 at 10:24 AM Fixed. It was a server problem -- nothing to do with Firefox. Sorry for the inconvenience. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and select your username and password later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.