search

rassaman / ichm

Automatically exported from code.google.com/p/ichm
0 stars 0 forks source link

Suggestion: Change Default Text Encoding #72

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Platform:
Mac

What version of the product are you using? On what operating system?
Version 1.4 (07f4788) on Mac OS X 10.5.6

Please provide any additional information below.
Nearly all of my CHM files are Unicode, so every time I open a file I have to 
manually change the 
encoding. Could you add an option to change the default encoding?

Original issue reported on code.google.com by matthew....@gmail.com on 14 Feb 2009 at 2:25

GoogleCodeExporter commented 8 years ago 
i've got the same problem too.
so i am now downloading the source code and try to find out

Original comment by R.Saku...@gmail.com on 14 Aug 2009 at 6:16

GoogleCodeExporter commented 8 years ago 
Happens to me too!

Original comment by camif...@gmail.com on 27 Aug 2009 at 5:04

GoogleCodeExporter commented 8 years ago 
I have an idea, maybe we could change the plist like this

<key>name</key>
<string></string>
<key>title</key>
<string>Default</string>

to

<key>name</key>
<string>UTF-8</string>
<key>title</key>
<string>Default</string>

Original comment by dgg321...@gmail.com on 5 Dec 2009 at 11:57

GoogleCodeExporter commented 8 years ago 
You can do this by your own risk. I should warn you that by this way, you break 
the native encoding sniffing 
funtioanality.

Original comment by iamawal...@gmail.com on 6 Dec 2009 at 3:15

GoogleCodeExporter commented 8 years ago 
OK, is there a better solution then? Thanks.

Original comment by dgg321...@gmail.com on 7 Dec 2009 at 1:13

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Yes, this is extremely annoying. Esp. since in some files by changing the 
encoding you lose your place in the file. 

Either the encoding detection code should be smarter or the default should be a 
user facing preference. The option to change the encoding from the menu should 
remain though.

Original comment by veritas....@gmail.com on 17 Jul 2010 at 12:00

GoogleCodeExporter commented 8 years ago 
I have the same problem here. The default encoding should be change by the user 
in the preferences.

Original comment by christia...@gmail.com on 8 Feb 2011 at 6:51

GoogleCodeExporter commented 8 years ago 
I would add my voice to those wishing for default encoding to be a user 
preference.

That way we don't have to change it every time we open a file.  Simple fix.  :P

Original comment by basler.e...@gmail.com on 22 Jan 2012 at 12:34

GoogleCodeExporter commented 8 years ago 
I'd add my voice to solving this problem.  iChm is wonderful freeware and could 
really use this simple fix.  Just add a user preference or make their last 
choice permanent until they change it again.  

I need unicode for all my ebooks, and I have to switch the format every time I 
open a reference book.

Version: 1.4.3

Original comment by basler.e...@gmail.com on 16 Jan 2013 at 12:58