Yes, you can create links in the CB!
See What shortcuts can I use for linking to other information?
Escaped HTML such as & or — will print differently depending on whether you are sending a public message or a private message. In public messages, the escaped HTML will be printed "as is". Private messages do accept
escaped HTML though.
The chatterbox attempts to parse things that look like HTML tags, and it generally does a pretty good job. If text surrounded by angle brackets looks like an HTML tag, the chatterbox will either:
If the angle-enclosed text does not look like HTML, then the chatterbox leaves the text as you wrote it, except that the angle brackets themselves are converted to numeric entities, so that they render correctly in people's browsers.
- leave it in the text stream, if it is allowed HTML;
- remove it, if it is "unallowed"/pseudo HTML; or
- replace it with something appropriate.
Cases like these (allowed HTML or clearly not HTML) are rendered as expected:
Cases like these (unallowed/pseudo HTML) are stripped from the text stream:
- <i><a href="http://www.perl.org/">Perl</a></i> prints Perl in the chatterbox
- if ( $a < $b && $c > $d ) ... - is rendered as shown
Because square brackets are used in the Everything code for easy linking between pages, you cannot use them to enclose anything you don't want linked. They may be used separately
or inside out, however.
who would ever use ][ in the chatterbox?
[login] prints login
As a quick work around you can type [ and
this will fool the chatterbox into creating a link to a
node called [ so $arr[0] becomes
Other Special Characters
All other special characters may be typed as is. (Unicode??)
When you type code in the chatterbox, you should normally enclose it in
<code> tags. This prevents the CB from possibly interpreting and changing your code. For example,
if you want to type the following code:
and you don't put it in <code> tags, it will come out looking like this:
Even more drastic things can happen if your code contains angle brackets!
Back to the PerlMonks FAQ