* Arne Heizmann <[EMAIL PROTECTED]> wrote:
> > I can tell you the reasons for using koi8-r, euc-jp etc instead of utf-8
> > for the httpd docs. The resulting documents are significant smaller.
>
> ru:15169 => 20713
> ru+gzip:5454 => 6160
>
> ja:14063 => 16595
> ja+gzip:
André Malo wrote:
I can tell you the reasons for using koi8-r, euc-jp etc instead of utf-8
for the httpd docs. The resulting documents are significant smaller.
ru:15169 => 20713
ru+gzip:5454 => 6160
ja:14063 => 16595
ja+gzip:4833 => 5237
Hardly "significantly small
>
> > BTW I don't believe that UTF-8 page is *significant* larger - most of
> the
> > characters (e.g. HTML code) are still represented with one byte.
>
> If you have messy HTML code, this argument happens to be true ;-)
I usually don't ;-)
> If you have more text and each russian character ta
* "Denis Gerasimov" <[EMAIL PROTECTED]> wrote:
> BTW I don't believe that UTF-8 page is *significant* larger - most of the
> characters (e.g. HTML code) are still represented with one byte.
If you have messy HTML code, this argument happens to be true ;-)
If you have more text and each russian ch
>
> Veysel Harun Sahin wrote:
> >
> > I want to use russian charset
>
> Why are people still creating new websites with these obsolete character
> sets? Why not just use UTF-8? It's been around for long enough...
>
Okay, I also think that is a good idea (especially for multi-language
sites), b
Thanks Denis :)
.htaccess file has solved the problem.
Best regards.
On 5/31/05, André Malo <[EMAIL PROTECTED]> wrote:
> * Arne Heizmann <[EMAIL PROTECTED]> wrote:
>
> > Veysel Harun Sahin wrote:
> > >
> > > I want to use russian charset
> >
> > Why are people still creating new websites with t
* Arne Heizmann <[EMAIL PROTECTED]> wrote:
> Veysel Harun Sahin wrote:
> >
> > I want to use russian charset
>
> Why are people still creating new websites with these obsolete character
> sets? Why not just use UTF-8? It's been around for long enough...
I can tell you the reasons for using koi8
Veysel Harun Sahin wrote:
I want to use russian charset
Why are people still creating new websites with these obsolete character
sets? Why not just use UTF-8? It's been around for long enough...
**
This email and any files t
No problem.
There are at least 4 solutions:
1. Put the line
AddDefaultCharset windows-1251
To your .htaccess file (see
http://httpd.apache.org/docs-2.0/mod/core.html#adddefaultcharset)
2. Add charset support to your scripting engine.
If you use PHP you may put the folloewing line to your ph
Thanks Ivan. But i am hosting my site at a web hosting company and i
don't have access the configuration file. Is there another solution?
On 5/30/05, Ivan Barrera A. <[EMAIL PROTECTED]> wrote:
> >>
> >
> >
> >
> > Delete the AddDefaultCharset directive from httpd.conf
> >
>
> Or put your charset
>>
>
>
>
> Delete the AddDefaultCharset directive from httpd.conf
>
Or put your charset in that place :
AddDefaultCharset windows-1251
(sorry i forgot to put this on the other email)
>
>>Is there any way to override the default charset and use the ones
>>which appear on the meta tags witho
> I am hosting my site at a web hosting company. I want to use russian
> charset and set my meta tags like " content="text/html; charset=windows-1251" />". But they don't seem to
> work. When i validate my pages through w3c markup validation service
> my pages' encoding seems iso-8859-9. And I see
12 matches
Mail list logo
