Greek text

Freeway
1

I am designing a website in English and Greek and am finding that when I view what I have so far published through Firefox or Safari, all the HTML Greek text comes out as ‘code’. The Greek text typed into a graphic box appears fine. When I switch my Firefox to read the site in Unicode - the ‘code’ becomes Greek. But this is relying upon the user to switch over. How can I make sure, from within Freeway, that the HTML text will read as Greek? I have tried setting it as Unicode and as Greek (MacOS) but it always slips back into code when viewed from a browser.

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

2

Hi Sharon,

I just sent you an email through support. I’ll rewrite it here as a
reference for others.

The encoding type is defined in the HTM page and it can be overridden
by the browser. To make sure the browser uses the necessary encoding
type (without it needing to be overridden) change the encoding in
Freeway. To do this click the page and in the Inspector palette change
the Encoding option to the one you need (in your case it’s Unicode).
The encoding option can be found in the Output settings which is the
third icon from the top left.

I hope this helps.

Joe

On 31 Dec 2008, at 09:47, Sharon Huyshe wrote:

I am designing a website in English and Greek and am finding that
when I view what I have so far published through Firefox or Safari,
all the HTML Greek text comes out as ‘code’. The Greek text typed
into a graphic box appears fine. When I switch my Firefox to read
the site in Unicode - the ‘code’ becomes Greek. But this is relying
upon the user to switch over. How can I make sure, from within
Freeway, that the HTML text will read as Greek? I have tried setting
it as Unicode and as Greek (MacOS) but it always slips back into
code when viewed from a browser.

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

3

Hello Joe,

Many thanks for your reply. I am still having problems. Leave it for this
evening - I’ll send you some screen shots over the next few days - maybe I
am doing something else wrong!!

Have a wonderful evening. Happy 2009!
XSx

Hi Sharon,

I just sent you an email through support. I’ll rewrite it here as a
reference for others.

The encoding type is defined in the HTM page and it can be overridden
by the browser. To make sure the browser uses the necessary encoding
type (without it needing to be overridden) change the encoding in
Freeway. To do this click the page and in the Inspector palette change
the Encoding option to the one you need (in your case it’s Unicode).
The encoding option can be found in the Output settings which is the
third icon from the top left.

I hope this helps.

Joe

On 31 Dec 2008, at 09:47, Sharon Huyshe wrote:

I am designing a website in English and Greek and am finding that
when I view what I have so far published through Firefox or Safari,
all the HTML Greek text comes out as ‘code’. The Greek text typed
into a graphic box appears fine. When I switch my Firefox to read
the site in Unicode - the ‘code’ becomes Greek. But this is relying
upon the user to switch over. How can I make sure, from within
Freeway, that the HTML text will read as Greek? I have tried setting
it as Unicode and as Greek (MacOS) but it always slips back into
code when viewed from a browser.

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

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

4

Freeway wouldn’t let me send the attachment. I shall put the images on the
website…

XSx

Hiya there,

Happy 2009!

As threatened, I am attaching the screen shots. Showing how the master and
page look in Freeway; then with preview (so far so good!) and then through
the browser (boo hoo!).

Do you think it could be the font?

I don’t know if there are any other options?

Thank you!!!
XSx

Hello Joe,

Many thanks for your reply. I am still having problems. Leave it for this
evening - I’ll send you some screen shots over the next few days - maybe I
am doing something else wrong!!

Have a wonderful evening. Happy 2009!
XSx

Hi Sharon,

I just sent you an email through support. I’ll rewrite it here as a
reference for others.

The encoding type is defined in the HTM page and it can be overridden
by the browser. To make sure the browser uses the necessary encoding
type (without it needing to be overridden) change the encoding in
Freeway. To do this click the page and in the Inspector palette change
the Encoding option to the one you need (in your case it’s Unicode).
The encoding option can be found in the Output settings which is the
third icon from the top left.

I hope this helps.

Joe

On 31 Dec 2008, at 09:47, Sharon Huyshe wrote:

I am designing a website in English and Greek and am finding that
when I view what I have so far published through Firefox or Safari,
all the HTML Greek text comes out as ‘code’. The Greek text typed
into a graphic box appears fine. When I switch my Firefox to read
the site in Unicode - the ‘code’ becomes Greek. But this is relying
upon the user to switch over. How can I make sure, from within
Freeway, that the HTML text will read as Greek? I have tried setting
it as Unicode and as Greek (MacOS) but it always slips back into
code when viewed from a browser.

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

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

5

Freeway wouldn’t let me send the attachment.

You mean you couldn’t post an attachment to the Freewaytalk list? :slight_smile:

Remember that many people here read this via email. You don’t really
want to send hundreds of people unsolicited email attachments, hmm?
:slight_smile: That’s why you can’t send attachments here.

The general presumption is that if you’re experimenting with a web
design tool that you can find a little bit of web space somewhere to
post experiments and examples.

I’m not sure I’ll be able to help with the Greek text problem but
I’ll have a look when the grabs are online. Happy New Year!

k

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

6

If the font you are using does not contain the entire UTF-8 character
map (and there are relatively few that do) then you will have missing
glyphs such as you describe when you set your page to Unicode
character encoding. If you stick to a font that is known to contain
(or reference in other alternate fonts) the entire gamut, then you can
pretty much guarantee a good experience for your visitors.

Try making a new Font Set in Freeway, and apply it to the text where
you’re having the problem. From the main menu, choose Edit / Font
Sets. In the dialog, click on New, and choose Lucida Grande from your
font list. Then paste the following alternates in for the Windows
folk, overwriting whatever is there:

'Lucida Grande', 'Lucida Sans Unicode', 'Lucida Sans', Lucida, sans-

serif’

Be sure to include the single-quotes to delineate the multi-word font
names. Give your font set a name so you can find it in the Font-family
picker in the Inspector.

Now Control-click on each of your named styles, select Edit Style from
the contextual menu, and change the font set from whatever it is now
to your Lucida style. If you were seeing glitchy font drawing in
Freeway, this problem should disappear the moment you okay the dialog.
Re-publish, and you should see your characters in the browser.

Lucida Grande is one of the larger fonts you can use, character map-
wise. It’s used by Mac OS X to draw all the menus in the operating
system in all of the many languages that it’s localized into. If your
characters are missing from that font, you’re not likely to find them
elsewhere. (Mostly, that’s just impossible.)

If you need particular characters that are usually only found in one
language (Cherokee, for example), then you may have better luck using
a non-Unicode encoding, one specific to that language you want to use.
But then your visitors will need to have enabled that encoding in
their browser – it can get quite esoteric at the further reaches of
the problem. I suspect that Unicode will work for you in this case,
Greek letters are pretty widely represented in most fonts.

Walter

On Jan 1, 2009, at 2:01 PM, Sharon Huyshe wrote:

Do you think it could be the font?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

7

Thank you!

Freeway wouldn’t let me send the attachment.

You mean you couldn’t post an attachment to the Freewaytalk list? :slight_smile:

Remember that many people here read this via email. You don’t really
want to send hundreds of people unsolicited email attachments, hmm?
:slight_smile: That’s why you can’t send attachments here.

The general presumption is that if you’re experimenting with a web
design tool that you can find a little bit of web space somewhere to
post experiments and examples.

I’m not sure I’ll be able to help with the Greek text problem but
I’ll have a look when the grabs are online. Happy New Year!

k

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

8

Thank you! Shall see if it works. It was Helvetica - which one would imagine
would be OK pretty much out there and all over the place…
Happy 2009.

If the font you are using does not contain the entire UTF-8 character
map (and there are relatively few that do) then you will have missing
glyphs such as you describe when you set your page to Unicode
character encoding. If you stick to a font that is known to contain
(or reference in other alternate fonts) the entire gamut, then you can
pretty much guarantee a good experience for your visitors.

Try making a new Font Set in Freeway, and apply it to the text where
you’re having the problem. From the main menu, choose Edit / Font
Sets. In the dialog, click on New, and choose Lucida Grande from your
font list. Then paste the following alternates in for the Windows
folk, overwriting whatever is there:

‘Lucida Grande’, ‘Lucida Sans Unicode’, ‘Lucida Sans’, Lucida, sans-
serif’

Be sure to include the single-quotes to delineate the multi-word font
names. Give your font set a name so you can find it in the Font-family
picker in the Inspector.

Now Control-click on each of your named styles, select Edit Style from
the contextual menu, and change the font set from whatever it is now
to your Lucida style. If you were seeing glitchy font drawing in
Freeway, this problem should disappear the moment you okay the dialog.
Re-publish, and you should see your characters in the browser.

Lucida Grande is one of the larger fonts you can use, character map-
wise. It’s used by Mac OS X to draw all the menus in the operating
system in all of the many languages that it’s localized into. If your
characters are missing from that font, you’re not likely to find them
elsewhere. (Mostly, that’s just impossible.)

If you need particular characters that are usually only found in one
language (Cherokee, for example), then you may have better luck using
a non-Unicode encoding, one specific to that language you want to use.
But then your visitors will need to have enabled that encoding in
their browser – it can get quite esoteric at the further reaches of
the problem. I suspect that Unicode will work for you in this case,
Greek letters are pretty widely represented in most fonts.

Walter

On Jan 1, 2009, at 2:01 PM, Sharon Huyshe wrote:

Do you think it could be the font?

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

9

Helvetica maps to Arial by default, which is a pretty crummy knock-off
font commissioned by Microsoft when they wanted a sans-serif but
didn’t want to pay the licensing fees to Linotype. Cheap bastards…
They’ve redeemed themselves somewhat with Georgia and Verdana, both
designed by Matthew Carter and optimized for screen display.

Walter

On Jan 1, 2009, at 3:57 PM, Sharon Huyshe wrote:

Thank you! Shall see if it works. It was Helvetica - which one would
imagine
would be OK pretty much out there and all over the place…
Happy 2009.

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options