- From: Lucinda DeWitt <ladewitt@lucindadewitt.com>
- Date: Fri, 23 Nov 2007 09:04:30 -0600
- To: Leif Halvard Silli <hyperlekken@lenk.no>
- Cc: Irene.Vatton@inrialpes.fr, "www-amaya@w3.org" <www-amaya@w3.org>
Leif, I'm a MacOSX user who had the same problem you describe. I had to change the preference (from ascii to UTF-8) hit "Apply" and then exit the program for the preference to "stick". It now consistently produces new documents as UTF-8. I agree the easiest solution would be to have utf-8 (or ISO-8859-1) be the default. I also noticed that there were some old amaya.plist files in my prefereneces folder. I deleted them and kept only the newest one named fr.inria.amaya.plist Perhaps this will help with some of the preferences issues. BTW--I use multiple tabs, never multiple windows. I was told some of the preferences commands don't "apply" unless you open a New Window (rather than a new tab). Not sure if this might help troubleshoot your situation. I've also had the problem with Amaya freezing during copy operations (all of a sudden the copy functions are grey-ed out and I can't do anything except exit and restart), but have not been able to reproduce it consistently. Just wanted to reaffirm that you are not the only Mac user with these issues. Lucinda DeWitt Leif Halvard Silli wrote: > > Irene Vatton 22.11.2007 16:04: >> Hi, >> >> The encoding of Preferences dialogue is used for new created documents. >> If you want to change the encoding of an existing document you have to >> use the Save as command. >> > > I did not ask for help to use Amaya. I reported a bug - and proposed a > possible workaround. If you want to know more about the bug, please ask > about the things that was unclear in my message. Or try to find a PPC > Mac OS X machineso you can test for yourself. -- Lucinda DeWitt DeWitt DeConstruction 2021 East 34th Street Minneapolis, MN 55407 (612) 721-6290 http://lucindadewitt.com
Received on Friday, 23 November 2007 15:04:55 UTC