| Re: browser url with #... [message #173235 is a reply to message #173233] |
Mon, 28 March 2011 22:03  |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 3/28/2011 5:00 PM, Twayne wrote:
> In news:2516140(dot)VqM8IeB0Os(at)PointedEars(dot)de,
> Thomas 'PointedEars' Lahn<PointedEars(at)web(dot)de> typed:
>> Jerry Stuckle wrote:
>>
>>> Thomas 'PointedEars' Lahn wrote:
>>>> Twayne wrote:
>
> ....
>
>>
>> "Twayne" has a misconception about what a bookmark is,
>> and so have you.
>
> Actually, I have no misconceptions at all. In two of the particular programs
> I use, they call the "#" to be a bookmark regardless of how it's used, and
> to create such a link, the menu item is to Insert; Bookmark. A LOT of
> wysiwyg programs use the same terminology. Thus, if an external site lets
> you know where there is a "bookmark" (and that's what they call it on those
> sites), you can send a surfer right to the "bookmarked" location within the
> file using the "#" sign.
>
> Rather than concentrate on the question that was asked, you decided to
> debate the labelling for an octothorpe in this context. So, a sensibe answer
> might have been that, more technically, it's called ... in order to be most
> accurate.
>
>>
>
> ...
>
>> "Twayne" is missing the point because the reason for the
>> OP's problem is not that a "bookmark" (in that wrong
>> sense) cannot be found, but because the fragment
>> identifier is not part of the *request* URI (as we have
>> already discussed).
>
> No - if the "#", or bookmark, or misnomered "fragment identifier" as you
> prefer, as far as I'm concerned, I like to use the clearest acceptable
> language possible. You on the other hand appear as though rather than adding
> information, you want to dismiss perfectly good information and restate the
> very same thing in more technical language that a LOT few people will
> understand.
It is commonly used by web developers to identify a position within a
page - a "bookmark". This is different from the bookmark saved in your
web browser.
>>
>>> And I know I'm not quoting like YOU want.
>>
>> The quoting style I am *asking* (you) *for* is not
> ...
> The quoting style you felt it necessary to mention did no harm to the post;
> it was quite clear what was response and what wasn't. Your comment there was
> totally uncalled for but if you just had to say something, why couldn't you
> take what appears to be a newbie under your wing and politely try to help
> them? You're a lousy poster and I imagine just as irritating to those around
> you as you try to be here.
>
> Oh, and why the nick change?
And there was no nick change.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]