[wpkg-users] [Bug 291] wpkg.js won't run on non-uncode is set to c04

bugzilla-daemon at bugzilla.wpkg.org bugzilla-daemon at bugzilla.wpkg.org
Sat Oct 22 23:06:15 CEST 2016


Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #6 from Rainer Meier <r.meier at wpkg.org> ---
Alright, I think I found the root cause of this issue. In some specific
language settings Windows does not write unicode text files by default but is
using local codepages.
In case of Chinese (Hong Kong SAR) setting on Vista this is causing an issue
due to Vista containing the (TM) and (R) symbols which is written to the log

I have solved this by forcing the log files to be written in unicode.

I also fixed an issue reported on the mailing list about WPKG now writing the
running registry key.


Changes 2016-10-22, v1.3.2-RC2 by Rainer Meier <r.meier (at) wpkg.org>
FIX: Forcing OS to write logfile in Unicode to fix exception 800a0005 when
     writing unicode characters to the log on OS with non-unicode application
     settings set to languages like "Chinese (Hong Kong SAR)".
     Fixes bug 291. Thanks to "isd".
FIX: Setting running state in registry (HKLM\Software\WPKG\running)) on WPKG
     Thanks to Niels Thiele for reporting this on the mailing list.

WPKG 1.3.2-RC2 has not been released yet. Though you can get the latest wpkg.js
from Sourceforge:

(Download it using the "Download this file" link on top of the page.

As always it's safe to just drop-replace your wpkg.js with the SVN version.

Please report if this fixes your problem.

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20161022/94a2d8ed/attachment.html>

More information about the wpkg-users mailing list