On 8/9/2011 6:17 AM, Tim wrote: > On Mon, 2011-08-08 at 18:15 -0700, Paul Allen Newell wrote: >> assuming case-insensitivity > [...] > > > > Once you've set yourself a rule, it's easier to be consistent throughout > your site. Particularly if you put enough thought into it, ahead of > time, that you won't need to break it. > Tim: Over the decades I've certainly learned the value of rules. That being said, the rules evolve as I learn more and more. And then there are those which weren't thought out, such as case-sensitivity differences between Windows and Linux. I made the mistake of assuming that I'd never be migrating code between the two and was sloppy on Windows as I focused on dealing with 8.3 naming. Retrofitting, just like porting code, does have its few groans of "I missed that one". I do try to have rules which work globally for html, C++, Python, text, etc. rather than different rules for different uses. Obviously, can't do this all the time (and in some cases, rarely does it hold any time), but it strikes me better to first try to view top down. Yours is a good rule, though I accept the shift key as a fact of life (this letter is evidence of that; otherwise, capitalization would be lost). I prefer underbar to hyphen for space as hyphen is a legit character, but I can see that such is just a matter of personal choice. I've worked in enough places whose C++ coding standards are camelBack that it is second nature to me (I only started using it because I had to ... you are right about the problems with what can be created if camelBack is applied without a good proof-read). I wish the Chicago Manual of Style would weigh in on url name conventions (not to mention typography in code). Not that I'd agree with them, but it would be a good starting point. Thanks, Paul -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
