| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09656 | Bug reports | Other | public | 2015-06-01 15:21 | 2015-06-24 22:49 |
| Reporter | duvemyster | Assigned To | c_schmitz | ||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | unable to reproduce | ||
| Product Version | 2.05+ | ||||
| Summary | 09656: Using Google Chrome to send Spanish invitations seems to result in encoding differences | ||||
| Description | Sending the default Spanish invitation from Chrome Version 43.0.2357.81 m results in Outlook 2013 in the ó being replaced with a ? outlined in a diamond in the subject line and in "inter鳠y colaboraci | ||||
| Steps To Reproduce |
| ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | Build 150520 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | Google Chrome Version 43.0.2357.81 m | ||||
| Database type & version | MySQL 5.1 | ||||
| Server OS (if known) | Linux | ||||
| Webserver software & version (if known) | Apache/2.2 | ||||
| PHP Version | 5.4.10 | ||||
| Git branch / Pull Request URL | |||||
 |
The description above was truncated, though the gist of the report may already be intuit-able from the images uploaded. The description entered had the rest of the text in shown the first line of the "from body 1.PNG" image above and may not have like the last few characters. It was along the lines of: "Sending the default Spanish invitation from Chrome Version 43.0.2357.81 m results in Outlook 2013 in the ó being replaced with a ? outlined in a diamond in the subject line and in "inter鳠y colaboraci..." in the body of the message in place of "interés y colaboración! However, this problem does not occur when sending from Firefox." |
|
|
I cannot reproduce this. duvemyster, can you please send me (tpartner[at]partnersinc.biz) an invitation to a test survey so I can see how my Outlook 2013 renders it? |
 |
duvemyster, there was a bug in a previous version where we fixed some JavaScript. |
|
|
This mystery is solved once again thanks to c_schmitz. It was indeed due to my browser cache. |
|
|
Great! |
