My personaly opinion is UTF-8. The sooner we get everyone using it, the
sooner we don't have these annoying charset issues :( 

-Karl 

On Thu, Feb 18, 2010 at 08:05:42AM -0500, Jeff Squyres wrote:
> Thanks!  I changed it to use the lengthy &#... encoding and it is appearing 
> fine on my site; let's see what happens when you guys update (the actual 
> taglines are in mirrors.txt; the php reads in this file and outputs pretty 
> html for the page itself).
> 
> Any ideas why the old way worked on my server and not any others?
> 
> Finally, should I *also* change the page encoding to be UTF-8, or should I 
> just leave it?
> 
> 
> On Feb 18, 2010, at 7:34 AM, WebGate dv6 wrote:
> 
> > Hello,
> > Right, UTF-8 solve that for sure
> > But please remember , when you synchronize , you custom UTF-8 will be
> > overwritten to the original ISO-8859-1.
> > So better way keep it as I suggest, work for any encoding.
> >  
> > 
> > -----Original Message-----
> > From: mirrors-boun...@open-mpi.org [mailto:mirrors-boun...@open-mpi.org] On
> > Behalf Of Karl Vollmer
> > Sent: יום ה 18 פברואר 2010 14:16
> > To: List for Open MPI web mirror site administrators
> > Subject: Re: [Mirrors] Webgate.il admins...
> > 
> > Jeff,
> > 
> >   I'm not a webgate admin, and my way may be wrong. But I've always used the
> >   HTML codes when adding non-ascii characters to a webpage otherwise encoded
> >   in ISO-????
> > 
> >   On that note it appears the problem is that the page headers are ISO-???
> >   not UTF-8
> > 
> >   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
> >   "http://www.w3.org/TR/html4/strict.dtd";>
> >   <HTML>
> >   <HEAD>
> >   <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
> > 
> >   At the top of the html code.
> > 
> >   Changing the content="???" to
> > 
> >   text/html; charset=UTF-8
> > 
> >   in the /include/http_header.inc Fixed it on
> >   http://mirror.its.dal.ca/openmpi
> > 
> >   Let me know once you've seen it and I'll revert the file so I'm inline
> >   with upstream.
> > 
> > -Karl
> > 
> > On Wed, Feb 17, 2010 at 09:51:11PM -0500, Jeff Squyres wrote:
> > > Webgate admins --
> > >
> > > I was proud of myself for getting the hebrew characters in the tagline of
> > your site listed properly here:
> > >
> > >     http://www.open-mpi.org/community/mirrors/
> > >
> > > However, this exact same text does not display properly on any of Open
> > MPI's mirrors, even yours:
> > >
> > >     http://mpi.webgate.co.il/community/mirrors/
> > >
> > > As an ugly american, I rarely deal with i18n kinds of issues.  :-(  Can
> > you hit me with a clue bat as to what I'm doing wrong?
> > >
> > > --
> > > Jeff Squyres
> > > jsquy...@cisco.com
> > >
> > > For corporate legal information go to:
> > > http://www.cisco.com/web/about/doing_business/legal/cri/
> > >
> > >
> > > _______________________________________________
> > > mirrors mailing list
> > > mirr...@open-mpi.org
> > > http://www.open-mpi.org/mailman/listinfo.cgi/mirrors
> > >
> > _______________________________________________
> > mirrors mailing list
> > mirr...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/mirrors
> > 
> > 
> > __________ Information from ESET NOD32 Antivirus, version of virus signature
> > database 4876 (20100218) __________
> > 
> > The message was checked by ESET NOD32 Antivirus.
> > 
> > http://www.eset.com
> > 
> > 
> > 
> > 
> > 
> > __________ Information from ESET NOD32 Antivirus, version of virus signature
> > database 4876 (20100218) __________
> > 
> > The message was checked by ESET NOD32 Antivirus.
> > 
> > http://www.eset.com
> > 
> > 
> > 
> > _______________________________________________
> > mirrors mailing list
> > mirr...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/mirrors
> > 
> 
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> 
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> 
> _______________________________________________
> mirrors mailing list
> mirr...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mirrors
> 

Reply via email to