If you could, please provide a patch to address this problem. I think it'd be a good thing to change, and since you're already familiar with this set of code, it'd be a great contribution. :)
Chris On Sep 29, 2010, at 1:37 AM, Thias wrote: > Hi, > > I really like Hardware Growler, but would like to report a small bug: > when hardware has a name with non ascii characters (for instance ™ in > Microsoft Hardware), the display gets mangled: typically the ™ gets > changed into two weird characters. > > I had a quick look at the code, and I think the problem is that the > hardware name is encoded in utf-8 (like most things in Mac OS X those > days), but the code specifies the ascii-encoding, which probably > reverts to Iso-latin-1 or Mac-Roman in presence of characters above > 128. > > For instance here, in USBNotifier.c:71 > > The code > > CFStringRef deviceName = > CFStringCreateWithCString(kCFAllocatorDefault, deviceNameChars, > kCFStringEncodingASCII); > > Should probably use kCFStringEncodingUTF8 instead of > kCFStringEncodingASCII > > Keep up the good work! > > Cheers > > Matthias > > > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
