| Author |
Message |
pb
Joined: 04 Sep 2007
Posts: 32
|
 Posted: Tue Sep 04, 2007 1:28 am Post subject: VV Log Viewer |
 |
|
The log viewer with vvscheduler in pro 1.3.1 is better than the one in 2build20114. Why? Because the type is too spread out in the newer one, which allows much less to be seen. I am using win2ksp4; maybe it's different with different os.
Please return to the print spacing in pro v 1.3.1.
(However, I see you fixed the issue with horizontal scrolling not going a screen width at at time.)
Hmm... but if I start the viewer from vvscheduler 2, the unicode stuff is not visible. Only non-unicode stuff previously written by v1.3.1 is visible. Why use unicode when you don't have to, anyway? Takes double the space for nothing.
Therefore, the log viewer in v2b2014 is imho broken.
--peter |
|
| Back to top |
|
 |
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
|
| Back to top |
|
|
pb
Joined: 04 Sep 2007
Posts: 32
|
| Posted: Tue Sep 04, 2007 6:40 pm Post subject: VV log viewer |
|
|
| TGRMN Software wrote: | Hi, could it be that you are viewing a log file which is half ASCII and half UNICODE?
thanks |
Yes, the log file's initial part is ascii written by the previous version of VV Pro (1.3.1). So, I am going to guess that the viewer assumes that if the file starts in ascii it should be all ascii?
Why do you want to use unicode anyway, if the locale is US English?
Does this also account for the wider character and line spacing?
--peter |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
| Posted: Wed Sep 05, 2007 12:58 am Post subject: |
|
|
Hello
yes, please try starting with an empty log. Since version 2.0, the log files are in UNICODE, so they can support all characters of the world. If you have a file in your profile which has a non-english character that will be handled fine by ViceVersa.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
pb
Joined: 04 Sep 2007
Posts: 32
|
| Posted: Wed Sep 05, 2007 1:24 am Post subject: VV log viewer |
|
|
Ok, I reset the log. I guess your point is that some file name might have unicode characters in it, and that would not display right in the log file. Nevertheless, I think it's wasteful and an unnecessary nuisance to use unicode for the US english locale.
Note that this means that earlier versions of VV must not write to the same log files as the latest versions. Maybe a better design would be to use markup in the log file to turn unicode on and off.
Also, please note my unhappiness with the wider line and character spacing in the log file viewer. This just presents less information in more space, without any improvement in readability.
--peter |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8769
|
| Posted: Wed Sep 05, 2007 6:02 am Post subject: |
|
|
Hi
| Quote: | | Also, please note my unhappiness with the wider line and character spacing in the log file viewer. This just presents less information in more space, without any improvement in readability. |
This must be due to the font used by Windows to display UNICODE characters instead of ASCII, as no code was changed there....
| Quote: | | I think it's wasteful and an unnecessary nuisance to use Unicode for the US English locale. |
An option we are thinking of adding is to be able to set UNICODE log files on or off. Indeed, if UNICODE is not needed the log files are unnecessarily large (double size).
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
pb
Joined: 04 Sep 2007
Posts: 32
|
| Posted: Wed Sep 05, 2007 5:43 pm Post subject: |
|
|
| TGRMN Software wrote: |
An option we are thinking of adding is to be able to set UNICODE log files on or off. Indeed, if UNICODE is not needed the log files are unnecessarily large (double size). |
Well, this is only a very minor issue compared to things like VV not exiting or crashes, but it might be nice to improve it if you find yourself with too much spare time. (Also, as someone else mentioned in some other thread, using unicode also restricts the tools that can be used to view and process these log files. E.g., piping through grep would be inconvenient.)
The trouble with an option to set unicode on or off, though I would like it, is that that would just lead to 99% of your users complaining that there are too many arcane options.
--peter |
|
| Back to top |
|
|
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
