[Pmwiki-users] pmwiki.org converted to 2.0.devel27
John Rankin
john.rankin
Mon Nov 29 14:18:30 CST 2004
On Tuesday, 30 November 2004 4:12 AM, Patrick R. Michaud <pmichaud at pobox.com> wrote:
>> The markup
>> {text:text definition}
>> generates
>> <dfn title='text definition'>text</dfn>
>> Thus
>> {'^superscript^':'^superscript^'}
>> generates
>> <dfn title="'^superscript^'"><sup>superscript</sup><dfn>
>
>The use of a single colon as the significant character seems to invite
>markup conflicts -- i.e., does
> {mailto:pmichaud at pobox.com}
>become
> {<a href='mailto:pmichaud at pobox.com'>pmichaud at pobox.com</a>}
>or
> <dfn title='pmichaud at pobox.com'>mailto</dfn>
...
>
>Perhaps {:text:text definition} instead?
Or Scott's suggestion of {:text|text definition}
In either case, we have to be a bit careful with examples such as
{:[[http://www.pmwiki.org|pmwiki]]:[[http://www.pmwiki.org|pmwiki]]}
The code currently passes over anything in [[ ... ]] on the LHS.
>
...
>> And if you just write {text:text definition} ie with no leading
>> markup characters, it generates
>> <dfn title='text definition' class='definition'>text</dfn>
>> The definition class adds a border-bottom: 1px dotted; style.
>
>Correctly detecting leading markup characters might be a bit tricky,
>although I guess you could simply assume that anything not beginning
>with an alphanumeric (or quote?) is some sort of markup and so
>should use class='markup' instead of class='definition' in the
><dfn> tag.
Currently the code uses class='definition' if the text starts with
[[:alnum:]] and a plain <dfn> otherwise. One reason is that some
(most / all?) browsers display <dfn> as plain text, which is good
if one wants to see the markup effect, but not so good if it
really is a term definition.
>
>Pm
>
--
JR
--
John Rankin
More information about the pmwiki-users
mailing list