[Libreoffice-bugs] [Bug 117608] Unbearable slow layout/UI refresh

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117608

--- Comment #6 from Buovjaga  ---
(In reply to Kochise from comment #5)
> Will see is the new master is better, but keep in mind that even a PDF
> export of the document displays the same vector graphics without any
> problem. When developing, at least when testing, please use a "normal"
> computer to feel the "vibe" of an average user. Do you coders ever do some
> profiling ? I mean, like speed and/or memory consumption ? That would reveal
> some things.

I am not a coder, but I do profiling.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118241] FILEOPEN XLSX Basic code with CreateObject("Scripting.FileSystemObject") and “For Each ” loop does not work

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118241

Buovjaga  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #4 from Buovjaga  ---
NEW per comment 3

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 82760] Arrows from MSO shapes have wrong heads

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82760

--- Comment #12 from Ruslan Kabatsayev  ---
Still present in 6.0.4.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118341] Line styles not preserved in WPG1 file

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118341

David Tardon  changed:

   What|Removed |Added

Summary|Line styles not preserved   |Line styles not preserved
   |in imported WPG file|in WPG1 file

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118341] Line styles not preserved in imported WPG file

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118341

David Tardon  changed:

   What|Removed |Added

Product|LibreOffice |Document Liberation Project
  Component|Draw|General
 CC||dtar...@redhat.com
Version|4.2.4.2 release |unspecified
   Severity|normal  |enhancement

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118361] FILEOPEN DOCX: Footnote separator Line position is wrong in RTL doc

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118361

--- Comment #2 from Fahad Al-Saidi  ---
Created attachment 143084
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143084=edit
docx file opened in writer

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118361] New: FILEOPEN DOCX: Footnote separator Line position is wrong in RTL doc

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118361

Bug ID: 118361
   Summary: FILEOPEN DOCX: Footnote separator Line position is
wrong in RTL doc
   Product: LibreOffice
   Version: 6.0.5.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: fahad.alsa...@gmail.com

Created attachment 143082
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143082=edit
test file

I have footnotes in docx file in RTL direction when I open the file in writer
the Footnote separator Line position is set to Left which is wrong. 

Please have look into screen shots & test file.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118361] FILEOPEN DOCX: Footnote separator Line position is wrong in RTL doc

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118361

--- Comment #1 from Fahad Al-Saidi  ---
Created attachment 143083
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143083=edit
docx file open in word 2016

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118360] Beta2 Pre-Release Not Available from public facing server where Advertisement at Bugzilla located for WindowsX64 and Windows_x86(32 Bit)

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118360

Mike Kaganski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||cl...@documentfoundation.or
   ||g
 Ever confirmed|0   |1

--- Comment #2 from Mike Kaganski  ---
Confirm. The pre-releases on dev-builds only contain 6.0.5.2 for win.

Christian, could you please have a look?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118350] Writer can't handle RTL direction from MS office odt file.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118350

--- Comment #5 from Fahad Al-Saidi  ---
Created attachment 143081
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143081=edit
word 2016 screen shot

to be clear here is how it looks in word 2016

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118350] Writer can't handle RTL direction from MS office odt file.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118350

Fahad Al-Saidi  changed:

   What|Removed |Added

 Attachment #143080|in windows  |Writer in windows
description||

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118350] Writer can't handle RTL direction from MS office odt file.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118350

--- Comment #4 from Fahad Al-Saidi  ---
(In reply to Susan Gessing from comment #2)
> I opened the attachment in each of the following builds. I wasn't able to
> reproduce the problem. (Windows 8.1)
> 
> Version: 6.0.5.2 (x64)
> Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
> CPU threads: 4; OS: Windows 6.3; UI render: GL; 
> Locale: en-US (en_US); Calc: CL
> 
>  and
> 
> Version: 6.2.0.0.alpha0+
> Build ID: b1740fba0d1e6e3d69c3781734509317f42a0e4f
> CPU threads: 4; OS: Windows 6.3; UI render: GL; 
> TinderBox: Win-x86@42, Branch:master, Time: 2018-06-15_08:49:04
> Locale: en-US (en_US); Calc: CL


You may not notice the direction. It is Right in Word and left in Writer. I
have tested the doc in windows and I can reproduce it.

Version: 6.0.5.2 (x64)
Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU threads: 1; OS: Windows 6.1; UI render: default; 
Locale: en-US (en_US); Calc: group

See the attached screen shot and please confirm.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118350] Writer can't handle RTL direction from MS office odt file.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118350

--- Comment #3 from Fahad Al-Saidi  ---
Created attachment 143080
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143080=edit
in windows

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118237] FILESAVE DOCX w:themeColor and w:themeShade attributes get duplicated inside w:color tag

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118237

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||3790

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118360] Beta2 Pre-Release Not Available from public facing server where Advertisement at Bugzilla located for WindowsX64 and Windows_x86(32 Bit)

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118360

Richard_416282  changed:

   What|Removed |Added

URL||https://dev-builds.libreoff
   ||ice.org/pre-releases/win/x8
   ||6_64/LibreOfficeDev_6.1.0.0
   ||.beta2_Win_x64.msi

--- Comment #1 from Richard_416282  ---
add link for place where advert and subsequent download should be.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118360] New: Beta2 Pre-Release Not Available from public facing server where Advertisement at Bugzilla located for WindowsX64 and Windows_x86(32 Bit)

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118360

Bug ID: 118360
   Summary: Beta2 Pre-Release Not Available from public facing
server where Advertisement at Bugzilla located for
WindowsX64 and Windows_x86(32 Bit)
   Product: LibreOffice
   Version: 6.1.0.0.beta2+
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: richard416...@yahoo.ca

Description:
When Browsing LibreOffice Bugzilla Bug reporting tool,, the tool has a banner
advertisement indicating LO 6.1 Beta2 is available, yet when image is clicked,
and link:

https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases

IS followed to the links for Windows32, and WindowsX64/

The only directory available is 6/0/5 instead of 6.1.0.0.beta2_Win_x64 as
pointed to :

https://dev-builds.libreoffice.org/pre-releases/win/x86_64/LibreOfficeDev_6.1.0.0.beta2_Win_x64.msi

Steps to Reproduce:
1.Open And /or follow links to bugzilla
2. Click on Image in centre top of screen
3. Follow links for Windows32 or Windows_x64.

Actual Results:
NGinix.

PAth not found.

Expected Results:
Begin download 6.1.0.0.beta2_Win_x64.


Reproducible: Always


User Profile Reset: No



Additional Info:
Using FireFox 60.0.2 x64 current version (up to date)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118265] Wrong font display of slides with some fonts when OpenGL enabled on W10

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118265

Pierre C  changed:

   What|Removed |Added

Version|6.0.0.0.beta1   |6.1.0.0.beta1+

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 114845] FILESAVE: PPTX Incorrect position of shapes after RT

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114845

--- Comment #5 from Commit Notification 
 ---
Justin Luth committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=682cf3242272346ad9955cd050a47554930fa8b6

tdf#114845: unit test to prevent a bad fix

It will be available in 6.2.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.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 114845] FILESAVE: PPTX Incorrect position of shapes after RT

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114845

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:6.2.0

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: sd/qa

2018-06-24 Thread Justin Luth
 sd/qa/unit/export-tests-ooxml2.cxx |3 +++
 1 file changed, 3 insertions(+)

New commits:
commit 682cf3242272346ad9955cd050a47554930fa8b6
Author: Justin Luth 
Date:   Sat Jun 23 22:17:32 2018 +0300

tdf#114845: unit test to prevent a bad fix

The fix I was about to suggest broke this file on round-trip.
It is not enough to just exclude if not a group-shape, or
else the group-shape detection is not good enough.

Change-Id: I0048bb9221262afdd373b18b5d73ec9468b7d670
Reviewed-on: https://gerrit.libreoffice.org/56340
Tested-by: Jenkins
Reviewed-by: Justin Luth 

diff --git a/sd/qa/unit/export-tests-ooxml2.cxx 
b/sd/qa/unit/export-tests-ooxml2.cxx
index 041c90b10398..1b3a20e0a256 100644
--- a/sd/qa/unit/export-tests-ooxml2.cxx
+++ b/sd/qa/unit/export-tests-ooxml2.cxx
@@ -1292,7 +1292,10 @@ void SdOOXMLExportTest2::testSmartartRotation2()
 xDocShRef->DoClose();
 
 xmlDocPtr pXmlDocContent = parseExport(tempFile, "ppt/slides/slide1.xml");
+assertXPath(pXmlDocContent, 
"/p:sld/p:cSld/p:spTree/p:grpSp/p:sp[3]/p:txBody/a:p/a:r/a:t", "Text");
 assertXPath(pXmlDocContent, 
"/p:sld/p:cSld/p:spTree/p:grpSp/p:sp[3]/p:txBody/a:bodyPr", "rot", "1080");
+assertXPath(pXmlDocContent, 
"/p:sld/p:cSld/p:spTree/p:grpSp/p:sp[3]/p:spPr/a:xfrm/a:off", "x", "2276280");
+assertXPath(pXmlDocContent, 
"/p:sld/p:cSld/p:spTree/p:grpSp/p:sp[3]/p:spPr/a:xfrm/a:off", "y", "3158280");
 }
 
 void SdOOXMLExportTest2::testGroupsPosition()
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-bugs] [Bug 117608] Unbearable slow layout/UI refresh

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117608

--- Comment #5 from Kochise  ---
Yeah, thanks to have noticed the vector graphics, but those were made in 2002
on a Pentium class computer with something like 64MB memory and about 1GHz
clock rate without any problem using Visio and Office of that time. I really
don't think we needs a super computer with 32GB of memory to just display those
vector graphics in 2018. OK it's a different engine, but these are still simple
vectors.

Will see is the new master is better, but keep in mind that even a PDF export
of the document displays the same vector graphics without any problem. When
developing, at least when testing, please use a "normal" computer to feel the
"vibe" of an average user. Do you coders ever do some profiling ? I mean, like
speed and/or memory consumption ? That would reveal some things.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118358] Pressed the "X" icon to close an .odt file. Got ta crash message. Windows 10.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118358

V Stuart Foote  changed:

   What|Removed |Added

Crash report or|["rtl_ustr_ascii_compareIgn |["rtl_ustr_ascii_compareIgn
crash signature|oreAsciiCase_WithLength"]   |oreAsciiCase_WithLength()"]

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118358] Pressed the "X" icon to close an .odt file. Got ta crash message. Windows 10.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118358

V Stuart Foote  changed:

   What|Removed |Added

Crash report or|[rtl_ustr_ascii_compareIgno |["rtl_ustr_ascii_compareIgn
crash signature|reAsciiCase_WithLength] |oreAsciiCase_WithLength"]

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118358] Pressed the "X" icon to close an .odt file. Got ta crash message. Windows 10.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118358

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
Crash report or||[rtl_ustr_ascii_compareIgno
crash signature||reAsciiCase_WithLength]
 OS|All |Windows (All)
 Ever confirmed|0   |1
Version|unspecified |5.4.7.2 release
 CC||vstuart.fo...@utsa.edu

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91565] REPORT BUILDER: Missing insert field icon in Add Field dialog

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91565

--- Comment #10 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 78814] Oracle Report Builder parameter "visible" not working

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=78814

--- Comment #10 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 49319] EDITING: Cannot change a polygon point to Smooth Transition

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49319

--- Comment #21 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 94102] Impress saves as SWF but it's impossible play it

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94102

--- Comment #7 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 107536] REPORTBUILDER: Pie chart colours revert to defaults in generated report

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107536

--- Comment #3 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 99985] UDF does not work in Report Builder

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99985

--- Comment #9 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 107300] Bibliography database - no CANCEL button

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107300

--- Comment #7 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 94564] TextShape with fit to frame doesn't work correctly in small shapes

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94564

--- Comment #6 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83279] VIEWING: Scrollbar missing in report builder after closing properties panel

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83279

--- Comment #5 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 68781] FILEOPEN Report Builder produced chart-in-writer drops date values

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=68781

--- Comment #9 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 106297] Paste special MS Word .doc to Writer only pastes the first page

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106297

--- Comment #2 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 52430] EDITING: Report-Builder - conditional print expression won't work with repeated section

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=52430

--- Comment #9 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 90344] Shape anchors incorrectly (file attached)

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90344

--- Comment #6 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 95462] Find toolbar doesnt appear in full screen mode

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=95462

--- Comment #15 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 107225] Wrong position of textbox in shape, if shape is contained in a frame

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107225

--- Comment #3 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 106015] Extension Manager hangs after unticking a checkbox while installing an extension

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106015

--- Comment #3 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 55202] EDITING: Report-Builder - Vertical position of text with shapes in the background impossible

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=55202

--- Comment #10 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-ux-advise] [Bug 95462] Find toolbar doesnt appear in full screen mode

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=95462

--- Comment #15 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


[Libreoffice-bugs] [Bug 87012] REPORT-BUILDER: Charts without content if chart contain date or time

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87012

--- Comment #11 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101016] REPORT BUILDER: Charts aren't shown when using grouped data from same datasource the report uses

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101016

--- Comment #2 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 99751] EDITING : Need to select multiple objects to add Glue Points to table

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99751

--- Comment #2 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 105441] styles don't resize shape with "resize shape to fit text"

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105441

--- Comment #2 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 94375] Impossible use of exported flash/swf

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94375

--- Comment #5 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 68619] REPORTBUILDER: Functions in fields were changed to user-defined-functions in properties of the field, if fieldnames have special characters

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=68619

--- Comment #27 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 106621] Additional glue points in group are not visible

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106621

--- Comment #6 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 82760] Arrows from MSO shapes have wrong heads

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82760

--- Comment #11 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 95168] Background Color Removed from OOXML shapes with hatching

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=95168

--- Comment #2 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 53253] REPORTBUILDER: Automatic page break destroys details group

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=53253

--- Comment #8 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 52944] EDITING: Report-Builder - Edit column Header/Footer has no function

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=52944

--- Comment #16 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 68327] SVG: draw:glue-points cannot be defined outside svg:viewbox

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=68327

--- Comment #12 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: lotuswordpro/source sw/source

2018-06-24 Thread Andrea Gelmini
 lotuswordpro/source/filter/lwpfoundry.cxx |2 +-
 sw/source/core/unocore/unomap.cxx |2 +-
 sw/source/uibase/utlui/content.cxx|4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

New commits:
commit bef51263c2904fbee0d1283f0cbd32d89af1cbe4
Author: Andrea Gelmini 
Date:   Sat Jun 23 14:28:45 2018 +0200

Fix typos

Change-Id: I8787f619d68073e4bbd293d5863736c0cfff1632
Reviewed-on: https://gerrit.libreoffice.org/56315
Tested-by: Jenkins
Reviewed-by: Jens Carl 

diff --git a/lotuswordpro/source/filter/lwpfoundry.cxx 
b/lotuswordpro/source/filter/lwpfoundry.cxx
index 2f56998ee4b7..40420d92244c 100644
--- a/lotuswordpro/source/filter/lwpfoundry.cxx
+++ b/lotuswordpro/source/filter/lwpfoundry.cxx
@@ -442,7 +442,7 @@ LwpOrderedObject* 
LwpOrderedObjectManager::Enumerate(LwpOrderedObject * pLast)
 LwpListList* pList = nullptr;
 if(pLast)
 {
-// We're at the end of Last's list (not Liszt's list).
+// We're at the end of Last's list (not list's list).
 // Start with the next active list
 pList = dynamic_cast(pLast->GetListList().obj().get());
 pList= GetNextActiveListList(pList);
diff --git a/sw/source/core/unocore/unomap.cxx 
b/sw/source/core/unocore/unomap.cxx
index 3dffbe6859fc..1c242d610de7 100644
--- a/sw/source/core/unocore/unomap.cxx
+++ b/sw/source/core/unocore/unomap.cxx
@@ -328,7 +328,7 @@ const SfxItemPropertyMapEntry* 
SwUnoPropertyMapProvider::GetPropertyMapEntries(s
 cppu::UnoType::get(),
 PropertyAttribute::READONLY, 0},
 // #i71182#
-// missing map entry for property 
+// missing map entry for property 
 { OUString(UNO_NAME_PAGE_TOGGLE), RES_HORI_ORIENT,  
cppu::UnoType::get(), PROPERTY_NONE ,MID_HORIORIENT_PAGETOGGLE },
 { OUString(UNO_NAME_RELATIVE_HEIGHT), RES_FRM_SIZE, 
cppu::UnoType::get()  , PROPERTY_NONE, 
MID_FRMSIZE_REL_HEIGHT },
 { OUString(UNO_NAME_RELATIVE_HEIGHT_RELATION), 
RES_FRM_SIZE, cppu::UnoType::get(),  PROPERTY_NONE, 
MID_FRMSIZE_REL_HEIGHT_RELATION },
diff --git a/sw/source/uibase/utlui/content.cxx 
b/sw/source/uibase/utlui/content.cxx
index 5ed2db49a19d..645469eb143f 100644
--- a/sw/source/uibase/utlui/content.cxx
+++ b/sw/source/uibase/utlui/content.cxx
@@ -393,7 +393,7 @@ void SwContentType::Init(bool* pbInvalidateWindow)
 if(nullptr != pbInvalidateWindow)
 {
 // need to check visibility (and equal entry number) after
-// creation due to a sorted liszt being used here (before,
+// creation due to a sorted list being used here (before,
 // entries with same index were compared already at 
creation
 // time what worked before a sorted list was used)
 *pbInvalidateWindow = checkVisibilityChanged(
@@ -689,7 +689,7 @@ void SwContentType::FillMemberList(bool* 
pbLevelOrVisibilityChanged)
 if(nullptr != pbLevelOrVisibilityChanged)
 {
 // need to check visibility (and equal entry number) after
-// creation due to a sorted liszt being used here (before,
+// creation due to a sorted list being used here (before,
 // entries with same index were compared already at 
creation
 // time what worked before a sorted list was used)
 *pbLevelOrVisibilityChanged = checkVisibilityChanged(
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-commits] core.git: sc/CppunitTest_sc_viewpaneobj.mk

2018-06-24 Thread Jens Carl
 sc/CppunitTest_sc_viewpaneobj.mk |   29 -
 1 file changed, 29 deletions(-)

New commits:
commit d6f66fd08b9950a9af96a7745266e5003e3c8a32
Author: Jens Carl 
Date:   Sun Jun 24 22:55:58 2018 +

Remove obsolete (cargo-cult copied) dependencies

Change-Id: I5dea60a3833802473c133ef3060183c3ed790f6f
Reviewed-on: https://gerrit.libreoffice.org/56365
Tested-by: Jenkins
Reviewed-by: Jens Carl 

diff --git a/sc/CppunitTest_sc_viewpaneobj.mk b/sc/CppunitTest_sc_viewpaneobj.mk
index fb960c37ae20..7936d21677b9 100644
--- a/sc/CppunitTest_sc_viewpaneobj.mk
+++ b/sc/CppunitTest_sc_viewpaneobj.mk
@@ -18,43 +18,14 @@ $(eval $(call 
gb_CppunitTest_add_exception_objects,sc_viewpaneobj, \
 ))
 
 $(eval $(call gb_CppunitTest_use_libraries,sc_viewpaneobj, \
-basegfx \
-comphelper \
 cppu \
-cppuhelper \
-drawinglayer \
-editeng \
-for \
-forui \
-i18nlangtag \
-msfilter \
-oox \
 sal \
-salhelper \
-sax \
-sb \
-sc \
-sfx \
-sot \
 subsequenttest \
-svl \
-svt \
-svx \
-svxcore \
test \
-tk \
-tl \
-ucbhelper \
unotest \
-utl \
-vbahelper \
-vcl \
-xo \
 ))
 
 $(eval $(call gb_CppunitTest_set_include,sc_viewpaneobj,\
--I$(SRCDIR)/sc/source/ui/inc \
--I$(SRCDIR)/sc/inc \
 $$(INCLUDE) \
 ))
 
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-bugs] [Bug 118359] Error mesage when attempting to create Master Document with File >> Send option

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118359

Richard_416282  changed:

   What|Removed |Added

URL||https://help.libreoffice.or
   ||g/Common/Create_Master_Docu
   ||ment

--- Comment #1 from Richard_416282  ---
Update Issue.

Add URL Link for Current Web page for help documentation.

https://help.libreoffice.org/Common/Create_Master_Document

Next steps : 

Reset User Profile.

Download 6.1 Beta to confirm anomoly, then verify of User Profile changed

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 43021] Macros: FilePicker method setDisplayDirectory shows wrong folder with native dialog Win 7 (64-bit)

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43021

--- Comment #44 from Sherilyn  ---
It still works for me.
192.168.0.1 https://19216801help.com/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118359] New: Error mesage when attempting to create Master Document with File >> Send option

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118359

Bug ID: 118359
   Summary: Error mesage when attempting to create Master Document
with File >> Send option
   Product: LibreOffice
   Version: 5.4.1.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: richard416...@yahoo.ca

Description:
When following the Online version for Help, to Create a Master Document, the
instructions say to click the following steps.

1. Click on  File >> Send >> Create Master Document 

This open a save dialoge, and the option to save a master document is
presented, yet when a name is selected, and save is pressed, a message:

"Can't Create Document", with an icon of a warning bulb, and the verion string
in the upper left corner of the error box.

The only option is to click "OK".


Solution was to click "File >> New >> Create Master Document"

Works as expected.

Steps to Reproduce:
1.Open New Document 
2.Click on help , fill in section "Create Master Document"
3.Get web link : https://help.libreoffice.org/Common/Create_Master_Document
4. Follow instructions in Docuemnt.
5. Click File >> Send >> Create Master Document.
6. New Window appears [Save]
7. Fill in name of master document.
8. Click SAVE



Actual Results:
Error Window ”5.4.1.2 Cant Save Document”; "OK" button in centre.

Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; 
Locale: en-CA (en_CA)

Expected Results:
Error Window ”5.4.1.2 Cant Save Document”; "OK" button in centre.

Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; 
Locale: en-CA (en_CA)

Expected Results:

Expected same result as clicking File > Create New  Master Document.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; 
Locale: en-CA (en_CA)

User Profile Not Reset Yet. Next step is to reset profile, and re-attempt.

Possible Error on Documentation, that instructions should say

CLick File >> New >> Create New Master; instead of Send >> Create Master.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 34355] Option to show track changes in margin is missing

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34355

--- Comment #39 from Sherilyn  ---
Improved track changes in LO is crucial for most users in professional
environments.
gmail sign up https://www.just4dummies.com/gmail-sign-up

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-ux-advise] [Bug 34355] Option to show track changes in margin is missing

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34355

--- Comment #39 from Sherilyn  ---
Improved track changes in LO is crucial for most users in professional
environments.
gmail sign up https://www.just4dummies.com/gmail-sign-up

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


[Libreoffice-bugs] [Bug 107993] FORMATTING: Free space filling broken with thousands separator

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107993

Aron Budea  changed:

   What|Removed |Added

Version|5.3.3.2 release |4.0.0.3 release
 OS|Windows (All)   |All
   Hardware|x86-64 (AMD64)  |All

--- Comment #4 from Aron Budea  ---
Still in 6.1 beta2, see attachment 143062.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 107575] [META] Number format bugs and enhancements

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107575
Bug 107575 depends on bug 118338, which changed state.

Bug 118338 Summary: Character-fill doesn't work with space thousand separators
https://bugs.documentfoundation.org/show_bug.cgi?id=118338

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 107993] FORMATTING: Free space filling broken with thousands separator

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107993

Aron Budea  changed:

   What|Removed |Added

 CC||ba...@caesar.elte.hu

--- Comment #3 from Aron Budea  ---
*** Bug 118338 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118338] Character-fill doesn't work with space thousand separators

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118338

Aron Budea  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Aron Budea  ---
My bad, I just noticed this has already been filed before. Let's mark as
duplicate.

*** This bug has been marked as a duplicate of bug 107993 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118221] Calc fails to render cell-applied kerning=off (default setting) for single-line cells, kerning=off only is rendered for single line cells if at least one character has

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118221

--- Comment #40 from Aron Budea  ---
Is this the same as bug 107250?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 107250] Kerning pairs from font are applied even when pair kerning is disabled

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107250

Aron Budea  changed:

   What|Removed |Added

   Priority|low |medium
   Severity|minor   |normal

--- Comment #13 from Aron Budea  ---
Still in 6.1 beta2. Let's reset importance, as proper alignment of numbers is
actually significant in a spreadsheet application.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118313] FILESAVE Error when saving odg containing curve

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118313

Susan Gessing  changed:

   What|Removed |Added

 CC||susanjea...@yahoo.com

--- Comment #3 from Susan Gessing  ---

I was able to save with no problem on Windows 8.1, on the following:

Version: 6.0.5.2 (x64)
Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
Locale: en-US (en_US); Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118333] Crash in: SfxItemPool::Remove(SfxPoolItem const &) when reloading a file

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118333

robert.funn...@mcgill.ca changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 117987] Repeat Cell Highlighting Not Working Correctly

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117987

--- Comment #4 from Commit Notification 
 ---
Maxim Monastirsky committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=2fd31c75b677b145cf56404348857e60befcabff

tdf#117987 tdf#118138 Compare with the currently used color

It will be available in 6.2.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.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: include/svx svx/source

2018-06-24 Thread Maxim Monastirsky
 include/svx/PaletteManager.hxx |4 
 svx/source/tbxctrls/PaletteManager.cxx |   23 +--
 svx/source/tbxctrls/tbcontrl.cxx   |   16 +++-
 3 files changed, 8 insertions(+), 35 deletions(-)

New commits:
commit 1305aaefa4ec327556f6bff237604b5f9689b936
Author: Maxim Monastirsky 
Date:   Sun Jun 24 22:37:01 2018 +0300

Kill the useless PaletteManager "last color" thing

Change-Id: Iafd4677460bf6ee2cc5bb7cd3f67c2719865a151
Reviewed-on: https://gerrit.libreoffice.org/56360
Tested-by: Jenkins
Reviewed-by: Maxim Monastirsky 

diff --git a/include/svx/PaletteManager.hxx b/include/svx/PaletteManager.hxx
index ed8f639374f3..486edd94b4a2 100644
--- a/include/svx/PaletteManager.hxx
+++ b/include/svx/PaletteManager.hxx
@@ -43,7 +43,6 @@ class SVX_DLLPUBLIC PaletteManager
 svx::ToolboxButtonColorUpdater* mpBtnUpdater;
 
 XColorListRef   pColorList;
-Color   mLastColor;
 std::deque  maRecentColors;
 std::vector> m_Palettes;
 
@@ -68,9 +67,6 @@ public:
 
 longGetColorCount();
 longGetRecentColorCount();
-
-const Color& GetLastColor();
-voidSetLastColor(const Color& rLastColor);
 voidAddRecentColor(const Color& rRecentColor, const OUString& 
rColorName, bool bFront = true);
 
 voidSetBtnUpdater(svx::ToolboxButtonColorUpdater* pBtnUpdater);
diff --git a/svx/source/tbxctrls/PaletteManager.cxx 
b/svx/source/tbxctrls/PaletteManager.cxx
index 27c84cdbfd56..40f99c9074ab 100644
--- a/svx/source/tbxctrls/PaletteManager.cxx
+++ b/svx/source/tbxctrls/PaletteManager.cxx
@@ -43,7 +43,6 @@ PaletteManager::PaletteManager() :
 mnCurrentPalette(0),
 mnColorCount(0),
 mpBtnUpdater(nullptr),
-mLastColor(COL_AUTO),
 maColorSelectFunction(PaletteManager::DispatchColorCommand),
 m_context(comphelper::getProcessComponentContext())
 {
@@ -307,16 +306,6 @@ long PaletteManager::GetRecentColorCount()
 return maRecentColors.size();
 }
 
-const Color& PaletteManager::GetLastColor()
-{
-return mLastColor;
-}
-
-void PaletteManager::SetLastColor(const Color& rLastColor)
-{
-mLastColor = rLastColor;
-}
-
 void PaletteManager::AddRecentColor(const Color& rRecentColor, const OUString& 
rName, bool bFront)
 {
 auto itColor = std::find_if(maRecentColors.begin(),
@@ -348,8 +337,6 @@ void PaletteManager::AddRecentColor(const Color& 
rRecentColor, const OUString& r
 void PaletteManager::SetBtnUpdater(svx::ToolboxButtonColorUpdater* pBtnUpdater)
 {
 mpBtnUpdater = pBtnUpdater;
-if (mpBtnUpdater)
-mLastColor = mpBtnUpdater->GetCurrentColor();
 }
 
 void PaletteManager::SetColorSelectFunction(const std::function& aColorSelectFunction)
@@ -366,12 +353,12 @@ void PaletteManager::PopupColorPicker(weld::Window* 
pParent, const OUString& aCo
 aColorDlg.SetMode(svtools::ColorPickerMode::Modify);
 if (aColorDlg.Execute(pParent) == RET_OK)
 {
+Color aLastColor = aColorDlg.GetColor();
 if (mpBtnUpdater)
-mpBtnUpdater->Update( aColorDlg.GetColor() );
-mLastColor = aColorDlg.GetColor();
-OUString sColorName = ("#" + 
mLastColor.AsRGBHexString().toAsciiUpperCase());
-NamedColor aNamedColor = std::make_pair(mLastColor, sColorName);
-AddRecentColor(mLastColor, sColorName);
+mpBtnUpdater->Update(aLastColor);
+OUString sColorName = ("#" + 
aLastColor.AsRGBHexString().toAsciiUpperCase());
+NamedColor aNamedColor = std::make_pair(aLastColor, sColorName);
+AddRecentColor(aLastColor, sColorName);
 maColorSelectFunction(aCommandCopy, aNamedColor);
 }
 }
diff --git a/svx/source/tbxctrls/tbcontrl.cxx b/svx/source/tbxctrls/tbcontrl.cxx
index e8694d85d223..ad1d096aa95f 100644
--- a/svx/source/tbxctrls/tbcontrl.cxx
+++ b/svx/source/tbxctrls/tbcontrl.cxx
@@ -2850,7 +2850,6 @@ void SvxColorToolBoxControl::EnsurePaletteManager()
 {
 m_xPaletteManager.reset(new PaletteManager);
 m_xPaletteManager->SetBtnUpdater(m_xBtnUpdater.get());
-m_xPaletteManager->SetLastColor(m_xBtnUpdater->GetCurrentColor());
 }
 }
 
@@ -2892,8 +2891,6 @@ VclPtr 
SvxColorToolBoxControl::createPopupWindow( vcl::Window* pPar
 IMPL_LINK(SvxColorToolBoxControl, SelectedHdl, const NamedColor&, rColor, void)
 {
 m_xBtnUpdater->Update(rColor.first);
-if (m_xPaletteManager)
-m_xPaletteManager->SetLastColor(rColor.first);
 }
 
 void SvxColorToolBoxControl::statusChanged( const 
css::frame::FeatureStateEvent& rEvent )
@@ -2920,8 +2917,6 @@ void SvxColorToolBoxControl::statusChanged( const 
css::frame::FeatureStateEvent&
 rEvent.State >>= aColor;
 }
 m_xBtnUpdater->Update( aColor );
-if (m_xPaletteManager)
-m_xPaletteManager->SetLastColor(aColor);
 }
 else if ( rEvent.State >>= bValue )
 pToolBox->CheckItem( nId, bValue );
@@ -2937,6 +2932,7 @@ void 

[Libreoffice-bugs] [Bug 118138] Last used color part of background color split button not working correctly

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118138

--- Comment #4 from Commit Notification 
 ---
Maxim Monastirsky committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=2fd31c75b677b145cf56404348857e60befcabff

tdf#117987 tdf#118138 Compare with the currently used color

It will be available in 6.2.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.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118138] Last used color part of background color split button not working correctly

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118138

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:6.2.0

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 117987] Repeat Cell Highlighting Not Working Correctly

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117987

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:6.2.0

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118333] Crash in: SfxItemPool::Remove(SfxPoolItem const &) when reloading a file

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118333

--- Comment #2 from robert.funn...@mcgill.ca ---
Created attachment 143079
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143079=edit
Anonymized version of file that crashed

This is anonymized version of the file that I was editing when the crash
occurred. I had done some editing (mostly removing highlighting, I think,
either by setting No Fill or by clearing direct formatting) when I did a Reload
and LO crashed.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: include/svx svx/source sw/source

2018-06-24 Thread Maxim Monastirsky
 include/svx/tbcontrl.hxx|1 -
 svx/source/tbxctrls/tbcontrl.cxx|9 +
 sw/source/uibase/shells/textsh1.cxx |   19 +--
 3 files changed, 14 insertions(+), 15 deletions(-)

New commits:
commit 2fd31c75b677b145cf56404348857e60befcabff
Author: Maxim Monastirsky 
Date:   Sun Jun 24 17:38:05 2018 +0300

tdf#117987 tdf#118138 Compare with the currently used color

... when deciding whether to toggle highlighting. Had to move
the whole thing into sw, as otherwise there is no way to
correctly handle the "brush" mode (as the toolbox controller
in svx has no way to know in advance which text will be
selected by the user).

Change-Id: Id2dec4c3647332e82260d12da1311b249f5b9c12
Reviewed-on: https://gerrit.libreoffice.org/56358
Tested-by: Jenkins
Reviewed-by: Maxim Monastirsky 

diff --git a/include/svx/tbcontrl.hxx b/include/svx/tbcontrl.hxx
index bf089f87153a..ded664983f21 100644
--- a/include/svx/tbcontrl.hxx
+++ b/include/svx/tbcontrl.hxx
@@ -212,7 +212,6 @@ class SVX_DLLPUBLIC SvxColorToolBoxControl : public 
cppu::ImplInheritanceHelper<
 std::shared_ptr m_xPaletteManager;
 BorderColorStatus m_aBorderColorStatus;
 bool m_bSplitButton;
-bool m_bIsNoFill;
 sal_uInt16 m_nSlotId;
 ColorSelectFunction m_aColorSelectFunction;
 DECL_LINK(SelectedHdl, const NamedColor&, void);
diff --git a/svx/source/tbxctrls/tbcontrl.cxx b/svx/source/tbxctrls/tbcontrl.cxx
index 5a9b89af6551..e8694d85d223 100644
--- a/svx/source/tbxctrls/tbcontrl.cxx
+++ b/svx/source/tbxctrls/tbcontrl.cxx
@@ -2767,7 +2767,6 @@ 
com_sun_star_comp_svx_FontNameToolBoxControl_get_implementation(
 SvxColorToolBoxControl::SvxColorToolBoxControl( const 
css::uno::Reference& rContext ) :
 ImplInheritanceHelper( rContext, nullptr, OUString() ),
 m_bSplitButton(true),
-m_bIsNoFill(false),
 m_nSlotId(0),
 m_aColorSelectFunction(PaletteManager::DispatchColorCommand)
 {
@@ -2892,9 +2891,6 @@ VclPtr 
SvxColorToolBoxControl::createPopupWindow( vcl::Window* pPar
 
 IMPL_LINK(SvxColorToolBoxControl, SelectedHdl, const NamedColor&, rColor, void)
 {
-if (m_xBtnUpdater->GetCurrentColor() != rColor.first)
-m_bIsNoFill = false;
-
 m_xBtnUpdater->Update(rColor.first);
 if (m_xPaletteManager)
 m_xPaletteManager->SetLastColor(rColor.first);
@@ -2957,11 +2953,8 @@ void SvxColorToolBoxControl::execute(sal_Int16 
/*nSelectModifier*/)
 Color aColor = m_xPaletteManager->GetLastColor();
 
 auto aArgs( comphelper::InitPropertySequence( {
-{ m_aCommandURL.copy(5), css::uno::makeAny( COL_TRANSPARENT ) }
+{ m_aCommandURL.copy(5), css::uno::makeAny(aColor) }
 } ) );
-if (!m_bIsNoFill)
-aArgs[0].Value <<= sal_Int32( m_xPaletteManager->GetLastColor() );
-m_bIsNoFill = !m_bIsNoFill;
 dispatchCommand( aCommand, aArgs );
 
 OUString sColorName = ("#" + aColor.AsRGBHexString().toAsciiUpperCase());
diff --git a/sw/source/uibase/shells/textsh1.cxx 
b/sw/source/uibase/shells/textsh1.cxx
index 5495f890566c..e905d9667913 100644
--- a/sw/source/uibase/shells/textsh1.cxx
+++ b/sw/source/uibase/shells/textsh1.cxx
@@ -1205,16 +1205,23 @@ void SwTextShell::Execute(SfxRequest )
 if (nSlot != SID_ATTR_CHAR_COLOR_EXT)
 {
 rWrtSh.StartUndo( SwUndoId::INSATTR );
-rWrtSh.SetAttrItem(
-SvxBrushItem( rEdtWin.GetWaterCanTextBackColor(), 
RES_CHRATR_BACKGROUND) );
+
+SfxItemSet aCoreSet( rWrtSh.GetView().GetPool(), 
svl::Items<
+ RES_CHRATR_BACKGROUND, 
RES_CHRATR_BACKGROUND,
+ RES_CHRATR_GRABBAG, 
RES_CHRATR_GRABBAG>{} );
+rWrtSh.GetCurAttr( aCoreSet );
+
+// Remove highlight if already set of the same color
+const SvxBrushItem& rBrushItem = 
aCoreSet.Get(RES_CHRATR_BACKGROUND);
+if ( aSet == rBrushItem.GetColor() )
+aSet = COL_TRANSPARENT;
+
+rWrtSh.SetAttrItem( SvxBrushItem(aSet, 
RES_CHRATR_BACKGROUND) );
 
 // Remove MS specific highlight when background is set
 rWrtSh.SetAttrItem( SvxBrushItem(RES_CHRATR_HIGHLIGHT) );
 
 // Remove shading marker
-SfxItemSet aCoreSet( rWrtSh.GetView().GetPool(), 
svl::Items{} );
-rWrtSh.GetCurAttr( aCoreSet );
-
 const SfxPoolItem *pTmpItem;
 if( SfxItemState::SET == aCoreSet.GetItemState( 
RES_CHRATR_GRABBAG, false,  ) )
 {
@@ -1231,7 +1238,7 @@ void SwTextShell::Execute(SfxRequest )
 }
 else
 rWrtSh.SetAttrItem(
-SvxColorItem( rEdtWin.GetWaterCanTextColor(), 
RES_CHRATR_COLOR) );
+

Bringing attributes draw:fontwork-xyz to ODF?

2018-06-24 Thread Regina Henschel

Hi all,

LibreOffice has a feature Fontwork, which is actually a "text along 
path". This feature exists from the beginning. You find it in the DTD of 
OpenOffice.org 1.0.


When OpenOffice.org had switched to ODF, these attributes were written 
unchanged to file and so does LibreOffice. But these attributes were 
never specified in ODF.


I have started to work on a specification. But before I continue to work 
on it, I think, there should be a general decision: Do we want to 
specify these attributes, or do we change the implementation to write 
these attributes in loext-namespace for ever and drop it for ODF strict? 
Or any other suggestion?


Kind regards
Regina


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice-bugs] [Bug 114149] LibreOffice does not display self set icons in own toolbars, only text is displayed

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114149

Maxim Monastirsky  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||momonas...@gmail.com
 Status|NEEDINFO|RESOLVED

--- Comment #5 from Maxim Monastirsky  ---


*** This bug has been marked as a duplicate of bug 106784 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 105225] Color palette cannot be chosen in various places

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105225

--- Comment #54 from Commit Notification 
 ---
Jim Raykowski committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=76d9d6c9bf0167d4203d7e2f6867254687915caa

tdf#105225 new background tab page for Calc Format Cells dialog

It will be available in 6.2.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.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: sc/source

2018-06-24 Thread Jim Raykowski
 sc/source/ui/attrdlg/attrdlg.cxx |4 ++--
 sc/source/ui/view/tabvwsha.cxx   |8 
 2 files changed, 10 insertions(+), 2 deletions(-)

New commits:
commit 76d9d6c9bf0167d4203d7e2f6867254687915caa
Author: Jim Raykowski 
Date:   Tue Jun 5 23:02:20 2018 -0800

tdf#105225 new background tab page for Calc Format Cells dialog

Change-Id: Iee26630fa47fedcfc134969cc4d3e13d939fbb77
Reviewed-on: https://gerrit.libreoffice.org/55357
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens 

diff --git a/sc/source/ui/attrdlg/attrdlg.cxx b/sc/source/ui/attrdlg/attrdlg.cxx
index 3ad3c86f8747..16163f7473b0 100644
--- a/sc/source/ui/attrdlg/attrdlg.cxx
+++ b/sc/source/ui/attrdlg/attrdlg.cxx
@@ -57,8 +57,8 @@ ScAttrDlg::ScAttrDlg(vcl::Window* pParent, const SfxItemSet* 
pCellAttrs)
 RemoveTabPage( "asiantypography" );
 OSL_ENSURE(pFact->GetTabPageCreatorFunc( RID_SVXPAGE_BORDER ), 
"GetTabPageCreatorFunc fail!");
 AddTabPage( "borders",  pFact->GetTabPageCreatorFunc( 
RID_SVXPAGE_BORDER ), nullptr );
-OSL_ENSURE(pFact->GetTabPageCreatorFunc( RID_SVXPAGE_BACKGROUND ), 
"GetTabPageCreatorFunc fail!");
-AddTabPage( "background",  pFact->GetTabPageCreatorFunc( 
RID_SVXPAGE_BACKGROUND ), nullptr );
+OSL_ENSURE(pFact->GetTabPageCreatorFunc( RID_SVXPAGE_BKG ), 
"GetTabPageCreatorFunc fail!");
+AddTabPage( "background",  pFact->GetTabPageCreatorFunc( RID_SVXPAGE_BKG 
), nullptr );
 AddTabPage( "cellprotection" ,  ScTabPageProtection::Create,nullptr );
 }
 
diff --git a/sc/source/ui/view/tabvwsha.cxx b/sc/source/ui/view/tabvwsha.cxx
index 42a1245ef8c4..90c30f148695 100644
--- a/sc/source/ui/view/tabvwsha.cxx
+++ b/sc/source/ui/view/tabvwsha.cxx
@@ -64,6 +64,8 @@
 
 #include 
 
+#include 
+
 using namespace com::sun::star;
 
 bool ScTabViewShell::GetFunction( OUString& rFuncStr, FormulaError nErrCode )
@@ -481,6 +483,12 @@ void ScTabViewShell::ExecuteCellFormatDlg(SfxRequest& 
rReq, const OString 
 std::shared_ptr pOldSet(new 
SfxItemSet(pOldAttrs->GetItemSet()));
 std::shared_ptr pNumberInfoItem;
 
+pOldSet->MergeRange(XATTR_FILLCOLOR, XATTR_FILLCOLOR);
+
+sal_uInt16 nWhich = pOldSet->GetPool()->GetWhich( SID_ATTR_BRUSH );
+SvxBrushItem aBrushItem(static_cast(pOldSet->Get(nWhich)));
+setSvxBrushItemAsFillAttributesToTargetSet(aBrushItem, *pOldSet);
+
 pOldSet->MergeRange(SID_ATTR_BORDER_STYLES, SID_ATTR_BORDER_DEFAULT_WIDTH);
 
 // We only allow these border line types.
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-commits] core.git: sw/source

2018-06-24 Thread Xisco Fauli
 sw/source/ui/config/optload.cxx  |2 ++
 sw/source/uibase/inc/cption.hxx  |   12 
 sw/source/uibase/inc/optload.hxx |   15 +++
 3 files changed, 17 insertions(+), 12 deletions(-)

New commits:
commit b34ed105d5eead1cb7657d0a8fc23a524cf28d31
Author: Xisco Fauli 
Date:   Tue Jun 19 17:12:09 2018 +0200

tdf#118240 Filter category in Autocaption as done in insert caption

Change-Id: I138a47419a7c18f59ecc1e0935b669546fcee6e6
Reviewed-on: https://gerrit.libreoffice.org/56115
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens 

diff --git a/sw/source/ui/config/optload.cxx b/sw/source/ui/config/optload.cxx
index 11525600f450..dc05b9f35417 100644
--- a/sw/source/ui/config/optload.cxx
+++ b/sw/source/ui/config/optload.cxx
@@ -462,12 +462,14 @@ SwCaptionOptPage::SwCaptionOptPage(vcl::Window* pParent, 
const SfxItemSet& rSet)
 , m_sNone(SwResId(SW_STR_NONE))
 , pMgr(new SwFieldMgr())
 , bHTMLMode(false)
+, m_aTextFilter(m_sNone)
 {
 get(m_pCheckLB, "objects");
 get(m_pLbCaptionOrder, "captionorder");
 get(m_pPreview, "preview");
 get(m_pSettingsGroup, "settings");
 get(m_pCategoryBox, "category");
+m_pCategoryBox->SetTextFilter(_aTextFilter);
 get(m_pFormatText, "numberingft");
 get(m_pFormatBox, "numbering");
 get(m_pNumberingSeparatorFT, "numseparatorft");
diff --git a/sw/source/uibase/inc/cption.hxx b/sw/source/uibase/inc/cption.hxx
index 3942fe4e0293..037debb11369 100644
--- a/sw/source/uibase/inc/cption.hxx
+++ b/sw/source/uibase/inc/cption.hxx
@@ -35,18 +35,6 @@
 class SwFieldMgr;
 class SwView;
 
-class TextFilterAutoConvert : public TextFilter
-{
-private:
-OUString m_sLastGoodText;
-OUString m_sNone;
-public:
-TextFilterAutoConvert(const OUString )
-: m_sNone(rNone)
-{
-}
-virtual OUString filter(const OUString ) override;
-};
 
 class SwCaptionDialog : public SvxStandardDialog
 {
diff --git a/sw/source/uibase/inc/optload.hxx b/sw/source/uibase/inc/optload.hxx
index fb84a7b5ff2d..ef6f828b67e9 100644
--- a/sw/source/uibase/inc/optload.hxx
+++ b/sw/source/uibase/inc/optload.hxx
@@ -43,6 +43,19 @@ public:
 static FieldUnit GetValue(sal_uInt32 i);
 };
 
+class TextFilterAutoConvert : public TextFilter
+{
+private:
+OUString m_sLastGoodText;
+OUString m_sNone;
+public:
+TextFilterAutoConvert(const OUString )
+: m_sNone(rNone)
+{
+}
+virtual OUString filter(const OUString ) override;
+};
+
 class SwLoadOptPage : public SfxTabPage
 {
 private:
@@ -170,6 +183,8 @@ private:
 SwFieldMgr* pMgr;
 bool bHTMLMode;
 
+TextFilterAutoConvert m_aTextFilter;
+
 DECL_LINK(SelectHdl, ComboBox&, void);
 DECL_LINK(SelectListBoxHdl, ListBox&, void);
 DECL_LINK(ModifyHdl, Edit&, void);
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-commits] core.git: sw/qa sw/source

2018-06-24 Thread Serge Krot
 sw/qa/extras/uiwriter/data/tdf113877_blank.odt |binary
 sw/qa/extras/uiwriter/data/tdf113877_blank_ownStandard.odt |binary
 sw/qa/extras/uiwriter/uiwriter.cxx |   68 +
 sw/source/core/txtnode/ndtxt.cxx   |   43 
 4 files changed, 110 insertions(+), 1 deletion(-)

New commits:
commit baf3cec77db5f03200c038101e77720fae2ffba3
Author: Serge Krot 
Date:   Mon Jun 18 18:15:55 2018 +0200

tdf#113877 Insert doc: merge list into text with specifc style

When inserting document, in the current position the text could have custom
style but really it is the same Standard style. Therefore we should not
merge first inserted node into the insert position and just overwrite
style in the insert position with text style from the inserted node.

Change-Id: Ib67c56bed3d30f356f83dc0b4d4a1710def10853
Reviewed-on: https://gerrit.libreoffice.org/56052
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens 

diff --git a/sw/qa/extras/uiwriter/data/tdf113877_blank.odt 
b/sw/qa/extras/uiwriter/data/tdf113877_blank.odt
new file mode 100755
index ..741d7d5e6d0a
Binary files /dev/null and b/sw/qa/extras/uiwriter/data/tdf113877_blank.odt 
differ
diff --git a/sw/qa/extras/uiwriter/data/tdf113877_blank_ownStandard.odt 
b/sw/qa/extras/uiwriter/data/tdf113877_blank_ownStandard.odt
new file mode 100755
index ..3dbebda6f93c
Binary files /dev/null and 
b/sw/qa/extras/uiwriter/data/tdf113877_blank_ownStandard.odt differ
diff --git a/sw/qa/extras/uiwriter/uiwriter.cxx 
b/sw/qa/extras/uiwriter/uiwriter.cxx
old mode 100644
new mode 100755
index d2086048ad94..e6ab7cdaf515
--- a/sw/qa/extras/uiwriter/uiwriter.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter.cxx
@@ -302,6 +302,8 @@ public:
 void testTdf72942();
 void testTdf113877();
 void testTdf113877NoMerge();
+void testTdf113877_default_style();
+void testTdf113877_Standard_style();
 void testMsWordCompTrailingBlanks();
 void testCreateDocxAnnotation();
 void testTdf107976();
@@ -496,6 +498,8 @@ public:
 CPPUNIT_TEST(testTdf72942);
 CPPUNIT_TEST(testTdf113877);
 CPPUNIT_TEST(testTdf113877NoMerge);
+CPPUNIT_TEST(testTdf113877_default_style);
+CPPUNIT_TEST(testTdf113877_Standard_style);
 CPPUNIT_TEST(testMsWordCompTrailingBlanks);
 CPPUNIT_TEST(testCreateDocxAnnotation);
 CPPUNIT_TEST(testTdf107976);
@@ -5577,6 +5581,70 @@ void SwUiWriterTest::testTdf113877NoMerge()
 CPPUNIT_ASSERT(listId6 != listId7);
 }
 
+// Related test to testTdf113877(): Inserting into empty document a new 
document with list.
+// Insert position has NO its own paragraph style ("Standard" will be used).
+//
+// Resulting document should be the same for following tests:
+// - testTdf113877_default_style()
+// - testTdf113877_Standard_style()
+//
+void SwUiWriterTest::testTdf113877_default_style()
+{
+load(DATA_DIRECTORY, "tdf113877_blank.odt");
+
+// set a page cursor into the end of the document
+uno::Reference xModel(mxComponent, uno::UNO_QUERY);
+uno::Reference 
xTextViewCursorSupplier(xModel->getCurrentController(), uno::UNO_QUERY);
+uno::Reference 
xCursor(xTextViewCursorSupplier->getViewCursor(), uno::UNO_QUERY);
+xCursor->jumpToEndOfPage();
+
+// insert the same document at current cursor position
+{
+const OUString insertFileid = 
m_directories.getURLFromSrc(DATA_DIRECTORY) + 
"tdf113877_insert_numbered_list_abcd.odt";
+uno::Sequence 
aPropertyValues(comphelper::InitPropertySequence({ { "Name", 
uno::makeAny(insertFileid) } }));
+lcl_dispatchCommand(mxComponent, ".uno:InsertDoc", aPropertyValues);
+}
+
+const OUString listId1 = getProperty(getParagraph(1), "ListId");
+const OUString listId2 = getProperty(getParagraph(2), "ListId");
+const OUString listId3 = getProperty(getParagraph(3), "ListId");
+
+CPPUNIT_ASSERT_EQUAL(listId1, listId2);
+CPPUNIT_ASSERT_EQUAL(listId1, listId3);
+}
+
+// Related test to testTdf113877(): Inserting into empty document a new 
document with list.
+// Insert position has its own paragraph style derived from "Standard", but 
this style is the same as "Standard".
+//
+// Resulting document should be the same for following tests:
+// - testTdf113877_default_style()
+// - testTdf113877_Standard_style()
+//
+void SwUiWriterTest::testTdf113877_Standard_style()
+{
+load(DATA_DIRECTORY, "tdf113877_blank_ownStandard.odt");
+
+// set a page cursor into the end of the document
+uno::Reference xModel(mxComponent, uno::UNO_QUERY);
+uno::Reference 
xTextViewCursorSupplier(xModel->getCurrentController(), uno::UNO_QUERY);
+uno::Reference 
xCursor(xTextViewCursorSupplier->getViewCursor(), uno::UNO_QUERY);
+xCursor->jumpToEndOfPage();
+
+// insert the same document at current cursor position
+{
+const OUString insertFileid = 
m_directories.getURLFromSrc(DATA_DIRECTORY) + 

[Libreoffice-bugs] [Bug 100757] Linear solver says 'model is infeasible', when real problem is non-linearity

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100757

--- Comment #5 from Aron Budea  ---
Thomas, Julien, did you open Options... in the Solver dialog, and switch to
LibreOffice (or LibreOfficeDev) Linear Solver?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 112689] Replace chained O(U)StringBuffer::append() with operator+

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112689

harsh raj <3467ha...@gmail.com> changed:

   What|Removed |Added

   Assignee|3467ha...@gmail.com |libreoffice-b...@lists.free
   ||desktop.org

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 112689] Replace chained O(U)StringBuffer::append() with operator+

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112689

harsh raj <3467ha...@gmail.com> changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |3467ha...@gmail.com
   |desktop.org |

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118241] FILEOPEN XLSX Basic code with CreateObject("Scripting.FileSystemObject") and “For Each ” loop does not work

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118241

--- Comment #3 from himajin100...@gmail.com ---
Created attachment 143078
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143078=edit
reproducible document with simpler code

DON' FORGET TO PUT SOME FILES in C:\lolog 
I had 12 files there

Expected Result(in Excel VBA):
True

Actual Result(in LibreOffice StarBasic):
False

Minor note:
It seems StarBasic Adds "Option VBASupport 1", when it opens .xlsm . This
option is required to get Actual Result. if you don't have this line, you will
encounter a "type mismatch error". Even in this case you will not get the
Expected Result.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: extras/source

2018-06-24 Thread Marco A . G . Pinto
 extras/source/autocorr/lang/pt/DocumentList.xml |   20 
 1 file changed, 20 insertions(+)

New commits:
commit 402481e9024705c16ebc5f9872520c117d3b9abd
Author: Marco A.G.Pinto 
Date:   Fri Jun 22 12:18:40 2018 +0200

Added 20 autocorrect words to pt_PT

Change-Id: Iadff2f580e90487204e1c94a33d59921f4cc1cbe
Reviewed-on: https://gerrit.libreoffice.org/56277
Reviewed-by: Adolfo Jayme Barrientos 
Tested-by: Adolfo Jayme Barrientos 

diff --git a/extras/source/autocorr/lang/pt/DocumentList.xml 
b/extras/source/autocorr/lang/pt/DocumentList.xml
index 55c9918ea75e..820a99b0cadf 100644
--- a/extras/source/autocorr/lang/pt/DocumentList.xml
+++ b/extras/source/autocorr/lang/pt/DocumentList.xml
@@ -37,6 +37,7 @@
 
 
 
+
 
 
 
@@ -55,6 +56,8 @@
 
 
 
+
+
 
 
 
@@ -106,6 +109,7 @@
 
 
 
+
 
 
 
@@ -229,6 +233,7 @@
 
 
 
+
 
 
 
@@ -270,6 +275,8 @@
 
 
 
+
+
 
 
 
@@ -598,6 +605,8 @@
 
 
 
+
+
 
 
 
@@ -675,6 +684,7 @@
 
 
 
+
 
 
 
@@ -871,6 +881,7 @@
 
 
 
+
 
 
 
@@ -891,6 +902,7 @@
 
 
 
+
 
 
 
@@ -935,6 +947,7 @@
 
 
 
+
 
 
 
@@ -1380,6 +1393,7 @@
 
 
 
+
 
 
 
@@ -1514,6 +1528,7 @@
 
 
 
+
 
 
 
@@ -1637,6 +1652,8 @@
 
 
 
+
+
 
 
 
@@ -1775,6 +1792,7 @@
 
 
 
+
 
 
 
@@ -1783,6 +1801,7 @@
 
 
 
+
 
 
 
@@ -1938,6 +1957,7 @@
 
 
 
+
 
 
 
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-bugs] [Bug 118358] New: Pressed the "X" icon to close an .odt file. Got ta crash message. Windows 10.

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118358

Bug ID: 118358
   Summary: Pressed the "X" icon to close an .odt file. Got ta
crash message. Windows 10.
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: asciab...@aol.com

Pressed the "X" icon to close a >odt file. Got a crash message. Win 10.


crashreport.libreoffice.org/stats/crash_details/f1764cb0-f9be-4e7f-843e-c5d1da6dba2b

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118357] New: Clicking the page number in the status bar should bring up Go to Page dialog

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118357

Bug ID: 118357
   Summary: Clicking the page number in the status bar should
bring up Go to Page dialog
   Product: LibreOffice Online
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ba...@caesar.elte.hu
CC: michael.me...@collabora.com

In the desktop version this works, but not in online.
It should bring up the dialog tunneled from core.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118357] Clicking the page number in the status bar should bring up Go to Page dialog

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118357

Aron Budea  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118329] Chart for a table with three columns incorrectly extrapolates data for date range

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118329

V Stuart Foote  changed:

   What|Removed |Added

  Component|Calc|Chart
Summary|Diagram for a table with|Chart for a table with
   |three columns adds  |three columns incorrectly
   |fictitious entries  |extrapolates data for date
   ||range

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118329] Diagram for a table with three columns adds fictitious entries

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118329

V Stuart Foote  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|NEW
 Resolution|NOTABUG |---

--- Comment #5 from V Stuart Foote  ---
Will set this new then. Not clear what is expected behavior, but neither
setting the whole first column to dates, or forcing the actual date cells
(A3-A27) to be Date (de-CH) is allowing the X-Axis -> Scale "automatic" to pick
up correct "Date" format.

With the Scale automatic, the Date -> Minimum of the range is being
extrapolated.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: vcl/source

2018-06-24 Thread Saurav Chirania
 vcl/source/uitest/uiobject.cxx |   12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

New commits:
commit cb7e2b80022928b80a27fc6d71ff0721dbe6f601
Author: Saurav Chirania 
Date:   Fri Jun 22 20:46:34 2018 +0530

uitest logger: some changes in log statements

These changes will allow the interpreter introduced in
gerrit change number 56120
to understand these log statements.

Change-Id: I68a406cd19bbe1cfe5b6563025348263d564d5af
Reviewed-on: https://gerrit.libreoffice.org/56305
Tested-by: Jenkins
Reviewed-by: Markus Mohrhard 

diff --git a/vcl/source/uitest/uiobject.cxx b/vcl/source/uitest/uiobject.cxx
index e5ac0895dea8..b098205470eb 100644
--- a/vcl/source/uitest/uiobject.cxx
+++ b/vcl/source/uitest/uiobject.cxx
@@ -951,7 +951,8 @@ OUString ListBoxUIObject::get_action(VclEventId nEvent) 
const
 {
 sal_Int32 nPos = mxListBox->GetSelectedEntryPos();
 return this->get_type() + " Action:SELECT Id:" + mxListBox->get_id() +
-" POS:" + OUString::number(nPos) + " Parent:" + 
get_top_parent(mxListBox)->get_id();
+" Parent:" + get_top_parent(mxListBox)->get_id() +
+" {\"POS\": \"" + OUString::number(nPos) + "\"}";
 }
 else if (nEvent == VclEventId::ListboxFocus)
 {
@@ -1026,8 +1027,9 @@ OUString ComboBoxUIObject::get_action(VclEventId nEvent) 
const
 {
 sal_Int32 nPos = mxComboBox->GetSelectedEntryPos();
 return this->get_type() + " Action:SELECT Id:" +
-mxComboBox->get_id() + " POS:" + OUString::number(nPos) +
-" Parent:" + get_top_parent(mxComboBox)->get_id();
+mxComboBox->get_id() +
+" Parent:" + get_top_parent(mxComboBox)->get_id() +
+" {\"POS\": \"" + OUString::number(nPos) + "\"}";
 }
 else
 return WindowUIObject::get_action(nEvent);
@@ -1177,8 +1179,8 @@ OUString TabControlUIObject::get_action(VclEventId 
nEvent) const
 {
 sal_Int32 nPageId = mxTabControl->GetCurPageId();
 return this->get_type() + " Action:SELECT Id:" + 
mxTabControl->get_id() +
-" POS:" + OUString::number(mxTabControl->GetPagePos(nPageId)) +
-" Parent:" + get_top_parent(mxTabControl)->get_id();
+" Parent:" + get_top_parent(mxTabControl)->get_id() +
+" {\"POS\": \"" + 
OUString::number(mxTabControl->GetPagePos(nPageId)) + "\"}";
 }
 else
 return WindowUIObject::get_action(nEvent);
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-commits] core.git: external/liborcus sc/source

2018-06-24 Thread Vikas Mahato
 external/liborcus/0001-add-xml-path.patch |  119 ++
 sc/source/filter/inc/orcusinterface.hxx   |4 -
 sc/source/filter/orcus/interface.cxx  |8 +-
 sc/source/filter/orcus/xmlcontext.cxx |2 
 4 files changed, 126 insertions(+), 7 deletions(-)

New commits:
commit 9313dcc624e3898d2b10f8b0d6efba403a190c88
Author: Vikas Mahato 
Date:   Sun Jun 24 20:38:12 2018 +0530

Changes to orcus for implementing XML data provider

Change-Id: I70075f4240c75f0f46260bb77b160f0b75d6ae94
Reviewed-on: https://gerrit.libreoffice.org/56354
Tested-by: Jenkins
Reviewed-by: Markus Mohrhard 

diff --git a/external/liborcus/0001-add-xml-path.patch 
b/external/liborcus/0001-add-xml-path.patch
new file mode 100644
index ..3f9a16bb880f
--- /dev/null
+++ b/external/liborcus/0001-add-xml-path.patch
@@ -0,0 +1,119 @@
+diff --git a/include/orcus/xml_structure_tree.hpp 
b/include/orcus/xml_structure_tree.hpp
+index 
58cabfd116fa24e35ff27cf8d7512b6e73df33f4..c88808d24bd74c175fa4017328d3e54b4c588c5e
 100644
+--- a/include/orcus/xml_structure_tree.hpp
 b/include/orcus/xml_structure_tree.hpp
+@@ -127,6 +127,20 @@ public:
+ size_t get_xmlns_index(xmlns_id_t ns) const;
+
+ std::string get_xmlns_short_name(xmlns_id_t ns) const;
++
++/**
++ * Get a XPath like ID for the element inside of the XML tree.
++ *
++ */
++std::string get_path() const;
++
++/**
++ * Select an element by a path expression. The path expression may be
++ * generated by xml_structure_tree::walker::get_path.
++ *
++ * @param path a simple XPath like expression
++ */
++element select_by_path(const std::string& path);
+ };
+
+ xml_structure_tree(xmlns_context& xmlns_cxt);
+diff --git a/src/liborcus/xml_structure_tree.cpp 
b/src/liborcus/xml_structure_tree.cpp
+index 
2778bc05f32841a9441bf471913872e119256895..6622bc57cd2595f12bba80d4bbdb5c24cd6e7bc6
 100644
+--- a/src/liborcus/xml_structure_tree.cpp
 b/src/liborcus/xml_structure_tree.cpp
+@@ -12,6 +12,7 @@
+ #include "orcus/exception.hpp"
+
+ #include "orcus/string_pool.hpp"
++#include "string_helper.hpp"
+
+ #include 
+ #include 
+@@ -275,6 +276,15 @@ struct xml_structure_tree_impl
+ {
+ delete mp_root;
+ }
++
++std::string get_element_str(const xml_structure_tree::entity_name& name) 
const
++{
++ostringstream ss;
++if (m_xmlns_cxt.get_index(name.ns) != index_not_found)
++ss << m_xmlns_cxt.get_short_name(name.ns) << ":";
++ss << name.name;
++return ss.str();
++}
+ };
+
+ struct xml_structure_tree::walker_impl
+@@ -423,6 +433,66 @@ string 
xml_structure_tree::walker::get_xmlns_short_name(xmlns_id_t ns) const
+ return mp_impl->m_parent_impl.m_xmlns_cxt.get_short_name(ns);
+ }
+
++string xml_structure_tree::walker::get_path() const
++{
++ostringstream ss;
++for (auto& element : mp_impl->m_scopes)
++{
++ss << "/" << mp_impl->m_parent_impl.get_element_str(element.name);
++}
++
++return ss.str();
++}
++
++xml_structure_tree::element xml_structure_tree::walker::select_by_path(const 
std::string& path)
++{
++pstring p(path);
++std::vector parts = string_helper::split_string(p, '/');
++if (parts.empty())
++throw general_error("invalid format for path");
++
++// string_helper::split_string will create an empty first element due to 
leading '/'
++if (parts[0] != "")
++{
++throw general_error("invalid format for path");
++}
++else
++{
++parts.erase(parts.begin());
++}
++
++if (parts.empty())
++throw general_error("invalid format for path");
++
++element_ref root_ref(mp_impl->mp_root->name, _impl->mp_root->prop);
++if (pstring(mp_impl->m_parent_impl.get_element_str(root_ref.name)) != 
parts[0])
++throw general_error("path does not match any element");
++
++std::vector scopes;
++scopes.push_back(root_ref);
++
++for (size_t i = 1; i < parts.size(); ++i)
++{
++const elem_prop& prop = *scopes.back().prop;
++bool found = false;
++for (auto& child : prop.child_elements)
++{
++if (pstring(mp_impl->m_parent_impl.get_element_str(child.first)) 
== parts[i])
++{
++scopes.emplace_back(child.first, child.second);
++found = true;
++break;
++}
++}
++if (!found)
++throw general_error("path does not match any element");
++}
++
++std::swap(mp_impl->m_scopes, scopes);
++const element_ref& ref = mp_impl->m_scopes.back();
++return element(ref.name, ref.prop->repeat);
++}
++
+ xml_structure_tree::xml_structure_tree(xmlns_context& xmlns_cxt) :
+ mp_impl(new xml_structure_tree_impl(xmlns_cxt)) {}
diff --git a/sc/source/filter/inc/orcusinterface.hxx 
b/sc/source/filter/inc/orcusinterface.hxx

[Libreoffice-bugs] [Bug 118337] Evenly fill space between repeated character-fill in number formats

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118337

--- Comment #2 from Aron Budea  ---
(In reply to Laurent BP from comment #1)
> From my point of view, alignment of decimal separator requires using a
> monospaced font.

This bug report isn't really about alignment of decimal separator, but that's a
good point to check. In fact the alignment of decimal separator used to be fine
in versions < 5.3 even with a non-monospace font like Liberation Sans, but it
changed in 5.3, and I'm not sure that's correct.

Can be seen easily with the following example (use locale-specific decimal
separator instead of "."):
111.111
222.222

The above issue seems to be the same as bug 118221.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118356] GTK3: opening sort dialog takes a long time

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118356

Jean-Baptiste Faure  changed:

   What|Removed |Added

   Keywords||regression

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118356] New: GTK3: opening sort dialog takes a long time

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118356

Bug ID: 118356
   Summary: GTK3: opening sort dialog takes a long time
   Product: LibreOffice
   Version: 6.1.0.0.beta2+
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jbfa...@libreoffice.org

Step to reproduce:
1/ open a new empty file in Calc
2/ click the sort button or menu Data > Sort...

The dialog take a very long time to appear if the backend is GTK3. It is
instantaneous with backend GTK2. With GTK3, it does not depend if OpenGL is
enable or not.
Reproducible with current master too.

Does not happen in LO 6.0.4, so regression.

Version: 6.1.0.0.beta2+
Build ID: 1c3ed9156690577f28eda3d0638e89c64ad231d8
Threads CPU : 4; OS : Linux 4.4; UI Render : par défaut; VCL: gtk3; 
Ubuntu_16.04_x86-64
Locale : fr-FR (fr_FR.UTF-8); Calc: threaded

Version: 6.2.0.0.alpha0+
Build ID: 03c14b836ab03735870b36c2388fd88782b97550
CPU threads: 4; OS: Linux 4.4; UI render: GL; VCL: gtk2; 
Ubuntu_16.04_x86-64
Locale: fr-FR (fr_FR.UTF-8); Calc: threaded

Best regards. JBF

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118354] Draw just closes if to try select table in file

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118354

kompilainenn <79045_79...@mail.ru> changed:

   What|Removed |Added

   Keywords||bibisectRequest

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118354] Draw just closes if to try select table in file

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118354

kompilainenn <79045_79...@mail.ru> changed:

   What|Removed |Added

   Keywords||regression

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-ux-advise] [Bug 118355] Menu Styles miss "Body Text" entry in Writer

2018-06-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118355

--- Comment #1 from Dieter Praas  ---
In LO 6.1 next style is "Text Body", which is in the list of styles.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


  1   2   3   4   >