Re: [Phpwiki-talk] gettext problems

[Jeff D. <da...@da...>]

>I agree 100% with you, while I can see the point on using gettext with
>a languaje like C, I still cannot see the point on using gettext on
>a languaje like PHP.

Not that I'm completely sold on gettext either, but one big advantage
of using gettext (particularly for developers/translators who use emacs)
is the ability to use the GNU gettext tools to do things like
find new strings to be translated in (changed) source code, and
merge those new strings into the translation (.po) files.

Note that PhpWiki _should_ (is designed to) work even if
PHP was compiled without gettext support.  If it doesn't, that's
a bug.  Report it.

>a solution based on $HTTP_SERVER_VARS["HTTP_ACCEPT_LANGUAGE"]
>(ie. the client browser languaje) ... is IMO better ...


1. You wouldn't want HTTP_ACCEPT_LANGUAGE to affect the default
   pgsrc.

2. Since the page content of a particular wiki are (most often)
   primarily in one language, there's not a whole lot of point
   in allowing the viewer to select various languages for the
   templates/dates...

(see also
  <http://phpwiki.sourceforge.net/phpwiki/index.php?MultiLingualWiki>)