I found the reason why X-Chat 2.0.x on Win32 forgets I10N after a
while.
The bug can be re-created easily: Just DCC SEND a file using the
file selection dialog by typing:
/DCC SEND <nickname>
After that, new windows will created with English buttons and text.
Repeat the step above:
/DCC SEND <nickname>
This time send a file from the directory where X-Chat was installed
to and new windows will use the national text again.
So it appears the file selection dialog not only CWDs to the
originating directory temporarily, but also CWDs the X-Chat workdir.
My suggestion for a solution would be as follows:
On X-Chat startup, convert the relative directory .\locale\<user
language>\LC_MESSAGES\xchat.mo to the absolute path for this system
language>for later access.
It might also be helpful to have xchat remember the path last used for
sending a file without having xchat cwd to there, or at least have it
cwd back to the workdir later.
--
Sincerly, yours
Ziggy SpaceRat
--
XChat-discuss: mailing list for XChat users
Archive: http://mail.nl.linux.org/xchat-discuss/
> On X-Chat startup, convert the relative directory .\locale\<user
> language>\LC_MESSAGES\xchat.mo to the absolute path for this system
> language>for later access.
> It might also be helpful to have xchat remember the path last used for
> sending a file without having xchat cwd to there, or at least have it
> cwd back to the workdir later.
Converting is not possible, because locale directory is hardcoded into
sources, and thus into binary. So solution would seem to be cwd back.
--
Sincerely yours,
SilvereX
> Ziggy SpaceRat wrote:
>
> > On X-Chat startup, convert the relative directory .\locale\<user
> > language>\LC_MESSAGES\xchat.mo to the absolute path for this system
> > language>for later access.
> > It might also be helpful to have xchat remember the path last used for
> > sending a file without having xchat cwd to there, or at least have it
> > cwd back to the workdir later.
>
> Converting is not possible, because locale directory is hardcoded into
> sources, and thus into binary. So solution would seem to be cwd back.
Problem is solved in 2.0.6b (and nativefile7 patch).
--
Peter.