Dear Pierre,
Is there a good reason to bother the user with these declarations ? In what case the user may use ✠ and not wanting ✠ to be printed..?
To answer these questions, a little bit of understanding of how software works is necessary. TeX is, at its core, a layout engine. It has two inputs: - the font - the text and one output: - the PDF Suppose you type the text "abc", what TeX (or any layout engine like Word, LibreOffice, Adobe InDesign, etc.) does is basically just ask the font to render "abc", nothing else. If the font cannot render "abc" (because it doesn't have the character "a" in it), then there's just no output. TeX doesn't know how to render "abc" if no font defines them. It's like if you try to type "ཀ་ག་" (some tibetan characters) in Word and force the selection of the "Times New Roman" font, you'll get nothing, because the Times New Roman font doesn't contain tibetan glyphs. In the same way, if you ask for the rendering of ✠ by a font that doesn't contain it, then it won't work. That's as simple as that. Gregorio doesn't aim at being a superstructure above TeX that guesses what the users wants by mapping ✠ to the current font or, if the font doesn't have the glyph, to a fallback font. Gregorio is just a TeX style to typeset gregorian chant, what you're using is TeX, and TeX doesn't know how to render ✠ (nor any character) if it's not in the font you're using. Thank you, -- Elie _______________________________________________ Gregorio-users mailing list Gregorio-users@gna.org https://mail.gna.org/listinfo/gregorio-users
