From 9548274f3933e14e11bb105e9d52f07bf17f0a8b Mon Sep 17 00:00:00 2001 From: Richard Heck Date: Mon, 18 Mar 2013 18:56:38 -0400 Subject: [PATCH] I'm not absolutely sure about this, but it seems to me as if we need the master buffer here, too: in looking up fonts during XHTML output. I'm half tempted to pass the master buffer to these routines, though there are times, I think, when we want the actual buffer: e.g., when looking up branches. --- src/Paragraph.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Paragraph.cpp b/src/Paragraph.cpp index 8df7ab7026..e803ac5036 100644 --- a/src/Paragraph.cpp +++ b/src/Paragraph.cpp @@ -2861,7 +2861,7 @@ docstring Paragraph::simpleLyXHTMLOnePar(Buffer const & buf, if (isDeleted(i)) continue; - Font font = getFont(buf.params(), i, outerfont); + Font font = getFont(buf.masterBuffer()->params(), i, outerfont); // emphasis if (font_old.emph() != font.fontInfo().emph()) { @@ -2895,7 +2895,7 @@ docstring Paragraph::simpleLyXHTMLOnePar(Buffer const & buf, retval += inset->xhtml(xs, np); } } else { - char_type c = getUChar(buf.params(), i); + char_type c = getUChar(buf.masterBuffer()->params(), i); if (style.pass_thru || runparams.pass_thru) xs << c; -- 2.39.2