Thread

  1. error messages not only English

    jose' soares <sferac@bo.nettuno.it> — 1998-05-22T10:52:19Z

    Hi all,
    
    I see that PostgreSQL mainly gives error messages in English, I see also that
    in some cases there's the possibility to configure it to give messages in 
    other languages like global.c that may be configured to give messages in
    German.
    MySQL gives the possibility to configure it using an external file containing
    the messages by specifying it using the parameter LANGUAGE=<language>
    where <language> is one of the following:
    
                   czech
                   english
                   french
                   germany
                   italian
                   norwegian
                   norwegian-ny
                   polish
                   portuguese
                   spanish
                   swedish
    
    It will be great if we could have also this feature on PostreSQL. 
    I'm available to help on translation to Portuguese, Spanish and Italian.
                                                            Jose'
    
    
    
  2. Re: [GENERAL] error messages not only English

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-05-22T14:20:45Z

    Added to TODO.
    
    > 
    > Hi all,
    > 
    > I see that PostgreSQL mainly gives error messages in English, I see also that
    > in some cases there's the possibility to configure it to give messages in 
    > other languages like global.c that may be configured to give messages in
    > German.
    > MySQL gives the possibility to configure it using an external file containing
    > the messages by specifying it using the parameter LANGUAGE=<language>
    > where <language> is one of the following:
    > 
    >                czech
    >                english
    >                french
    >                germany
    >                italian
    >                norwegian
    >                norwegian-ny
    >                polish
    >                portuguese
    >                spanish
    >                swedish
    > 
    > It will be great if we could have also this feature on PostreSQL. 
    > I'm available to help on translation to Portuguese, Spanish and Italian.
    >                                                         Jose'
    > 
    > 
    > 
    
    
    -- 
    Bruce Momjian                          |  830 Blythe Avenue
    maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
      +  If your life is a hard drive,     |  (610) 353-9879(w)
      +  Christ can be your backup.        |  (610) 853-3000(h)
    
    
  3. Re: [GENERAL] error messages not only English

    Marc G. Fournier <scrappy@hub.org> — 1998-05-22T14:45:10Z

    On Fri, 22 May 1998, Bruce Momjian wrote:
    
    > Added to TODO.
    > 
    > > 
    > > Hi all,
    > > 
    > > I see that PostgreSQL mainly gives error messages in English, I see also that
    > > in some cases there's the possibility to configure it to give messages in 
    > > other languages like global.c that may be configured to give messages in
    > > German.
    > > MySQL gives the possibility to configure it using an external file containing
    > > the messages by specifying it using the parameter LANGUAGE=<language>
    > > where <language> is one of the following:
    > > 
    > >                czech
    > >                english
    > >                french
    > >                germany
    > >                italian
    > >                norwegian
    > >                norwegian-ny
    > >                polish
    > >                portuguese
    > >                spanish
    > >                swedish
    > > 
    > > It will be great if we could have also this feature on PostreSQL. 
    > > I'm available to help on translation to Portuguese, Spanish and Italian.
    
    Hrmmm...create an 'include/utils/errmsg.h file that is a link created by
    configure based on a --with-language=<insert your language here>...the
    file would contain:
    
    #define <ERRMSG TOKEN> "Error message in your language"
    
    Then use the TOKEN with elog...
    
    If we did something like this, we wouldn't have to convert all at once
    either, just as we pick up a new one...
    
    
    
    
    
    
  4. Re: [GENERAL] error messages not only English

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-05-22T14:49:41Z

    > Hrmmm...create an 'include/utils/errmsg.h file that is a link created by
    > configure based on a --with-language=<insert your language here>...the
    > file would contain:
    > 
    > #define <ERRMSG TOKEN> "Error message in your language"
    > 
    > Then use the TOKEN with elog...
    > 
    > If we did something like this, we wouldn't have to convert all at once
    > either, just as we pick up a new one...
    
    Also only a small set of error messages get sent to users.  Most of them
    are rarely used or are for debugging.
    
    -- 
    Bruce Momjian                          |  830 Blythe Avenue
    maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
      +  If your life is a hard drive,     |  (610) 353-9879(w)
      +  Christ can be your backup.        |  (610) 853-3000(h)
    
    
  5. Re: [GENERAL] error messages not only English

    Marc G. Fournier <scrappy@hub.org> — 1998-05-22T14:53:30Z

    On Fri, 22 May 1998, Bruce Momjian wrote:
    
    > > Hrmmm...create an 'include/utils/errmsg.h file that is a link created by
    > > configure based on a --with-language=<insert your language here>...the
    > > file would contain:
    > > 
    > > #define <ERRMSG TOKEN> "Error message in your language"
    > > 
    > > Then use the TOKEN with elog...
    > > 
    > > If we did something like this, we wouldn't have to convert all at once
    > > either, just as we pick up a new one...
    > 
    > Also only a small set of error messages get sent to users.  Most of them
    > are rarely used or are for debugging.
    
    	True, but having those also in various languages makes us more
    "admin friendly" *grin*
    
    	If this looks good, I'll setup the appropriate configure related
    issues...let me know...
    
    
    
    
  6. Re: [GENERAL] error messages not only English

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-05-22T14:55:53Z

    > 
    > 	True, but having those also in various languages makes us more
    > "admin friendly" *grin*
    > 
    > 	If this looks good, I'll setup the appropriate configure related
    > issues...let me know...
    
    One nice thing is that all the error messages are wrapped up in elog(),
    so we can easily extract them, and make macros for them.
    
    -- 
    Bruce Momjian                          |  830 Blythe Avenue
    maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
      +  If your life is a hard drive,     |  (610) 353-9879(w)
      +  Christ can be your backup.        |  (610) 853-3000(h)
    
    
  7. Re: [HACKERS] Re: [GENERAL] error messages not only English

    Vadim Mikheev <vadim@krs.ru> — 1998-05-26T15:46:21Z

    The Hermit Hacker wrote:
    > 
    > Hrmmm...create an 'include/utils/errmsg.h file that is a link created by
    > configure based on a --with-language=<insert your language here>...the
    > file would contain:
    > 
    > #define <ERRMSG TOKEN> "Error message in your language"
               ^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > 
    > Then use the TOKEN with elog...
    > 
    > If we did something like this, we wouldn't have to convert all at once
    > either, just as we pick up a new one...
    
    Sometime ago we told about using error codes in elog (and put them to the
    client) - this would very useful for non-interactive applications...
    
    How about to implement this ?
    
    Vadim
    
    
  8. Re: [HACKERS] Re: [GENERAL] error messages not only English

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-05-26T16:08:15Z

    > 
    > The Hermit Hacker wrote:
    > > 
    > > Hrmmm...create an 'include/utils/errmsg.h file that is a link created by
    > > configure based on a --with-language=<insert your language here>...the
    > > file would contain:
    > > 
    > > #define <ERRMSG TOKEN> "Error message in your language"
    >            ^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > > 
    > > Then use the TOKEN with elog...
    > > 
    > > If we did something like this, we wouldn't have to convert all at once
    > > either, just as we pick up a new one...
    > 
    > Sometime ago we told about using error codes in elog (and put them to the
    > client) - this would very useful for non-interactive applications...
    > 
    > How about to implement this ?
    
    Added to TODO.  The first part was already there:
    
    * allow international error message support and add error codes
    
    
    -- 
    Bruce Momjian                          |  830 Blythe Avenue
    maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
      +  If your life is a hard drive,     |  (610) 353-9879(w)
      +  Christ can be your backup.        |  (610) 853-3000(h)