in reply to Re: RFC: Entity names for square brackets.
in thread RFC: Entity names for square brackets.

Cough*MathXML*Cough. Requires browser support, but is a much cleaner way to go.

Also, there's no need for HTML-escapes for {}; they aren't metachars in Everything. [ and ] are only needed because they're metachars in Everything-text and not HTML. HTML should provide HTML-escapes for everything else that can't be typed directly on a standard US 101-key QUERTY -- if not, it's not considered common enough.

In other words, it isn't Everything's job to make up for (percived) problems in HTML that it didn't cause.

Confession: It does an Immortal Body good.

  • Comment on Re: Re: RFC: Entity names for square brackets.

Replies are listed 'Best First'.
Re: Re: Re: RFC: Entity names for square brackets.
by mattr (Curate) on Jul 21, 2002 at 08:26 UTC
    Natch, you're right. Though I don't carry an entity table in my head (for a current project I am wondering how for example to display, and better yet input, an Old English "OE" character used in a wine product name). So I still would like a curly entity so I don't have to carry that extra info in my head.. oops too late.

    To follow up, HTML can do images, how come PM (/ Everything?) can't I wonder. The phrase a picture is worth a thousand words may be true if we use compressed formats.

[reply]

      It's generaly easy to find HTML entity names; do a google search for HTML entity OE or suchlike. (You don't even have to clickthrough for this one; Œ is Œ, as you can see reading the snippet of the first hit.) (BTW, for input you should support UTF-8 chars 338 and 339 (AKA /\x{152}/i), as well as /oe/i. The info on codepoints is in that same table, if you remember that the &#nnn; syntax uses decimal nnn.

      Oh, and PM/Everything can pass-through any tag it's told to; it's being told not to passthrough <img> tags. I rather wonder why. I suppose there is a worry people will put <img> tags pointing to porn or other things undeseriable here. (On homenodes, it will allow them IFF the users's level supports homenode images, IIRC.)

      Update: I almost forgot: when do you need an entity for curlies? They aren't metachars in HTML nor Everything.

      Confession: It does an Immortal Body good.

[reply]
[d/l]
        Thank you! Very good info. No need for curly entities anymore since now I've memorized that they don't need 'em.

        I will certainly study this table and thak you for the info on UTF-8.

        I'm building a database for a wine merchant and I'm worrying about how to search/input accented characters and the OE. There are problems with Japanese keyboards and fonts for this, so I am thinking about converting OE to the entity on display, but to ignore accents when searching. Of course I'm probably going to write Word/PDF so that's a different story maybe.

        About the <img> tag, yes the danger of porn uploads is obvious but seriously we could make very good use of diagrams, and we often talk about diagramming, so I would think that if l33t porn jokes is the danger then it should be connected to level privileges. Perhaps there is a security or diskspace/bandwidth problem with uploads, but I'm going to think about putting images on my server to go along with posts, if necessary to the discussion. Can't think of one now, though it might have been useful recently talking about Quantum:: in Ovid's thread.

[reply]

In Section Perl Monks Discussion