if (tmpinset)
to.insertInset(j, tmpinset, tmpfont, change);
} else {
- if (!to.checkInsertChar(tmpfont))
- return false;
to.insertChar(j, tmpchar, tmpfont, change);
}
return true;
// Make sure that we keep the language when
// breaking paragrpah.
if (tmp->empty()) {
- LyXFont changed = tmp->getFirstFontSettings();
+ LyXFont changed = tmp->getFirstFontSettings(bparams);
LyXFont old = par.getFontSettings(bparams, par.size());
changed.setLanguage(old.language());
tmp->setFont(0, changed);
if (moveItem(par, tmp, bparams, i, j - pos, change))
++j;
}
+ // Move over end-of-par change attr
+ tmp.setChange(tmp.size(), par.lookupChange(par.size()));
+
// If tracking changes, set all the text that is to be
// erased to Type::INSERTED.
for (pos_type k = pos_end; k >= pos; --k) {
pos_type pos_end = next.size() - 1;
pos_type pos_insert = par.size();
+ // What happens is the following. Later on, moveItem() will copy
+ // over characters from the next paragraph to be inserted into this
+ // position. Now, if the first char to be so copied is "red" (i.e.,
+ // marked deleted) and the paragraph break is marked "blue",
+ // insertChar will trigger (eventually, through record(), and see
+ // del() and erase() in changes.C) a "hard" character deletion.
+ // Which doesn't make sense of course at this pos, but the effect is
+ // to shorten the change range to which this para break belongs, by
+ // one. It will (should) remain "orphaned", having no CT info to it,
+ // and check() in changes.C will assert. Setting the para break
+ // forcibly to "black" prevents this scenario. -- MV 13.3.2006
+ par.setChange(par.size(), Change::UNCHANGED);
+
+ Change::Type cr = next.lookupChange(next.size());
// ok, now copy the paragraph
for (pos_type i = 0, j = 0; i <= pos_end; ++i) {
Change::Type change = next.lookupChange(i);
if (moveItem(next, par, bparams, i, pos_insert + j, change))
++j;
}
+ // Move the change status of "carriage return" over
+ par.setChange(par.size(), cr);
pars.erase(pars.begin() + par_offset + 1);
}