In a website I haven’t looked at for some time all diacritical signs display as odd combinations of characters when viewed in Safari or Firefox.
Look at the first word on the fifth text line, which should read één, the second one in the second paragraph: financiële, or five words before the last word: geïnteresseerd.
I’m not aware of using odd settings anywhere.
Any clues?
Thanks!
Maybe this helps to unravel this problem.
The diacritic signs show up in the right way when previewing in the Freeway main window, or when previewing in Safari when activated from within Freeway.
It’s only after uploading to the host and browsing th problem occurs.
Your hosting provider is probably sending a header with a character encoding (charset) other than Unicode. You can work around this two ways. The best is to ask your host to change, or to try an .htaccess file to change the preference. For the latter, use an application like TextWrangler (a programmer’s text editor) to create a file containing only this line of code:
AddDefaultCharset UTF-8
Use an FTP application to connect to your server, and navigate into the folder containing all your site files (public_hmtl or htdocs are popular names for this folder). Make sure your FTP application has its option to “show hidden files” enabled, because you are looking for a file named .htaccess (with a leading dot), and by convention, files that begin with a dot are hidden in a Unix server. If there is already an .htaccess file in that folder, open it, and add the line of code above somewhere near the bottom of the other text in the file. If there isn’t such a file, then upload your text file that you created, and rename it to .htaccess. Now visit your site in a browser and see what happens. If you get an error message, then delete that file (if you created it) or remove that line (if you altered an existing file). It should work, and you should see your accented characters correctly after this.
If you can’t get the .htaccess trick to work, then the work-around in Freeway is to open the Document Setup dialog, and change the Default encoding to Western (Windows Latin 1), then make the same change on each master page in the Output tab of the Inspector. Publish again, and Freeway will use escape sequences to make the non-ASCII characters (which won’t be screwed up by the server you’re using).
Walter
On Feb 20, 2014, at 4:13 AM, Jurjen Hooghiemstra wrote:
Maybe this helps to unravel this problem.
The diacritic signs show up in the right way when previewing in the Freeway main window, or when previewing in Safari when activated from within Freeway.
It’s only after uploading to the host and browsing th problem occurs.
Thanks Walter,
This solved it, adding a .htaccess file.
I will try to find out if my host changed anything anyway, it’s rather odd to find my website slightly crippled without any action on my side…