[Libreoffice-bugs] [Bug 94216] Unable to Install x86 5.0.1.2 on x86-64 W10: Error 1303
https://bugs.documentfoundation.org/show_bug.cgi?id=94216 --- Comment #29 from Michael --- Just did an install of LibreOffice_6.1.1_Win_x64.msi and have the exact same problem. System went to uninstall the old version 6.0 and left behind a directory ../LibreOffice/program then the install failed and the directory can not be erased. $ ls -al Li* LibreOffice: total 32 drwxrwx---+ 1 SYSTEMSYSTEM 0 Oct 23 00:35 . drwxr-x---+ 1 NT SERVICE+TrustedInstaller NT SERVICE+TrustedInstaller 0 Oct 23 01:29 .. drwxr-x--- 1 Unknown+User Unknown+Group 0 Oct 23 00:18 program Had to define a new directory to install and that worked fine. But now I have an empty directory that I cannot erase (even as Administrator). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: ucb/source
ucb/source/ucp/webdav-neon/webdavcontent.cxx | 23 ++-
1 file changed, 2 insertions(+), 21 deletions(-)
New commits:
commit 39bbfa61653ba7c3cca0aed739559914c78edc89
Author: Arkadiy Illarionov
AuthorDate: Mon Oct 22 21:42:09 2018 +0300
Commit: Noel Grandin
CommitDate: Tue Oct 23 07:39:01 2018 +0200
Remove redundant comparisons, copy properties unconditionally
e06afb0c9546ddcde1cedd75f59001396ac6fdf2 follow-up
Change-Id: Ic4449c9424c622aeabbf5be49826d68d95dd93eb
Reviewed-on: https://gerrit.libreoffice.org/62195
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/ucb/source/ucp/webdav-neon/webdavcontent.cxx
b/ucb/source/ucp/webdav-neon/webdavcontent.cxx
index 0c4267e9a728..247b75f990e8 100644
--- a/ucb/source/ucp/webdav-neon/webdavcontent.cxx
+++ b/ucb/source/ucp/webdav-neon/webdavcontent.cxx
@@ -1380,28 +1380,9 @@ uno::Reference< sdbc::XRow > Content::getPropertyValues(
{
sal_Int32 nProps = 0;
sal_Int32 nCount = rProperties.getLength();
-for ( sal_Int32 n = 0; n < nCount; ++n )
+for ( sal_Int32 n = 0; n < nCount; ++n, ++nProps )
{
-const OUString & rName = rProperties[ n ].Name;
-
-std::vector< OUString >::const_iterator end
-= m_aFailedPropNames.end();
-
-auto it = std::find(m_aFailedPropNames.cbegin(), end,
rName);
-if ( it != end )
-{
-// the failed property in cache is the same as the
requested one,
-// so add it to the requested properties list
-aProperties[ nProps ] = rProperties[ n ];
-nProps++;
-}
-
-// XXX something strange happens here: identical code
for different conditions
-if ( it == end )
-{
-aProperties[ nProps ] = rProperties[ n ];
-nProps++;
-}
+aProperties[ nProps ] = rProperties[ n ];
}
aProperties.realloc( nProps );
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Mon, 22 Oct 2018 at 17:25:11 +0200, Lionel Elie Mamane wrote:
> On Mon, Oct 22, 2018 at 04:33:21PM +0200, Guilhem Moulin wrote:
>> On Mon, 22 Oct 2018 at 11:51:35 +0200, Lionel Elie Mamane wrote:
>>> On Wed, Oct 17, 2018 at 09:03:45PM +0200, Guilhem Moulin wrote:
SSH is only used for transport, a git processed is exec()'ed on the
remote just like for git-daemon(1), so the only overhead is
crypto-related. The handshake is a one-off thing, thus negligible
when you're transferring a large amount of data at once; (...) As
for symmetric crypto overhead, (...) the overhead should be
negligible.
>
>>> All I know is that about 1/2/3 years ago ('t was I think in some
>>> coworking space in Brussels, probably a hackfest) I showed Michael
>>> Meeks how to have a separate "push" url (with ssh: protocol) and
>>> "pull" url (with git: protocol) and he was very happy at the
>>> speed-up.
>
>> Might be orthogonal to the git:// vs. https:// vs. ssh://
>> discussion. Gerrit uses JGit as Git implementation, while
>> git-daemon(1) spawns “normal” (C-based) git-upload-pack(1)
>> processes.
>
> For us developers of LibreOffice, and thus consumers of the Gerrit /
> Git service of freedesktop.org and TDF, whether the difference comes
> from the protocol itself or a different git implementation on the
> server to serve the different protocols is intellectually interesting
> (thanks for that!), but materially inconsequential: if using git: will
> be faster, we will use git:.
Following the same logic, you want gerrit.libreoffice.org to serve
content over plain http:// so you can save the two round-trips when you
launch your browser to submit your reviews? Oo
FWIW, we're stuck with git:// for the years to come because there is no
smooth upgrade path for clients; if I were to deploy the service today I
would most likely skip git-daemon(1). Things have changed since 2012,
encryption is faster (there are modern stream ciphers and hardware
acceleration is more widespread), and for situations like this one there
is no reason not to encrypt data in transit.
>> I recall Norbert and I sat down during FOSDEM 2017 to solve perf
>> issues with our JGit deployment. Perhaps you configured your
>> ‘remote..pushurl’ at the same time :-)
>
> I can easily believe it was earlier.
Then it was before my time, so no idea what the bottleneck was.
>> Anyway, it's easy enough to benchmark no-op `git fetch` on core. master
>> is currently at c99732d59bc6, and I'm fetching from the same datacenter
>> to avoid metrics being polluted with network hiccups.
>
> Yes, but no. You also test in an environment where a network RTT is
> probably about one fifth to one third of a millisecond, and bandwidth
> at least 100Mbps if not 1000Mbps? In that case, everything will be
> fast. Time difference will be lost in noise.
I was arguing that C git and Jgit's performances are indistinguishable
on the current instance. Transport overhead is the normal batch-mode
SSH (resp. TLS) overhead for ssh:// (resp. https://) remotes.
As mentioned earlier the protocol is essentially the same for git:// and
http:// (on servers supporting smart HTTP). In both cases there is a
first round-trip (client hello + server git-upload-pack advertisement),
and another if the client is missing some object(s) (client sends list
of missing objects and receives a pack back). For http:// these are
done in two sequential requests to the same connection (resp. ‘GET
/$REPO/info/refs?service=git-upload-pack’ and ‘POST
/$REPO/git-upload-pack’); for git:// there are equivalent requests in
the Git wire protocol.
https:// is just http:// wrapped in TLS, which costs an extra 2 round-trips
(TLS 1.3 brings that down to a single extra round-trip, but we don't offer
it yet).
For ssh://, what happens under the hood (as witnessed when adding
“GIT_TRACE=1” to the environment) is that an ssh process is spawned to
run git-upload-pack on the remote machine:
ssh -p 29418 gerrit.libreoffice.org git-upload-pack "/core"
Counting round-trips for SSH isn't trivial, but let me try:
* Client & server greet each other (in parallel)
* Client & server initiate KEX (in parallel)
* Key EXchange
* Client & server send NEWKEYS (in parallel)
* Client requests service, wait for response
* Client send each pubkey one at a time, waits for response; for the
one that's accepted by the server, it sends the signed response and
waits for the server to ack
* Client asks to open a new channel, waits for response
* Client asks to execute command in said channel, wait for response
* […]
* Server sends EOF and closes channel
* Client acks, closes channels, and disconnects
So if the latency is symmetric and the first key offered is accepted by
the server, that makes a constant overhead of 8.5 round-trips. (When
using an existing — multiplexed — connection the overhead becomes 2.5
round-trips.) Additionally, the sending side must wait for the client
to adjust
[Libreoffice-commits] core.git: filter/source
filter/source/xslt/export/wordml/ooo2wordml_list.xsl |3 +++ 1 file changed, 3 insertions(+) New commits: commit 2995a95d8efa727ea53b06323c0b2bdc52e1aed0 Author: Julien Nabet AuthorDate: Mon Oct 22 23:01:25 2018 +0200 Commit: Julien Nabet CommitDate: Tue Oct 23 07:18:29 2018 +0200 tdf#120795: fix ooo2wordml_list.xsl syntax See errors in comments from tracker Regression from: https://cgit.freedesktop.org/libreoffice/core/commit/?id=1501df419ea4d40358d705a281fd9662088ba51e Change-Id: I9bbf970ac2b8cbf8fcc448f0847f61e8606797c7 Reviewed-on: https://gerrit.libreoffice.org/62205 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/filter/source/xslt/export/wordml/ooo2wordml_list.xsl b/filter/source/xslt/export/wordml/ooo2wordml_list.xsl index e3c9614d6e06..67337bc4eab3 100644 --- a/filter/source/xslt/export/wordml/ooo2wordml_list.xsl +++ b/filter/source/xslt/export/wordml/ooo2wordml_list.xsl @@ -228,12 +228,15 @@ + + + ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: dbaccess/source
dbaccess/source/ui/browser/sbagrid.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 9deabca91c8fd899fd162f4a16a1061793e8a10e Author: Julien Nabet AuthorDate: Mon Oct 22 23:12:09 2018 +0200 Commit: Julien Nabet CommitDate: Tue Oct 23 07:17:41 2018 +0200 tdf#120773: simplify condition in sbagrid.cxx:1265 Change-Id: If907fe0310f4983ddf1917c6ca88f2cebf4c45aa Reviewed-on: https://gerrit.libreoffice.org/62206 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/dbaccess/source/ui/browser/sbagrid.cxx b/dbaccess/source/ui/browser/sbagrid.cxx index 9f80745f3a11..4726dd8c58f6 100644 --- a/dbaccess/source/ui/browser/sbagrid.cxx +++ b/dbaccess/source/ui/browser/sbagrid.cxx @@ -1262,7 +1262,7 @@ sal_Int8 SbaGridControl::AcceptDrop( const BrowserAcceptDropEvent& rEvt ) if (IsCurrentAppending()) --nCorrectRowCount; // the current data record doesn't really exist, we are appending a new one -if ((nCol == BROWSER_INVALIDID) || (nRow >= nCorrectRowCount) || nCol == 0 || nCol == BROWSER_INVALIDID ) +if ( (nCol == BROWSER_INVALIDID) || (nRow >= nCorrectRowCount) || (nCol == 0) ) // no valid cell under the mouse cursor break; ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 61393] PDF: Missing objects editing a PDF coming from Winword
https://bugs.documentfoundation.org/show_bug.cgi?id=61393 prue...@gmail.com changed: What|Removed |Added Version|4.0.0.2 rc |6.1.2.1 release --- Comment #15 from prue...@gmail.com --- Issue still reproducible with Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe -- 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 113174] Formula Input Line does not save the size if you increase it
https://bugs.documentfoundation.org/show_bug.cgi?id=113174 --- Comment #3 from Evan --- Bug still present Version: 6.0.6.2 Build ID: 1:6.0.6-0ubuntu0.18.04.1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); Calc: group -- 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 113174] Formula Input Line does not save the size if you increase it
https://bugs.documentfoundation.org/show_bug.cgi?id=113174 Evan changed: What|Removed |Added Summary|Formula Input Line does |Formula Input Line does not |save the size if you|save the size if you |increase it |increase 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 120811] New: FORMATTING: I want more slides on a single handout page
https://bugs.documentfoundation.org/show_bug.cgi?id=120811 Bug ID: 120811 Summary: FORMATTING: I want more slides on a single handout page Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: takeshi.diadoc...@gmail.com I would like to use the handout mode (size A0) for generating a poster presentation from a set of slides. For this purpose, I need to put 15 slides on a single A0 page. However, there are no other options for the number of slides per page than 1, 2, 3, 4, 6, and 9. Is there a way to manually add a new layout to the Master Handout? -- 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 120810] New: Extreme lag from using Japanese characters with English letters
https://bugs.documentfoundation.org/show_bug.cgi?id=120810 Bug ID: 120810 Summary: Extreme lag from using Japanese characters with English letters Product: LibreOffice Version: 6.1.2.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ashsu...@outlook.com I'm not sure if it has anything to do with the fonts mixing or just the Japanese font itself. But, I have written lots of notes in equal amounts of Japanese and English in the same document. Unlike complete English text which scrolls and types smoothly, 1k or less of Japanese characters causes tons of lag from both typing, scrolling, and document uploading. It becomes impossible to use the processor but not the UI itself. i.e. using menus and clicking buttons. -- 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 65188] RTF adds Indention to Tabstop
https://bugs.documentfoundation.org/show_bug.cgi?id=65188 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 80110] UPDATE: get 'checking for an update failed' error when checking for updates
https://bugs.documentfoundation.org/show_bug.cgi?id=80110 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 81057] Error importing a DOC document with tabs with fill character
https://bugs.documentfoundation.org/show_bug.cgi?id=81057 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 102157] DIALOG: Reset button doesnt reset values in paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=102157 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 67014] Customizations made to Writer are not present in Master Document view
https://bugs.documentfoundation.org/show_bug.cgi?id=67014 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 90009] UI: button size inconsistent, the buttons are not the same height in the Chart Wizard and in the options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=90009 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 80110] UPDATE: get 'checking for an update failed' error when checking for updates
https://bugs.documentfoundation.org/show_bug.cgi?id=80110 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 66580] exported PDF is invalid because of forbidden custom keys in the trailer
https://bugs.documentfoundation.org/show_bug.cgi?id=66580 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 95664] Cropped radio button within "Transparency" dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=95664 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107484] Non-english font names claim to be substituted in font name toolbar control
https://bugs.documentfoundation.org/show_bug.cgi?id=107484 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103183] Pasting text from OneNote fails
https://bugs.documentfoundation.org/show_bug.cgi?id=103183 --- Comment #24 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 75458] FILEOPEN DOC: carriage-return-positioned tables not exactly spaced on page same as Word
https://bugs.documentfoundation.org/show_bug.cgi?id=75458 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 101766] FILESAVE: In 'Save to Remote Server' dialog the 'Create Folder' button doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=101766 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99113] Incorrect location tables in the document
https://bugs.documentfoundation.org/show_bug.cgi?id=99113 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 76974] Language autodetection bug for empty lines
https://bugs.documentfoundation.org/show_bug.cgi?id=76974 --- Comment #13 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 77753] FILESAVE: Embedding font does not work for a particular file with emoji and symbols in Unicode 6
https://bugs.documentfoundation.org/show_bug.cgi?id=77753 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 80655] VIEWING: 'Page Width' and 'Optimal View' dont work correctly in print preview
https://bugs.documentfoundation.org/show_bug.cgi?id=80655 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 100916] Solver does not find the optimal solution
https://bugs.documentfoundation.org/show_bug.cgi?id=100916 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 102599] RTF Paste doesnt retain numbered list
https://bugs.documentfoundation.org/show_bug.cgi?id=102599 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 72456] Font Embedding does not work on MacOS
https://bugs.documentfoundation.org/show_bug.cgi?id=72456 --- Comment #14 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111679] DOCX Import - tables converted to text
https://bugs.documentfoundation.org/show_bug.cgi?id=111679 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 34955] Deleting numbering item which restarts numbering fails to retain restart
https://bugs.documentfoundation.org/show_bug.cgi?id=34955 --- Comment #9 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112861] FILEOPEN: connector's rotation not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=112861 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 105608] Bottom action button area in dialog windows do not align with above content area
https://bugs.documentfoundation.org/show_bug.cgi?id=105608 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 96942] Dialog’s buttons localized to operating system language and do not match LibreOffice’s UI language
https://bugs.documentfoundation.org/show_bug.cgi?id=96942 --- Comment #9 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 49893] FILEOPEN: RTF: Image in header not displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=49893 --- Comment #16 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113310] Special characters: A favorite character is only added to recent, if you insert it from the special characters dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=113310 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 57464] RTF Copying across paragraphs creates broken ANSI content
https://bugs.documentfoundation.org/show_bug.cgi?id=57464 --- Comment #21 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 109296] Snap package: LO can't open or save remote files
https://bugs.documentfoundation.org/show_bug.cgi?id=109296 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105608] Bottom action button area in dialog windows do not align with above content area
https://bugs.documentfoundation.org/show_bug.cgi?id=105608 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 88214] FILEOPEN RTF: Empty lines after line breaks have the default document font
https://bugs.documentfoundation.org/show_bug.cgi?id=88214 --- Comment #13 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113174] Formula Input Line does save the size if you increase it
https://bugs.documentfoundation.org/show_bug.cgi?id=113174 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 81507] FILESAVE: DOCX - w:sdtContent not exported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=81507 --- Comment #9 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 100506] Addition ability to copy result of search in dialogue Find
https://bugs.documentfoundation.org/show_bug.cgi?id=100506 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 92015] wrong language detection in style:rfc-language-tag when country is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=92015 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 34722] FILEOPEN: Text boxes are not shown in generated .doc documents
https://bugs.documentfoundation.org/show_bug.cgi?id=34722 --- Comment #18 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 79695] FILEOPEN: MS Word 2013 ODF shows red question marks after formula
https://bugs.documentfoundation.org/show_bug.cgi?id=79695 --- Comment #13 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 81134] EDITING: Chart size not retained when chart has empty data set
https://bugs.documentfoundation.org/show_bug.cgi?id=81134 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 90353] FILEOPEN DOC: TABLE VIEWING destroyed
https://bugs.documentfoundation.org/show_bug.cgi?id=90353 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120809] Undo and redo enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=120809 Leandro Martín Drudi changed: What|Removed |Added CC||sanipache...@outlook.com.ar --- Comment #1 from Leandro Martín Drudi --- Created attachment 145915 --> https://bugs.documentfoundation.org/attachment.cgi?id=145915=edit Undo list The phrase is: "pensó en salir corriendo. Pero" Undo word by word in this phrase 10 undo actions when only one can be much more useful. -- 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 120809] New: Undo and redo enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=120809 Bug ID: 120809 Summary: Undo and redo enhancement Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sanipache...@outlook.com.ar Description: [ES] En la actualidad, los comandos deshacer y rehacer almacenan una palabra, un espacio, un signo de puntuación por cada comando. Entonces, en la frase "Este párrafo es de ejemplo", un clic deshace "Ejemplo", otro clic deshace el espacio, otro clic el "de", otro clic, el espacio, otro clic "es". De la forma actual, en un texto de 50 palabras podrías ocupar todos los comandos deshacer. Lo que propongo como posibilidad (obviamente dejo en manos de los expertos como lograrlo) que se usen bloques determinados por signos de puntuación, o bien alguna pausa, o cierta cantidad de caracteres. Esto permitiría, quizá, en vez de poder deshacer dos o tres líneas de texto, una página entera. Quizá más. [EN] Currently, the undo and redo commands store a word, a space, a punctuation mark for each command. Then, in the sentence "This paragraph is an example", one click undoes "Example", another click undoes the space, another click the "an", another click, the space, another click "is". In the current way, in a text of 50 words you could occupy all the undo commands. What I propose as a possibility (obviously I leave in the hands of experts how to achieve it) that blocks are used determined by punctuation marks, or some pause, or a certain number of characters. This would allow, perhaps, instead of being able to undo two or three lines of text, a whole page. Maybe more. Steps to Reproduce: 1. Write a phrase with 5 words and 4 spaces. 2. Undo 9 actions to return to the beginning 3. Redo 9 actions to return to the text. Actual Results: 1 word, 1 action. 1 space ( ), 1 action. 1 comma, dot, etc. 1 action. Expected Results: In some way, an oration, paragraph can be 1 action. Reproducible: Always User Profile Reset: Yes Additional Info: [ES] Este cambio es sumamente imprescindible para ámbitos donde los documentos largos llevan mucha redacción y correcciones y volver a un punto anterior debe ser en un tiempo optimizado. En lo personal, como escritor, es realmente molesto, contraproducente y muy lento deshacer un texto de 50 palabras añadidas y que, para volver al punto previo a añadirlas a las palabras, tener que deshacer una palabra, espacio o signo a la vez. A la vez, aumentar la cantidad de acciones a deshacer o usar el control de cambios muchas veces no nos dan la flexibilidad que uno requiere o resultan demasiado complejas para ciertas acciones. En otro sentido mucho menos formal, resulta absurdo el funcionamiento actual. [EN] This change is extremely essential for areas where long documents have a lot of writing and corrections and to return to an earlier point should be in an optimized time. Personally, as a writer, it is really annoying, counterproductive and very slow to undo a text of 50 words added and that, to return to the previous point to add them to the words, having to undo a word, space or sign at a time. At the same time, increasing the number of actions to be undone or using change control often does not give us the flexibility that one requires or they are too complex for certain actions. In a much less formal sense, the current functioning is absurd. -- 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 120808] Problems with configuration of page size defined as "Oficio" in Colombia, Venezuela, Bolivia, Chile, Guatemala...
https://bugs.documentfoundation.org/show_bug.cgi?id=120808 --- Comment #1 from Albert Acer --- The solution for this anomaly in LibreOffice would be that the development team could define a page size with the name "Oficio Latinoamericano", or "Folio", or "Oficio 2", another reason to try to seduce Latin American users offering them an alternative tailored to their needs. -- 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 120808] New: Problems with configuration of page size defined as "Oficio" in Colombia, Venezuela, Bolivia, Chile, Guatemala...
https://bugs.documentfoundation.org/show_bug.cgi?id=120808
Bug ID: 120808
Summary: Problems with configuration of page size defined as
"Oficio" in Colombia, Venezuela, Bolivia, Chile,
Guatemala...
Product: LibreOffice
Version: 6.1.2.1 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: albac...@gmail.com
Description:
In Colombia, Venezuela, Bolivia, Chile, Guatemala and Other Latin American
countries, the size of the paper "Oficio" (Oficio Latinoamericano), used for
the production of institutional documents, does not coincide with the
dimensions of the sheet of paper "Oficio" American, of the United States,
defined in all versions of LibreOffice and OpenOffice existing until today.
Likewise, in Argentina and Brazil the Latin American paper "Oficio" is called
"Folio" because its dimensions are based on the British or Anglo-Saxon paper
measures known as Folio or "Foolscap".
Steps to Reproduce:
1. Open LibreOffice 6.1.2 or any previous version in Spanish.
2. Go to Writer or Calc or Impress
3. Go to "Format" / "Formato".
4. Go to "Page" / "Página".
5. Go to "Page" Tab / "Página".
6. Open the "Format" drop-down list box ("Formato").
Actual Results:
1. Open LibreOffice 6.1.2 or any previous version in Spanish.
2. Go to Writer or Calc or Impress
3. Go to "Format" / "Formato".
4. Go to "Page" / "Página".
5. Go to "Page" Tab / "Página".
6. Open the "Format" drop-down list box ("Formato").
Missing page size "Oficio Latinoamericano" or "Folio" or "Oficio 2" with
dimensions 8.5 X 13 inches (21.59 cm X 33 cm).
Expected Results:
Solution for Latin American countries: Colombia, Venezuela, Bolivia, Chile,
Guatemala and others. New page size "Oficio Latinoamericano" or "Folio" or
"Oficio 2" with dimensions 8.5 X 13 inches (21.59 cm X 33 cm).
Reproducible: Always
User Profile Reset: Yes
Additional Info:
[Information automatically included from LibreOffice]
Locale: es
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
--
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 120409] Digital Signatures -> Select certificate got missing on 6.2 alpha
https://bugs.documentfoundation.org/show_bug.cgi?id=120409 Adolfo Jayme changed: What|Removed |Added Resolution|FIXED |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 69593] FILEOPEN: PPTX import with shapes causes text to disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=69593 --- Comment #18 from Keith Curtis --- Yes, the bug is still present in 6.1.2.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 113857] Export to pdf from Writer: did not protect pdf from copy / print
https://bugs.documentfoundation.org/show_bug.cgi?id=113857 --- Comment #2 from photoshop...@comcast.net --- This does not work in macOS 10.14.0 + LO 6.0.6.2 either. 1. Create document 2. File > Export As > PDF 3. Security, set passwords 4. Choose no changes, no allowance of copying. 5. Export 6. Open PDF and highlight any text, command-C. 7. Open another document, command-V. The text from step 6 pastes. Copy protection does not work at all. This is an old bug; it needs to be 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 120278] With version 6.2.1.2 cannot save doc to NAS drive due to insufficient permission
https://bugs.documentfoundation.org/show_bug.cgi?id=120278 --- Comment #2 from r.mario...@fdcx.net --- Resorted to version 6.0.6.2 and that works just fine with remote access/saves. -- 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 90709] Inconvenient closure of " Styles " pop-up window
https://bugs.documentfoundation.org/show_bug.cgi?id=90709 Adolfo Jayme changed: What|Removed |Added Summary|Inconvenient closure of " |Inconvenient closure of " |Styles and Formatting " |Styles " pop-up window |pop-up window | -- 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 65587] Elements pane: Items not reachable without mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=65587 Adolfo Jayme changed: What|Removed |Added Severity|normal |major CC||f...@libreoffice.org -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120807] New: Crash on Crl+Shift+F10 in F5 floating Navigator page number field
https://bugs.documentfoundation.org/show_bug.cgi?id=120807 Bug ID: 120807 Summary: Crash on Crl+Shift+F10 in F5 floating Navigator page number field Product: LibreOffice Version: 5.1.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rayk...@gmail.com Steps to reproduce: 1) Open Writer 2) F5 to show Navigator window 3) Click in page number field 4) Press Ctrl+Shift+F10 to dock the Navigator window Result: Crash Reproduced in: Version 5.1.6.2 Build ID: 1:5.1.6~rc2~0ubuntu1~xenial4 CPU threads: 1; OS: Linux 4.4; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group and Version: 6.2.0.0.alpha0+ Build ID: 6626281b4a123cfb5e2c8f449b55f4acd46ee198 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); 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 119289] Failure to sing existing pdf on LibreOffice 6.1.0.3.(x64) on Win10
https://bugs.documentfoundation.org/show_bug.cgi?id=119289 --- Comment #5 from Juan Jose Pablos --- Please try current version libo-master64~2018-10-22_01.47.50_LibreOfficeDev_6.2.0.0.alpha1_Win_x64.msi It worked 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 105605] [META] Digital signatures bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105605 Bug 105605 depends on bug 120409, which changed state. Bug 120409 Summary: Digital Signatures -> Select certificate got missing on 6.2 alpha https://bugs.documentfoundation.org/show_bug.cgi?id=120409 What|Removed |Added Status|UNCONFIRMED |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 120409] Digital Signatures -> Select certificate got missing on 6.2 alpha
https://bugs.documentfoundation.org/show_bug.cgi?id=120409 Juan Jose Pablos changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Juan Jose Pablos --- I just Download - - libo-master64~2018-10-22_01.47.50_LibreOfficeDev_6.2.0.0.alpha1_Win_x64.msi and I can manage to sign just fine. -- 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 119862] Navigation Pane, sidebar mode, autonomous vertical jump to current selected heading item
https://bugs.documentfoundation.org/show_bug.cgi?id=119862 --- Comment #12 from R. Bingham --- "I also do not observe any of the line item selection clearings when focusing in the document view." Yes, IF by intent or just randomly you activate the cursor in any part of the document hierarchically "covered" by a paragraph with a style property of outline HEADER #N where #N is low enough to be an NP-displayed heading level item. The NP has a setting for the highest outline-level #N header style to be displayed. In the demo doc this is set to 6. It happens the in the the demo document I constructed, the only document page/text area NOT covered by an NP-displayed heading level item is the TITLE PAGE. To further show this, open the demo document. Should open with cursor on the title page and if the NP is showing then no NP heading line item selected. Manually insert a page break while on the title page. You now have page preceding any text covered by an outline header style paragraph. You can add any text you want as long as its style does not include an outline level property < 7 and it will not show in the NP. When the cursor is in this text the NP should NOT show any selection highlight. I learned the hard way this is why reproducing this bug/feature behavior is so dependent on replicating the exact click-stream sequence indicated. Clicking anywhere in the document edit window, even outside to the side of the doc WYSIWYG image, activates the edit cursor *somewhere* in the document. Different behaviors occur in the NP depending on *where* in the doc text structure the cursor is active. -- 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 34754] Undo of Ole object deletion only restores object, not also its undo stack
https://bugs.documentfoundation.org/show_bug.cgi?id=34754 Adolfo Jayme changed: What|Removed |Added Summary|Undo of Ole object deletion |Undo of Ole object deletion |only restores object, not |only restores object, not |also it's undo stack|also its undo stack -- 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 120774] kde5: Rearranging Impress slides via drag'n'drop not always working as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=120774 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Xisco Faulí --- Reproduced in Version: 6.2.0.0.alpha0+ Build ID: 3846561f79cf9065abd9ca83c9fbfbe7e52e28e2 CPU threads: 1; OS: Linux 4.13; UI render: default; VCL: kde5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-10-21_02:45:54 Locale: en-US (en_US.UTF-8); 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 120794] CRASH while selecting a drawing line
https://bugs.documentfoundation.org/show_bug.cgi?id=120794 --- Comment #4 from Xisco Faulí --- I can still reproduce it in Version: 6.2.0.0.alpha1+ Build ID: 7da3947535d1b3aac23b3d0a72e94396960ee751 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded using 'rm -rf instdir/user/ && instdir/program/swriter' -- 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 120764] Font and Font Size selection dropdown menus unresponsive under Wayland in Ubuntu 18.10 Cosmic
https://bugs.documentfoundation.org/show_bug.cgi?id=120764 Maxim Monastirsky changed: What|Removed |Added CC||momonas...@gmail.com --- Comment #1 from Maxim Monastirsky --- This might help: https://gerrit.libreoffice.org/62207/ -- 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 120798] LBO Calc : Format cellules "Centrer sur colonnes" impossible SANS fusion de cellules
https://bugs.documentfoundation.org/show_bug.cgi?id=120798 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from m.a.riosv --- Agree, it's very useful, it was also in 123. -- 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 100236] Squiggly accents render incorrectly in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=100236 --- Comment #5 from Commit Notification --- Mark Hung committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ae9f37ba753519ae4a2ae6384d052d417359602f tdf#100236 Implement linestyles with dash and dots. It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: cppcanvas/source
cppcanvas/source/mtfrenderer/mtftools.cxx | 197 ++
1 file changed, 93 insertions(+), 104 deletions(-)
New commits:
commit ae9f37ba753519ae4a2ae6384d052d417359602f
Author: Mark Hung
AuthorDate: Sun Oct 21 00:04:33 2018 +0800
Commit: Mark Hung
CommitDate: Tue Oct 23 00:55:50 2018 +0200
tdf#100236 Implement linestyles with dash and dots.
Allow append dashes to have dash and dot line styles.
Segment length parameters were taken from cppcanvas, also restructure
the code to use the same appendDashes function.
Change-Id: I17c0796dbe722c4c6d5e91d0e318570a52a2514c
Reviewed-on: https://gerrit.libreoffice.org/62084
Tested-by: Jenkins
Reviewed-by: Mark Hung
diff --git a/cppcanvas/source/mtfrenderer/mtftools.cxx
b/cppcanvas/source/mtfrenderer/mtftools.cxx
index 75c7d6069146..0680e05f3ca8 100644
--- a/cppcanvas/source/mtfrenderer/mtftools.cxx
+++ b/cppcanvas/source/mtfrenderer/mtftools.cxx
@@ -319,28 +319,92 @@ namespace cppcanvas
::basegfx::B2DRectangle( nX1, nY1, nX2, nY2 ) ) );
}
-void appendDashes( ::basegfx::B2DPolyPolygon& o_rPoly,
+bool appendDashes( ::basegfx::B2DPolyPolygon& o_rPoly,
const double nX,
- const double nY,
+ double nY,
const double nLineWidth,
- const double nLineHeight,
- const double nDashWidth,
- const double nDashSkip )
+ double nLineHeight,
+ sal_Int8 nLineStyle,
+ bool bIsOverline)
{
-const sal_Int32 nNumLoops(
-static_cast< sal_Int32 >(
-std::max( 1.0,
-nLineWidth / nDashSkip ) + .5) );
+static const int aDottedArray[] = { 1, 1, 0};
// DOTTED LINE
+static const int aDotDashArray[]= { 1, 1, 4, 1, 0};
// DASHDOT
+static const int aDashDotDotArray[] = { 1, 1, 1, 1, 4, 1, 0};
// DASHDOTDOT
+static const int aDashedArray[] = { 5, 2, 0};
// DASHED LINE
+static const int aLongDashArray[] = { 7, 2, 0};
// LONGDASH
+const int *pArray = nullptr;
+bool bIsBold = false;
+
+switch(nLineStyle)
+{
+case LINESTYLE_BOLDDOTTED:
+bIsBold = true;
+BOOST_FALLTHROUGH;
+case LINESTYLE_DOTTED:
+pArray = aDottedArray;
+break;
+
+case LINESTYLE_BOLDDASH:
+bIsBold = true;
+BOOST_FALLTHROUGH;
+case LINESTYLE_DASH:
+pArray = aDashedArray;
+break;
+
+case LINESTYLE_BOLDLONGDASH:
+bIsBold = true;
+BOOST_FALLTHROUGH;
+case LINESTYLE_LONGDASH:
+pArray = aLongDashArray;
+break;
+
+case LINESTYLE_BOLDDASHDOT:
+bIsBold = true;
+BOOST_FALLTHROUGH;
+case LINESTYLE_DASHDOT:
+pArray = aDotDashArray;
+break;
+case LINESTYLE_BOLDDASHDOTDOT:
+bIsBold = true;
+BOOST_FALLTHROUGH;
+case LINESTYLE_DASHDOTDOT:
+pArray = aDashDotDotArray;
+break;
+}
-double x = nX;
-for( sal_Int32 i=0; ihttps://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 120806] New: Zotero icon dpi
https://bugs.documentfoundation.org/show_bug.cgi?id=120806 Bug ID: 120806 Summary: Zotero icon dpi Product: LibreOffice Version: 6.1.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ghavami...@hotmail.com Plus could update for hi dpi screen on windows and Linux platforms? -- 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 120805] New: The document recovery routine - if you choose to start to restore a non-existant file,
https://bugs.documentfoundation.org/show_bug.cgi?id=120805 Bug ID: 120805 Summary: The document recovery routine - if you choose to start to restore a non-existant file, Product: LibreOffice Version: 6.0.0.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dry57...@yahoo.com Description: the next box that shows only gives the choice 'OK', it fails and returns to the same box - you can not get back to the box showing the choices 'start - discard' I think the bug is that the 'discard/start' flag is not cleared on re-entry to the routine, because you can not get back to a 'discard or start' choice You can only get out, you can not ignore and continue - I can not use 'office' until this is cleared. I down loaded the latest version today (10-22-2018), installed - no errors no change. Steps to Reproduce: 1.Office reported that it crashed, tried to save existing file. 2.On startup it entered Document Recovery routine. 3.entered 'start to see what the file might be - got trapped in a loop Actual Results: got trapped in a loop. Had to exit - close window or use escape key. Expected Results: hoped to discard and clear or at least ignore and proceed into program. Reproducible: Always User Profile Reset: Yes Additional Info: Could not get into the program to access help. Not sure how to reset user-profile, I renamed the config folder, it just re-created it, no joy. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: vcl/inc vcl/source
vcl/inc/fontselect.hxx |4 ++--
vcl/inc/impfontcache.hxx |4 ++--
vcl/source/font/fontcache.cxx|4 ++--
vcl/source/font/fontinstance.cxx |5 -
vcl/source/font/fontselect.cxx |4 ++--
vcl/source/outdev/font.cxx | 32 +++-
6 files changed, 23 insertions(+), 30 deletions(-)
New commits:
commit c766a05ae0354f1bc9763b725f91069975b37bd3
Author: Jan-Marek Glogowski
AuthorDate: Mon Oct 22 18:38:44 2018 +
Commit: Jan-Marek Glogowski
CommitDate: Tue Oct 23 00:20:25 2018 +0200
Antialias drawing is part of the font selection
At least on Windows antialias-drawing has to be selected via
LOGFONTW.lfQuality passed to CreateFont, so InitFont is too late.
Change-Id: Ie81c5f0074fdbcf1f0e74fbff31a5df663a67884
Reviewed-on: https://gerrit.libreoffice.org/62200
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski
diff --git a/vcl/inc/fontselect.hxx b/vcl/inc/fontselect.hxx
index 51f70997ac53..e021f7a0c775 100644
--- a/vcl/inc/fontselect.hxx
+++ b/vcl/inc/fontselect.hxx
@@ -37,8 +37,8 @@ class Size;
class VCL_DLLPUBLIC FontSelectPattern : public FontAttributes
{
public:
-FontSelectPattern( const vcl::Font&, const OUString&
rSearchName,
- const Size&, float
fExactHeight );
+FontSelectPattern(const vcl::Font&, const OUString& rSearchName,
+ const Size&, float fExactHeight, bool bNonAntialias =
false);
#ifdef _WIN32
FontSelectPattern( const PhysicalFontFace&, const Size&,
float fExactHeight, int
nOrientation, bool bVertical );
diff --git a/vcl/inc/impfontcache.hxx b/vcl/inc/impfontcache.hxx
index ee39883f2199..25bc970c97a9 100644
--- a/vcl/inc/impfontcache.hxx
+++ b/vcl/inc/impfontcache.hxx
@@ -82,8 +82,8 @@ public:
ImplFontCache();
~ImplFontCache();
-rtl::Reference GetFontInstance(
PhysicalFontCollection const *,
- const vcl::Font&, const Size& rPixelSize, float
fExactHeight);
+rtl::Reference GetFontInstance(PhysicalFontCollection
const *,
+ const vcl::Font&, const Size& rPixelSize, float
fExactHeight, bool bNonAntialias = false);
rtl::Reference GetGlyphFallbackFont(
PhysicalFontCollection const *, FontSelectPattern&,
LogicalFontInstance* pLogicalFont,
int nFallbackLevel, OUString& rMissingCodes );
diff --git a/vcl/source/font/fontcache.cxx b/vcl/source/font/fontcache.cxx
index b8e4bec2b5ce..51a04a34b769 100644
--- a/vcl/source/font/fontcache.cxx
+++ b/vcl/source/font/fontcache.cxx
@@ -97,10 +97,10 @@ ImplFontCache::~ImplFontCache()
}
rtl::Reference ImplFontCache::GetFontInstance(
PhysicalFontCollection const * pFontList,
-const vcl::Font& rFont, const Size& rSize, float fExactHeight )
+const vcl::Font& rFont, const Size& rSize, float fExactHeight, bool
bNonAntialias )
{
// initialize internal font request object
-FontSelectPattern aFontSelData(rFont, rFont.GetFamilyName(), rSize,
fExactHeight);
+FontSelectPattern aFontSelData(rFont, rFont.GetFamilyName(), rSize,
fExactHeight, bNonAntialias);
return GetFontInstance( pFontList, aFontSelData );
}
diff --git a/vcl/source/font/fontinstance.cxx b/vcl/source/font/fontinstance.cxx
index 7a889fa65a7c..0a7bc91c57af 100644
--- a/vcl/source/font/fontinstance.cxx
+++ b/vcl/source/font/fontinstance.cxx
@@ -55,11 +55,6 @@ LogicalFontInstance::LogicalFontInstance(const
PhysicalFontFace& rFontFace, cons
{
}
-void LogicalFontInstance::SetNonAntialiased(bool bNonAntialiased)
-{
-const_cast(_aFontSelData)->mbNonAntialiased =
bNonAntialiased;
-}
-
LogicalFontInstance::~LogicalFontInstance()
{
mpUnicodeFallbackList.reset();
diff --git a/vcl/source/font/fontselect.cxx b/vcl/source/font/fontselect.cxx
index f879f9c5a7ac..e5b35bb24560 100644
--- a/vcl/source/font/fontselect.cxx
+++ b/vcl/source/font/fontselect.cxx
@@ -31,7 +31,7 @@ const char FontSelectPattern::FEAT_PREFIX = ':';
const char FontSelectPattern::FEAT_SEPARATOR = '&';
FontSelectPattern::FontSelectPattern( const vcl::Font& rFont,
-const OUString& rSearchName, const Size& rSize, float fExactHeight )
+const OUString& rSearchName, const Size& rSize, float fExactHeight, bool
bNonAntialias)
: maSearchName( rSearchName )
, mnWidth( rSize.Width() )
, mnHeight( rSize.Height() )
@@ -39,7 +39,7 @@ FontSelectPattern::FontSelectPattern( const vcl::Font& rFont,
, mnOrientation( rFont.GetOrientation() )
, meLanguage( rFont.GetLanguage() )
, mbVertical( rFont.IsVertical() )
-, mbNonAntialiased( false )
+, mbNonAntialiased(bNonAntialias)
, mbEmbolden( false )
{
maTargetName = GetFamilyName();
diff --git a/vcl/source/outdev/font.cxx b/vcl/source/outdev/font.cxx
index 9904ecf304d4..e3b7f1a2acaa
[Libreoffice-commits] core.git: include/vcl svx/source vcl/source
include/vcl/font.hxx| 11 +++
include/vcl/outdev.hxx |1 -
svx/source/svdraw/svdotextdecomposition.cxx | 14 +-
vcl/source/gdi/pdfwriter_impl.cxx |2 +-
vcl/source/outdev/text.cxx |2 +-
vcl/source/outdev/textline.cxx | 10 --
6 files changed, 14 insertions(+), 26 deletions(-)
New commits:
commit 6d3843a415bb74a00a40f312b7771db27060cf0b
Author: Jan-Marek Glogowski
AuthorDate: Mon Oct 22 18:25:35 2018 +
Commit: Jan-Marek Glogowski
CommitDate: Tue Oct 23 00:18:55 2018 +0200
Implement IsUnderlineAbove in vcl::Font
There was even a duplicate implementation...
Change-Id: I192ac2ec8e5b8dd0e6b3ab9b9ddf0bf53df546ab
Reviewed-on: https://gerrit.libreoffice.org/62199
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski
diff --git a/include/vcl/font.hxx b/include/vcl/font.hxx
index 2dc0a5b326cd..02dab4d8b51e 100644
--- a/include/vcl/font.hxx
+++ b/include/vcl/font.hxx
@@ -163,10 +163,21 @@ public:
typedef o3tl::cow_wrapper< ImplFont > ImplType;
+inline bool IsUnderlineAbove() const;
+
private:
ImplType mpImplFont;
};
+inline bool Font::IsUnderlineAbove() const
+{
+if (!IsVertical())
+return false;
+// the underline is right for Japanese only
+return (LANGUAGE_JAPANESE == GetLanguage()) ||
+ (LANGUAGE_JAPANESE == GetCJKContextLanguage());
+}
+
}
#endif // _VCL_FONT_HXX
diff --git a/include/vcl/outdev.hxx b/include/vcl/outdev.hxx
index f661bb377636..c9f9d06db17c 100644
--- a/include/vcl/outdev.hxx
+++ b/include/vcl/outdev.hxx
@@ -1201,7 +1201,6 @@ private:
SAL_DLLPRIVATE void ImplDrawStrikeoutChar( long nBaseX, long
nBaseY, long nX, long nY, long nWidth, FontStrikeout eStrikeout, Color aColor );
SAL_DLLPRIVATE void ImplDrawMnemonicLine( long nX, long nY, long
nWidth );
-SAL_DLLPRIVATE static bool ImplIsUnderlineAbove( const vcl::Font& );
static
SAL_DLLPRIVATE long ImplGetTextLines( ImplMultiTextLineInfo&
rLineInfo, long nWidth, const OUString& rStr, DrawTextFlags nStyle, const
vcl::ITextLayout& _rLayout );
diff --git a/svx/source/svdraw/svdotextdecomposition.cxx
b/svx/source/svdraw/svdotextdecomposition.cxx
index b98ee9e053ba..e5e0ee273e11 100644
--- a/svx/source/svdraw/svdotextdecomposition.cxx
+++ b/svx/source/svdraw/svdotextdecomposition.cxx
@@ -90,7 +90,6 @@ namespace
DECL_LINK(decomposeBlockBulletPrimitive, DrawBulletInfo*, void);
DECL_LINK(decomposeStretchBulletPrimitive, DrawBulletInfo*, void);
-static bool impIsUnderlineAbove(const vcl::Font& rFont);
void impCreateTextPortionPrimitive(const DrawPortionInfo& rInfo);
static drawinglayer::primitive2d::BasePrimitive2D*
impCheckFieldPrimitive(drawinglayer::primitive2d::BasePrimitive2D* pPrimitive,
const DrawPortionInfo& rInfo);
void impFlushTextPortionPrimitivesToLinePrimitives();
@@ -152,17 +151,6 @@ namespace
drawinglayer::primitive2d::Primitive2DContainer const &
getPrimitive2DSequence();
};
-bool impTextBreakupHandler::impIsUnderlineAbove(const vcl::Font& rFont)
-{
-if(!rFont.IsVertical())
-{
-return false;
-}
-
-// the underline is right for Japanese only
-return (LANGUAGE_JAPANESE == rFont.GetLanguage()) ||
(LANGUAGE_JAPANESE == rFont.GetCJKContextLanguage());
-}
-
void impTextBreakupHandler::impCreateTextPortionPrimitive(const
DrawPortionInfo& rInfo)
{
if(rInfo.maText.isEmpty() || !rInfo.mnTextLen)
@@ -284,7 +272,7 @@ namespace
// check UnderlineAbove
const bool bUnderlineAbove(
-drawinglayer::primitive2d::TEXT_LINE_NONE != eFontLineStyle &&
impIsUnderlineAbove(rInfo.mrFont));
+drawinglayer::primitive2d::TEXT_LINE_NONE != eFontLineStyle &&
rInfo.mrFont.IsUnderlineAbove());
// prepare strikeout data
const drawinglayer::primitive2d::TextStrikeout eTextStrikeout(
diff --git a/vcl/source/gdi/pdfwriter_impl.cxx
b/vcl/source/gdi/pdfwriter_impl.cxx
index 48475a52fba8..badc1af9a11c 100644
--- a/vcl/source/gdi/pdfwriter_impl.cxx
+++ b/vcl/source/gdi/pdfwriter_impl.cxx
@@ -6839,7 +6839,7 @@ void PDFWriterImpl::drawLayout( SalLayout& rLayout, const
OUString& rText, bool
)
)
{
-bool bUnderlineAbove = OutputDevice::ImplIsUnderlineAbove(
m_aCurrentPDFState.m_aFont );
+bool bUnderlineAbove = m_aCurrentPDFState.m_aFont.IsUnderlineAbove();
if( m_aCurrentPDFState.m_aFont.IsWordLineMode() )
{
Point aStartPt;
diff --git a/vcl/source/outdev/text.cxx b/vcl/source/outdev/text.cxx
index cd9ba5e628e3..3bc2ced9a3b5 100644
--- a/vcl/source/outdev/text.cxx
+++ b/vcl/source/outdev/text.cxx
@@ -300,7 +300,7 @@ void OutputDevice::ImplDrawTextDirect( SalLayout&
rSalLayout,
[Libreoffice-bugs] [Bug 120760] FILEOPEN Z-order of objects in attached DOCX is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=120760 Aron Budea changed: What|Removed |Added Version|4.4.0.3 release |4.0.0.3 release -- 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 120760] FILEOPEN Z-order of objects in attached DOCX is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=120760 Aron Budea changed: What|Removed |Added Blocks||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 117692] Frame at top of page moves into header with wrong padding when reloading exported DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=117692 Aron Budea changed: What|Removed |Added Blocks||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 104556] FILEOPEN DOCX: Misplaced vertical red line (drawing object)
https://bugs.documentfoundation.org/show_bug.cgi?id=104556 Aron Budea changed: What|Removed |Added Blocks||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 119697] FILEOPEN DOCX Text box Shape (with absolute position to column in Word?) is positioned incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=119697 Aron Budea changed: What|Removed |Added Blocks||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 107582] FILESAVE: DOC Background is lost after roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=107582 Aron Budea changed: What|Removed |Added Blocks||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 116256] DOCX Import: incorrect placement of textbox in table.
https://bugs.documentfoundation.org/show_bug.cgi?id=116256 Aron Budea changed: What|Removed |Added Blocks||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=120804 Aron Budea changed: What|Removed |Added Ever confirmed|0 |1 Depends on||107582, 120760, 116256, ||119697, 117692, 100830, ||104556, 107104 Status|UNCONFIRMED |NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100830 [Bug 100830] FILEOPEN: OOXML - Transparency Not Imported for Bitmap Filled Shapes https://bugs.documentfoundation.org/show_bug.cgi?id=104556 [Bug 104556] FILEOPEN DOCX: Misplaced vertical red line (drawing object) https://bugs.documentfoundation.org/show_bug.cgi?id=107104 [Bug 107104] Arrow is missed when opening a word document in LibreOffice, the there is transparent text box on top of arrow https://bugs.documentfoundation.org/show_bug.cgi?id=107582 [Bug 107582] FILESAVE: DOC Background is lost after roundtrip https://bugs.documentfoundation.org/show_bug.cgi?id=116256 [Bug 116256] DOCX Import: incorrect placement of textbox in table. https://bugs.documentfoundation.org/show_bug.cgi?id=117692 [Bug 117692] Frame at top of page moves into header with wrong padding when reloading exported DOCX https://bugs.documentfoundation.org/show_bug.cgi?id=119697 [Bug 119697] FILEOPEN DOCX Text box Shape (with absolute position to column in Word?) is positioned incorrectly https://bugs.documentfoundation.org/show_bug.cgi?id=120760 [Bug 120760] FILEOPEN Z-order of objects in attached DOCX is wrong -- 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 119229] Provide compatibility with comment replies in MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=119229 --- Comment #3 from egor.kat...@gmail.com --- Created attachment 145914 --> https://bugs.documentfoundation.org/attachment.cgi?id=145914=edit What comment replies look like in Word -- 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 119229] Provide compatibility with comment replies in MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=119229 --- Comment #2 from egor.kat...@gmail.com --- Created attachment 145913 --> https://bugs.documentfoundation.org/attachment.cgi?id=145913=edit Comment with reply Open with Word and Libre office to compare the output. -- 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 104442] [META] OOXML shape (DrawingML and VML) related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104442 Aron Budea changed: What|Removed |Added Depends on||120804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- 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 120804] New: [META] Bugs introduced by initial DrawingML shape import in DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=120804 Bug ID: 120804 Summary: [META] Bugs introduced by initial DrawingML shape import in DOCX Product: LibreOffice Version: 4.3.0.4 release Hardware: All OS: All Status: UNCONFIRMED Keywords: implementationError Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ba...@caesar.elte.hu Blocks: 104442 Let's track bugs that can be traced back to the following commit here: https://cgit.freedesktop.org/libreoffice/core/commit/?id=57450afb768c085df0ba2344aa94b5f843060178 author Miklos Vajna 2013-12-03 11:59:42 +0100 committer Miklos Vajna 2013-12-03 15:39:04 +0100 "DOCX import: declare wps as a supported feature" Some background info: https://vmiklos.hu/blog/lo-writer-drawingml-shape-improvements.html Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104442 [Bug 104442] [META] OOXML shape (DrawingML and VML) related issues -- 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 120760] FILEOPEN Z-order of objects in attached DOCX is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=120760 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords|bibisectRequest |bibisected --- Comment #3 from Aron Budea --- Thanks for the bisect, Xisco! Since wps support was new development, these days I'm inclined to not regard that as a regression, but as implementationError. The issue with Z-order of the red image was introduced in the following range (bibisected using repo bibisect-43all: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=83837d6514217c82ebe8d56dddf89fa34f4b5435..2815396a1813cb3956c5aba066de49a7f34bc657 I'm inclined to think either of the following commits from Cedric are responsible: https://cgit.freedesktop.org/libreoffice/core/commit/?id=da53c44d7074499db2d0ba57eee09bde6152e7ea author Cédric Bosdonnat 2012-07-31 14:46:59 +0200 committer Cédric Bosdonnat 2012-07-31 15:22:23 +0200 n#772094: pictures was eaten by document default LR settings https://cgit.freedesktop.org/libreoffice/core/commit/?id=ae126d43e4737ab39e53827d9ad3bd6983577b1f author Cédric Bosdonnat 2012-07-31 15:19:23 +0200 committer Cédric Bosdonnat 2012-07-31 15:22:23 +0200 n#772094: writerfilter, pictures anchored in header/footer won't be opaque -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: Branch 'libreoffice-6-1' - sfx2/source
sfx2/source/sidebar/SidebarController.cxx |2 ++ 1 file changed, 2 insertions(+) New commits: commit 5de85be43198804573787d4186b156b5931c4a9f Author: Caolán McNamara AuthorDate: Mon Oct 22 14:37:14 2018 +0100 Commit: Katarina Behrens CommitDate: Mon Oct 22 23:37:03 2018 +0200 cannot interact with chart sidebar as the previous deck is still active Change-Id: I7972ef73b8c11ae78569fa1c7dc0a244ebba3f30 Reviewed-on: https://gerrit.libreoffice.org/62182 Tested-by: Jenkins Reviewed-by: Katarina Behrens diff --git a/sfx2/source/sidebar/SidebarController.cxx b/sfx2/source/sidebar/SidebarController.cxx index 4f2b3e900d6a..14b40e58a6f8 100644 --- a/sfx2/source/sidebar/SidebarController.cxx +++ b/sfx2/source/sidebar/SidebarController.cxx @@ -732,6 +732,8 @@ void SidebarController::SwitchToDeck ( if (bForceNewPanels && !bForceNewDeck) // already forced if bForceNewDeck CreatePanels(rDeckDescriptor.msId, rContext); +if (mpCurrentDeck && mpCurrentDeck != rDeckDescriptor.mpDeck) +mpCurrentDeck->Hide(); mpCurrentDeck.reset(rDeckDescriptor.mpDeck); if ( ! mpCurrentDeck) ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: Branch 'libreoffice-6-1' - sc/qa sc/source
sc/qa/unit/data/ods/tdf62268.ods |binary sc/qa/unit/helper/qahelper.cxx |3 + sc/qa/unit/subsequent_export-test.cxx | 59 +++-- sc/qa/unit/subsequent_filters-test.cxx | 26 -- sc/source/filter/xml/xmlimprt.cxx | 21 +++ sc/source/filter/xml/xmlimprt.hxx |5 ++ sc/source/filter/xml/xmlrowi.cxx | 16 7 files changed, 94 insertions(+), 36 deletions(-) New commits: commit 693953dd4699887bd3f5bca2c3582b5fae1d6992 Author: Vasily Melenchuk AuthorDate: Fri Apr 6 20:19:10 2018 +0300 Commit: Katarina Behrens CommitDate: Mon Oct 22 23:30:23 2018 +0200 tdf#62268: allow row height recalculation on document load During document load rows with style:use-optimal-row-height="true" should recalculate it's height. * includes: Row height tolerance level increase for unittest * tdf#118086: calc: invalid row autoheight fixed Change-Id: Ib38b5b753d9ff8352116d77851d228c5d77bd530 Reviewed-on: https://gerrit.libreoffice.org/52521 Reviewed-by: Katarina Behrens Tested-by: Jenkins Reviewed-by: Thorsten Behrens (cherry picked from commit 1e55a47e89a9d9d6cf9cb3993484022aaf2c097b) Reviewed-on: https://gerrit.libreoffice.org/61898 Tested-by: Jenkins diff --git a/sc/qa/unit/data/ods/tdf62268.ods b/sc/qa/unit/data/ods/tdf62268.ods new file mode 100644 index ..da88adfd25cd Binary files /dev/null and b/sc/qa/unit/data/ods/tdf62268.ods differ diff --git a/sc/qa/unit/helper/qahelper.cxx b/sc/qa/unit/helper/qahelper.cxx index 8aa9cc883568..d414b1abfb96 100644 --- a/sc/qa/unit/helper/qahelper.cxx +++ b/sc/qa/unit/helper/qahelper.cxx @@ -754,7 +754,8 @@ void ScBootstrapFixture::miscRowHeightsTest( TestParam const * aTestValues, unsi bool bOpt = !(rDoc.GetRowFlags( nRow, nTab ) & CRFlags::ManualSize); CPPUNIT_ASSERT_EQUAL(aTestValues[ index ].pData[ i ].bOptimal, bOpt); } -CPPUNIT_ASSERT_EQUAL(nExpectedHeight, nHeight); +// Due to some minor differences on Mac this comparison is made bit fuzzy +CPPUNIT_ASSERT_LESSEQUAL( 15, abs( nHeight - nExpectedHeight ) ); } } xShell->DoClose(); diff --git a/sc/qa/unit/subsequent_export-test.cxx b/sc/qa/unit/subsequent_export-test.cxx index ea0792f5acee..36f62373e7e0 100644 --- a/sc/qa/unit/subsequent_export-test.cxx +++ b/sc/qa/unit/subsequent_export-test.cxx @@ -1034,60 +1034,57 @@ void ScExportTest::testOutlineExportXLSX() // We expected that exactly 13 unique Nodes will be produced assertXPath(pSheet, "/x:worksheet/x:cols/x:col", 13); -// We need to save all 30 rows, as it provides information about outLineLevel -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[1]", "r", "1"); +// First row is empty and default so it is not written into XML file +// so we need to save 29 rows, as it provides information about outLineLevel +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[1]", "r", "2"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[1]", "hidden", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[1]", "outlineLevel", "0"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[1]", "outlineLevel", "1"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[1]", "collapsed", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[2]", "r", "2"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[2]", "r", "3"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[2]", "hidden", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[2]", "outlineLevel", "1"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[2]", "outlineLevel", "2"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[2]", "collapsed", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[3]", "r", "3"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[3]", "r", "4"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[3]", "hidden", "false"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[3]", "outlineLevel", "2"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[3]", "collapsed", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[4]", "r", "4"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[4]", "r", "5"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[4]", "hidden", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[4]", "outlineLevel", "2"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[4]", "outlineLevel", "3"); assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[4]", "collapsed", "false"); -assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[5]", "r", "5"); +assertXPath(pSheet, "/x:worksheet/x:sheetData/x:row[5]", "r", "6");
[Libreoffice-bugs] [Bug 119228] There is no way to flag/mark comments as resolved
https://bugs.documentfoundation.org/show_bug.cgi?id=119228 Cor Nouws changed: What|Removed |Added Summary|Flag comments as resolved |There is no way to ||flag/mark comments as ||resolved -- 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 48416] Allow typing while saving; during autosave LibreOffice doesn't accept typing/input
https://bugs.documentfoundation.org/show_bug.cgi?id=48416 Cor Nouws changed: What|Removed |Added Summary|Allow typing while saving |Allow typing while saving; ||during autosave LibreOffice ||doesn't accept typing/input CC||c...@nouenoff.nl -- 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 120773] core/dbaccess/source/ui/browser/sbagrid.cxx:1265: possible typo in if expression ?
https://bugs.documentfoundation.org/show_bug.cgi?id=120773 Julien Nabet changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #5 from Julien Nabet --- https://gerrit.libreoffice.org/#/c/62206/ -- 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 104443] Add 'Row' tab to Table Properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=104443 --- Comment #7 from Cor Nouws --- (In reply to Roman Kuznetsov from comment #5) > Created attachment 145898 [details] > (Mockup) New tab Rows in Dialogue table properties in Writer @kompilanen: looks nice - how to indicate when whole table's property to break is disabled, so that per row the boxes for breaking are disabled too ? -- 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 120795] LO Writer: Error saving the document: Write error The file could not be written
https://bugs.documentfoundation.org/show_bug.cgi?id=120795 Julien Nabet changed: What|Removed |Added CC||nem...@numbertext.org, ||serval2...@yahoo.fr Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #2 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. I noticed these logs: file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl:342: parser error : Opening and ending tag mismatch: when line 234 and choose ^ file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl:343: parser error : Opening and ending tag mismatch: when line 231 and template ^ file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl:344: parser error : Opening and ending tag mismatch: when line 228 and stylesheet ^ file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl:345: parser error : Premature end of data in tag choose line 215 ^ file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl:345: parser error : Premature end of data in tag template line 213 ^ file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl:345: parser error : Premature end of data in tag stylesheet line 19 ^ compilation error: file file:///home/julien/lo/libreoffice/instdir/program/../share/xslt/export/wordml/ooo2wordml.xsl line 27 element include xsl:include : unable to load file:/home/julien/lo/libreoffice/instdir/share/xslt/export/wordml/ooo2wordml_list.xsl Regression from https://cgit.freedesktop.org/libreoffice/core/commit/?id=1501df419ea4d40358d705a281fd9662088ba51e Just some elements missing I submitted this patch on gerrit: https://gerrit.libreoffice.org/#/c/62205/ -- 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 119370] Sidebar - Calc sidebar unresponsive when editing a chart
https://bugs.documentfoundation.org/show_bug.cgi?id=119370 --- Comment #12 from Katarina Behrens (CIB) --- Im Caolan fixed this in https://cgit.freedesktop.org/libreoffice/core/commit/?id=542a9a340972da7739c33465620ffe48da8745dd but please retest -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] online.git: Mobile/Mobile.xcodeproj
Mobile/Mobile.xcodeproj/project.pbxproj |8
1 file changed, 4 insertions(+), 4 deletions(-)
New commits:
commit 8266582cc4a59991597ee512989474230e4f0994
Author: Tor Lillqvist
AuthorDate: Mon Oct 22 23:14:07 2018 +0300
Commit: Tor Lillqvist
CommitDate: Mon Oct 22 23:24:21 2018 +0300
ICU version has been bumped
Change-Id: I135f989dcd65c3aeb5d12dc4f14839cb1e30f6ec
diff --git a/Mobile/Mobile.xcodeproj/project.pbxproj
b/Mobile/Mobile.xcodeproj/project.pbxproj
index 9dbda55f2..3d0f71332 100644
--- a/Mobile/Mobile.xcodeproj/project.pbxproj
+++ b/Mobile/Mobile.xcodeproj/project.pbxproj
@@ -30,7 +30,7 @@
BE5EB5D421400DC100E0826C /* DocumentBroker.cpp in Sources */ =
{isa = PBXBuildFile; fileRef = BE5EB5D321400DC100E0826C /* DocumentBroker.cpp
*/; };
BE5EB5D621401E0F00E0826C /* Storage.cpp in Sources */ = {isa =
PBXBuildFile; fileRef = BE5EB5D521401E0F00E0826C /* Storage.cpp */; };
BE5EB5DA2140363100E0826C /* ios.mm in Sources */ = {isa =
PBXBuildFile; fileRef = BE5EB5D92140363100E0826C /* ios.mm */; };
- BE5EB5DC2140480B00E0826C /* icudt62l.dat in Resources */ = {isa
= PBXBuildFile; fileRef = BE5EB5DB2140480B00E0826C /* icudt62l.dat */; };
+ BE5EB5DC2140480B00E0826C /* icudt63l.dat in Resources */ = {isa
= PBXBuildFile; fileRef = BE5EB5DB2140480B00E0826C /* icudt63l.dat */; };
BE6362C22153B5B500F4237E /* MobileCoreServices.framework in
Frameworks */ = {isa = PBXBuildFile; fileRef = BE6362C12153B5B500F4237E /*
MobileCoreServices.framework */; };
BE8D772C2136762500AC58EA /* AppDelegate.mm in Sources */ = {isa
= PBXBuildFile; fileRef = BE8D772B2136762500AC58EA /* AppDelegate.mm */; };
BE8D772F2136762500AC58EA /* DocumentBrowserViewController.mm in
Sources */ = {isa = PBXBuildFile; fileRef = BE8D772E2136762500AC58EA /*
DocumentBrowserViewController.mm */; };
@@ -86,7 +86,7 @@
BE5EB5D321400DC100E0826C /* DocumentBroker.cpp */ = {isa =
PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.cpp.cpp;
path = DocumentBroker.cpp; sourceTree = ""; };
BE5EB5D521401E0F00E0826C /* Storage.cpp */ = {isa =
PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.cpp.cpp;
path = Storage.cpp; sourceTree = ""; };
BE5EB5D92140363100E0826C /* ios.mm */ = {isa =
PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.cpp.objcpp;
name = ios.mm; path = ../../ios/ios.mm; sourceTree = ""; };
- BE5EB5DB2140480B00E0826C /* icudt62l.dat */ = {isa =
PBXFileReference; lastKnownFileType = file; name = icudt62l.dat; path =
"../../../../ios-device/workdir/CustomTarget/ios/resources/icudt62l.dat";
sourceTree = ""; };
+ BE5EB5DB2140480B00E0826C /* icudt63l.dat */ = {isa =
PBXFileReference; lastKnownFileType = file; name = icudt63l.dat; path =
"../../../../ios-device/workdir/CustomTarget/ios/resources/icudt63l.dat";
sourceTree = ""; };
BE636210215101D000F4237E /* WebSocketHandler.hpp */ = {isa =
PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.cpp.h; path
= WebSocketHandler.hpp; sourceTree = ""; };
BE6362C12153B5B500F4237E /* MobileCoreServices.framework */ =
{isa = PBXFileReference; lastKnownFileType = wrapper.framework; name =
MobileCoreServices.framework; path =
System/Library/Frameworks/MobileCoreServices.framework; sourceTree = SDKROOT; };
BE8D77272136762500AC58EA /* Mobile.app */ = {isa =
PBXFileReference; explicitFileType = wrapper.application; includeInIndex = 0;
path = Mobile.app; sourceTree = BUILT_PRODUCTS_DIR; };
@@ -282,7 +282,7 @@
BE8D85BD214055F2009F1860 /* share */,
BE8D85C1214055F2009F1860 /* udkapi.rdb */,
BE8D85C7214055F3009F1860 /* unorc */,
- BE5EB5DB2140480B00E0826C /* icudt62l.dat */,
+ BE5EB5DB2140480B00E0826C /* icudt63l.dat */,
BE00F89721396585001CE2D4 /* bundle.css */,
BE00F89921396585001CE2D4 /* bundle.js */,
BE00F89E21396585001CE2D4 /* images */,
@@ -669,7 +669,7 @@
BE8D85C9214055F3009F1860 /* filter in Resources
*/,
BE8D85CD214055F3009F1860 /* registry in
Resources */,
BE00F8A821396585001CE2D4 /* images in Resources
*/,
- BE5EB5DC2140480B00E0826C /* icudt62l.dat in
Resources */,
+ BE5EB5DC2140480B00E0826C /* icudt63l.dat in
Resources */,
BE8D85CE214055F3009F1860 /* oovbaapi.rdb in
Resources */,
BE00F8A721396585001CE2D4 /* loleaflet-help.html
in Resources */,
[Libreoffice-bugs] [Bug 92222] FILESAVE: Shapes with Default Line Width Changed on Roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=9 Luke changed: What|Removed |Added Summary|FILESAVE: Shapes with |FILESAVE: Shapes with |Default Line Weigh(Width) |Default Line Width Changed |Changed on Roundtrip|on Roundtrip -- 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 92222] FILESAVE: Shapes with Default Line Weigh(Width) Changed on Roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=9 Luke changed: What|Removed |Added Summary|FILESAVE: Shapes Line |FILESAVE: Shapes with |Weigh(Width) changed on |Default Line Weigh(Width) |round trip |Changed on Roundtrip -- 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 92222] FILESAVE: Shapes Line Weigh(Width) changed on round trip
https://bugs.documentfoundation.org/show_bug.cgi?id=9 Luke changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=84 | |205 | -- 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
