I probably should have done this a long time ago, ... in any case ... I changed some anchor tags on the BALUG web site. Most notably adding: http://www.balug.org/#Meetings-general http://www.balug.org/#Meetings-upcoming http://www.balug.org/#Install_Fests While retaining backwards compatibility respectively with: http://www.balug.org/#Meetings%20(general) http://www.balug.org/#Meetings%20(upcoming) http://www.balug.org/#Install%20Fests or the generally equivalent for those first two: http://www.balug.org/#Meetings%20%28general%29 http://www.balug.org/#Meetings%20%28upcoming%29

If you ever forget precisely what they are, the "primary" ones can be found linked from the links near the top of the web page, and of course inspecting the page source will reveal all of them.

Rationale: A) many email clients don't nicely parse URLs ending with ) in text, often taking the URL to end before the ); and substituting %29 for ) - which in most cases will then cause them to include it (and likewise %28 for () starts looking rather ugly. Likewise the space, which must be as %20, doesn't look as nice in email and the like. Also, I've seen some browsers which don't handle URL ending in ) vs. %29 the same(!) B) And no reason to break backwards compatibility, so the old anchors will also still work (at least no worse than they did before).

Do keep in mind that the text is case sensitive (this is generally the case on Linux and Unix-like operating systems - except for the DNS portion* of the URLs), and _ and - characters are distinct. So, these will also all work: http://wWw.BaLuG.oRg/#Meetings-general http://www.BALUG.org/#Meetings-upcoming http://WWW.balug.ORG/#Install_Fests But these won't: http://www.balug.org/#Meetings-General http://www.balug.org/#Meetings_upcoming http://www.balug.org/#Install-Fests

*that would be the domain part of the below: resource_type://[user[:password]@]domain[:port]/[filepathname][?query_string][#anchor] Where the portions within [] above are optional