dksrlgks123 / rainmeter

Automatically exported from code.google.com/p/rainmeter
0 stars 0 forks source link

Problem with WebParser and "local files" with Cyrillic chars in the path. #139

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
There appears to be an issue where WebParser breaks if the "path" of a
local file (i.e. Url=file://) has non ANSI chars in it.  So a user with a
user name in Cyrillic for instance cannot access local files in his skin
path.  We tried putting a CodePage= statement on the WebParser measure(s),
but this is not effective. I think CodePage is only used for encoding the
returned results, and has no effect on the call to the local file.  The
rest of Rainmeter is fine with the Cyrillic chars, but not WebParser and
Url=file://

Original issue reported on code.google.com by jsmor...@gmail.com on 20 Jan 2010 at 4:59

GoogleCodeExporter commented 8 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

GoogleCodeExporter commented 8 years ago
Is this attached file useful for this problem?

Original comment by spx268 on 31 Jan 2010 at 7:47

Attachments:

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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:

GoogleCodeExporter commented 8 years ago
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:

GoogleCodeExporter commented 8 years ago
Perfect. I appreciate your hard work to solve minor problems.

Original comment by kenz0.sa...@gmail.com on 2 Feb 2010 at 6:19

GoogleCodeExporter commented 8 years ago
Yes, me too! ;-)

Original comment by jsmor...@gmail.com on 2 Feb 2010 at 9:24

GoogleCodeExporter commented 8 years ago
Thank you for your testing. ;)
Fixed them in r326.

Original comment by spx268 on 3 Feb 2010 at 8:10

GoogleCodeExporter commented 8 years ago

Original comment by jsmor...@gmail.com on 3 Feb 2010 at 1:09