Russian FAQ page charset problem
Current page with FAQ in Russian
(http://www.postgresql.org/docs/faqs.FAQ_russian.html) has charset
problem: the text is in koi-8r, while HTML source has this line:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
It'd be great to fix it: either to change meta line or convert
contents to UTF8 (I personally would choose the latter).
--
Sincerely yours,
Nikolay Samokhvalov
Postgresmen LLC, http://postgresmen.ru
Nikolay, by history reasons, Russian FAQ translation come in KOI8-R encoding.
But, PostgreSQL site has UTF-8.
2Bruce: I can convert Russian translation into UTF-8 and correct HTML header.
What you think about it?
2008/9/12 Nikolay Samokhvalov <samokhvalov@gmail.com>:
Show quoted text
Current page with FAQ in Russian
(http://www.postgresql.org/docs/faqs.FAQ_russian.html) has charset
problem: the text is in koi-8r, while HTML source has this line:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />It'd be great to fix it: either to change meta line or convert
contents to UTF8 (I personally would choose the latter).--
Sincerely yours,
Nikolay Samokhvalov
Postgresmen LLC, http://postgresmen.ru--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Nikolay Samokhvalov wrote:
Current page with FAQ in Russian
(http://www.postgresql.org/docs/faqs.FAQ_russian.html) has charset
problem: the text is in koi-8r, while HTML source has this line:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />It'd be great to fix it: either to change meta line or convert
contents to UTF8 (I personally would choose the latter).
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.
On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.
What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?
--
Sincerely yours,
Nikolay Samokhvalov
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:
On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?
I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.
We could do that, but it is also a question of what the author prefers
for editing. We don't require UTF-8 in other places. And I don't feel
comfortable converting everything (FAQ or not) to UTF-8, because that
loses information in some cases.
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.
Done.
I only touched the HTML one - seems the text one is already in latin
characters?
//Magnus
Hmm. At this time, everything all right.
But, How do I do at the next time after update? Would be I convert
Russian translation to UTF-8 or leave it in KO8-R, before send it to
Bruce?
2008/9/15 Magnus Hagander <magnus@hagander.net>:
Show quoted text
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.Done.
I only touched the HTML one - seems the text one is already in latin
characters?//Magnus
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Виктор Вислобоков wrote:
Hmm. At this time, everything all right.
But, How do I do at the next time after update? Would be I convert
Russian translation to UTF-8 or leave it in KO8-R, before send it to
Bruce?
Please do all your work in UTF-8, and sen UTF-8 only patches to Bruce.
The best way to get started is probably to grab the just converted file
from CVS and work off that one.
//Magnus
Okay :)
2008/9/15 Magnus Hagander <magnus@hagander.net>:
Show quoted text
Виктор Вислобоков wrote:
Hmm. At this time, everything all right.
But, How do I do at the next time after update? Would be I convert
Russian translation to UTF-8 or leave it in KO8-R, before send it to
Bruce?Please do all your work in UTF-8, and sen UTF-8 only patches to Bruce.
The best way to get started is probably to grab the just converted file
from CVS and work off that one.//Magnus
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.
No, the conversion to a UTF8 header is done by the web infrastructure;
the file in CVS is in the native Russian encoding, koi8-r, and I don't
know how to change that.
However, it now seems all the FAQs are in ASCII or UTF8 so I think we
are OK going into the future.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
On Tue, Sep 23, 2008 at 7:01 PM, Bruce Momjian <bruce@momjian.us> wrote:
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.No, the conversion to a UTF8 header is done by the web infrastructure;
the file in CVS is in the native Russian encoding, koi8-r, and I don't
know how to change that.
That's the iconv -f bit suggested above, that I thought you were doing.
However, it now seems all the FAQs are in ASCII or UTF8 so I think we
are OK going into the future.
Yup, Magnus converted them.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote:
On Tue, Sep 23, 2008 at 7:01 PM, Bruce Momjian <bruce@momjian.us> wrote:
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.No, the conversion to a UTF8 header is done by the web infrastructure;
the file in CVS is in the native Russian encoding, koi8-r, and I don't
know how to change that.That's the iconv -f bit suggested above, that I thought you were doing.
Nope, never did that, and I don't have the proper locales on my sever.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Bruce Momjian wrote:
Dave Page wrote:
On Tue, Sep 23, 2008 at 7:01 PM, Bruce Momjian <bruce@momjian.us> wrote:
Dave Page wrote:
On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
<samokhvalov@gmail.com> wrote:On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
This was already discussed on the pgsql-www list recently, but there has
been no resolution on what to do yet.What about using UTF8 for Russian text? Why not simply "iconv -f
koi8-r -t utf8 ..."?I thought that was what Bruce was going to do. He has other priorities
at the moment though, so perhaps one of the the committers could
handle it.No, the conversion to a UTF8 header is done by the web infrastructure;
the file in CVS is in the native Russian encoding, koi8-r, and I don't
know how to change that.That's the iconv -f bit suggested above, that I thought you were doing.
Nope, never did that, and I don't have the proper locales on my sever.
That's not locale, that's encoding. And it's independent of what locales
you have - AFAIK as long as you have iconv, you should be good.
For next time, that is - since it's already fixed this time :-)
//Magnus