Comment #15 on issue 876 by [email protected]: UTF-8 support broken in Linux and MacOsX - workaround available http://code.google.com/p/openmeetings/issues/detail?id=876
hm no that is not the solution ... the error is only thrown when txt is null ... that is correct of course. NULL is no string and has no function *charCodeAt* ... lets see if the function at all detects special characters -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenMeetings developers" 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/openmeetings-dev?hl=en -~----------~----~----~----~------~----~------~--~---
