Closed GoogleCodeExporter closed 9 years ago
I have actually heard the report of such a problem in the past. Apparently, this
problem seems to depend on user's environment.
At least in my test, this problem was reproduced in vista or 7, but there was
not the
problem in XP or 2000.
WebParser is completely dependent on Internet Explorer installed in Windows, so
I'm
not sure, but I think the version of IE is the key to a problem.
Anyway, I think it is necessary to modify WebParser according to the change in
the
specification of IE.
Original comment by kenz0.sa...@gmail.com
on 21 Jan 2010 at 2:04
Is this attached file useful for this problem?
Original comment by spx268
on 31 Jan 2010 at 7:47
Attachments:
To be honest I can't really test as I only have english character set. We will
need
to get someone who uses Russian or Japanese or Korean or something on the
forums to
test and let us know.
Original comment by jsmor...@gmail.com
on 31 Jan 2010 at 8:38
It seems that the problem has fixed in a Japanese environment at least.
However, although this is not an important problem, the problem which is not
displayed on a log file and ABOUT is not solved yet. It doesn't seem possible to
write the character except ASCII in a log file.
I think it is the best that everything is solved including this problem.
Original comment by kenz0.sa...@gmail.com
on 1 Feb 2010 at 5:03
Attachments:
Try this.
----
- The coded character set of the logfile is changed to UTF-8. (ccs=UTF-8)
http://msdn.microsoft.com/en-us/library/yeby3zcb%28VS.80%29.aspx
- "MS Shell Dlg 2" is now used for the ABOUT dialog box.
http://support.microsoft.com/kb/282187
Original comment by spx268
on 1 Feb 2010 at 6:50
Attachments:
Perfect. I appreciate your hard work to solve minor problems.
Original comment by kenz0.sa...@gmail.com
on 2 Feb 2010 at 6:19
Yes, me too! ;-)
Original comment by jsmor...@gmail.com
on 2 Feb 2010 at 9:24
Thank you for your testing. ;)
Fixed them in r326.
Original comment by spx268
on 3 Feb 2010 at 8:10
Original comment by jsmor...@gmail.com
on 3 Feb 2010 at 1:09
Original issue reported on code.google.com by
jsmor...@gmail.com
on 20 Jan 2010 at 4:59