in reply to Re^6: Larger profile pic than 80KB?
in thread Larger profile pic than 80KB?

Which I think is pretty lame

I really like it for the inventive way you made it pure pictorial via the ok hand for the letter k and the teapot for the letter t.

Googling for "ott" revealed that Ol Chiki script contains a letter with the name ott ... and it's shaped like a camel hump! ... leading to:

👌🇨 ᱴ

To make it pure pictorial we might try:

👌🌊🐪 

👁️🍾👍🦟

Replies are listed 'Best First'.
Re^8: Larger profile pic than 80KB?
by kcott (Archbishop) on Oct 23, 2023 at 14:08 UTC

    ++ Very inventive!

    At first glance, I thought the middle character was a shrimp (jumping out of the water). This led to my initial attempt at a translation:

    "OK, don't come the raw prawn with me, Perl!"

    After some research:

    • 🦐 U+1F990 SHRIMP
    • 🌊 U+1F30A WATER WAVE

    Another thought was the minimalistic Unicode (but not emoji) replacement of the current Ken with Kensp; — but that would just look like:

    — K 

    and the cleverness would be lost in the rendering.

    Post-preview footnote: Although HTML5 allows named character references without a leading ampersand, it would appear that PM does not. The markup "Kensp;" renders here as "Kensp;". I needed to change that to "K " to get the "K " you see above. Further loss of cleverness. :-(

    — Ken

[reply]
[d/l]
[select]
      Although HTML5 allows named character references without a leading ampersand

      Are you completely sure about that? I don't see how it would work in practice as there are enough genuine words in many languages which might precede a semi-colon and then would be ambiguous, eg. baring; would get parsed into bå which would be surprising to say the least.

      🦛

[reply]
[d/l]
        "Are you completely sure about that?"

        Well I was: I argued the same as you when I first encountered it. I even recall giving a similar example where it would fail.

        However, looking into it a bit further, I find (in "HTML Living Standard: 13.1.4 Character references"):

        "Character references must start with a U+0026 AMPERSAND character (&)."

        So, you're right and I'm wrong for the current iteration of the (perpetual WIP) HTML5 standard. I dislike these so-called "living documents" for this very reason. Anyway, thanks for prompting me to re-research this. ++

        — Ken

[reply]

        This an update to my previous reply, two days ago.

        It occurs to me that what I had seen was a required, leading ampersand and an optional, trailing semicolon.

        I suspect the lack of ampersands in the very long list of "HTML Living Standard: 13.5 Named character references" threw me. I see the Note there mentions "... some appear both with and without the trailing semicolon ...".

        I always include both the ampersand and semicolon. The one exception is in the post above where I was trying to be clever and failed miserably. :-(

        Again, thanks for pointing this out.

        — Ken

[reply]

In Section Perl Monks Discussion