Emojis in URL fragment breaks navigation

Haveing the following Slide in my Presentation in RevealJS;

<section>
        <h1>Disclaimer</h1>
        <p class="fragment current-only">Cuztomized with ❤️</p>
</section>

Does not work and outputs the error:

Loading page http://localhost:3000 ...
Loading page finished with status: 200
Reveal JS plugin activated
Printing slide #/5      (6/6) ...not support cmap format:14

URIError: URI malformed

removing the emoji, everything works.

[JPtenBerge]

I’ve tried to pin down what’s causing the error. It doesn’t seem to be Puppeteer. It’s this line that causes the error:

const font = Font.create(buffer, { type: 'ttf', hinting: true });

To give a bit of context, here is a bit more code. It’s from decktape.js, starting at line 405.

// Consolidate duplicate fonts
function parseFont(fontObject) {
	const pdfStreamInput = cpyCxtParser.parseNewObject(fontObject.getObjectID());
	const fontDictionary = pdfStreamInput.toJSObject();
	
	// See "Introduction to Font Data Structures" from PDF specification
	if (fontDictionary.Subtype.value === 'Type0') {
	// TODO: properly support composite fonts with multiple descendants
	const descendant = cpyCxtParser
		    .parseNewObject(fontDictionary.DescendantFonts.toJSArray()[0].getObjectID())
		    .toJSObject();
	if (descendant.Subtype.value == 'CIDFontType2') {
		const descriptor = cpyCxtParser
		    .parseNewObject(descendant.FontDescriptor.getObjectID())
		    .toJSObject();
		const id = descriptor.FontFile2.getObjectID();
		const buffer = readStream(cpyCxtParser.parseNewObject(id));
		const font = Font.create(buffer, { type: 'ttf', hinting: true });

It’s this last line that gives the not support cmap format:14 error. I checked what’s in the font dictionary as well:

{
	BaseFont: PDFName { value: 'SegoeUIEmoji' },
	DescendantFonts: PDFArray {},
	Encoding: PDFName { value: 'Identity-H' },
	Subtype: PDFName { value: 'Type0' },
	ToUnicode: PDFIndirectObjectReference {},
	Type: PDFName { value: 'Font' }
}

Does the fonteditor-core library have trouble working with SegoeUIEmoji and is that why @gabyx solution with the EmojiOne font works? It’s all still a bit vague to me to be honest. I’m hoping someone (@astefanutti?) can shed some more light on this. Are there alternatives to fonteditor-core we might be able to use?

[astefanutti]

Thanks a lot for the input. I’m not entirely sure the not support cmap format:14 message is the cause of the URIError: URI malformed. I need to dig into it.

fonteditor-core was the most robust font parsing OSS library I could find a couple of years ago. It is possible to switch to another library if one exists that’s more robust.