[wp-polyglots] error page prob

[Nikolay Bachiyski]

Ran Yaniv Hartstein wrote:
> Gettext gets loaded - the message is localized, but the user has to 
> count on the browser to both know the right encoding and switch the 
> directionality.

Yeah, you are right. I was talking about a completely different case. Sorry.

Nikolay.



> 
> On 11/27/06, * Nikolay Bachiyski* <nbachiyski at developer.bg 
> <mailto:nbachiyski at developer.bg>> wrote:
> 
>     Ran Yaniv Hartstein wrote:
>      > However, that function isn't available for e.g. during the
>     installation.
> 
>     Unfortunately you cannot use translated strings before the gettext
>     library has loaded  and the library could not load if wp-config.php is
>     missing, so the error aying that wp-config is missing is logically
>     un-internationalizationable!
> 
>     However, if you want the error message to appear in your message -
>     replace the original file with your own version and place it in the
>     dist/ directory in your repository.
> 
>     Happy (hacking|translating),
>     Nikolay
> 
>      >
>      > The error message you see if you don't have a wp-config.php file
>     can't
>      > use wp_die() as far as I can tell
>      >
>      > On 11/27/06, *Sewar* <xsewarx at gmail.com
>     <mailto:xsewarx at gmail.com> <mailto:xsewarx at gmail.com
>     <mailto:xsewarx at gmail.com>>> wrote:
>      >
>      >     wp_die() function added in 2.1 for fix this bug and display error
>      >     messages in nice page.
>      >
>      >     See: http://trac.wordpress.org/ticket/2902
>      >     < http://trac.wordpress.org/ticket/2902>
>      >
>      >
>      >     On 11/27/06, *Ran Yaniv Hartstein* <ran.hartstein at gmail.com
>     <mailto:ran.hartstein at gmail.com>
>      >     <mailto: ran.hartstein at gmail.com
>     <mailto:ran.hartstein at gmail.com>>> wrote:
>      >
>      >         This is a particularly problematic issue with languages
>     that use
>      >         completely different scripts and are written from Right
>     to Left,
>      >         like Hebrew or Arabic.
>      >
>      >         A possible solution is having the wp_die() function available
>      >         everywhere in wordpress, and using it for all error messages.
>      >
>      >
>      >         On 11/27/06, *Ralf Schmitt* < ralf.schmitt at schlund.de
>     <mailto:ralf.schmitt at schlund.de>
>      >         <mailto:ralf.schmitt at schlund.de
>     <mailto:ralf.schmitt at schlund.de>>> wrote:
>      >
>      >
>      >             Hi list,
>      >
>      >             I've found another issue that comes to surface when
>      >             wordpress is used in conjunction with utf-8 translations.
>      >
>      >             BUG:
>      >             When one triggers an error-page (for example not all
>      >             parameters for a comment). Worpress creates a page
>      >             which contains the translated error message. This page
>      >             contains no html tag information (no header, no body
>     tags)
>      >             just pure text information. So browser don't know for
>     sure
>      >             which encoding to use. IE for example fails to render
>     utf-8
>      >             characters.
>      >
>      >             EXAMPLE (german utf-8)
>      >             Fehler: Bitte füll die notwendigen Felder aus (Name,
>      >             E-Mail-Adresse).
>      >
>      >             regards
>      >
>      >             Ralf
>