Seen on 5.1.4.2x64 (build f99d75f39f1c57ebdd7ffc5f42867c12031db97a) Win10home and on Elementary Linux Freya 0.3 (Ubuntu 14.04): Version: 5.3.0.0.beta1 Build ID: 690f553ecb3efd19143acbf01f3af4e289e94536 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; VCL: gtk2; Layout Engine: new; Locale: it-IT (it_IT.UTF-8); Calc: group 1. in Writer type just a word 2. hit CTRL+F10 to enable unprintable symbols visibility 3. leaving keyboard's cursor at the end of paragraph hit CTRL+ALT+C to insert a comment OUTPUT: the mirrored P reporting the end of paragraph is shifted on the right.
Created attachment 129145 [details] EndOfParagraph symbol shifted on the right See attachment
Confirmed with 5.1.0.3 and 5.2.3.3 / Windows 7. Doesn't happen in 5.0.0.5. => regression
3747e55ab76b05904deb47d0791857c2c1ee4911 is the first bad commit commit 3747e55ab76b05904deb47d0791857c2c1ee4911 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Aug 15 16:10:09 2015 -0700 source 26d8d33f3adfcbfd49ef1ea809202deabcea4957 # bad: [05d11632892a322664fb52bac90b2598b7fb7544] source 5616d22b57a9a5e57d545e912e029162a230829b # good: [c1efd324c6ad448ac9edb030dc9738b9e6899e4d] source ab465b90f6c6da5595393a0ba73f33a1e71a2b65 git bisect start '05d11632892a322664fb52bac90b2598b7fb7544' 'oldest' # bad: [97526ab777da7e58ce283c05498262ecdd4d6f7f] source 4ea70f87f7a2b61eda6e5ab1f48debf6fcfadc1f git bisect bad 97526ab777da7e58ce283c05498262ecdd4d6f7f # bad: [97526ab777da7e58ce283c05498262ecdd4d6f7f] source 4ea70f87f7a2b61eda6e5ab1f48debf6fcfadc1f git bisect bad 97526ab777da7e58ce283c05498262ecdd4d6f7f # good: [2202cdaa0eae3f646f1285a0ea45934edeb26e8a] source a88bf8fd10c42a15e5d6e66da656889c82b4933a git bisect good 2202cdaa0eae3f646f1285a0ea45934edeb26e8a # good: [13169de9868218d603d1ae26805ebf4583e7d628] source 6f98a0ab51cc5c860576b4ad44478b438cc5a5eb git bisect good 13169de9868218d603d1ae26805ebf4583e7d628 # bad: [1c81e0f3ca26bf56c3e7948016ca44369345a120] source 48a047f2f4e7b4b3bed33a99d37fd48025381646 git bisect bad 1c81e0f3ca26bf56c3e7948016ca44369345a120 # bad: [2a060e13c75dba5681397fc3b994a9abddcb55fc] source 866e287adee448c1c8b431c6c084d3fe3283649d git bisect bad 2a060e13c75dba5681397fc3b994a9abddcb55fc # good: [ef09eb8df0418a65cbd4cc14953cf1ef8d0f343c] source ca6c2bab8771a209fde937599bf9cecea2b77104 git bisect good ef09eb8df0418a65cbd4cc14953cf1ef8d0f343c # good: [9bb89f78f7e42311e81cf2bf0ea6f1a59041d479] source b5be942585db167aae58a4b820e9786f80a84096 git bisect good 9bb89f78f7e42311e81cf2bf0ea6f1a59041d479 # good: [c11f783d99cb2f0e8e99f85befcd2d0178acfbc1] source 2bfeabde75d1e99879465fee6fe6a97357739ae2 git bisect good c11f783d99cb2f0e8e99f85befcd2d0178acfbc1 # bad: [f988305b8f230085b0e6ddc1abed78fbcce9247a] source 0a22f4fd6d7496678822731a7bdd37687f717adf git bisect bad f988305b8f230085b0e6ddc1abed78fbcce9247a # good: [ffa457586a6e2602181ffc38a4062db7134010ae] source f089de7dc5c367a3123129b08a9050b3bacc4eba git bisect good ffa457586a6e2602181ffc38a4062db7134010ae # good: [81e7e4741dbb9ea5a72af1402da3988bf4f7e665] source 929954e0108897c4882660b4ce9cb5d4cf1077ec git bisect good 81e7e4741dbb9ea5a72af1402da3988bf4f7e665 # bad: [3ee37671577ec70c0505a3d7993c95854fd59ece] source 6cd04e9ea447a4828a6fc03d47a7d136f3914501 git bisect bad 3ee37671577ec70c0505a3d7993c95854fd59ece # bad: [3747e55ab76b05904deb47d0791857c2c1ee4911] source 26d8d33f3adfcbfd49ef1ea809202deabcea4957 git bisect bad 3747e55ab76b05904deb47d0791857c2c1ee4911 # first bad commit: [3747e55ab76b05904deb47d0791857c2c1ee4911] source 26d8d33f3adfcbfd49ef1ea809202deabcea4957
This bug started with the following commit. Adding Cc: to Mark Hung. Please take a look sometimes. author Mark Hung <marklh9@gmail.com> 2015-08-07 16:18:20 (GMT) committer Norbert Thiebaud <nthiebaud@gmail.com> 2015-08-15 23:07:32 (GMT) "Fix tdf#82176 CJK: Cursor position, line selection and non-printing characters do not take account of hanging punctuation. Note that placing a cursor next to the hanging puncuation is still not possible, but the selection and the non-printing characters works fine now."
*** Bug 105090 has been marked as a duplicate of this bug. ***
Mark Hung committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=542421402d4e4f32bd9c499673d7a3fa98b00683 tdf#104270 count hanging margin only if there is hanging portion. It will be available in 5.4.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Commit Notification from comment #6) > It will be available in 5.4.0. What I don't understand: Why not fix the problem in the "Still" (5.1) or "Fresh" (5.2) releases, but in the "over-next"? Especially when considering that the fix is like a three-line-change! So will we ever get a stable and bug-free release?
it needs to be backported. @Mark, could you please cherry-pick it to 5.3.X and 5.2.X and close it as RESOLVED WORKSFORME? Regards
Mark Hung committed a patch related to this issue. It has been pushed to "libreoffice-5-3": http://cgit.freedesktop.org/libreoffice/core/commit/?id=bf357ae90811edc101ff13774c2e28a16bb5420d&h=libreoffice-5-3 tdf#104270 count hanging margin only if there is hanging portion. It will be available in 5.3.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Mark Hung committed a patch related to this issue. It has been pushed to "libreoffice-5-2": http://cgit.freedesktop.org/libreoffice/core/commit/?id=e9e63fc49962270b51a4ec6aa2d6b41f5256ac02&h=libreoffice-5-2 tdf#104270 count hanging margin only if there is hanging portion. It will be available in 5.2.6. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.