> Now I guess I move on to text factories so I can hit several files with this
> approach.

Actually, you can do that with the Multi-File Search command, in the
Search menu.







>
> On Jun 3, 10:41 am, Bruce Van Allen <[email protected]> wrote:
> > On 2010-06-03, Nick A wrote:
> >
> > >Now I'm stuck with a search window that lists all the tags that were
> > >found, but I don't know how to delete them all. Intuitively I want to
> > >select all and delete, but it doesn't seem to work like that. Using
> > >the find/find all/replace dialog box doesn't seem to be able to do it
> > >all at once. How do I do this all at once?
> >
> > You need to study BBEdit more. There (of course) is a Replace
> > All command.
> >
> > BUT before you do that...
> >
> > What people have been suggesting is using the search pattern for
> > thetableelement markup and replacing each instance with '' -- nothing.
> >
> > Before you do that, you might consider replacingtableelement
> > markup with some easily identifiable character(s), allowing you
> > to more easily see where the formertablemarkup was, and also
> > use additional find/replace steps to begin putting your
> > non-tablemarkup/css in place.
> >
> > If I were dismantling tables with this brute force "I have to do
> > it fast" approach, perhaps not knowing for sure yet exactly how
> > the contents of the tables will be marked up in the new version,
> > I would at least throw in some white space. Something like
> > replacing <table> tags with two blank lines, <tr> tags with one
> > blank line, and <td> & <th> tags with a newline and a tab
> > (\r\t). That would at least let me see the what was left in
> > separate pieces.
> >
> > You could just as easily replace <table> tags with <div> tags,
> > <tr> tags with <p>, and <td> & <th> with <span>. Taking this
> > further, try:
> >    replace <table> tags with <div class="former_table">
> >    replace <tr> tags with <p class="former_row">
> >    replace <th> tages with <span class="former_heading">
> >    replace <td> tags with <span class="former_cell">
> >
> > You're not stuck forever with those classes named "former..." --
> > you can always do find/replace on them once the stuff being
> > marked up is integrated with your new css/markup scheme. In the
> > meantime, though, you have every piece of the formertable's
> > content marked up with style-able structures.
> >
> > But this really depends on whether thetable'sorganization of
> > its contents maps closely to how you want to organize the
> > content in the new version. It probably won't map well, and
> > you'll have to do some hand work rearranging the content to work
> > with css layout. Then I think your job is simpler if you do
> > something like what I've suggested in above with white space.
> >
> > HTH
> >
> >     - Bruce
> >
> > _bruce__van_allen__santa_cruz_ca_
>
> --
> You received this message because you are subscribed to the
> "BBEdit Talk" discussion group on Google Groups.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/bbedit?hl=en
> If you have a feature request or would like to report a problem,
> please email "[email protected]" rather than posting to the group.

-- 
You received this message because you are subscribed to the 
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/bbedit?hl=en
If you have a feature request or would like to report a problem, 
please email "[email protected]" rather than posting to the group.

Reply via email to