Opened 8 years ago

Closed 8 years ago

#1193 closed defect (fixed)

wrapper log encoding

Reported by: zzz Owned by: zzz
Priority: minor Milestone: 0.9.11
Component: apps/console Version: 0.9.10
Keywords: Cc:
Parent Tickets: Sensitive: no


<denixx> I have one question: is it configurable to make wrapper.log always in UTF-8?
<eche|on> the wrapper should be configureable. But I do not know where and how
<denixx> As I understood, wrapper create this file without "UTF-8" string, so this file is in cp1251 for my PC.
<denixx> It looks like I should ask zzz :)
<denixx> File is in cp1251, but this page: opens file like it is in UTF-8.
<zzz> thats a bug then
<denixx> "2013/12/23 19:48:44 | Unable to write to the configured log directory: C:\Windows\system32\config\systemprofile\AppData?\Roaming\i2p (??????? ?? ??????? ????? ????????? ????. (0x3))"
<denixx> As you can understand, those question marks is a russian message from OS.
<zzz> find the setting, add it to wrapper.config, if it works let us know what to add
<denixx> Ok, thanks.
<zzz> says you can't change it
<denixx> Eh. If it is so, maybe router console should read that file without "UTF-8"?
<denixx> I mean it should not read file as UTF-8?
<zzz> that would be the fix, yes

  • zzz writes ticket

The S.O. post is as of 3.5.17, but I don't see anything in the release notes thru 3.5.24

So we should read the wrapper log in platform encoding in /logs in the console?


Change History (2)

comment:1 Changed 8 years ago by zzz

Owner: set to zzz
Status: newaccepted

comment:2 Changed 8 years ago by zzz

Resolution: fixed
Status: acceptedclosed

Fixed in 7e55a9f0914d73edfb148ad46bc1b7892fe811e9 0.9.10-9-rc to read with default encoding if wrapper is present.

Note: See TracTickets for help on using tickets.