Project

General

Profile

Defect #190

executeClientSideJS doesn´t return some special chars

Added by Victor Rojo Carballo over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Patrick Talbot
Start date:
11/23/2010
Due date:
% Done:

0%

Estimated time:
Browser (if web client):

Description

I noticed that the latest release (1.0.1) fix the issue #175, but there are some special chars with the same behavior.
For example: #,€,º,ª,&,¡,¿

Thanks for your effort guys!

History

#1

Updated by Patrick Talbot over 13 years ago

This is different. I presume this is a problem of charset encoding.
I guess you receive scrambled characters instead, is that it?

The other one was that the ':' character was used as a separator for parameters.

#2

Updated by Victor Rojo Carballo over 13 years ago

Not, I only receive the string before the character '#' for example (like with ':').
I think that you can check it in the sample solution of the #175.

Thanks!

#3

Updated by Patrick Talbot over 13 years ago

  • Status changed from New to Closed

Fixed with v1.0.2: using encodeURIComponent instead of encodeURI

@Victor: please refrain from assigning 'Urgent' issues to me. I'm not the author of this plugin.
Thanks

Also available in: Atom PDF