View Issue Details

IDProjectCategoryView StatusLast Update
0000706Far ManagerEditorpublic2009-02-22 09:41
Reportertheultramage Assigned ToDrKnS  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version2.0 
Summary0000706: opening very short file gives messed up encoding
DescriptionI sometimes create a small temp file to write stuff to.
Sometimes, FAR will not use the right codepage in Editor mode. As a result, anything I write will show up as ?? (probably wrong unicode codepage).
Additional InformationSteps to reproduce:
1. created a file called 'x'
2. write 'r370'
3. press F2 (save)
4. press ESC (exit)
5. press F4 (edit) on the new file
see here that what you wrote becomes '??'
6. press F6 (switch to view mode)
see here that it shows ok
7. press F4 (hexadecimal view)
see here that the data is still ASCII
TagsNo tags attached.
Build780

Activities

theultramage

2009-01-19 14:55

reporter   bugnote:0002340

Last edited: 2009-01-19 15:02

Revision: 2470

PS: if you write '1234' instead of 'r370', the file saves as ASCII. Problem also occurs with the string 'r370, r374, r375'.
This is a very strange issue...

Joey

2009-01-24 16:44

reporter   bugnote:0002361

Well, not exactly strange, probably. Telling ASCII and Unicode apart without some kind of BOM or other marker can lead to this results, as also demonstrated here: http://blogs.msdn.com/michkap/archive/2006/06/14/631016.aspx

theultramage

2009-02-10 11:26

reporter   bugnote:0002400

Today I found out that it's treating all of my source code files that begin with a logo/banner (// ____________________________ and such) as 'unicode'.

The worst thing about this is, that I can't find a way to switch the encoding! Neither F8 nor shift+F8 open up a dialog to change it...

The only workaround I found was to use shift+f4, to manually key in the file name (doesn't auto-select the name under cursor), and manually choose the ANSI encoding. Then the file will open correctly, and furthermore, FAR will remember this choice... for this one file.

theultramage

2009-02-10 11:30

reporter   bugnote:0002401

> Telling ASCII and Unicode apart without some kind of BOM or other marker can lead to this results

Please don't default to 'unicode' (microsoft UTF-16?) when there is no BOM... Doesn't the standard demand that all files encoded this way have a BOM?

If unicode files without a BOM are rare, then open them in ANSI mode and let the user switch the encoding, instead of what FAR is doing right now.

DrKnS

2009-02-21 20:18

administrator   bugnote:0002558

build 780.

theultramage

2009-02-22 08:41

reporter   bugnote:0002560

Tried a few of the above inputs, all viewed ok in the editor. Thank you for the fix!

Issue History

Date Modified Username Field Change
2009-01-19 14:53 theultramage New Issue
2009-01-19 14:53 theultramage Status new => assigned
2009-01-19 14:53 theultramage Assigned To => vskirdin
2009-01-19 14:55 theultramage Note Added: 0002340
2009-01-19 14:58 theultramage Note Edited: 0002340
2009-01-19 15:02 theultramage Note Edited: 0002340
2009-01-24 16:44 Joey Note Added: 0002361
2009-02-10 11:26 theultramage Note Added: 0002400
2009-02-10 11:30 theultramage Note Added: 0002401
2009-02-21 20:18 DrKnS Assigned To vskirdin => DrKnS
2009-02-21 20:18 DrKnS Note Added: 0002558
2009-02-21 20:18 DrKnS Status assigned => feedback
2009-02-22 08:41 theultramage Note Added: 0002560
2009-02-22 09:41 DrKnS Build => 780
2009-02-22 09:41 DrKnS Status feedback => closed
2009-02-22 09:41 DrKnS Resolution open => fixed
2009-02-22 09:41 DrKnS Fixed in Version => 2.0