Re: [boost] spaces in URIs

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-10-09 09:59:08

Beman Dawes wrote:
> At 08:43 PM 10/8/2002, David Abrahams wrote:
> 
>  >> Applying the fix to both files results in links with are both valid,
>  >> in the sense of meeting specs, and working, in the sense that browsers
>  >> can use them as intended. One without the other isn't helpful.
>  >
>  >Yes, but if other pages are linked to that page, I've broken
>  >them. That's why I was trying to grep for all instances of spaces in
>  >URIs. When I failed at that, I gave up.
> 
> Could any of the regex experts help us out?  As Dave says, what we need 
> is a regular expression that will detect that a URL has a space in it.

After several attempts, I've come with

     grep "href=\"[^\" ]* .*\"" `find ~/Work/boost -name "*.htm"`

which seems to work, producing the attached list.

- Volodya


/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>Where is located the latest version of the Boost Test Library?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>I found a bug. Where could I report it?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>I have a request for a new feature. Where could I ask for it?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>How to create test case?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>How to create test suite?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>Why did I get a linker error when compiling my test program?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>How could I redirect testing output?</LI>
/home/ghost/Work/boost/libs/test/doc/faq.htm:    <LI>I want different default log trace level</LI>
/home/ghost/Work/boost/libs/test/doc/output_test_stream.htm:    The pattern file name is specified in the class output_test_stream constructor. 
/home/ghost/Work/boost/libs/test/doc/output_test_stream.htm:    If second argument of the class output_test_stream constructor 
/home/ghost/Work/boost/libs/test/doc/index.htm:          Open Issues<BR>
/home/ghost/Work/boost/libs/timer/timer.htm:      <td>timer</td>
/home/ghost/Work/boost/libs/timer/timer.htm:      <td>progress_timer</td>
/home/ghost/Work/boost/libs/timer/timer.htm:      <td>progress_display</td>
/home/ghost/Work/boost/libs/timer/timer.htm:class progress_timer : public timer, noncopyable  {
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			enforcement of semantics (by being <a href="../utility/utility.htm#class noncopyable">
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			current scope. Because it is noncopyable, 
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			to. <b>T</b> must meet the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:  template&lt;typename T&gt; class scoped_ptr : noncopyable {
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			a complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">common 
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			pointer common requirements.</P>
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			not throw exceptions. See the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			pointer common requirements.</p>
/home/ghost/Work/boost/libs/smart_ptr/scoped_ptr.htm:			complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">common 
/home/ghost/Work/boost/libs/smart_ptr/smart_ptr.htm:			the common requirements) is <b>std::bad_alloc</b>, 
/home/ghost/Work/boost/libs/smart_ptr/smart_ptr.htm:			throwing exceptions by the common requirements.</p>
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:			to. <b>T</b> must meet the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:			<P><B>Notes:</B> <B>T</B> need not be a complete type. See the smart pointer <A href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:			<P><B>Notes:</B> <B>T</B> need not be a complete type. See the smart pointer <A href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:				be a complete type. See the smart pointer <A href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:				<B>T</B> need not be a complete type. See the smart pointer <A href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:			<P><B>Notes:</B> <B>T</B> need not be a complete type. See the smart pointer <A href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:			<P><B>Notes:</B> <B>T</B> need not be a complete type. See the smart pointer <A href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/weak_ptr.htm:				pointer common requirements.</P>
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			to. <b>T</b> must meet the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			pointer common requirements.</p>
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			pointer common requirements.</p>
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			pointer common requirements.</p>
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			stored pointer. <b>T</b> need not be a complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">common 
/home/ghost/Work/boost/libs/smart_ptr/shared_array.htm:			complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">common 
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			enforcement of semantics (by being <a href="../utility/utility.htm#class noncopyable">
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			current scope. Because it is noncopyable, 
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			to. <b>T</b> must meet the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			required be a complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			destructors do not throw exceptions. See the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			destructors do not throw exceptions. See the smart pointer <a href="smart_ptr.htm#Common requirements">
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			pointer common requirements.</p>
/home/ghost/Work/boost/libs/smart_ptr/scoped_array.htm:			complete type. See the smart pointer <a href="smart_ptr.htm#Common requirements">common 
/home/ghost/Work/boost/libs/filesystem/doc/faq.htm:toolkit functions.&nbsp; See Failed Attempts.</p>
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:Class path<br>
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:Non-member functions</p>
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:    const path operator<< ( const char * lhs, const path &amp; rhs );
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:    const path operator<< ( const std::string &amp; lhs, const path &amp; rhs );
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:    <i>// Also see </i>Undocumented non-member functions<i> below</i>
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:  <p><b>Note:</b> Also see non-member operator<< functions.</p>
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:<p><b>See:</b> Representation example 
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:system-specific representation of 
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:<p><b>See:</b> Representation example 
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:system-specific representation of 
/home/ghost/Work/boost/libs/filesystem/doc/path.htm:<p><b>See:</b> Representation example 
/home/ghost/Work/boost/libs/filesystem/doc/design.htm:Abandoned Designs<br>
/home/ghost/Work/boost/libs/filesystem/doc/design.htm:FAQ.</p>
/home/ghost/Work/boost/libs/filesystem/doc/index.htm:<p>Class directory_iterator 
/home/ghost/Work/boost/libs/filesystem/doc/index.htm:by directory path.</p>
/home/ghost/Work/boost/libs/filesystem/doc/index.htm:directory path information to indicate the file or 
/home/ghost/Work/boost/libs/filesystem/doc/operations.htm:Class directory_iterator<br>
/home/ghost/Work/boost/libs/filesystem/doc/operations.htm:&nbsp;&nbsp;&nbsp; Other functions<br>
/home/ghost/Work/boost/libs/filesystem/doc/operations.htm:Non-member functions<br>
/home/ghost/Work/boost/libs/filesystem/doc/operations.htm:    class directory_iterator
/home/ghost/Work/boost/libs/filesystem/doc/operations.htm:      // other functions
/home/ghost/Work/boost/libs/filesystem/doc/operations.htm:Naming Rationale.</p>
/home/ghost/Work/boost/libs/utility/utility.htm:  <li>Function templates next() and prior()</li>
/home/ghost/Work/boost/libs/utility/utility.htm:  <li>Class noncopyable</li>
/home/ghost/Work/boost/more/feature_model_diagrams.htm:<p>In their seminal book, Generative Programming, Czarnecki and Eisenecker (C&E)
/home/ghost/Work/boost/more/feature_model_diagrams.htm:Feature Description.</p>
/home/ghost/Work/boost/more/formal_review_process.htm:Notes for Review Managers<br>
/home/ghost/Work/boost/more/formal_review_process.htm:<p>The final &quot;accept&quot; or &quot;reject&quot; decision is made by the <a href="#Review Manager">
/home/ghost/Work/boost/more/submission_process.htm:  <li>Web site posting.</li>
/home/ghost/Work/boost/more/submission_process.htm:<p>Subscribe to the mailing list for a
/home/ghost/Work/boost/more/submission_process.htm:boost.org web site.&nbsp; The closer the submission file mirrors the final <a href="lib_guide.htm#Directory structure">directory
/home/ghost/Work/boost/more/lib_guide.htm:&nbsp;&nbsp;&nbsp; Design and programming<br>
/home/ghost/Work/boost/more/lib_guide.htm:&nbsp;&nbsp;&nbsp; <a href="#Design and Programming">Directory structure and 
/home/ghost/Work/boost/more/lib_guide.htm:&nbsp;&nbsp;&nbsp; Naming consistency<br>
/home/ghost/Work/boost/more/lib_guide.htm:&nbsp;&nbsp;&nbsp; Source code fonts rationale<br>
/home/ghost/Work/boost/more/lib_guide.htm:&nbsp;&nbsp;&nbsp; Rationale rationale<br>
/home/ghost/Work/boost/more/lib_guide.htm:    <li>Design and Programming</li>
/home/ghost/Work/boost/more/lib_guide.htm:    <li>Directory Structure</li>
/home/ghost/Work/boost/more/lib_guide.htm:    policy</a>. See Naming consistency.</li>
/home/ghost/Work/boost/more/lib_guide.htm:      <li>Use fixed-width fonts.&nbsp; See fonts rationale.</li>
/home/ghost/Work/boost/more/lib_guide.htm:    the particular library. See Naming consistency. The primary directory may have sub-directories.</li>
/home/ghost/Work/boost/more/header.htm:    with macro names from other's code.&nbsp; The <a href="#Sample header">sample
/home/ghost/Work/boost/more/header.htm:    directives.&nbsp; Thus the header sample header&nbsp;
/home/ghost/Work/boost/more/header.htm:<p>The alert reader will have noticed that the <a href="#Sample header">sample
/home/ghost/Work/boost/more/test_policy.htm:<p>Boost uses an automatic  regression test suite which generates HTML <a href="../status/compiler_status.html#Compiler Status Tables">compiler
/home/ghost/Work/boost/index.htm:      &#149;&nbsp;Commercial Support<br>