Many thanks for all your help. I got it going well, the job is done and I learnt a bit as well!
Cheers Detlef on 29/8/06 3:28 PM, Russell Sandon Klenetsky at [EMAIL PROTECTED] wrote: > > Detlef - > > Someone with more technical expertise could probably elaborate/correct here > (also, since I'm new to this list, someone please scold me if this discussion > belongs elsewhere), but here is some advice from my experience with Find & > Replace: > > It sometimes happens that what you see in your text window is not the actual > character(s) you need to search for. This can happen when your source file > includes non-printable characters, or has been translated incorrectly > somewhere along the way (I've had to hack through files for people that > probably went from Outlook to Word to HTML to Unix-based web server to MSIE > copied back to Outlook to Eudora to BBEdit... it can get ugly, but I've found > BBEdit to be very versatile at dealing with these issues). When coming across > these anomalies, BBEdit may skip, approximate, and/or "arbitrarily" assign a > character to symbolize those odd or non-printable characters on screen. > > When a search is ineffective, often I will copy from the source text and paste > it into the Find window directly, instead of re-typing what _appears_ to be > the character(s) I'm searching for. Another thing to check for are > "Invisibles". Go to Edit -> Text Options... , and check "Show Invisibles". > This often sheds some light on why things are not going as expected. > > > To guess what happened in your example: > >> 1. I don't know why, but some Pipe "|" characters have translated to: %7c > > %7c is the url-encoded version of "|" (pipe). (If you do a google search for > "|" you'll see your query has been replaced by %7c in your location bar). It > would be extremely odd if the Find & Replace command is doing that to your > files on its own, esp. if the replacement string is blank. It's possible that > with some of the files you're loading -- based on file extension or lack > thereof -- BBEdit has to "guess" which character set to use. Perhaps it is > re-saving your files and translating the "pipes" (and other non-url-safe > characters?) to its url-encoded equivalent.... very strange. You can play > with the various preferences under "Text Files: Opening" and ": Saving" to see > if changing the default encoding makes a difference. > > -Russ -- ------------------------------------------------------------------ Have a feature request? Not sure the software's working correctly? If so, please send mail to <[EMAIL PROTECTED]>, not to the list. List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml> List archives: <http://www.listsearch.com/BBEditTalk.lasso> To unsubscribe, send mail to: <[EMAIL PROTECTED]>
