Re: eng21337 -- A Pidgin plugin

Interesting post. Regarding your first TODO note, HTML::Entities's decode_entities() function (or, perhaps, the two-element _decode_entities() function) look like a possible solution for you. The decode_entities() function would replace any entity; the two-element _decode_entities() function allows you to specify which entities should be decoded.

HTH.

Comment on Re: eng21337 -- A Pidgin plugin

Replies are listed 'Best First'.
Re^2: eng21337 -- A Pidgin plugin by Lawliet (Curate) on Jan 25, 2009 at 18:00 UTC
Interesting post. .oO( Interesting does not necessarily mean good :P ) Thank you for the suggestion -- I just try to keep the number of used modules to a minimum to save the user the hassle of installing them. And you didn't even know bears could type.	[reply]
Re^3: eng21337 -- A Pidgin plugin by atcroft (Abbot) on Jan 25, 2009 at 18:50 UTC
In this case, "interesting" was that I was just looking a week or two ago at the plugin system, but didn't have time for more than a cursory look, so this gave me something I can experiment from (when I again have some free time). As to your trying to keep modules to a minimum, I can understand that, but I think this would give you more flexibility for later, if you decide you want to decode more than just & . Just my humble opinion, though, and I'm open to there being other considerations I may be missing. If nothing else, it might be worth a look at "borrowing" the appropriate code, as an option. HTH (and good post).	[reply]