[DOCS] This approach to non-ASCII names does not work

2006-09-19 Thread Tom Lane
openjade -V draft-mode -wall -wno-unused-param -wno-empty -D . -c 
/usr/share/sgml/docbook/dsssl-stylesheets/catalog -d stylesheet.dsl -i 
output-html -t sgml postgres.sgml
openjade:release.sgml:567:14:E: "353" is not a character number in the document 
character set
openjade:release.sgml:1085:56:E: "305" is not a character number in the 
document character set
openjade:release.sgml:1085:63:E: "305" is not a character number in the 
document character set
openjade:release.sgml:1497:35:E: "305" is not a character number in the 
document character set
openjade:release.sgml:1497:42:E: "305" is not a character number in the 
document character set
openjade:release.sgml:1662:38:E: "305" is not a character number in the 
document character set
openjade:release.sgml:1662:45:E: "305" is not a character number in the 
document character set
make: *** [html] Error 1

regards, tom lane

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [DOCS] This approach to non-ASCII names does not work

2006-09-19 Thread Bruce Momjian
Tom Lane wrote:
> openjade -V draft-mode -wall -wno-unused-param -wno-empty -D . -c 
> /usr/share/sgml/docbook/dsssl-stylesheets/catalog -d stylesheet.dsl -i 
> output-html -t sgml postgres.sgml
> openjade:release.sgml:567:14:E: "353" is not a character number in the 
> document character set
> openjade:release.sgml:1085:56:E: "305" is not a character number in the 
> document character set
> openjade:release.sgml:1085:63:E: "305" is not a character number in the 
> document character set
> openjade:release.sgml:1497:35:E: "305" is not a character number in the 
> document character set
> openjade:release.sgml:1497:42:E: "305" is not a character number in the 
> document character set
> openjade:release.sgml:1662:38:E: "305" is not a character number in the 
> document character set
> openjade:release.sgml:1662:45:E: "305" is not a character number in the 
> document character set
> make: *** [html] Error 1

Wow, our documentation characterset is "ISO-8859-1":

CONTENT="text/html; charset=ISO-8859-1"

Should we change it to UTF8?

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [DOCS] This approach to non-ASCII names does not work

2006-09-19 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> openjade:release.sgml:567:14:E: "353" is not a character number in the 
>> document character set

> Wow, our documentation characterset is "ISO-8859-1":
>   CONTENT="text/html; charset=ISO-8859-1"
> Should we change it to UTF8?

I'm betting you should change those numbers from octal to decimal,
actually.

regards, tom lane

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [DOCS] This approach to non-ASCII names does not work

2006-09-19 Thread Bruce Momjian
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> openjade:release.sgml:567:14:E: "353" is not a character number in the 
> >> document character set
> 
> > Wow, our documentation characterset is "ISO-8859-1":
> > CONTENT="text/html; charset=ISO-8859-1"
> > Should we change it to UTF8?
> 
> I'm betting you should change those numbers from octal to decimal,
> actually.

Those numbers are decimal, but certainly cannot be represented in
ISO-8859-1.  They are multi-byte, one is Turkish.

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [DOCS] This approach to non-ASCII names does not work

2006-09-19 Thread Bruce Momjian
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Tom Lane wrote:
> > >> openjade:release.sgml:567:14:E: "353" is not a character number in the 
> > >> document character set
> > 
> > > Wow, our documentation characterset is "ISO-8859-1":
> > >   CONTENT="text/html; charset=ISO-8859-1"
> > > Should we change it to UTF8?
> > 
> > I'm betting you should change those numbers from octal to decimal,
> > actually.
> 
> Those numbers are decimal, but certainly cannot be represented in
> ISO-8859-1.  They are multi-byte, one is Turkish.

Actually, I got the codes from here:

http://www.pemberley.com/janeinfo/latin1.html#latexta

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 6: explain analyze is your friend