Home → Bug Reports →

Special Characters Published with Additional characters

• Edit

scolli9

24 Aug, 2012 08:45 PM

I have users that have used the Copyright symbol and other special characters in formats and static files. On preview they seem fine, once published a  appears before the special character. I have directed them to the Escape Tool for their Velocity scripts. For html and css, I have instructed them to use hex references. I wanted to bring it to your attention.
Here is an example:
Cascade view of test-output.css:
.test{content: " »"} Published version:
.test{content: " »"} OS level via vi with hex:
0000000: 2e74 6573 747b 636f 6e74 656e 743a 2022 .test{content: "
0000010: 20c2 bb22 7d0a .."}.

Sure enough there is a c2 (hex for Â) added before the bb (hex for ») on the source file.

1. 1 Posted by chaoaj on 26 Aug, 2012 10:23 PM

   

   Steve,

   This sounds like a character encoding issue. You might check the
   Destination you are publishing to in Cascade and try to make sure the
   Output checkbox that has this description Publish ASCII characters instead
   of Unicode is checked on and see if that fixes the issue.

   Regards,
   @lvin
   ------------------------
   Alvin Chao ­ IT Web
   JMU - MSC 5734 - Massanutten Hall 293
   Harrisonburg, VA 22807
   540-568-6206
   [email blocked]
   http://educ.jmu.edu/~chaoaj

   • Edit

2. 2 Posted by scolli9 on 27 Aug, 2012 02:55 PM

   

   Here is the response from the user:

   After some checking this appears to fix it for page published (items that are within velocity script and XSLT are output correctly). However, this did not fix the issue for the file published. Example is the _includes/css/test-output.css inside the Emory Main site.

   I double checked and it did not resolve the css instance.

   • Edit

3. Support Staff 3 Posted by Tim on 27 Aug, 2012 03:01 PM

   

   Steve,

   Can you try temporarily disabling Smart Publishing (in System Menu -> Preferences -> Content -> Smart Publishing) and then try to publish this CSS file once again? I'm curious to see if that helps with the published file.

   Be sure to enable Smart Publishing again after doing this test (assuming you had it enabled prior to this discussion).

   Let us know if that does the trick.

   Thanks

   • Edit

4. 4 Posted by chaoaj on 27 Aug, 2012 03:10 PM

   

   Steve,

   We've also run into similar issues with XML encoding and have used XML
   escapes like this: ߞ for emdash and & for ampersand in some
   items where we aren't doing full on publishing or where we can't use
   EscapeTool for formatting. Here's a list of some substitutions:
   http://www.jmu.edu/demotemplates/htmlentities.shtml

   Regards,
   @lvin
   ------------------------
   Alvin Chao ­ IT Web
   JMU - MSC 5734 - Massanutten Hall 293
   Harrisonburg, VA 22807
   540-568-6206
   [email blocked]
   http://educ.jmu.edu/~chaoaj

   • Edit

5. 5 Posted by Ryan Griffith on 28 Aug, 2012 12:14 PM

   

   Steve, have you tried replacing the symbol within the CSS declaration with it's entity equivalent, » ? I believe as long as the page loading the CSS is setting the encoding to UTF-8 in the head, it should convert the entity to the proper symbol.

   For reference, I found the entity on this page.

   • Edit

6. 6 Posted by scolli9 on 28 Aug, 2012 03:45 PM

   

   Tim, your change didn't seem to fix the css publish.
   With the switch to ASCII they say it remedy the pressing issue which was the velocity/XSLT. They can live with the css work around. Thanks.

   • Edit

7. Ryan Griffith closed this discussion on 05 Sep, 2012 02:20 PM.