| View previous topic :: View next topic |
| Author |
Message |
jom
Junior Member
Joined: 16 Jun 2007
Posts: 14
|
 Posted: Sun Oct 11, 2009 12:55 pm Post subject: Compare by content default format UTF8 |
 |
|
I compare UTF8 html files a lot of the time, and TC defaults to ansi format, (probably because there is no UTF-8 BOM signature in my files).
There is a menu to change the compare to UTF-8, but it is very tedious to have to select this option each time I want to compare two files.
Is there a simple option to set the default compare format for when TC does not recognize the file format? So that instead of defaulting to ansi, I could tell it to default to UTF-8 instead? This would save me a lot of time. |
|
| Back to top |
|
 |
ghisler(Author)
Site Admin
Joined: 04 Feb 2003
Posts: 24621
Location: Switzerland
|
| Posted: Tue Oct 13, 2009 1:27 pm Post subject: |
|
|
Unfortunately there is no simple solution. You could use a scripting tool to make this change in the dialog with a single keypress. I'm open to suggestions how to solve this in TC 8.
_________________
Author of Total Commander
http://www.ghisler.com |
|
| Back to top |
|
|
jom
Junior Member
Joined: 16 Jun 2007
Posts: 14
|
| Posted: Wed Oct 14, 2009 12:29 pm Post subject: |
|
|
When TC first finds a text file format it doesnt recognize, it defaults to ANSI so I manually change the filetype to UTF8 via the "Choose Encoding" dialog.
A very simple solution is for TC to "remember" this selection in the "Choose Encoding" dialog.
Next time TC finds a text file it doesn't recognize, instead of defaulting to ANSI, it used the option I previously selected in the "Choose Encoding" dialog.
In other words I only need to tell TC once in a session that my files are UTF8, (and not repeatedly every time I compare a new file).
Another solution would be to add a setting to wincmd.ini, for example:
AssumedFileFormatWhenUnrecognised = UTF8
Instead of defaulting to ANSI, it would default to UTF8 |
|
| Back to top |
|
|
MVV
Power Member
Joined: 03 Aug 2008
Posts: 4541
Location: Russian Federation
|
|
| Back to top |
|
|
jom
Junior Member
Joined: 16 Jun 2007
Posts: 14
|
| Posted: Thu Oct 15, 2009 1:58 am Post subject: |
|
|
Sure it would be nice to have better detection too. But what when detection fails? This is what I am talking about.
The procedure for manually selecting encoding format is very tedious, because you have to do it each time for each new file.
This could be improved with a simple mod, so you only have to select the format once, instead of every time. |
|
| Back to top |
|
|
MVV
Power Member
Joined: 03 Aug 2008
Posts: 4541
Location: Russian Federation
|
| Posted: Thu Oct 15, 2009 2:09 am Post subject: |
|
|
| jom wrote: | Sure it would be nice to have better detection too. But what when detection fails? This is what I am talking about.
The procedure for manually selecting encoding format is very tedious, because you have to do it each time for each new file. |
Good UTF-8 detection DLL won't fails if it is written for your codepage. E.g. for Russian letters UTF-8 contains pairs of characters that are impossible in Russian.
TC compare tool allows to select TWO compare encodings - one for each file. So what one should remember TC if they are not the same?
_________________
VirtualPanel plugin: Temporary panel for TC (forum)
TOTALCMD.NET: TCFS2, NTLinks, CopyTree, AskParam, ConPaste, Sudo… |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
