Development Discussion Board

Personally I have no plans whatsoever. I do maintain the Noto fork but I have no plans for it either.

The only reliable emoji set that's on a public CDN is Twemoji and it uses a different naming scheme as the one used in s9e\TextFormatter. Switching to it would require some work.

odf wrote: Wed Nov 22, 2017 8:24 am Hi JoshyPHP s9e/highlighter looks great, I installed it on a board run by phpBB 3.2 and tried it but does not seem to work! What might be a problem?

Hundreds, maybe thousands of things. If you post a link to your board that will narrow the scope.

I'm considering forking either Twemoji or Noto with filenames that match Emojione for backward compatibility, but I need to check that it can be hosted by a free CDN such as cdnjs.

Twemoji
https://raw.githubusercontent.com/twitter/twemoji/gh-pages/2/72x72/1f600.png https://raw ...

we hit a brick wall because someone thinks this is too much work or whatever.


I'd like you to take a moment to ask yourself why you don't implement this feature, since you clearly want it. Even if you don't know PHP, it isn't a difficult language to learn. Could it be because it is too much ...

Context: in 3.1, it was possible to create two BBCodes using the same name; One without an attribute and the other with. This was presumably to handle polymorphic BBCodes such as [url] or [quote] . In 3.2.1, it is still possible to create two BBCodes in the ACP but only one of them will effectively ...

Rawgit could work. jsDelivr is an option, too. Does anybody here know about free CDNs?

The issue with Noto is that the gradients make them look mushy at low resolution. Try resizing them to 18 × 18, the size of emoji here. I'm waiting for the SVGs to become available to see if it's much better than the resized PNGs.

I've got to say that while I don't think Emojione is evil for changing their business model, the sudden change is a huge pain in my ass.

Mozilla's emoji are not actively maintained. As far as I know, the only two open source emoji sets being actively maintained are Twitter's Twemoji and Google's ...

That's incorrect. BBCode definitions and default templates are stored in PHP files and style templates in pseudo-HTML files but they could just as well be stored in the database like any other BBCode.

If you add too many BBCodes by default then you'll have another group of users asking for a way to delete them. There's no winning this.

The correct way to deal with it is to treat the default BBCodes the same way as custom BBCodes and add an option to add more BBCodes from a list of predefined ...