Okay... I'll check in the change after Charles finishes the M5 build
On Tue, Sep 8, 2009 at 12:10 PM, jon wrote:
>
> Aha,
>
> It is a header problem. If the charset is specified in the content-
> type IE will pick the right encoding. I added the following to my
> Boot (I already had LiftRules.
Aha,
It is a header problem. If the charset is specified in the content-
type IE will pick the right encoding. I added the following to my
Boot (I already had LiftRules.useXhtmlMimeType = false):
LiftRules.determineContentType = {
case _ => "text/html; charset=utf-8"
}
Maybe
On Tue, Sep 8, 2009 at 10:37 AM, jon wrote:
>
> Ah, IE7 seems to be confused about the character encoding of the
> page. When the encoding is set to "Auto Select" it chooses "Western
> European (Windows)" and the © displays as ©. If I turn off "Auto
> Select" and manually set to "Unicode (UTF
Ah, IE7 seems to be confused about the character encoding of the
page. When the encoding is set to "Auto Select" it chooses "Western
European (Windows)" and the © displays as ©. If I turn off "Auto
Select" and manually set to "Unicode (UTF-8)" it displays correctly.
I have LiftRules.early.app
On Mon, Sep 7, 2009 at 11:38 PM, jon wrote:
>
> Hi,
>
> I've noticed that some special char xml tags are being interpreted by
> lift rather than passing through to the browser.
>
> source code in my template:
>
> &
> ©
> "
> »
> <
> >
>
>
>
