> if it’s about easier maintenance or nicer code, you might do something like
> this:
>
> %%
> \version "2.19.47"
> computer-modern = ##f
> flqq = #(if computer-modern #{ \markup { \char #"#xF101" } #} "»")
> \markup \flqq
> %%
Nice one, thanks!
Actually, in my specific case, I’
On 29.08.2016 23:26, Erik Ronström wrote:
I found another workaround: even though the glyph variants share the same
codepoint in the font, the alternative glyphs are actually defined in the
unicode ”Private Use Area”, so they also have codepoints of their own. So I
just replaced all » characte
> On 29 Aug 2016, at 23:26, Erik Ronström wrote:
>
> I found another workaround: even though the glyph variants share the same
> codepoint in the font, the alternative glyphs are actually defined in the
> unicode ”Private Use Area”, so they also have codepoints of their own. So I
> just repla
I found another workaround: even though the glyph variants share the same
codepoint in the font, the alternative glyphs are actually defined in the
unicode ”Private Use Area”, so they also have codepoints of their own. So I
just replaced all » characters in the lilypond source with the unicode
> On 29 Aug 2016, at 22:02, Erik Ronström wrote:
> I’m using Computer Modern in my score to match the surrounding text (set in
> LaTeX). However, I discovered that the french quotes (guillemet) display
> differently in the lyrics, compared to the TeX text (see attached image).
There is LuaLaT
