Page 1 of 1

Bug Report: Invalid encoding detection

Posted: Fri Jun 24, 2011 7:49 pm
by Ivan
I've alpeady posted this issue to the other topic. I think it will be better to post it to a separate topic. Sorry for duplicating.
---
TC has a problem with encoding detection when it is UTF without BOM. TC detects encoding as ANSI. TC is unable to find national symbols when I tried to search files containing them. For test purposes I've used a very simple text file contain two words "Test" in English and Russian. Total file size is 12 bytes (4 for english and 8(2*4) for Russian).

I've uploaded a screenshot which is description of the problem.
http://imageshack.us/photo/my-images/53 ... oding.png/
Could you check it, please?

Thank you.

p.s. One of the earlier versions of TC2 was able to find and display such files correctly.

Re: Bug Report: Invalid encoding detection

Posted: Thu Sep 22, 2011 1:53 pm
by Ivan
Hello.

Can you, please, add a new ottion to the preferences that will force format detection as UTF8 withoit BOM instead of ANSI?

Thank you.

Re: Bug Report: Invalid encoding detection

Posted: Thu Sep 29, 2011 7:13 pm
by DVV
Ivan wrote:Can you, please, add a new option to the preferences that will force format detection as UTF8 withoit BOM instead of ANSI?
+1.
Just today encountered a problem with a lot of UTF-8 without BOM files: TextCrawler could not replace cyrillic text there. (As I understand, it's because TextCrawler treated those files as ANSI.)

Re: Bug Report: Invalid encoding detection

Posted: Tue Nov 27, 2012 1:46 pm
by vaidulis
Hello,

I have the same problem with TC encoding detection. I mean TC detects files UTF without BOM as ANSI.
So we need some solution to solve this problem, because I also use national letters.

Thank you for any help and info.

p.s. I hope I don't need to create the same topic the third time... and we'll solve this problem once and forever :)

BR
vaidulis

Re: Bug Report: Invalid encoding detection

Posted: Wed Nov 28, 2012 7:28 pm
by DigitalVolcano
You can force the encoding output be to UTF8 in the options screen (Replace tab->Output encoding), this may help.

Re: Bug Report: Invalid encoding detection

Posted: Tue Dec 04, 2012 8:03 am
by vaidulis
Yes I saw this feature and this doesn't help. The problem is because TC detects files UTF8 without BOM as ANSI and then it doesn't recognise national letters and can't make changes correctly.
So now I convert manually these files to UTF8 with BOM that TC could recognise them correctly and in that case it works fine. But this process is uncomfortable...

Any more ideas or solutions? :)

Thanx in advance.

BR
vaidulis