[Libreoffice-bugs] [Bug 129164] Missing Menu Format/Zone/Define

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129164

--- Comment #6 from y.leme...@wanadoo.fr ---
(In reply to Julien Nabet from comment #5)
> Heiko/Xisco: I don't remember "print area" is present in Writer but am not
> sure.
> Any thoughts here?

I think that you ask the right question : is Zone/Definir an actual option of
writer ?
If not (Zone/Definir is only available under calc), that bug is NOT a bug ;
only a dream of my mind. Please will you forgive me and close the thread ?

In fact, under writer, restriction of impress is possible page by page, NOT
zone by zone

Thank you for your help !
y.leme...@wanadoo.fr

-- 
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 129203] Split Cell Recommendations

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129203

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org
   Keywords|needsUXEval |
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #1 from Heiko Tietze  ---
Sounds reasonable. We have to implement it with check boxes instead the radio
buttons and spinners next to it. Or just the spinners as 1 could mean no
change.

-- 
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 129058] [UX] Repeat shortcut (Ctrl+Shift+Y) is too far for short-finger users using en (qwerty) keyboard

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129058

--- Comment #4 from Heiko Tietze  ---
>From the design meeting:

   + I always use TWO hands for that keyboard shortcuts =) (Roman)
   + keyboard issue for English, see also bug 115052 for other than English 
   + Excel (or all MSO) uses F4 (or ctrl+Y) for "repeat last action" (but the
 same key also for redo)
   + shift+ctrl+r? - cannot press it without hurting myself, ctrl+alt+r works
   + alt+ should be reserved for hotkeys
   + keep it - common, usable (maybe not for everyone), consistent (Heiko)
   + more opinions needed (Roman)
   => keep it boiling for a week

-- 
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 33173] Tabbed UI (Writer): Division/section-per-tab (similar to Lotus WordPro)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33173

--- Comment #43 from Heiko Tietze  ---
No question that we have to improve the Navigator, a proposal is here [1]. But
despite all the shortcommings the basic way of dealing with content is working
well. From the WYSIWYG point of view I doubt that putting content in tabbed
sections is working well for the majority of users. And there are also many
requests to have tabs for multiple documents in one app that would clash with
your proposal.

[1]
https://design.blog.documentfoundation.org/2016/07/31/how-the-navigator-may-support-object-handling-in-libreoffice-draw/

-- 
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 129221] Numbered bullets don't restart after header in importred .docx file

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129221

Dieter Praas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dgp-m...@gmx.de
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from Dieter Praas  ---
Thank you for reporting the bug. Please attach a sample docx-file, as this
makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive
information before attaching it)

-- 
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 99477] EDITING: "View> Freeze Cells> Freeze First..." does not work if the sheet is already frozen

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99477

Heiko Tietze  changed:

   What|Removed |Added

URL|https://www.hpsupportphonen |
   |umbers.com/how-to-fix-error |
   |-code-49-4c02/  |

-- 
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 128912] Document property "Keywords" are exported incorrectly to PDF property (extra quotes)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128912

Dieter Praas  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||dgp-m...@gmx.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
  Component|Writer  |Printing and PDF export

--- Comment #1 from Dieter Praas  ---
I confirm the described behaviour with

Version: 6.5.0.0.alpha0+ (x64)
Build ID: 89f0af144c18efafe2573801641689a1432c0cae
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-GB
Calc: threaded

-- 
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 125257] [META] Tip of the day

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125257
Bug 125257 depends on bug 128712, which changed state.

Bug 128712 Summary: Is the explanation  clear in tip nr. 14 about selection 
zooming?
https://bugs.documentfoundation.org/show_bug.cgi?id=128712

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
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 126754] FONT FEATURES DIALOG: Wrong OpenType tag for fractions in "font features" dialog

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126754

Dieter Praas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #4 from Dieter Praas  ---
(In reply to Tobias Hemm from comment #3)
> What RGB stated is absolutely correct.

=> Status 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 129215] PDF Hyperlink in writer not resolving.

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129215

Dieter Praas  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from Dieter Praas  ---
Steve, thank you for reporting the bug. Could you please

a) try to reproduce it with the latest version of LibreOffice from
https://www.libreoffice.org/download/libreoffice-fresh/ ?

and (if this doesn't solve your problem)

b) provide a clearer set of step-by-step instructions on how to reproduce the
problem or add a sample document.

Please change it back to 'UNCONFIRMED' if the bug is still present in the
latest version. Change to RESOLVED WORKSFORME, if the problem went away.

-- 
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 127472] Translation error: The German word "Datenbank" is not equivalent to "date base"

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127472

--- Comment #3 from Dieter Praas  ---
(In reply to Julien Nabet from comment #2)
> Dieter/Andreas/Sophia/Thomas: any thoughts about a correct translation here?

I prefer "Basisdatum": It's close to the English word and it's meaning is clear
within the specific context.

-- 
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 127305] Auto-fill QR Code dialog Box for selected text from the document

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127305

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:6.5.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 127305] Auto-fill QR Code dialog Box for selected text from the document

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127305

--- Comment #2 from Commit Notification 
 ---
shubham goyal committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/704a558b8689beb1a83a3e2d21481e0ea118e134

tdf#127305 display selected text in URL field QR Code Dialog

It will be available in 6.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://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 127022] menu bar is broken in RTL interface on Windows

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127022

Boaz Dodin  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 99477] EDITING: "View> Freeze Cells> Freeze First..." does not work if the sheet is already frozen

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99477

Ronan Smith  changed:

   What|Removed |Added

URL||https://www.hpsupportphonen
   ||umbers.com/how-to-fix-error
   ||-code-49-4c02/

--- Comment #27 from Ronan Smith  ---
The post is informative and the topic is discussed is really good keep on
sharing new things. If you facing any problem regarding of HP Error 49.4 c02
visite our website click here
https://www.hpsupportphonenumbers.com/how-to-fix-error-code-49-4c02/

-- 
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 128466] Not possible to paste a picture from the clipboard in a spreadsheet in calc on iOS

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128466

--- Comment #5 from Commit Notification 
 ---
Tor Lillqvist committed a patch related to this issue.
It has been pushed to "libreoffice-6-4":

https://git.libreoffice.org/core/commit/c45acdcdd022a17559b9f7b85790c656a1599339

tdf#128466: Accept also JPEG

It will be available in 6.4.0.1.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://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 128466] Not possible to paste a picture from the clipboard in a spreadsheet in calc on iOS

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128466

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:6.5.0|target:6.5.0 target:6.4.0.1

-- 
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 129222] New: + transfer data to new tab

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129222

Bug ID: 129222
   Summary: + transfer data to new tab
   Product: LibreOffice
   Version: 6.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: toddandma...@zoho.com

Dear Libre Office,

You do have a Windows version of Calc, so this might be a "Feature, not a
"Bug".

1) open a fresh, blank spreadsheet

2) in 1:1 put "one" is a text.  Do not click off the cell

3) go to the bottom left and click the "+" sign to get a new division tab.

Your text will now be transferred to the new tab and removed from the first.

If you click off the cell to save it before clicking the "+" sign, your text
stays where it should.

So the bug is that clicking the "+" sign should close whatever you have open
before creating the new tab.

-T

-- 
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 33173] Tabbed UI (Writer): Division/section-per-tab (similar to Lotus WordPro)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33173

--- Comment #42 from Todd  ---
(In reply to Heiko Tietze from comment #41)
> I don't see the advantage over the Navigator [1] or master documents [2].
> Users who are familiar with one kind of interaction may prefer this but
> there is no requirement missing, AFAICS. So the suggestion is to not change
> what we have (and where other users are familiar with).
> And while we have some interest in the topic, it's at the same time quite
> old and of less importance for the whole product. So setting back to medium.

Heiko,

I am the original porter (OP) of this request.

I do constantly used both.  In my technical opinion, although your are
absolutely correct, both do work, your method is a good 10 times more difficult
to use and is not as intuitive to the user.  Please do not look at this a "we
already have a way, don't fix what is not broken", but as "how can we make this
more user friendly". If you like doing thing the obscure, difficult way, leave
the current method in place as an alternative.

You already support tabs in Calc, so add the feature to Writer should be a
piece of cake.

It would be wonderful if you would institute this request and would EVER fix
the envelope printing, then I and others could FINALLY get off the DEFUNCT Word
Pro, which works better than Writer and has been dead and unsupported for about
20 years or so.

This is what tabs looks like in Calc.  Here are two tabs.  One is "January" and
its 1:1 text is "Month 1"; the second its "February" and its 1:1 text is "Month
02":

   


 
  Month 01
 

   

   


 
  Month 02
 

   


You now have an army of folks also requesting this, so it is time it got
implemented.

Many thanks,
-T

-- 
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 109425] Libreoffice Notebookbar is not exposing accessible events needed for screen reader users.

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109425

--- Comment #39 from V Stuart Foote  ---
@Andreas, Jim, *

So testing on Windows 10 Home 64-bit en-US with NVDA 2019.2 and todays TB77
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 790b5de8941d8f8d98c73ed1343289d7220211ad
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded

The additional GTK Focus events have restored reasonable keyboard navigation to
the NB, had a few sequencing issues within groupings, but so much closer now.
Thanks!

But for some reason the focus A11Y 'accessible events' are not fired when
advancing through the NB in its nested position in the app frame.  But if you
reduce the width of the frame, collapsing the NB, the popup bar exposed with
the 'chevrons' exposes all of the accessible events.

What is different between controls held on the NB, versus the same controls
held in the overflow 'chevrons' popup that allows the UNO controls 'accessible
event' to fire?

And otherwise, continue to have issues with a non-functional F10 & F6 movements
when the main menubar is not exposed. Seems too fragile, and prone to losing
track of position in the UI.  No recovery with keyboard, requiring a blind
mouse click into the document canvas to recover focus.

-- 
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 129221] New: Numbered bullets don't restart after header in importred .docx file

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129221

Bug ID: 129221
   Summary: Numbered bullets don't restart after header in
importred .docx file
   Product: LibreOffice
   Version: 6.2.7.1 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: u...@flanagan-consulting.com

Description:
Original Word docx has numbered lists under subheads.  Numbering restarts with
"1" after each subhead.  When opened by LO 6.2.7.1 (from openSuSe) the list
numbering continues through the subheads and does not restart at "1" each time.
Saving file as .odt preserves this error.

Steps to Reproduce:
1.  Open .docx file
2.  Numbered lists continue through subheads
3.

Actual Results:
Numbered lists do not restart at "1" after subhead

Expected Results:
Numbered lists start with "1" after a header.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Have seen his file display by Word and numbering restarts after headers.

Version: 6.2.7.1
Build ID: 20(Build:1)
CPU threads: 12; OS: Linux 4.12; UI render: default; VCL: kde5; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

-- 
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 58941] Support enabling optional smart font features

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58941

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
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 71732] [META] Bugs related to text rendering, typography and font features in LO

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=71732

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||129219


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=129219
[Bug 129219] Further refinement of OpenType/Graphite Font features in the
“Character” dialogue
-- 
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 129219] Further refinement of OpenType/Graphite Font features in the “Character” dialogue

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129219

V Stuart Foote  changed:

   What|Removed |Added

 CC||dr.khaled.ho...@gmail.com,
   ||heiko.tietze@documentfounda
   ||tion.org,
   ||martin_hos...@sil.org,
   ||qui...@gmail.com,
   ||vstuart.fo...@utsa.edu
 Status|UNCONFIRMED |NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=58
   ||941
Summary|Different Implementation of |Further refinement of
   |OpenType Font Features in   |OpenType/Graphite Font
   |the “Character” Dialogue|features in the “Character”
   ||dialogue
 Blocks||71732
Version|6.2.8.2 release |6.2.0.3 release
 Ever confirmed|0   |1

--- Comment #3 from V Stuart Foote  ---
The work referred to was done for bug 58941

Example panels from other applications for handling OpenType features, and some
relevant discussion of technical limitations of current Graphite modeled
solution implemented with HarfBuzz libs. 

But sure, probably room for additional refinement of the GUI.

@Hieko, should this go through additional UX/Design work-up? Or, just leave it
to our sage devs...


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=71732
[Bug 71732] [META] Bugs related to text rendering, typography and font features
in LO
-- 
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 129212] Hints is not word wrapped into the hint window

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129212

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||vstuart.fo...@utsa.edu

--- Comment #1 from V Stuart Foote  ---
fixed for 6.3.4 release

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

-- 
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 113050] FILEOPEN: PDF freezes Draw, 46-pages, 1.2 MB, created by Distiller

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113050

--- Comment #9 from QA Administrators  ---
Dear Mike,

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 101674] FILEOPEN PDF Massive low performance trying to make simple edits on a complex, one page PDF

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101674

--- Comment #6 from QA Administrators  ---
Dear E.Mi,

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 119873] Useless padding in video object

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119873

--- Comment #6 from QA Administrators  ---
Dear Ingo von Borstel,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
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 121211] IMPORT: Calc range 'table definition only option selected' fails to create table

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121211

--- Comment #8 from QA Administrators  ---
Dear Robert Großkopf,

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 121756] Empty area under embedded table after redo (disappearing after clicking into the embedded table)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121756

--- Comment #5 from QA Administrators  ---
Dear Telesto,

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 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121210

--- Comment #14 from QA Administrators  ---
Dear Robert Großkopf,

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 89887] FileOpen: Drawing is not visible in DOCX file

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89887

--- Comment #10 from QA Administrators  ---
Dear Sergey Kozyr,

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 128843] enhancement: if text is already in a section, ask for confirmation before linking a file in the section

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128843

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
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 128942] Remove frame around rotation wheel within Position and Size / Ratation dialog

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128942

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
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 121557] Printing document with frame and controls

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121557

--- Comment #4 from QA Administrators  ---
Dear libreoffice,

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 61424] CONFIGURATION: Normal view not possible with custom short cut key

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=61424

--- Comment #24 from QA Administrators  ---
Dear bugquestcontri,

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 121209] TABLEWIZARD: Field type isn't correctly recognized for Integer and Boolean using automatic field type recognition

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121209

--- Comment #6 from QA Administrators  ---
Dear Robert Großkopf,

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 121526] DOCX Import Textbox inserted in header created with Word moves down in Writer

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121526

--- Comment #5 from QA Administrators  ---
Dear NISZ LibreOffice Team,

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 120978] dxf file missing text

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120978

--- Comment #5 from QA Administrators  ---
Dear david chen,

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 121524] DOCX Import 5cm high Footer created with Word become disabled in Writer

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121524

--- Comment #5 from QA Administrators  ---
Dear NISZ LibreOffice Team,

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 121834] FILEOPEN DOCX Word Header looks different in Writer

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121834

--- Comment #5 from QA Administrators  ---
Dear Ettore Atalan,

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 119662] FILEOPEN PPTX embed EMF picture not displayed correctly

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119662

--- Comment #7 from QA Administrators  ---
Dear zyl,

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 52234] EDITING: Mouse pointer does not change timely to "move view" when drag modus changes to "without shadow"

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=52234

--- Comment #22 from QA Administrators  ---
Dear sunmoon51,

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 120722] Handles are not scaled properly on higher resolutions

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120722

--- Comment #32 from QA Administrators  ---
Dear 和尚蟹,

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 121548] 100% CPU usage after opening certain DOCX files

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121548

--- Comment #7 from QA Administrators  ---
Dear vsza+tdf,

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 120634] Unexpected change of table content paragraph style when deleting a row

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120634

--- Comment #7 from QA Administrators  ---
Dear Ulrich Gemkow,

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 120418] LibreOffice Base -> Set toolbar view, then switch between options -> Toolbar view returns to the original settings

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120418

--- Comment #12 from QA Administrators  ---
Dear Vera Blagoveschenskaya,

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 96324] Subscript missing in exported SVG (see comment 10)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96324

--- Comment #19 from QA Administrators  ---
Dear u.fuchs,

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 129157] there is a defect in the login page

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129157

--- Comment #2 from David Bowie  ---

Pretty great post. I just stumbled upon your blog and wanted to say that I’ve
truly loved browsing your blog posts.
http://thecomplaintpoint-au.com/lg-complaints-email-phone-number

-- 
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 87720] Default insert image anchor, wrapping, and spacing

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87720

--- Comment #37 from Aron Budea  ---
(In reply to Aron Budea from comment #36)
> Good catch, this has actually been set to "To Character" on master since,
> because of the very annoying bug 87719. The commit should be backported to
> 6.4, because it was introduced after branching 6.4.
And now it is:
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-4=d0aa2dbdf37aefe5b8d096fc5ea50cd13f87c5b0

-- 
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 129190] PIVOT CHARTS do not survive round-trip with flat ODS

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129190

m.a.riosv  changed:

   What|Removed |Added

 OS|Linux (All) |All

-- 
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 123408] the sum of this selection is wrong, an offset of 1/100.

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=123408

m.a.riosv  changed:

   What|Removed |Added

 CC||andrew...@biagionelli.com

--- Comment #4 from m.a.riosv  ---
*** Bug 129220 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 129220] I'm getting a repeatable error with the SUM() function

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129220

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |DUPLICATE

--- Comment #2 from m.a.riosv  ---


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

-- 
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 129127] Crash when sort by column of Excel 97-2003 file with specific data

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129127

Terrence Enger  changed:

   What|Removed |Added

 CC||lo_b...@iseries-guru.com

--- Comment #9 from Terrence Enger  ---
Working on debian-buster with a local build of commit 9ab43aeb,
2019-12-04, I reproduce Julien's SIGSEGV.

However in bibisect-linux-64-6.5 commit 4bea6716 s-h 304368c7, I
merely get an incorrect sort: naming columns by the original
positions:

expected :  B A C E D
observed :  A B C E D

-- 
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 100603] Spreadsheet not calculating properly, sum() not updated with auto-calculate or [f9]; hard-recalc needed

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100603

m.a.riosv  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #5 from m.a.riosv  ---
Works for me.
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 129216] Converting from DOC to DOCX should strip macros.

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129216

Aron Budea  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aron Budea  ---
Bug 108269's fix enabled roundtripping macros.
Bug 125338 has been opened about macros persisting when saved from DOCM to
DOCX, I have added the DOC case there as well, let's close this as dupe.

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

-- 
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 125338] Saving DOC(M) as DOCX doesn't get rid of macro

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125338

Aron Budea  changed:

   What|Removed |Added

 CC||dcnel...@zixcorp.com

--- Comment #6 from Aron Budea  ---
*** Bug 129216 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 97791] Calc:: Copying formulas DIVIDES prior combined Cells

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97791

m.a.riosv  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|NEW |RESOLVED

--- Comment #4 from m.a.riosv  ---
I'm remain thinking not a bug, if we paste, we also past the cell format, so
looks fine breaking the merged.

Reinforcing this idea, using context menu to past the formula doesn't modify
merged for destination cells.

-- 
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 108253] [META] Calc cell formula bugs and enhancements

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108253
Bug 108253 depends on bug 97791, which changed state.

Bug 97791 Summary: Calc:: Copying formulas DIVIDES prior combined Cells
https://bugs.documentfoundation.org/show_bug.cgi?id=97791

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |NOTABUG

-- 
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 108364] [META] Table/Row/Column/Cell management function bugs and enhancements

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108364
Bug 108364 depends on bug 97791, which changed state.

Bug 97791 Summary: Calc:: Copying formulas DIVIDES prior combined Cells
https://bugs.documentfoundation.org/show_bug.cgi?id=97791

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |NOTABUG

-- 
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 125338] Saving DOC(M) as DOCX doesn't get rid of macro

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125338

Aron Budea  changed:

   What|Removed |Added

Summary|Saving DOCM as DOCX doesn't |Saving DOC(M) as DOCX
   |get rid of macro|doesn't get rid of macro

-- 
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 125338] Saving DOCM as DOCX doesn't get rid of macro

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125338

--- Comment #5 from Aron Budea  ---
Created attachment 156343
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156343=edit
Sample DOC w macro

Same thing happens if the source is a DOC with macro. Attaching attachment
133753 converted to DOC in Word as a sample for that.
When converted to DOCX in LO, the macro persists.

-- 
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 97552] unexpected changes in formula references

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97552

m.a.riosv  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

--- Comment #11 from m.a.riosv  ---
There is not patch to fix, so the proper it's resolved as works for me.

-- 
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 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103381
Bug 103381 depends on bug 96977, which changed state.

Bug 96977 Summary: PIVOTTABLE FORMATTING: pivot table uses the formatted column 
label which cause errors when calling GETPIVOTDATA
https://bugs.documentfoundation.org/show_bug.cgi?id=96977

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
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 96977] PIVOTTABLE FORMATTING: pivot table uses the formatted column label which cause errors when calling GETPIVOTDATA

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96977

m.a.riosv  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #4 from m.a.riosv  ---
Works for me.
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 95308] Split indicator appears on top of comments

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=95308

m.a.riosv  changed:

   What|Removed |Added

   Severity|normal  |minor

--- Comment #5 from m.a.riosv  ---
Still
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 95307] Comments shown in wrong position when hovering over comment indicators

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=95307

--- Comment #5 from m.a.riosv  ---
Still
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 93334] [FILEOPEN] Problem importing CSV

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=93334

--- Comment #10 from m.a.riosv  ---
Works in the same way.
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 91192] Writer not recognizing a URL's trailing carat, hash mark, question mark, or backslash

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91192

m.a.riosv  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #9 from m.a.riosv  ---
Works for me.
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 90209] FORMATTING FILESAVE conditional formatting fails to be saved

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90209

--- Comment #5 from m.a.riosv  ---
Now the conditional format is not copied from G26:H26 to G27.
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 84763] Poor performance entering data with conditional formatting

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84763

--- Comment #10 from m.a.riosv  ---
Still
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 83116] Cannot convert dates with fractional seconds >= 0.9995

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83116

m.a.riosv  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #13 from m.a.riosv  ---
Looks works fine now.
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 73120] Cannot Find & Replace for a range, this function works for the entire sheet

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=73120

--- Comment #8 from m.a.riosv  ---
Still
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 71147] FILEOPEN: lwp-files open not or without charts/tables

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=71147

--- Comment #15 from m.a.riosv  ---
General Error, general input/output error
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 68720] FORMATTING: The cells in a column from csv-import that contain the currency symbol is not properly formatted as currency

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=68720

--- Comment #9 from m.a.riosv  ---
Still
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 59391] Naming a cell causes certain references using labeled ranges to go undefined; recalculate/autocalculate

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=59391

--- Comment #7 from m.a.riosv  ---
Still
Version: 6.3.3.2 (x64)
Build ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: en-US
Calc:

-- 
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 104049] Renaming paragraph style in Writer destroys the document

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104049

--- Comment #4 from m.a.riosv  ---
Still
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812
CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: 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 129220] I'm getting a repeatable error with the SUM() function

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129220

Andrew  changed:

   What|Removed |Added

 CC||andrew...@biagionelli.com

--- Comment #1 from Andrew  ---
Created attachment 156342
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156342=edit
Test case demonstrating the bug.

Faulty values are in cells A15 and A17.

-- 
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 129220] New: I'm getting a repeatable error with the SUM() function

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129220

Bug ID: 129220
   Summary: I'm getting a repeatable error with the SUM() function
   Product: LibreOffice
   Version: 6.2.8.2 release
  Hardware: Other
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: andrew...@biagionelli.com

Description:
The sum of 12 numbers using the SUM() function should be exactly 0.11, but
instead comes out to be:  0.1090
Doing an individual sum (A2+A3+...A13) gives the correct 0.11
Worse, the difference between these two gives:  0.00056899 instead
of the expected 0.0010

Details of the actual numbers used is below, in "steps to reproduce".

Detailed version & equipment info:
 - Calc reports:
Version: 6.2.8.2 (x64)
Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
 - Windows reports:
Processor:  Intel Core i5-8265U @ 1.60GHz 1.80 GHz

Steps to Reproduce:
1. In cells A2:A13 I have the following exact numbers (NOT formulas):
-37.12
0
18.56
0
0

0
0
0
18.56

0.11
2. In cell A15 I have:
=IF(A16="","",SUM(A2:A13))
3. In cell A16 I have:
=A2+A3+A4+A5+A6+A7+A8+A9+A10+A11+A12+A13
4. In cell A17 I have:
=IF(A15=A16,"",A16-A15)

5. Now, cells A15-A17 show the following values:
A15:  0.1090
A16:  0.1100
A17:  0.00056899

I tried this in a new spreadsheet (cell A1 is empty).

Actual Results:
A15:  0.1090
A16:  0.1100
A17:  0.00056899


Expected Results:
A15:  0.1100
A16:  0.1100
A17:  0.



Reproducible: Always


User Profile Reset: Yes



Additional Info:
 - LibreOffice Calc Help -> About reports:
Version: 6.2.8.2 (x64)
Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
 - Windows 10 Settings -> About reports:
Processor:  Intel Core i5-8265U @ 1.60GHz 1.80 GHz
Windows 10 Home
Version 1903
OS Build 18362.476

-- 
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 129219] Different Implementation of OpenType Font Features in the “Character” Dialogue

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129219

--- Comment #2 from Tobias Hemm  ---
Created attachment 156341
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156341=edit
Table with OpenType Features to be Implemented

-- 
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 129219] Different Implementation of OpenType Font Features in the “Character” Dialogue

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129219

--- Comment #1 from Tobias Hemm  ---
Created attachment 156340
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156340=edit
Demonstration of Possible Implementation in Character Dialogue

-- 
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 129219] New: Different Implementation of OpenType Font Features in the “Character” Dialogue

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129219

Bug ID: 129219
   Summary: Different Implementation of OpenType Font Features in
the “Character” Dialogue
   Product: LibreOffice
   Version: 6.2.8.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tobiasenthe...@mailbox.org

Description:
I prepared to file an enhancement for LO Writer regarding a graphical
implementation of OpenType features. When I was ready to file the enhancement,
I found that, from Version 6.2, something like that is already available. So I
updated from 6.1 to 6.2 in order to test it.

And I think It’s not badly done. But in my opinion it could be improved a lot.
My idea was to create a new tab called "OpenType" or "OpenType Features" in the
character dialogue. I would make it the second tab. I think this would be
better than "hiding" it below the font size column. These features become more
an more important, which is why I think that they deserve a more prominent
position in a separate tab and more space.

Furthermore, my suggestion would have been to not only group the features in a
sensible way in order to provide a clear and comprehensible overview, but also
to always show all features and "grey out" the ones not-available in a font.

The attached table shows a possible way of implementing and grouping the
features. (If multiple active features are possible, you could use checkboxes
(see attached image). If the features of one group are mutually exclusive and
therefore only one choice is allowed, use a bullet. For long lists with one
option, like with character variants, I would use a dropdown menu.)

Please consider that I am not sure about which of these features are mutually
exclusive and which are not, since I am not familiar with all of them from
practice. I am also not sure about how to group and order them. There are many
features. You can also give me a list with all features you implement, if you
want me to do more grouping work.

The list under the following link also provides orientation on grouping etc.:
https://en.wikipedia.org/wiki/List_of_typographic_features
A lot of information about OpenType features can be found under this link.

I attached an image that shows how it could look like, and the above mentioned
table shows the features that I would consider needed. For example, the
features "Swash" and "Contextual Swash" are missing as graphical options, at
the moment. The image is, however, just a demonstration; not all of the
features are considered here.

It would be great if you also implemented a description that appears on mouse
hover, e.g. if you hover over “Small Caps”, there arises the text “Substitutes
lower-case letters with small caps versions” and the abbreviation of the
feature, here "smcp" (also see image). You find these descriptions on the
Wikipedia page (see link above).

By the way, the current German translation of the implemented features is
pretty poor.
Can you please tell me how I can contribute to improving it?
You could also just pass on the attached table to your translation guys. It
contains a column with German translations.

If you need help or support for this implementation, you can ask me.
I am not a programmer, but I can help you find out information about the
OpenType features, and maybe I can test.


Actual Results:
no bug, therefore unnecessary

Expected Results:
no bug, therefore unnecessary


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
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 129218] VIEWING: Some svg are incorrectly rendered (maybe due to css)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129218

Do  changed:

   What|Removed |Added

 CC||domenico@gmail.com

--- Comment #1 from Do  ---
Created attachment 156339
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156339=edit
Mentioned SVG images

Images

-- 
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 129218] New: VIEWING: Some svg are incorrectly rendered (maybe due to css)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129218

Bug ID: 129218
   Summary: VIEWING: Some svg are incorrectly rendered (maybe due
to css)
   Product: LibreOffice
   Version: 6.3.3.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: domenico@gmail.com

Description:
I modify some svg using css in place xml attribute and I used nested translate.
So, some element are not displyed.

Just on Ubuntu version.

Steps to Reproduce:
1. add GaussianDistribugion_old.svg
2. add GaussianDistribugion.svg
3. add Tao_symbol.svg
4. add Luscher.svg

Actual Results:
1. good
2. miss the curve (path)
3. left line is not displyed
4. image is not centred and text is not displayed

Expected Results:
take a look in a browser or on windows


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
OpenGL vendor string: X.Org
OpenGL renderer string: AMD RS780 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.2.1
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 19.2.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

-- 
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 34722] FILEOPEN: Text boxes are not shown in generated .doc documents

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34722

--- Comment #25 from Regina Henschel  ---
(In reply to Julien Nabet from comment #24)
> Regina: taking a look at this one, I noticed that the log
> warn:legacy.osl:271686:271686:sw/source/filter/ww8/ww8graf.cxx:2596: Where
> is the Shape ?
> appeared first with mso_sptNotchedCircularArrow
> 
... 
> pRet is false because "GetCustomShapeContent( aObjData.eShapeType )" from
> line 4433
>  (see
> https://opengrok.libreoffice.org/xref/core/filter/source/msfilter/msdffimp.
> cxx?r=be3a8183#4433) returns nothing.
> 
> Indeed this function doesn't deal with case "mso_sptNotchedCircularArrow"
> (see
> https://opengrok.libreoffice.org/xref/core/svx/source/customshapes/
> EnhancedCustomShapeGeometry.cxx?r=d2702aea#8346)
> but when taking a look at how the other ones are implemented, it seems it's
> quite complex.
> I don't pretend I could succeed but are there some doc about how to
> implement them?

I don't know what you are looking for, and think, I cannot really help you.

The specification of the binary format is in [MS-ODRAW]: Office Drawing Binary
File Format
https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-olp/6ae2fd93-51fc-4e75-a54a-1b175c627b51

The shapes in question are legacy "text box" shapes in MS, German "Textfeld".
Those does not exists in modern docx.

OOo2.4.3 opens the file without problems, OOo3.2 crashes. The texts are legacy
rectangles there, not custom shapes and not frames. They are anchored "at
character". I see only three custom shapes, one for the rounded rectangle at
the top, one for the rectangle with text UNIT PLUS in the middle, and one for
the last rectangle at the bottom. The other lines are single lines.

-- 
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 127312] Erreur EDITER en tête et pied de page

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127312

Julien Nabet  changed:

   What|Removed |Added

 OS|All |Windows (All)
  Component|General |Calc
Product|libexttextcat   |LibreOffice
 CC||serval2...@yahoo.fr
Version|unspecified |6.3.0.4 release

--- Comment #3 from Julien Nabet  ---
Translation of initial description:
following LO update, I got a bug in header/footer customization.

When I enter text in header/footer editor, the text I want to write in central
zone... (there's something lacking here)
When I write my text, either:
- the window closes (there's a typo, it's not "ce ferme" but "se ferme")
- the text regularly changes zone without having typed something else than
letters.

On pc Debian x86-64 with LO Debian package 6.3.3, I don't reproduce this.

Do you reproduce this on a brand new file?
Could you give a try to last LO version 6.3.3?
Also, could you rename your LO directory profile (see
https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?

Also, as Xisco indicated, please provide an example 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 129217] New: Unable to zoom more or less than 100% - 200%

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129217

Bug ID: 129217
   Summary: Unable to zoom more or less than 100% - 200%
   Product: LibreOffice Online
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: franc...@webaf.net

I use Collabora in NextCloud with Yunohost
https://github.com/YunoHost-Apps/collabora_ynh

LOOLWSD
4.0.9 (git hash: 97c4185)
LOKit
Collabora Office 6.0-29 (git hash: e4c7ae6)

And my Calc sheets can only be zoomed in 100% or 200%

And I have some big sheet, coming from Excel that I would see in 50% or less.

But the only possible values are 100 and 200%.

Thanks.

-- 
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 127472] Translation error: The German word "Datenbank" is not equivalent to "date base"

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127472

Julien Nabet  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de,
   ||kain...@gmail.com,
   ||serval2...@yahoo.fr,
   ||sophia.schroeder@libreoffic
   ||e.org, thack...@nexgo.de

--- Comment #2 from Julien Nabet  ---
Dieter/Andreas/Sophia/Thomas: any thoughts about a correct translation here?

-- 
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 125286] FIREBIRD - Base not usable under Windows account with Chinese user name (UTF character support)

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125286

Julien Nabet  changed:

   What|Removed |Added

 CC||sberg...@redhat.com

--- Comment #8 from Julien Nabet  ---
On pc Debian x86-64 with master sources updated today, I created a new user
with non ascii characters and I don't reproduce this so I suppose it's indeed
Windows only.
Here's a codepointer to start:
https://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/firebird/Connection.cxx?r=f853ec31#172
172 m_sFirebirdURL = m_pDatabaseFileDir->GetFileName() + "/firebird.fdb";
173 m_sFBKPath = m_pDatabaseFileDir->GetFileName() + "/firebird.fbk";

I suppose "m_pDatabaseFileDir->GetFileName()" is ko but can't tell more.
We need someone who can build sources on Windows and who has a non ascii
profile directory.

Stephan: comparing method osl_getFileURLFromSystemPath sal/osl/unx/file_url.cxx
and sal/osl/w32/file_url.cxx, I noticed Unix version used RTL_TEXTENCODING_UTF8
and Windows version RTL_TEXTENCODING_ASCII_US, is it expected?
see
https://opengrok.libreoffice.org/xref/core/sal/osl/unx/file_url.cxx?r=0f874472#440

https://opengrok.libreoffice.org/xref/core/sal/osl/w32/file_url.cxx?r=895cd721#892

-- 
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 96228] [META] Container issue for Edit > Repeat actions (Ctrl+Shift+Y) that may be added/corrected

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96228

Thomas Lendo  changed:

   What|Removed |Added

 Depends on||129058


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=129058
[Bug 129058] [UX] Repeat shortcut (Ctrl+Shift+Y) is too far for short-finger
users using en (qwerty) keyboard
-- 
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 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98259

Thomas Lendo  changed:

   What|Removed |Added

 Depends on||129058


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=129058
[Bug 129058] [UX] Repeat shortcut (Ctrl+Shift+Y) is too far for short-finger
users using en (qwerty) keyboard
-- 
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 129058] [UX] Repeat shortcut (Ctrl+Shift+Y) is too far for short-finger users using en (qwerty) keyboard

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129058

Thomas Lendo  changed:

   What|Removed |Added

 Blocks||98259, 96228
 CC||thomas.le...@gmail.com

--- Comment #3 from Thomas Lendo  ---
Context menu was suggested in bug 108859.

A two-hand shortcut is the disadvantage for some languages. There are many
other bugs where non-english languages have problematic shortcuts for users.
This is the other way round.

It seems, MSO has the same shortcut for redo an undone action and repeat an
action.
https://support.office.com/en-us/article/undo-redo-or-repeat-an-action-84bdb9bc-4e23-4f06-ba78-f7b893eb2d28

If any other combination is favored, Y should remain a part of it.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=96228
[Bug 96228] [META] Container issue for Edit > Repeat actions (Ctrl+Shift+Y)
that may be added/corrected
https://bugs.documentfoundation.org/show_bug.cgi?id=98259
[Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
-- 
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 127939] iOS 13: not possible to close presentation when in full screen presentation mode

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127939

--- Comment #8 from Commit Notification 
 ---
Tor Lillqvist committed a patch related to this issue.
It has been pushed to "libreoffice-6-4":

https://git.libreoffice.org/core/commit/662f8d687a56d01e8b192aefdeed4051102d19e4

tdf#127939: Make slideshow touch input work properly again on iOS 13

It will be available in 6.4.0.1.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://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 129185] screen shot with bug description

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129185

patt.i...@hotmail.it changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |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 127939] iOS 13: not possible to close presentation when in full screen presentation mode

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127939

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:6.5.0 target:6.3.5   |target:6.5.0 target:6.3.5
   ||target:6.4.0.1

-- 
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 129213] function CONFIDENCE.NORM has wrong translation in dutch

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129213

Julien Nabet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||serval2...@yahoo.fr
 Ever confirmed|0   |1

--- Comment #1 from Julien Nabet  ---
On pc Debian x86-64 with master sources updated today, I don't reproduce this.

Could you give a try to last stable LO version 6.3.3?
Indeed, 6.0.7 is quite old.

-- 
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 129216] New: Converting from DOC to DOCX should strip macros.

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129216

Bug ID: 129216
   Summary: Converting from DOC to DOCX should strip macros.
   Product: LibreOffice
   Version: 6.3.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dcnel...@zixcorp.com

If you convert a DOC file that has macros to DOCX it leaves macros and seems to
give you a DOCM file that it renames to *.docx

I would expect it to strip the macros and give me a docx or throw an error if
it cannot.

As of LibreOffice 5.3.6.1 it would strip macros.

The command I am using is: soffice --headless --convert-to docx
"Testing_doc_with_macros.doc"

-- 
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 129215] New: PDF Hyperlink in writer not resolving.

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129215

Bug ID: 129215
   Summary: PDF Hyperlink in writer not resolving.
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ste...@gladucalled.com

Inserting a hyperlink to a local PDF file into a Writer doc (odt) will post,
but fails to open because of the following error.

"file:///Users/U15b/5_DOCS/t.481%20Passport%20Lorena%20Application.pdf" is not
an absolute URL that can be passed to an external application to open it.

* removing spaces in the PDF filename does not help.
* this does work with the PDF link inside a spreadsheet (ods) file.

Version info is as follows.
Version: 6.2.8.2
Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Thank you.

=Steve.

-- 
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 108458] Label changes for Toolbar use degrade function listing in the Customize dialog--have duplicate entries on the list

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108458

--- Comment #35 from Jim Raykowski  ---
gtk3 query-tooltip handling part:
https://gerrit.libreoffice.org/#/c/84587/

sal handling is WIP

-- 
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 101513] Making NotebookBar customizable

2019-12-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101513

--- Comment #20 from Commit Notification 
 ---
andreas kainz committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/5799555fbfe378b22b5b36e0e7f9573ec9b26a31

tdf#101513 arrangement of customizeable items in NB groupedbar comp

It will be available in 6.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://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

  1   2   3   >