G
Guest
I'm bogged down doing what seemed to me to be a relatively trivial task - to
use the FP gallery tool to display a bunch of images from work I've done,
where the image filenames are in multiple character sets - Greek, Cyrillic,
Slavic, and English.
I don't seem to be able to get ALL the character sets properly displayed in
any browser, as Frontpage always complains that one or more character sets is
not supported, and refuses to import the images until I rename them. If I set
the page encoding to Greek, all the Greek and English strings are displayed
correctly, but none of the others, and vice-versa.
I should note here that all the image files are supported graphic format, so
this has nothing whatever to do with the graphic file format. The character
sets used in the various filenames are Windows Unicode and supported and
displayed properly in Windows (XP 32, XP x64). I can also incorporate the
different character strings using manual SGML, but that is really clumsy and
time-consuming. And for 200+ images, about 40 of which are different
character sets, it's a real hassle, especially as the page is fairly dynamic,
with new entries appearing every couple of weeks.
This is frustrating the hell out of me. My workaround at the moment is to
render the text as small graphic banners using one of the (very few!) graphic
tools that handles multiple character sets, as hand-coding SGML is way too
time-consuming, but that's not the point. The point is, I should be able to
compose a page with ANY character set or language in Frontpage without
resorting to hand coding!
I deliberately set all my site fonts to enable broad character mapping
without resorting to ridiculous special fonts or character sets. All the
charactes I wish to display are fully supported in the standard Arial font
family. It just seems that FP is refusing to even try to work with the
characters.
I do appreciate that this may not be what Frontpage was designed to be able
to handle, but I live and work in a multilingual world, and I'm really
disappointed that FP now seems to be unable to handle a trivial task. It's
fine if Greek sites only ever display Greek character sets, or Cyrillic
sites, or Arabic, but this is "none of the above". I just can't be limited to
one or two character sets. (It's just not fair, boo-hoo, sob).
If I'm missing something important or obvious, please let me know, I may not
be seeing the wood for the trees here!
use the FP gallery tool to display a bunch of images from work I've done,
where the image filenames are in multiple character sets - Greek, Cyrillic,
Slavic, and English.
I don't seem to be able to get ALL the character sets properly displayed in
any browser, as Frontpage always complains that one or more character sets is
not supported, and refuses to import the images until I rename them. If I set
the page encoding to Greek, all the Greek and English strings are displayed
correctly, but none of the others, and vice-versa.
I should note here that all the image files are supported graphic format, so
this has nothing whatever to do with the graphic file format. The character
sets used in the various filenames are Windows Unicode and supported and
displayed properly in Windows (XP 32, XP x64). I can also incorporate the
different character strings using manual SGML, but that is really clumsy and
time-consuming. And for 200+ images, about 40 of which are different
character sets, it's a real hassle, especially as the page is fairly dynamic,
with new entries appearing every couple of weeks.
This is frustrating the hell out of me. My workaround at the moment is to
render the text as small graphic banners using one of the (very few!) graphic
tools that handles multiple character sets, as hand-coding SGML is way too
time-consuming, but that's not the point. The point is, I should be able to
compose a page with ANY character set or language in Frontpage without
resorting to hand coding!
I deliberately set all my site fonts to enable broad character mapping
without resorting to ridiculous special fonts or character sets. All the
charactes I wish to display are fully supported in the standard Arial font
family. It just seems that FP is refusing to even try to work with the
characters.
I do appreciate that this may not be what Frontpage was designed to be able
to handle, but I live and work in a multilingual world, and I'm really
disappointed that FP now seems to be unable to handle a trivial task. It's
fine if Greek sites only ever display Greek character sets, or Cyrillic
sites, or Arabic, but this is "none of the above". I just can't be limited to
one or two character sets. (It's just not fair, boo-hoo, sob).
If I'm missing something important or obvious, please let me know, I may not
be seeing the wood for the trees here!