Em 7 de fevereiro de 2018, Allin escreveu:
In response to both Henrique and Periklis in:
http://lists.wfu.edu/pipermail/gretl-users/2018-February/012912.html
http://lists.wfu.edu/pipermail/gretl-users/2018-February/012909.html
It would probably be helpful if you could run gretl.exe with the --debug
flag and report what you see in the console box that accompanies gretl in
that case, when you're trying these operations with non-ASCII filenames.
To do this you can either create a desktop shortcut to gretl and append the
--debug option flag in the Properties box (that's two dashes at the start,
before "debug") or you could invoke gretl with that option from a cmd.exe
window. This may give us more information about the precise step in the
processing of Windows filenames at which the encoding problem arises.
This is the Windows Command Prompt output:
<Windows output>
rcfile: 'C:\Users\Henrique\AppData\Roaming\gretl\.gretl2rc' (found)
langpref='Portuguese (Brazil)', langid=16, lcnumeric=1
lcode='portuguese-brazilian.1252' -> locale='Portuguese_Brazil.1252'
set_cp_from_locale: CP = 1252
read_win32_config: returning 0
set_up_windows_look: themepref = 'Clearlooks'
gtkrc = 'C:\Program Files\gretl\share\themes\Clearlooks\gtk-2.0\gtkrc'
</Windows output>
This is the Gretl output:
<Gretl output>
Gretl versão 2017e-git
Sessão atual: 2018-02-08 10:12
Lido o arquivo de dados C:\Program Files\gretl\data\misc\australia.gdt
Table 1. Test for readfile()
Falha ao abrir arquivo "C:/Users/Henrique/Documents/gretl/��a de
Queiroz/Table_1.txt": Invalid argument
Erro ao executar script: parando
string Table_1 = readfile("Table_1.txt")
</Gretl
output>
Best regards,
Henrique Andrade