From nobody@nowhere Sun Jun 17 06:59:19 2007 Replied: Wed, 12 Apr 95 22:09:27 -0400 Replied: Paul Coddington Received: from oldnova.npac.syr.edu by spica.npac.syr.edu (4.1/I-1.98K) id AA12612; Mon, 10 Apr 95 19:29:41 EDT Received: by oldnova.npac.syr.edu (4.1/N-0.12) id AA00950; Mon, 10 Apr 95 19:29:40 EDT Date: Mon, 10 Apr 1995 19:29:39 -0400 (EDT) From: Paul Coddington Subject: alias program To: Geoffrey Fox Cc: webmaster@oldnova.npac.syr.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have finally made an HTML aliasing program (using a lot of code written by Geoffrey) that seems to work (as usual, it took longer than expected). You can call it by ~paulc/bin/htmlalias my_file_name Here is what it does... Reads in all the aliases and associated URLs and document titles from the alias file. Copies my_file_name to my_file_name.alias (to make sure you keep a copy of the original) Edits my_file_name to replace the aliases, printing a list of aliases it finds to STDOUT. It replaces aliases of the form {alias}(hypertext bluewords) by hypertext bluewords {alias}() by document title for this alias {alias} not followed by any round brackets by {alias} # if the alias is not in the alias list ULR_for_this_alias !alias # if the alias is in the alias list (this is supposed to make !alias a comment - not sure if it works for all browsers) The idea behind this is that you can have embedded aliases, e.g. for images, such as Let me know if you have any problems. Paul From nobody@nowhere Sun Jun 17 06:59:19 2007 Received: from oldnova.npac.syr.edu by spica.npac.syr.edu (4.1/I-1.98K) id AA24142; Tue, 11 Apr 95 17:24:19 EDT Received: by oldnova.npac.syr.edu (4.1/N-0.12) id AA11833; Tue, 11 Apr 95 17:24:18 EDT Date: Tue, 11 Apr 1995 17:24:18 -0400 (EDT) From: Paul Coddington Subject: Re: As discussed Format for Aliases To: gcf@npac.syr.edu In-Reply-To: <9504060153.AA02573@nova.npac.syr.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 5 Apr 1995 gcf@oldnova.npac.syr.edu wrote: > Comments? There was only one thing I didn't like in your suggestions and that was > can write {INFOURL}{PCWchap1}(Introduction) where PCWchap1 is > relative address of PCW I think this is too complicated. I much prefering sticking to simpler {PCWchap1}(Introduction) format where {PCWchap1} can however be aliased to {PCW}/node_whatever.html and {PCW} aliased to {infomall}/npac/pcw From nobody@nowhere Sun Jun 17 06:59:19 2007 Replied: Thu, 11 May 95 20:18:58 -0400 Replied: Paul Coddington Received: from oldnova.npac.syr.edu by spica.npac.syr.edu (4.1/I-1.98K) id AA06082; Wed, 12 Apr 95 23:27:10 EDT Received: by oldnova.npac.syr.edu (4.1/N-0.12) id AA28231; Wed, 12 Apr 95 23:27:09 EDT Date: Wed, 12 Apr 1995 23:27:09 -0400 (EDT) From: Paul Coddington Subject: Re: alias program To: gcf@oldnova.npac.syr.edu In-Reply-To: <9504130209.AA27643@oldnova.npac.syr.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII OK, I can easily add that to the entry form. On Wed, 12 Apr 1995 gcf@oldnova.npac.syr.edu wrote: > Maybe its overkill but I did think that capturing more info > when alias formed could help management in long run > so syntax could be > alias@url@title@comment you dont want in blue words@authors intials@date entered