On Sunday, July 22, 2001, at 11:02 PM, Chris Nandor wrote:
> I think you are mistaken, a bit. It is not that perl uses a different
> character set in the two environments, it is that the two environments
> have different default character sets. perl itself emits the same
> data,
> but the terminal displays MacRoman while the web browser displays
> Latin-1. It might even be that the terminal and browser are completely
> "dumb" and just passing that information along to your font.
>
> Look in the Terminal app settings, see if it has a character set
> setting, or see if it has a Latin-1 font you can choose. Also, when
> viewing the CGI output in MSIE, look at Character Set and change
> it from
> Latin-1 to Mac.
>
> In general, perl doesn't care about character sets or know what
> character set a string is in (except for Unicode, which I don't know
> much about). It's all just data. It's how that data is rendered that
> changes between platforms/environments/applications/fonts/etc.
I would just like to know what is the most common way of handling
this. It's hard to believe the Perl script authors working on
scripts for languages that contain these extended characters are
going through a lot of trouble putting the accented characters in
their scripts. It seems that a tool like bbedit would be able to
take a script that was written using the extended characters and
convert the text to something compatible with perl.
I know that the few scripts I have found don't use either of the 2
coding methods Will mentioned. They seem to substitute one extended
character for another which Perl seems to convert to the correct
character when sending the html to the browser.
Steve
