what about editing a node? will the user editing the node
see their original shortcut link, or will they see the
expanded link?
if you can't easily edit these links afterward, then
their value is not as great. on the other hand, i doubt that
the expense of generating real links on-the-fly or storing
two copies of the node text (source and expanded) are worth
it either.
i think that having these sort of links go to a separate
page that lists the full link and perhaps redirects after
5 to 10 seconds would be the most maintainable
implementation.
that way, the author can simply edit the original text,
the user will have a chance to see what resource their being
sent to (and a chance to cancel), and it can be forward and
backward compatible (as long as there's no links with titles
matching /^(?:(RFC):(\d+)|(CPAN):(\w+(?:::\w+)*))$/ ).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.