The new upload is working fine.
Thanks so much for the option to disable the splash screen and the local settings file!
Regards,
Highend
TextCrawler 2.0 Beta available for trying out
It seems that the latest version breaks the search over more than one line...
File Filter: *.html
Start Location: D:\Users\Highend\Dokumente\Webauftritt
Standard -> Find -> Edit Find text
</li>
</li>
I hope these two lines with a lot of tabstops before and </li> at the end (+ a linebreak after the first </li>) are displayed correctly in this thread.
If I click on Find the search does not find any file that contains these two lines. But I have several files with them in that directory...
I left out a few beta versions but former ones had no problems to find text with several lines / linebreaks.
Can you have a look at it asap please?
Tia,
Highend
File Filter: *.html
Start Location: D:\Users\Highend\Dokumente\Webauftritt
Standard -> Find -> Edit Find text
</li>
</li>
I hope these two lines with a lot of tabstops before and </li> at the end (+ a linebreak after the first </li>) are displayed correctly in this thread.
If I click on Find the search does not find any file that contains these two lines. But I have several files with them in that directory...
I left out a few beta versions but former ones had no problems to find text with several lines / linebreaks.
Can you have a look at it asap please?
Tia,
Highend
Just d/l'd and am looking at / trying Beta release 2.03765.24060 (04/23), and notice in the Options Button - History Tab, there are two duplicate buttons for "Clear Reg Ex".
Maybe replace one of these with a "Clear All"?
Also in the there seems to be an isse with text sizing.
On the main screen on the STANDARD tab the Find and Replace is being cut off by the dialog boxes for text.
On REGULAR EXPRESSION tab, Red Ex and Replace have the same issue.
On the FUZZY SEARCH tab, the FIND WORD: / ALGORITHM: / and TOLLERANCE: text is overwritting into the respective dialog boxes.
Maybe replace one of these with a "Clear All"?
Also in the there seems to be an isse with text sizing.
On the main screen on the STANDARD tab the Find and Replace is being cut off by the dialog boxes for text.
On REGULAR EXPRESSION tab, Red Ex and Replace have the same issue.
On the FUZZY SEARCH tab, the FIND WORD: / ALGORITHM: / and TOLLERANCE: text is overwritting into the respective dialog boxes.
Highend -
The reason for this is that I changed the Textbox type in the zoom window (to allow colour highlighting), and now it returns LF rather than CR/LF for the line endings - so it won't find phrases across standard windows line endings anymore.
I need to correct this and add in a line endings type option!
The reason for this is that I changed the Textbox type in the zoom window (to allow colour highlighting), and now it returns LF rather than CR/LF for the line endings - so it won't find phrases across standard windows line endings anymore.
I need to correct this and add in a line endings type option!
Hi,
two things with the latest beta:
1) I just found that TC2 always kills my special characters (German Umlauts) in my files. That's not about searching and replacing, it's just what TC2 writes.
Example: Take a file with "��� test ���" in it, search for "test" and replace with "test".
With TC1 the file keeps unchanged, TC2 distorts all the umlauts.
The umlauts are also lost when importing the RegExt-Tester's RegEx.txt from the previous version.
2) What exactly are the options
regex-Culture Invariant and regex-ECMA-compatible for?
two things with the latest beta:
1) I just found that TC2 always kills my special characters (German Umlauts) in my files. That's not about searching and replacing, it's just what TC2 writes.
Example: Take a file with "��� test ���" in it, search for "test" and replace with "test".
With TC1 the file keeps unchanged, TC2 distorts all the umlauts.
The umlauts are also lost when importing the RegExt-Tester's RegEx.txt from the previous version.
2) What exactly are the options
regex-Culture Invariant and regex-ECMA-compatible for?
1) Thanks, you've found a genuine problem. It seems that it is missing out 'extended' characters when they are in plaintext files. If the files were UTF8 encoded it would work file. It would also work fine if the 'Binary mode' option is switched on (as in TC1 - though then it wouldn't be able to read any Unicode files).
Looks like i'm back to the problem of detecting plain ascii files again!
2) Culture Invariant:
http://msdn.microsoft.com/en-us/library ... #Invariant
ECMA Compatible
http://msdn.microsoft.com/en-us/library ... ECMAScript
Enabling This option may help if you can't get expressions from TC1 to work (TextCrawler 1.x used a ECMAscript compatible RegEx engine)
Looks like i'm back to the problem of detecting plain ascii files again!
2) Culture Invariant:
http://msdn.microsoft.com/en-us/library ... #Invariant
ECMA Compatible
http://msdn.microsoft.com/en-us/library ... ECMAScript
Enabling This option may help if you can't get expressions from TC1 to work (TextCrawler 1.x used a ECMAscript compatible RegEx engine)