syslog() on Windows for wide character View as Markdown

hi,

Thanks for the update :)

I still think that it should follow mbstring logic and API. Doing so
will provide 100% backward compatibility. If an application define
this setting as UTF-8 but some modules are not implemented with UTF-8
in mind, then the log may be broken.

Cheers,

2010/2/5 KITAZAKI Shigeru shigeru_kitazaki@cybozu.co.jp:

Hi,

We've improved a patch which makes syslog() to send UTF-8 strings to event
log on Windows. This patch introduces a new INI directive to switch to the
new behavior; the directive name is 'syslog_widechar'. This is a optional
feature only for Windows, and does not conflict current behavior or any
other settings.

More detailed information and the patch are here:
http://developer.cybozu.co.jp/oss/2010/02/php-syslog-patc.html

And many thanks to your suggestions in the thread of 'adding GB18030
support for mbstring'.

2010/2/1 Pierre Joye wrote:

• php_syslog.patch
  It has to be optional. Maybe a mbstring.syslog* option to set a given
  encoding for the syslog functions.

2010/2/1 Moriyoshi Koizumi wrote:

• php_syslog.patch
  It seems this doesn't relies on any mbstring settings, but just
  changed syslog() to take strings encoded in UTF-8 instead of the
  system's default encoding.  It'd look good to me if it had a new flag
  causing syslog() to switch to the new behaviour.

Regards,
KITAZAKI Shigeru

--

--
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org