Can anyone tell me why glyphs are shown as different characters or with an Å before them?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Your character set and the character set of the text file (HTML) generated by Freeway are out of synch. Try turning off Automatic encoding and switch to one of the Unicode options manually.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Walter… how do I do that?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Look on the output tab of the Page Inspector. There’s an option
labeled Encoding, which is probably stuck on Automatic.
Walter
On Aug 2, 2010, at 9:27 AM, Graham Meigh wrote:
Thanks Walter… how do I do that?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hmmm… done that. No success.
Take a look at
http://stepbeyond2.co.uk/test2/
I have dropped a few characters into the central text column.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The characters are being printed in the HTML as £ ° ½ literally.
Where are you copying them from? What characters are you seeing in
Freeway when you do? If you’re using the Web version of this mailing
list, you can paste your text directly in the message field and see
(in the live preview) how a properly-configured server treats them,
just for reference.
The thing that occurs to me is that your server is badly configured.
Some servers insist on sending a Content-type header with the charset
attribute set to something other than Unicode. Freeway sets the “magic
bits” in your generated HTML to whatever you set the Encoding to, and
your Web server is supposed to look at those, divine the charset of
the text file, and send a Content-type header to match. But some are
lazy and always send some default encoding unless you tell them
otherwise. So you might want to try changing your page encoding to
Windows Latin 1 or something in that range, and see if the problem
goes away.
Walter
On Aug 2, 2010, at 9:47 AM, Graham Meigh wrote:
Hmmm… done that. No success.
Take a look at
http://stepbeyond2.co.uk/test2/
I have dropped a few characters into the central text column.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options