On Tue, 14 Jun 2016, Henrique Andrade wrote:
Em 14 de junho de 2016, Allin escreveu:
> This is in response to Henrique Andrade's postings,
>
http://lists.wfu.edu/pipermail/gretl-users/2016-June/011883.html
>
http://lists.wfu.edu/pipermail/gretl-users/2016-June/011884.html
>
> It turns out that these issues could be fixed without great difficulty --
> see git and the current snapshots. We now intercept and modify "%s" string
> conversion specifiers for printf and sprintf so that numerical values
> indicating width and "precision" are taken to be in UTF-8 characters
rather
> than bytes.
>
> Since email is liable to mangle this sort of thing, I'm attaching a little
> PDF file which illustrates "before" and "after".
It worked just fine! Thanks!
> As for extra line-breaks appearing in some contexts on Windows, this is to
> do with the Windows-specific business of opening files in text versus binary
> mode; I think it should be fixed now too.
Dear Allin, unfortunately it didn't worked as I think it is expected.
Now we have problems trying to visualize text output created by the
"output" command using Notepad (the standard text editor on Windows).
Please take a look at the attached images.
IMHO if the solution is too difficult to implement I think the old
behavior is better because I believe the situation where the user
saves a text file to open with Notepad is a more common task than
re-open it in Gretl for further analysis.
OK, I have reverted the text -> binary mode change for the "outfile"
command. (We're all forced to live with the consequences of
Microsoft's decision to represent "newline" by two bytes -- either
missing or doubled newlines in many cross-platform contexts.)
Allin