Hi All, The preferences setting for the default new file encoding is ignored. The encoding from the last opened file is set as the encoding for all new files. Open a file with an 8859-1 encoding and this is the encoding for all new files. Then open a file with a Korean encoding. This is now the encoding for all new files. How does everyone think this should actually work? Regards, Jim H
On 05/29/2012 03:19 PM, Jim Hayward wrote: > Hi All, > > The preferences setting for the default new file encoding is ignored. > > The encoding from the last opened file is set as the encoding for all > new files. Open a file with an 8859-1 encoding and this is the encoding > for all new files. Then open a file with a Korean encoding. This is now > the encoding for all new files. > > How does everyone think this should actually work? hmm you're right, document.c:2387 does this, the session encoding (which is the last used encoding) is given priority over the newfile encoding set in the preferences. Should we always use the newfile encoding ? (I think so) Olivier -- -- Bluefish website http://bluefish.openoffice.nl/ Blog http://oli4444.wordpress.com/
On Wed, 2012-05-30 at 22:20 +0200, Olivier Sessink wrote: > Should we always use the newfile encoding ? (I think so) I think the preferences setting should always be used. Looking at the code after I noticed the problem, I didn't see a reason for encoding to be stored in the session file at all. Regards, Jim H
RSS Feed