1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Fixed v15: VIEW - encoding and CSV issues

Discussion in 'Support' started by nikbackm, Mar 31, 2013.

  1. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    I used VIEW with some ANSI (Windows 1252) files containing non-English characters like "åäö".

    It seems that VIEW often fails to detect the correct encoding and opens the file in UTF-8 mode which garbles the input. (Adding or removing a single line can cause VIEW to choose the wrong one)

    Is there some way to improve this, or maybe specify the encoding on the command line when opening the file?

    Refreshing (F5) the display when the file is opened seem to make VIEW choose the right encoding though. Strange. Would be good to be able to skip that step though.


    Another issue with VIEW is in CSV mode. It seems that displaying the gridlines cause my monitor (I turned off the speakers) to emit some low humming noise. Turning them off makes it go away. And vice versa.

    I would assume this is monitor specific, or have someone else noticed the same? Changing the gridline color to something other than black makes the humming less loud or makes it go away entirely.

    The problem is that hiding the gridlines is not remembered next time VIEW is started in CSV mode. You have to hide them again. Could this perhaps be changed? Or an option to specify if they are visible at startup added?

    (Best would be if there were no humming noise at all, but I realize this might be hard to fix reliably. Many different monitors out there - mine is an Eizo FlexScan S2402W)
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,860
    Likes Received:
    83
    Is this specific to v15 or does the same thing happen in v14?

    I have no idea how that could happen; I'll let Charles answer that one.
     
  3. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    Unfortunately I don't know, I've been a bit slow to update the last few years and is still on v12, which has no VIEW command.

    Seems like it should be easily fixable though since pressing F5 to refresh seems to resolve the issue.
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,860
    Likes Received:
    83
    VIEW comes from another developer (Charles Prineas), and I don't have the source code. I'll pass it on to Charles.
     
  5. FileViewer

    Joined:
    Aug 3, 2011
    Messages:
    37
    Likes Received:
    0
    VIEW does not auto-detect code pages - it always use the system code page (by default).

    If you would like to use Windows 1252 (eg, to display line drawing characters), you will have to set it manually by left-clicking on "ANS" in the bottom right of the status bar and then selecting "Character Encoding"->"Western European"->"Windows 1252".

    Once the code page is changed, it will be used for all further files - until you change it again.
    It is possible that VIEW may incorrectly identify the file as a UTF-8 file - in which case it doesn't use the code page to display the file.

    Note that you cannot specify what code page to use on the command line.

    Can you send me a file which exhibits this problem? (v at fileviewer.com)
    I really don't know what to say about this!

    You cannot permanently disable the vertical grid lines - but you can the horizontal grid lines (click on the arrow next to the CSV Mode button on the toolbar and select "CSV Options"). Perhaps this may make a difference.

    Also, if the files are being displayed on a white background, you may try changing it to something like a light gray to see if it makes a difference (select "Customize Colors" from the View menu).
     
  6. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,307
    Likes Received:
    39
    I remember seeing -- er, hearing this on old CRT monitors: strongly contrasty horizontal lines can cause the tube to make an audible noise. But I've never encountered it on an LCD!
     
  7. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    Yes, it's misidentified as UTF-8.

    I sent a mail with example files and a little more information.


    Thanks.

    I noticed myself that changing the grid color to dark grey fixed the noise.

    Turning the horizontal grid lines off also takes care of it, but I prefer to keep them visible. But dark-grey lines and light-grey background instead of black and white works very well so this is no longer a problem for me. Only until I had changed the default colors.

    Me neither until now (unless I never noticed before).

    It's not really that loud a noise, similar to a fluorescent lamp, but maybe not quite as strong as that.
     
  8. FileViewer

    Joined:
    Aug 3, 2011
    Messages:
    37
    Likes Received:
    0
    Thanks for sending me the files.

    There is a problem with how I identify UTF8 files. It will be fixed in a future update.
     
  9. FileViewer

    Joined:
    Aug 3, 2011
    Messages:
    37
    Likes Received:
    0
    This problem has been fixed in 15.00.33
     
  10. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    So it is.

    Thanks!
     

Share This Page