Hi i’m having problems with fonts in my FW Pro site. I initially assigned Verdana as the main font and created various styles for headings, bodycopy etc - but I noticed a problem displaying the ‘£’ symbol when i upload and preview in a browser.
I immediately changed the font to Helvetica, thinking that there may be an issue with Verdana, but this is creating the same problems.
Does anybody have any ideas what the problem could be or come across similar issues??
What encoding is your page set to? UTF-8 or something else? Can you
post a link?
Walter
On Jun 3, 2008, at 12:09 PM, lfcredbird7 wrote:
Hi i’m having problems with fonts in my FW Pro site. I initially
assigned Verdana as the main font and created various styles for
headings, bodycopy etc - but I noticed a problem displaying the ‘£’
symbol when i upload and preview in a browser.
I immediately changed the font to Helvetica, thinking that there
may be an issue with Verdana, but this is creating the same problems.
Does anybody have any ideas what the problem could be or come
across similar issues??
It’s not a font problem, it’s a problem in the source code: the £ signs are not appearing correctly in the code. Freeway usually gets this right, so I’m suspecting that something might be going wrong on the server side.
When you preview in a browser directly from Freeway (not from the uploaded site), do you see the £ signs or do you see the question marks?
Exactly which version of Freeway are you using? It appears as though the pound signs are being made in Unicode, but the page is being served as Latin 1. Try switching the page to UTF-8 manually, re-publish, and see if the problem goes away.
Normally, Automatic is a good thing, and works as expected. But you seem to have hit a bug. You might want to upgrade to the latest (last) version of Freeway 4, and see if that resolves the problem. Freeway 5 does not have this bug, but if you are holding back from updating legacy sites from 4 to 5, I can understand why you might need to stick with 4.
I’m interested in the answer to this, too. I was under the impression that Freeway always code characters correctly, depending on the encoding level set for the page, but it seems that this isn’t always true. Recently another person (Frances Taylor) had problems with £ signs appearing as question marks, finally solving the problems by using markup items with the entity code for the £ sign. But this shouldn’t be necessary in Freeway. Has something gone wrong in version 5?
I haven’t used “automatic” in quite some time - even now in FWY5. I prefer UTF 8, as it seems the number of extended characters I can type natively just work out.
Perhaps this is a secret plot to undermine only British currency ??
On Wed, Jun 4, 2008 at 6:14 AM, Michael wrote:
I’m interested in the answer to this, too. I was under the impression that Freeway always code characters correctly, depending on the encoding level set for the page, but it seems that this isn’t always true. Recently another person (Frances Taylor) had problems with £ signs appearing as question marks, finally solving the problems by using markup items with the entity code for the £ sign. But this shouldn’t be necessary in Freeway. Has something gone wrong in version 5?
Erns uses Gmail from the Web interface quite a lot. I’ve been trying
to fix his posts for various breakage (mostly starting new threads by
replying), but Google doesn’t set their headers quite right and so
the parser doesn’t manage them all that well.
Walter
On Jun 4, 2008, at 7:10 PM, DeltaDave wrote:
Is it just me? Or has the Big Erns finally flipped to the dark side.
Where did this gibberish that has appeared on the web forum come from?
Ouch! I didn’t realize that I was causing such a fuss. Short of
abandoning gmail, is there anything I can do on my end Walter, to make
your life less complicated?
How about if I post/reply in “text” format?
Oh, Dave – I’ve always been in the dark
On Wed, Jun 4, 2008 at 5:17 PM, Walter Lee Davis wrote:
Erns uses Gmail from the Web interface quite a lot. I’ve been trying
to fix his posts for various breakage (mostly starting new threads by
replying), but Google doesn’t set their headers quite right and so
the parser doesn’t manage them all that well.
On Jun 4, 2008, at 7:10 PM, DeltaDave wrote:
Is it just me? Or has the Big Erns finally flipped to the dark side.
