X-Git-Url: https://git.lyx.org/gitweb/?a=blobdiff_plain;f=src%2FRow.cpp;h=1e9e3eca2bc7fc74a0af3fcf5bc740d00441352b;hb=44dc38e120e04b7a6b1d275ff8e2f69993739b31;hp=697e526094b7f399801f4d62d24f7b39f5fc503a;hpb=6df593049c744c48dce7e169fd128a0d859c0253;p=lyx.git diff --git a/src/Row.cpp b/src/Row.cpp index 697e526094..1e9e3eca2b 100644 --- a/src/Row.cpp +++ b/src/Row.cpp @@ -19,6 +19,7 @@ #include "Row.h" #include "DocIterator.h" +#include "Language.h" #include "frontends/FontMetrics.h" @@ -391,6 +392,7 @@ void Row::add(pos_type const pos, Inset const * ins, Dimension const & dim, e.dim = dim; elements_.push_back(e); dim_.wid += dim.wid; + changebar_ |= ins->isChanged(); } @@ -479,7 +481,22 @@ bool Row::shortenIfNeeded(pos_type const keep, int const w, int const next_width // make a copy of the element to work on it. Element brk = *cit_brk; wid_brk -= brk.dim.wid; - if (brk.countSeparators() == 0 || brk.pos < keep) + /* + * Some Asian languages split lines anywhere (no notion of + * word). It seems that QTextLayout is not aware of this fact. + * See for reference: + * https://en.wikipedia.org/wiki/Line_breaking_rules_in_East_Asian_languages + * + * FIXME: Something shall be done about characters which are + * not allowed at the beginning or end of line. + * + * FIXME: hardcoding languages is bad. Put this information in + * `languages' file. + */ + bool const word_wrap = brk.font.language()->wordWrap(); + // When there is text before the body part (think description + // environment), do not try to break. + if (brk.pos < keep) continue; /* We have found a suitable separable element. This is the common case. * Try to break it cleanly (at word boundary) at a length that is both @@ -487,7 +504,7 @@ bool Row::shortenIfNeeded(pos_type const keep, int const w, int const next_width * - shorter than the natural width of the element, in order to enforce * break-up. */ - if (brk.breakAt(min(w - wid_brk, brk.dim.wid - 2), false)) { + if (brk.breakAt(min(w - wid_brk, brk.dim.wid - 2), !word_wrap)) { /* if this element originally did not cause a row overflow * in itself, and the remainder of the row would still be * too large after breaking, then we will have issues in