Hi,

Thanks for sending me an email, but unfortunately, you'll have to send it again.

Please send emails to [EMAIL PROTECTED] from now on.

Thanks,
Scott Arbeitman

-----Original Message-----
From: "Scott Arbeitman" <[EMAIL PROTECTED]>
To: "cfaussie@googlegroups.com" <cfaussie@googlegroups.com>
Subject: [cfaussie] Change Of Email
Date: Sun, 17 Sep 2006 18:31:01 -0500
Reply-To: cfaussie@googlegroups.com


> Hi,

> Thanks for sending me an email, but unfortunately, you'll have to send it 
> again.

> Please send emails to [EMAIL PROTECTED] from now on.

> Thanks,
> Scott Arbeitman

> -----Original Message-----
> Date: Mon, 18 Sep 2006 09:30:00 +1000
> From: Ryan Sabir <[EMAIL PROTECTED]>
> Subject: [cfaussie] Re: Simplified Chinese encoding [FIXED!]
> To: "'cfaussie@googlegroups.com'" <cfaussie@googlegroups.com>
> Reply-To: cfaussie@googlegroups.com


> > --262639760-41-1158535822-3812
> > Content-Type: text/plain
> > Content-Transfer-Encoding: quoted-printable

> > Hi all,
> > =20
> > Thanks for your help with this.
> > =20
> > Because this is a legacy site I was unable to change the character encoding=
> >  from gb2312 to UTF-8. Also it was an Access database so my dsn options wer=
> > e limited.
> > =20
> > What I did instead was basically strip the content-type information from th=
> > e http header, and let the browser decide what encoding to use. I did this =
> > by simply adding the line '<cfcontent type=3D"text/html">' to the top of th=
> > e cfm page.
> > =20
> > In the future I'll be using UTF-8 to avoid such issues.
> > =20
> > bye!
> > =20




> > From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behal=
> > f Of darryl lyons
> > Sent: Saturday, 16 September 2006 10:27 PM
> > To: cfaussie@googlegroups.com
> > Subject: [cfaussie] Re: Simplified Chinese encoding


> > Ryan,

> > I've only ever used UTF-8 in the past, as I found working with any other en=
> > coding (either getting data into or out of the database) to be pretty unrel=
> > iable. SQL Server for instance isn't too good at storing double-byte charac=
> > ters, but works with Unicode fine.=20

> > The other issue is forcing ColdFusion not to encode everything as Unicode b=
> > y default. You need to do this BEFORE the browser sees it (so in this case,=
> >  the META tag won't help you). Haikal's suggestion will probably do the tri=
> > ck (not that I have tried it before).=20

> > Darryl


> > On 14/09/06, Ryan Sabir <[EMAIL PROTECTED]> wrote:=20
> > Hey all,
> > =20
> > I'm trying to get some web pages to show in Simplfied Chinese encoding, but=
> >  the standard META tag doesn't seem to be working.
> > =20
> > When I look at this page:
> > http://www.miller.com.au/index.cfm?&setlanguage=3D2=20
> > =20
> > All the chinese characters are coming up wrong, however, when I go to the V=
> > iew->Encoding menu and manually set the encoding to gb2312, it looks fine.
> > =20
> > I have the=20
> > <meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dgb2312">=
> > =20
> > =20
> > line in there which is supposed to set the character encoding, but my brows=
> > er is defaulting to Unicode.
> > =20
> > This only started happenning when it moved from III5 on Win 2000 Server to =
> > IIS6 on Win 2003 Server. Is there a server setting I need to tweak to enabl=
> > e this?
> > =20
> > thanks.
> > =20
> > =20
> > =20
> > =20
> > Ryan Sabir
> > Technical Director

> > p: (02) 9274 8030
> > f: (02) 9274 8099
> > m: 0411 512 454
> > w: www.newgency.comNewgency Pty Ltd
> > Web | Multimedia | eMarketing

> > 224 Riley St
> > Surry Hills NSW 2010
> > Sydney, Australia

> > =20








> > --=20

> > Darryl
> > http://www.acheron.org/darryl/=20

> > 
> > --262639760-41-1158535822-3812
> > Content-Type: text/html
> > Content-Transfer-Encoding: quoted-printable

> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> > <HTML><HEAD>
> > <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
> > <META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
> > <BODY>
> > <DIV dir=3Dltr align=3Dleft><SPAN class=3D389502523-17092006><FONT color=3D=
> > #0000ff=20
> > size=3D2>Hi all,</FONT></SPAN></DIV>
> > <DIV dir=3Dltr align=3Dleft><SPAN class=3D389502523-17092006><FONT color=3D=
> > #0000ff=20
> > size=3D2></FONT></SPAN>&nbsp;</DIV>
> > <DIV dir=3Dltr align=3Dleft><SPAN class=3D389502523-17092006><FONT color=3D=
> > #0000ff=20
> > size=3D2>Thanks for your help with this.</FONT></SPAN></DIV>
> > <DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff size=3D2>Becaus=
> > e this is a=20
> > legacy site I was unable to change the character encoding from gb2312 to UT=
> > F-8.=20
> > Also it was an Access database so my dsn options were=20
> > limited.</FONT></SPAN></DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff=20
> > size=3D2></FONT></SPAN>&nbsp;</DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff size=3D2>What&n=
> > bsp;I did=20
> > instead was basically strip the content-type information from the http head=
> > er,=20
> > and let the browser decide what encoding to use. I did this by simply addin=
> > g the=20
> > line '&lt;cfcontent type=3D"text/html"&gt;' to the top of the cfm=20
> > page.</FONT></SPAN></DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff=20
> > size=3D2></FONT></SPAN>&nbsp;</DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff size=3D2>In the=
> >  future=20
> > I'll be using UTF-8 to avoid such issues.</FONT></SPAN></DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff=20
> > size=3D2></FONT></SPAN>&nbsp;</DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff=20
> > size=3D2>bye!</FONT></SPAN></DIV>
> > <DIV><SPAN class=3D389502523-17092006><FONT color=3D#0000ff=20
> > size=3D2></FONT></SPAN>&nbsp;</DIV>
> > <DIV><FONT color=3D#0000ff size=3D2></FONT><BR></DIV>
> > <BLOCKQUOTE=20
> > style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
> > d; MARGIN-RIGHT: 0px">
> >   <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
> >   <HR tabIndex=3D-1>
> >   <FONT face=3DTahoma size=3D2><B>From:</B> [EMAIL PROTECTED]
> >   [mailto:[EMAIL PROTECTED] <B>On Behalf Of </B>darryl=20
> >   lyons<BR><B>Sent:</B> Saturday, 16 September 2006 10:27 PM<BR><B>To:</B>=
> > =20
> >   cfaussie@googlegroups.com<BR><B>Subject:</B> [cfaussie] Re: Simplified Ch=
> > inese=20
> >   encoding<BR></FONT><BR></DIV>
> >   <DIV></DIV>Ryan,<BR><BR>I've only ever used UTF-8 in the past, as I found=
> > =20
> >   working with any other encoding (either getting data into or out of the=
> > =20
> >   database) to be pretty unreliable. SQL Server for instance isn't too good=
> >  at=20
> >   storing double-byte characters, but works with Unicode fine. <BR><BR>The =
> > other=20
> >   issue is forcing ColdFusion not to encode everything as Unicode by defaul=
> > t.=20
> >   You need to do this BEFORE the browser sees it (so in this case, the META=
> >  tag=20
> >   won't help you). Haikal's suggestion will probably do the trick (not that=
> >  I=20
> >   have tried it before). <BR><BR>Darryl<BR><BR>
> >   <DIV><SPAN class=3Dgmail_quote>On 14/09/06, <B class=3Dgmail_sendername>R=
> > yan=20
> >   Sabir</B> &lt;<A href=3D"mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>&=
> > gt;=20
> >   wrote:</SPAN>
> >   <BLOCKQUOTE class=3Dgmail_quote=20
> >   style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
> > 04,204,204) 1px solid">
> >     <DIV>
> >     <DIV>
> >     <DIV><SPAN><FONT size=3D2>Hey all,</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>I'm trying to get some web pages to show in=
> > =20
> >     Simplfied Chinese encoding, but the standard META tag doesn't seem to b=
> > e=20
> >     working.</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>When I look at this page:</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2><A=20
> >     onclick=3D"return top.js.OpenExtLink(window,event,this)"=20
> >     href=3D"http://www.miller.com.au/index.cfm?&amp;setlanguage=3D2"=20
> >     target=3D_blank>http://www.miller.com.au/index.cfm?&amp;setlanguage=3D2=
> > </A></FONT>=20
> >     </SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>All the chinese characters are coming up wron=
> > g,=20
> >     however, when I go to the View-&gt;Encoding menu and manually set the=
> > =20
> >     encoding to gb2312, it looks fine.</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>I have the </FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2>&lt;meta http-equiv=3D"content-type"=20
> >     content=3D"text/html; charset=3Dgb2312"&gt; </FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>line in there which is supposed to set the ch=
> > aracter=20
> >     encoding, but my browser is defaulting to Unicode.</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>This only started happenning when it moved fr=
> > om III5=20
> >     on Win 2000 Server&nbsp;to IIS6 on Win 2003 Server. Is there a server=
> > =20
> >     setting I need to tweak to enable this?</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2>thanks.</FONT></SPAN></DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV><SPAN><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
> >     <DIV>&nbsp;</DIV>
> >     <TABLE=20
> >     style=3D"PADDING-RIGHT: 0px; BORDER-TOP: rgb(204,204,204) 1px solid; PA=
> > DDING-LEFT: 0px; PADDING-BOTTOM: 15px; WIDTH: 100%; PADDING-TOP: 15px; BORD=
> > ER-BOTTOM: rgb(204,204,204) 1px solid; BACKGROUND-COLOR: rgb(230,230,230)"=
> > =20
> >     cellSpacing=3D0 cellPadding=3D0>
> >       <TBODY>
> >       <TR>
> >         <TD=20
> >           style=3D"VERTICAL-ALIGN: middle; WIDTH: 105px; TEXT-ALIGN: center=
> > "><IMG=20
> >           height=3D60 width=3D46 NOSEND=3D"1"></TD>
> >         <TD=20
> >         style=3D"FONT-SIZE: 10px; VERTICAL-ALIGN: top; WIDTH: 175px; COLOR:=
> >  rgb(102,102,102); FONT-FAMILY: Verdana,Arial,Helvetica,sans-serif"><SPAN=
> > =20
> >           style=3D"FONT-WEIGHT: bold; FONT-SIZE: 12px; COLOR: rgb(0,0,0)">R=
> > yan=20
> >           Sabir</SPAN><BR>Technical Director<BR><BR><STRONG>p:</STRONG> (02=
> > )=20
> >           9274 8030<BR><STRONG>f:</STRONG> (02) 9274 8099<BR><STRONG>m:</ST=
> > RONG>=20
> >           0411 512 454<BR><STRONG>w:</STRONG> <A=20
> >           style=3D"FONT-SIZE: 10px; COLOR: rgb(102,102,102); FONT-FAMILY: V=
> > erdana,Arial,Helvetica,sans-serif"=20
> >           onclick=3D"return top.js.OpenExtLink(window,event,this)"=20
> >           href=3D"http://www.newgency.com/"; target=3D_blank>www.newgency.co=
> > m</A></TD>
> >         <TD style=3D"WIDTH: 30px"><IMG height=3D97 width=3D1 NOSEND=3D"1"><=
> > /TD>
> >         <TD=20
> >         style=3D"FONT-SIZE: 10px; VERTICAL-ALIGN: top; COLOR: rgb(102,102,1=
> > 02); FONT-FAMILY: Verdana,Arial,Helvetica,sans-serif; TEXT-ALIGN: left"><ST=
> > RONG>Newgency=20
> >           Pty Ltd</STRONG><BR>Web | Multimedia | eMarketing<BR><BR>224 Rile=
> > y=20
> >           St<BR>Surry Hills NSW 2010<BR>Sydney, Australia</TD></TR></TBODY>=
> > </TABLE>
> >     <DIV>&nbsp;</DIV><BR><BR></DIV><BR></DIV></BLOCKQUOTE></DIV><BR><BR=20
> >   clear=3Dall><BR>-- <BR><BR>Darryl<BR><A=20
> >   href=3D"http://www.acheron.org/darryl/";>http://www.acheron.org/darryl/</A=
> > >=20
> >   <BR><br>
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~----------~----~----~----~------~----~------~--~---

Reply via email to