Because having a single way of parsing/replacing is too easy

[Lorne Kates]

http://i.imgur.com/qUh5qUj.png

[ben_lubar]

@Lorne-Kates said in Because having a single way of parsing/replacing is too easy:

That's intentional.

[El_Heffe]

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@Lorne-Kates said in Because having a single way of parsing/replacing is too easy:

That's intentional.

And the intention is . . . ?

[ben_lubar]

@El_Heffe said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@Lorne-Kates said in Because having a single way of parsing/replacing is too easy:

That's intentional.

And the intention is . . . ?

That is says :‌belt_onion:

[El_Heffe]

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@El_Heffe said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@Lorne-Kates said in Because having a single way of parsing/replacing is too easy:

That's intentional.

And the intention is . . . ?

That is says :‌belt_onion:

Why? Why not display ?

[djls45]

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@Lorne-Kates said in Because having a single way of parsing/replacing is too easy:

That's intentional.

Do the double-square-bracket placeholder forms and emojis get replaced using the same piece of code? Why can't they be separated?

[ben_lubar]

@djls45 said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@Lorne-Kates said in Because having a single way of parsing/replacing is too easy:

That's intentional.

Do the double-square-bracket placeholder forms and emojis get replaced using the same piece of code? Why can't they be separated?

Emojis were never replaced in badges. Just like they're not replaced in titles.

[djls45]

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

Just like they're not replaced in titles.

That's recent, though, isn't it? There's a number of threads around here that have several emojis in the titles that were replaced before the [[things-and-stuff]] fiasco.

[ben_lubar]

@djls45 said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

Just like they're not replaced in titles.

That's recent, though, isn't it? There's a number of threads around here that have several emojis in the titles that were replaced before the [[things-and-stuff]] fiasco.

Unicode emoji or colon-fake-emoji?

[djls45]

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

Just like they're not replaced in titles.

That's recent, though, isn't it? There's a number of threads around here that have several emojis in the titles that were replaced before the [[things-and-stuff]] fiasco.

Unicode emoji or colon-fake-emoji?

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

It does get replaced within quotes:

[ben_lubar]

@djls45 said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

@ben_lubar said in Because having a single way of parsing/replacing is too easy:

Just like they're not replaced in titles.

That's recent, though, isn't it? There's a number of threads around here that have several emojis in the titles that were replaced before the [[things-and-stuff]] fiasco.

Unicode emoji or colon-fake-emoji?

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

It does get replaced within quotes:

Maybe on ?

[RaceProUK]

@djls45 said in Because having a single way of parsing/replacing is too easy:

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

The only rendered emoji in topic titles are raw emoji; the :emoji: type has never been parsed in titles in NobeDD.

[sloosecannon]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

The only rendered emoji in topic titles are raw emoji; the :emoji: type has never been parsed in titles in NobeDD.

They have, however, been parsed in Discourse.

Also, in post text. Hence why it rendered as

Climate change

Honestly, not sure what the is here. Would you rather have

all
format capabilities in

• group title text
• because that would be tr

[djls45]

@sloosecannon said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

The only rendered emoji in topic titles are raw emoji; the :emoji: type has never been parsed in titles in NobeDD.

They have, however, been parsed in Discourse.

Also, in post text. Hence why it rendered as

Climate change

Honestly, not sure what the is here. Would you rather have

all
format capabilities in

• group title text
• because that would be tr

I don't think we need all the formatting capabilities applied to titles -- just the :emoji: replacements.

[accalia]

@djls45 said in Because having a single way of parsing/replacing is too easy:

@sloosecannon said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

The only rendered emoji in topic titles are raw emoji; the :emoji: type has never been parsed in titles in NobeDD.

They have, however, been parsed in Discourse.

Also, in post text. Hence why it rendered as

Climate change

Honestly, not sure what the is here. Would you rather have

all
format capabilities in

• group title text
• because that would be tr

I don't think we need all the formatting capabilities applied to titles -- just the :emoji: replacements.

workaround: Use Unicode like the goddess intended. that works just fine.

[RaceProUK]

@accalia said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

@sloosecannon said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

The only rendered emoji in topic titles are raw emoji; the :emoji: type has never been parsed in titles in NobeDD.

They have, however, been parsed in Discourse.

Also, in post text. Hence why it rendered as

Climate change

Honestly, not sure what the is here. Would you rather have

all
format capabilities in

• group title text
• because that would be tr

I don't think we need all the formatting capabilities applied to titles -- just the :emoji: replacements.

workaround: Use Unicode like the goddess intended. that works just fine.

A good idea in theory, but without OS-level support for entering them easily, it's left to either copypasta or keyboards with 62985698307538495972380 keys :P

[accalia]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

@sloosecannon said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@djls45 said in Because having a single way of parsing/replacing is too easy:

I'm pretty sure these used to be replaced:

Or am I remembering wrong?

The only rendered emoji in topic titles are raw emoji; the :emoji: type has never been parsed in titles in NobeDD.

They have, however, been parsed in Discourse.

Also, in post text. Hence why it rendered as

Climate change

Honestly, not sure what the is here. Would you rather have

all
format capabilities in

• group title text
• because that would be tr

I don't think we need all the formatting capabilities applied to titles -- just the :emoji: replacements.

workaround: Use Unicode like the goddess intended. that works just fine.

A good idea in theory, but without OS-level support for entering them easily, it's left to either copypasta or keyboards with 62985698307538495972380 keys :P

this is what i can only describe as...... a good problem to have.😜

🐱‍👤🐱‍👤🎂🐱‍💻

⚕☮

🍕🥞💇

[RaceProUK]

@accalia said in Because having a single way of parsing/replacing is too easy:

⚕

Even zoomed in, I can't work out what that's meant to be

Edit: OK, so I can just use Wiktionary

⚕ - Wiktionary, the free dictionary

[accalia]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia said in Because having a single way of parsing/replacing is too easy:

⚕

Even zoomed in, I can't work out what that's meant to be

👧📍🏁

[RaceProUK]

@accalia I'm afraid I don't speak emoji

[anotherusername]

@djls45 The topics that have emoji in the title are using Unicode emoji characters (🎤👂💩📧📷🔗🔥🔥😻🚘). The forum emoji replacements don't work there.

[accalia]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia I'm afraid I don't speak emoji

👧📍🏁

[anotherusername]

@RaceProUK Looks like the medical symbol. And I'm not even zoomed in... in fact, the blockquote made it smaller.

[RaceProUK]

@accalia said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia I'm afraid I don't speak emoji

👧📍🏁

Thanks. Can you translate this too please?

@accalia said in Because having a single way of parsing/replacing is too easy:

🐱‍👤🐱‍👤🎂🐱‍💻
⚕☮
🍕🥞💇

[accalia]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia I'm afraid I don't speak emoji

👧📍🏁

Thanks. Can you translate this too please?

@accalia said in Because having a single way of parsing/replacing is too easy:

🐱‍👤🐱‍👤🎂🐱‍💻
⚕☮
🍕🥞💇

🙅

[anotherusername]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia said in Because having a single way of parsing/replacing is too easy:

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia I'm afraid I don't speak emoji

👧📍🏁

Thanks. Can you translate this too please?

@accalia said in Because having a single way of parsing/replacing is too easy:

🐱‍👤🐱‍👤🎂🐱‍💻
⚕☮
🍕🥞💇

Cat adult plus cat adult resulted in birth of cat. Google.
All cats fixed. Peaceful now.
The woman can enjoy pizza, pancakes, and go get her hair cut without having to worry about kittens.

[boomzilla]

@accalia said in Because having a single way of parsing/replacing is too easy:

⚕

Looks like .

[accalia]

@boomzilla said in Because having a single way of parsing/replacing is too easy:

@accalia said in Because having a single way of parsing/replacing is too easy:

⚕

Looks like .

this may or may not have been intentional.

also it was an excuse to play with the emoji keyboard built into windows 10's OSK

[Lorne Kates]

@accalia said in Because having a single way of parsing/replacing is too easy:

👧📍🏁

No YOU lick MY lollipop until I finish.

[Arantor]

@accalia Win10 has an emoji keyboard?

[masonwheeler]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

A good idea in theory, but without OS-level support for entering them easily, it's left to either copypasta or keyboards with 62985698307538495972380 keys :P

Real Life Emoji Keyboard! – 02:13
— Tom Scott

???

[El_Heffe]

@anotherusername said in Because having a single way of parsing/replacing is too easy:

@djls45 The topics that have emoji in the title are using Unicode emoji characters The forum emoji replacements don't work there.

I think that was the point @Lorne-Kates was making. There should just be one parse/replace routine that applies to everything.

If you type :belt_onion: you should get no matter where it is. It doesn't really make sense to parse/replace in some areas but not others.

[accalia]

@Arantor said in Because having a single way of parsing/replacing is too easy:

@accalia Win10 has an emoji keyboard?

sure does.

it's right there next to your task bar in windows 10

click that and up pops a keyboard on your screen.

click the smiley face and......

BAM!

if you don't see the keyboard icon (and you probably don't as it doesn't automatically appear unless you have a touch input) simply right click on the task bar and check the option Show touch keyboard button

that will add the button to the taskbar. wait ten seconds or so for all the stuff behind the scenes to start running and you're set.

enjoy.

[RaceProUK]

@accalia And the best part is, the OSK covers the composer so you can't see what you're typing! 👌

[Arantor]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia And the best part is, the OSK covers the composer so you can't see what you're typing! 👌

Desktop and mobile are the same then!

[RaceProUK]

@Arantor , on desktop, the keyboard can be undocked from the bottom of the screen, and then it can be dragged where you like

[accalia]

@RaceProUK said in Because having a single way of parsing/replacing is too easy:

@accalia And the best part is, the OSK covers the composer so you can't see what you're typing! 👌

E_NO_REPRODUCE

😝

[JBert]

@accalia said in Because having a single way of parsing/replacing is too easy:

🐱‍👤🐱‍👤🎂🐱‍💻

⚕☮

🍕🥞💇

---

@anotherusername said in Because having a single way of parsing/replacing is too easy:

Cat adult plus cat adult resulted in birth of cat. Google.
All cats fixed. Peaceful now.
The woman can enjoy pizza, pancakes, and go get her hair cut without having to worry about kittens.

Is it possible that your browser does not support this emoji combination?

🐱‍👤 Ninja Cat Emoji

A cat that is also a ninja. Used as an unofficial mascot by Microsoft, and was available in the Segoe Color Emoji font included with Windows...

The Ninja Cat emoji is a sequence of the Cat Face and Bust in Silhouette emojis. These are combined using a zero width joiner between each character and display as a single emoji on supported platforms.

As if emojis weren't enough of a ...

[JBert]

But wait, there's more!

Apparently they're discussing to add new emoji combinations for the planets of the solar system, global warming, curly hair, gender neutral versions and even redheads.

[anotherusername]

@JBert You tell me...

[boomzilla]

@JBert said in Because having a single way of parsing/replacing is too easy:

redheads

Oh...then all is forgiven.