You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the following problem with the two methods mentioned in the Issue title.
I use a ID from the DOM to create an event summary and pass it into one of these function. The problem is that special chars like "öäüß" are getting scrambled and not get displayed like they should in the card or the created event.
Here is the sample I provided @lsale with, but maybe wants to look into it to.
Because I know Luca is crazy busy with traveling and stuff.
In my application the only difference is that the content of the DIV gets set from JavaScript and is later read from JavaScript to pass it into the CalendarComposerCard but I encounter the same problems with the encoding. In the sample the text already resides in the div when the application starts.
I tried blackberry.pim.calendar.createEvent as work around but this API is suffering from the same encoding error. I guess this is somehow related to the calendar itself maybe.
Hi guys,
I have the following problem with the two methods mentioned in the Issue title.
I use a ID from the DOM to create an event summary and pass it into one of these function. The problem is that special chars like "öäüß" are getting scrambled and not get displayed like they should in the card or the created event.
Here is the sample I provided @lsale with, but maybe wants to look into it to.
Because I know Luca is crazy busy with traveling and stuff.
https://github.com/splatterb0y/BB10-CalenderEncodingError
In my application the only difference is that the content of the DIV gets set from JavaScript and is later read from JavaScript to pass it into the CalendarComposerCard but I encounter the same problems with the encoding. In the sample the text already resides in the div when the application starts.
I tried blackberry.pim.calendar.createEvent as work around but this API is suffering from the same encoding error. I guess this is somehow related to the calendar itself maybe.
Cheers
Christian