Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-27 Thread Phpster
Sorry guys, I meant that the current application database is not configured for utf-8 Bastien Sent from my iPod On Jan 27, 2009, at 6:04, Per Jessen wrote: Jan Kaštánek wrote: Per Jessen: The gettext db doesn't support UTF8??? Uh oh, that's a show-stopper. It supports. We use it. B

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-27 Thread Per Jessen
Jan Kaštánek wrote: > Per Jessen: >> >> The gettext db doesn't support UTF8??? Uh oh, that's a show-stopper. > > It supports. We use it. But only in MsgStr (translation), not in MsgId > (original strings). > Yeah, I found out too. (from the GNU gettext docu). /Per Jessen, Zürich -- PHP Ge

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-27 Thread Jan Kaštánek
Per Jessen: > > The gettext db doesn't support UTF8??? Uh oh, that's a show-stopper. It supports. We use it. But only in MsgStr (translation), not in MsgId (original strings). -- toby http://toby.cz/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-27 Thread Per Jessen
Bastien Koert wrote: > No, as all of our users have to authorized to use the app, we store > the desired language in a field in the user record. However, we also > supply functionality via a drop down to allow the user to change the > language if desired. Okay, that's very similar to my approach.

RE: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-26 Thread Boyd, Todd M.
> -Original Message- > From: Bastien Koert [mailto:phps...@gmail.com] > Sent: Monday, January 26, 2009 12:23 PM > To: Per Jessen > Cc: php-general@lists.php.net > Subject: Re: [PHP] best practice wrt multi-lingual websites, gettext() > etc. ---8<--- > At

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-26 Thread Bastien Koert
On Mon, Jan 26, 2009 at 12:21 PM, Per Jessen wrote: > Phpster wrote: > > > Dunno if it's a best practice, but I store all the translations in the > > db for easy manipulation and extraction to a file for others to > > translate. That obviously involves both import and export utilities. > > Hi Bas

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-26 Thread Per Jessen
Phpster wrote: > Dunno if it's a best practice, but I store all the translations in the > db for easy manipulation and extraction to a file for others to > translate. That obviously involves both import and export utilities. Hi Bastien interesting - does this mean you're also coding for language

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-25 Thread Per Jessen
Richard Lynch wrote: > I can't help with the bits you are asking about, but I can give this > advice: > > Don't rely solely on the Apache/browser content-negotiation, please. > Don't worry, the site already has a user-override option. /Per Jessen, Zürich -- PHP General Mailing List (http:/

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-25 Thread Richard Lynch
I can't help with the bits you are asking about, but I can give this advice: Don't rely solely on the Apache/browser content-negotiation, please. This one time... I was in Paris. I was at an Internet Cafe. I couldn't change browser settings. Some sites that I knew were available in English sh

Re: [PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-25 Thread Phpster
Dunno if it's a best practice, but I store all the translations in the db for easy manipulation and extraction to a file for others to translate. That obviously involves both import and export utilities. At work we to the translation in real time thru a render page that combined the data f

[PHP] best practice wrt multi-lingual websites, gettext() etc.

2009-01-25 Thread Per Jessen
I am writing a small(ish) site which will eventually need to be available in several different languages. This needs to more or less transparent to the user, so I am using Apaches content negotiation features, which is working very well. The issues arise once I start looking at PHP and Javascript