Hi Brian,
The old system isn't accessible anymore (something went very wrong and even
though it's RAID and all, fsck ended up removing a bunch of files and making
the system unbootable). But from looking at the files in etc from the backups
I can deduce that LANG was set to the same thing as it is on the new system,
en_US.UTF-8.
I had tried setting these:
ns_param HackContentType 1
ns_param URLCharset "utf-8"
ns_param OutputCharset "utf-8"
ns_param HttpOpenCharset "utf-8"
Which did not work. I will try adding DefaultCharset just in case that is the
key, but I'm not holding my breath...
There is an environment variable I can set, PGCLIENTENCODING, which will let me
specify what encoding to use for the client, so I can add that to nsd-postgres.
But I'm not sure what to set it to - everything's already in UTF8, so there
shouldn't *be* any encoding issues (famous last words, I know :).
I can't restart the site during the day (very picky client) so will not be able
to try anything until late afternoon.
thanks,
janine
On Dec 1, 2010, at 3:32 AM, Fenton, Brian wrote:
> Hi Janine
>
> this may not be the answer but it can't do any harm. You should consider
> adding these to the AOLserver tcl file:
> ns_param HackContentType 1
> ns_param DefaultCharset utf-8
> ns_param HttpOpenCharset utf-8
> ns_param OutputCharset utf-8
> ns_param URLCharset utf-8
>
> Also, rule out any OS differences by checking your locale, LANG etc. Does
> Postgres have an equivalent to Oracle's NLS_LANG? Hopefully you won't have to
> dive into codepages and all that stuff!
>
> best wishes
> Brian Fenton
>
>
> ________________________________________
> From: AOLserver Discussion [[email protected]] On Behalf Of Janine
> Ohmer [[email protected]]
> Sent: 01 December 2010 05:19
> To: [email protected]
> Subject: [AOLSERVER] Charset differences between 3.3+ad13 and 4.0.10?
>
> Me again... still working out the last details on those sites I had to move.
>
> We're having some issues with characters like apostrophes and dashes either
> disappearing (Safari) or showing up as garbage characters (Firefox).
>
> I'm using the same version of Postgres and the same codebase. The databases
> on both systems use the UNICODE encoding. The main thing that's different is
> the AOLserver version. There isn't anything about charset in either the old
> or the new config file.
>
> Has anyone done this conversion (in recent memory, that is :) and knows what
> the problem might be?
>
> thanks,
>
> janine
>
> ---
> Janine Ohmer (formerly Sisk)
> President/CEO of furfly, LLC
> 503-693-6407
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[email protected]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
> field of your email blank.
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[email protected]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
> field of your email blank.
---
Janine Ohmer (formerly Sisk)
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[email protected]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
