I can't exit the program properly.

Bug #252152 reported by maijija117
6
Affects Status Importance Assigned to Milestone
The Mnemosyne Project
Fix Released
Undecided
Peter Bienstman

Bug Description

After I used the program, I can not exit the program properly.
Help me plz.
Your program benefits me so much.
I hope you can solve the problem.

Revision history for this message
Peter Bienstman (peter-bienstman) wrote :

I would try uninstalling the previous version completely before installing the new version.

If there are still problems after you try that, you would need to give more details, like what exactly happened, where there any error messages, ...

Also look for a file called error_log.txt in the directory C:\documents and settings\maijija117\.mnemosyne and tell me its contents.

Changed in mnemosyne-proj:
assignee: nobody → peter-bienstman
Revision history for this message
maijija117 (piya-gfs) wrote :

Thank. Now I can solve the problem myself. I had saved file xxx.mem with Thai letter and then I meet the problem.
So, I tried to save xxx.mem in Englis and the problem disappered.

Changed in mnemosyne-proj:
status: New → Fix Released
Revision history for this message
Rathann (dominik-greysector) wrote :

I also came across this one, when setting the .mem filename to "japoński.mem" (=Japanese in Polish). Is there any reason why non-ascii characters are a problem in filenames?

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/mnemosyne/pyqt_ui/main_dlg.py", line 506, in closeEvent
    backup_database()
  File "/usr/lib/python2.5/site-packages/mnemosyne/core/mnemosyne_core.py", line 1143, in backup_database
    f = gzip.GzipFile(filename + ".gz", 'w')
  File "/usr/lib64/python2.5/gzip.py", line 128, in __init__
    self._write_gzip_header()
  File "/usr/lib64/python2.5/gzip.py", line 155, in _write_gzip_header
    self.fileobj.write(fname + '\000')
UnicodeEncodeError: 'ascii' codec can't encode character u'\u0144' in position 37: ordinal not in range(128)

This is mnemosyne-1.1.1-r1. Has this already been fixed in current development code?

Revision history for this message
Peter Bienstman (peter-bienstman) wrote : Re: [Bug 252152] Re: I can't exit the program properly.

On Friday 10 October 2008 23:03:54 Rathann wrote:
> I also came across this one, when setting the .mem filename to
> "japoński.mem" (=Japanese in Polish). Is there any reason why non-ascii
> characters are a problem in filenames?

Yes, it's due to the interaction between Windows and Qt3, which is also
different on different localised versions of Windows and therefore difficult
to solve.

Hopefully the move to Qt4 in Mnemosyne 2.0 will alleviate this.

Peter

Revision history for this message
Rathann (dominik-greysector) wrote :

On Saturday, 11 October 2008 at 09:45, Peter Bienstman wrote:
> On Friday 10 October 2008 23:03:54 Rathann wrote:
> > I also came across this one, when setting the .mem filename to
> > "japoński.mem" (=Japanese in Polish). Is there any reason why non-ascii
> > characters are a problem in filenames?
>
> Yes, it's due to the interaction between Windows and Qt3, which is also
> different on different localised versions of Windows and therefore difficult
> to solve.
>
> Hopefully the move to Qt4 in Mnemosyne 2.0 will alleviate this.

Note that I'm using Linux (Fedora 9), not Windows. Couldn't this be fixed
at least for Linux?

Dominik

Revision history for this message
Peter Bienstman (peter-bienstman) wrote :

I have it working under Linux, provided I switch my entire system to using
Unicode to store filenames.

Peter

Revision history for this message
Rathann (dominik-greysector) wrote : Re: [Bug 252152] I can't exit the program properly.

On Saturday, 11 October 2008 at 15:20, Peter Bienstman wrote:
> I have it working under Linux, provided I switch my entire system to using
> Unicode to store filenames.

Well. My system is fully UTF-8, so that's not a problem. I notice that
the traceback mentions "ascii". I haven't looked at the actual code yet.

Dominik

Revision history for this message
Peter Bienstman (peter-bienstman) wrote :

Strange... At the moment, I don't really have much time to investigate this,
but any help you could provide by looking at the code would be much
appreciated!

Revision history for this message
Peter Bienstman (peter-bienstman) wrote :

Could you try again with 1.2?

Revision history for this message
Rathann (dominik-greysector) wrote :

Sorry for the long delay.

I've just retried with 1.2 and it seems to be working correctly. Thanks a lot.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.