The work QC is "Essential Blogging". This is QC2, the second quality check. But I think we may need a third--there are still problems like a zillion URLs ending in a / that shouldn't. (e.g., http://www.foo.com/example.html/) Gnash.
A QC is a quality control check. After an author turns in their final draft, it's converted to a publishing format (XML or Frame) and copyedited and line-broken. The result is sent out to authors and editor for checking--this is QC1. Then it's page broken, indexed, and sent out for QC2. QC2 is only a week or so before it goes to the printer.
So now I'm going through PDFs searching for "http://" and pointing out buggered URLs. Lucky me!
--Nat
Bad URLs (Score:1)
That's gotta be my #1 pet peeve of URLs anywhere.
--
xoa
Pet peeve (Score:2)
I second that. :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
I disagree (Score:1)
http://www.petdance.com/index.html
If you know that the web server is going to server up index.html and that's the file you are interested in referencing, I can see no bothering other people with the filename. However, the copyeditors at ORA have no clue about web server configurations. For instance, I frequently have index.pl files in the DocumentIndex list. Sometimes I'll have both an index.html and an index.pl (one of them is probably out of date). I guess I'm happy enough with the explicit filenames as
Re:I disagree (Score:1)
As to having index.html and index.pl in the same directory, that's the whole point of NOT specifying a file. Say you started with foo.com/dir/index.html, and now you realize you need some dynamic stuff. Now you have to point at foo.com/dir/index.pl. If you'd just started with foo.com/dir/, then the index.html to index.pl transformation could have hap
--
xoa