#437 encoding errors on reading should not display on stdout

closed-accepted
None
5
2012-04-22
2012-04-12
No

When opening a file (explicitly or through hypersearch for example) with foreign characters, an encoding error dialog may appear. The dialog is definitely in place. But in the same time the message is printed on standard output (standard error? - doesn't matter). I suggest not to print it in console. The gui dialog is sufficient. The user is informed about the suggested action to take.

From the user's point of view, this is not important, what is printed on standard error. But from the developer's standing, every line printed in console output makes me think that something's wrong with the code and at least a bug report is needed. That's why I would like to switch it off.

Entries that are printed to standard error by Log class are of WARNING and ERROR level. While I don't want to change this general assumption, it seems that the encoding messages' level should be lowered below WARNING, that is to NOTICE.

Any objections to such a change?

Discussion

  • Jarek Czekalski

    Jarek Czekalski - 2012-04-12
    • assigned_to: nobody --> jarekczek
     
  • Jarek Czekalski

    Jarek Czekalski - 2012-04-22
    • status: open --> closed-accepted
     
  • Jarek Czekalski

    Jarek Czekalski - 2012-04-22

    r21594

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks