12:16 p.m.
Hi,
I just downloaded and installed the latest (12/29/2006) windows build. I ran
a VECM and saved it as an icon to the session, which I then saved. I then
closed gretl and double clicked on the session icon (both my dataset and the
sessions are stored on my usb flash) to get the following warning
g_locale_to_utf8 failed for charset 'CP1253'
after continiously clicking on OK I finally got a script window that was
illigible. When I closed it gretl was still on, however, my session had not
been loaded.
Trying to open my session through the gretl gui is more successful, since I
am able to see the session window and the datafile. However, double clicking
on the vecm icon crashes gretl.
Although I have repeated the above a number of times, I have not tried to
replicate it with some other dataset, but thought it would be useful to
report.
P.S.
CP1253 is windows Greek.
Regards,
Tank
--
Dr. Thanassis Kalogeressis, Economist, Researcher,
Regional Development and Policy Research Unit (RDPRU),
http://www.uom.gr/rdpru
Dept of Economics, University of Macedonia
5:45 p.m.
On Thu, 4 Jan 2007, Athanasios Kalogeresis wrote:
I just downloaded and installed the latest (12/29/2006) windows
build. I ran a VECM and saved it as an icon to the session,
which I then saved. I then closed gretl and double clicked on
the session icon (both my dataset and the sessions are stored on
my usb flash) to get the following warning g_locale_to_utf8
failed for charset 'CP1253' after continiously clicking on OK I
finally got a script window that was illigible.
Could you please send me a copy of the session file? I think that
would help in figuring out what's going wrong here.
Thanks.
Allin Cottrell
8:37 a.m.
On Thu, 4 Jan 2007, I wrote:
On Thu, 4 Jan 2007, Athanasios Kalogeresis wrote:
> I just downloaded and installed the latest (12/29/2006) windows build. I
> ran a VECM and saved it as an icon to the session, which I then saved. I
> then closed gretl and double clicked on the session icon (both my dataset
> and the sessions are stored on my usb flash) to get the following warning
> g_locale_to_utf8 failed for charset 'CP1253' after continiously clicking on
> OK I finally got a script window that was illigible.
Could you please send me a copy of the session file? I think
that would help in figuring out what's going wrong here.
Never mind; I think I have found the problem(s) and if I'm right,
it doesn't really have anything to do with CP1253. I will make a
new Windows snapshot on Friday, and I'd be grateful if you could
see if it works for you.
Allin Cottrell
5:06 p.m.
I repeated what I did yesterday and I regret to say that I get the same
warning. The only difference is that I have to click on OK once to get it
out of the way and start gretl (BTW the script window appears again, equally
illegible).
On the other hand, I am happy to report that the crash (upon double-clicking
the VECM icon) has been solved.
I do, however, have another -newbe type- question. Are the session folders
(which are automatically created at the default gretl directory at
C:\Documents and Settings\user\Application Data\gretl\) supposed to be
empty?
2007/1/5, Allin Cottrell <cottrell(a)wfu.edu>:
On Thu, 4 Jan 2007, I wrote:
> On Thu, 4 Jan 2007, Athanasios Kalogeresis wrote:
>
>> I just downloaded and installed the latest (12/29/2006) windows build.
I
>> ran a VECM and saved it as an icon to the session, which I then saved.
I
>> then closed gretl and double clicked on the session icon (both my
dataset
>> and the sessions are stored on my usb flash) to get the following
warning
>> g_locale_to_utf8 failed for charset 'CP1253' after continiously
clicking on
>> OK I finally got a script window that was illigible.
>
> Could you please send me a copy of the session file? I think
> that would help in figuring out what's going wrong here.
Never mind; I think I have found the problem(s) and if I'm right,
it doesn't really have anything to do with CP1253. I will make a
new Windows snapshot on Friday, and I'd be grateful if you could
see if it works for you.
Allin Cottrell
_______________________________________________
Gretl-users mailing list
Gretl-users(a)ricardo.ecn.wfu.edu
http://ricardo.ecn.wfu.edu/mailman/listinfo/gretl-users
5:47 p.m.
On Fri, 5 Jan 2007, Athanasios Kalogeresis wrote:
I repeated what I did yesterday and I regret to say that I get
the same warning. The only difference is that I have to click on
OK once to get it out of the way and start gretl (BTW the script
window appears again, equally illegible).
The trouble here is that this is not a script file (it's a zipped
session file), yet it's being opened as if it were a script.
How exactly are you opening the file? I have tested here on Linux
(not yet on Windows), and I find that double-clicking the file
icon, or dragging it onto gretl, or opening it via the
"File/Session file/Open session" menu item, or giving the filename
as a command-line argument, now does the right thing with session
files. But if the file previously found its way (wrongly) onto
the list of recently-opened script files, then attempting to open
it from that list will produce the symptoms you describe.
On the other hand, I am happy to report that the crash (upon
double-clicking the VECM icon) has been solved.
OK, good.
I do, however, have another -newbe type- question. Are the
session folders (which are automatically created at the default
gretl directory at C:\Documents and Settings\user\Application
Data\gretl\) supposed to be empty?
They are temporary storage space for session elements such as
graph files. They're supposed to be cleaned up on exit. Of
course, if the program crashes, that won't happen :-(
Allin.
11:41 p.m.
On Fri, 5 Jan 2007, Athanasios Kalogeresis wrote:
I repeated what I did yesterday and I regret to say that I get
the same warning. The only difference is that I have to click on
OK once to get it out of the way and start gretl (BTW the script
window appears again, equally illegible).
OK, I've done some testing on Windows and I see what you mean.
There is now (in the current snapshot) a fix that works for
Windows too: session files should be opened as session files.
Thanks for the report on this.
Also I see your point about the empty session folders. On
Windows, these were not getting deleted on shut-down as they are
supposed to. I think this was due to Windows not supporting the
usual POSIX file operations (or not properly). I've tried putting
in place a fix for this but haven't managed to test it yet.
Allin Cottrell
2:10 p.m.
I'm happy to confirm that both fixes (i.e. bouble clicking on seesion files
to open and deletion of the 'temp' session folders on shut-down) work fine.
Thanks a lot,
2007/1/5, Allin Cottrell <cottrell(a)wfu.edu>:
On Fri, 5 Jan 2007, Athanasios Kalogeresis wrote:
> I repeated what I did yesterday and I regret to say that I get
> the same warning. The only difference is that I have to click on
> OK once to get it out of the way and start gretl (BTW the script
> window appears again, equally illegible).
OK, I've done some testing on Windows and I see what you mean.
There is now (in the current snapshot) a fix that works for
Windows too: session files should be opened as session files.
Thanks for the report on this.
Also I see your point about the empty session folders. On
Windows, these were not getting deleted on shut-down as they are
supposed to. I think this was due to Windows not supporting the
usual POSIX file operations (or not properly). I've tried putting
in place a fix for this but haven't managed to test it yet.
Allin Cottrell
_______________________________________________
Gretl-users mailing list
Gretl-users(a)ricardo.ecn.wfu.edu
http://ricardo.ecn.wfu.edu/mailman/listinfo/gretl-users
6704
days inactive
6707
days old
6 comments
2 participants
participants (2)
-
Allin Cottrell -
Athanasios Kalogeresis