Re: Test failure on some Windows systems with 125% display scaling, Chart2ImportTest::testAutomaticSizeBarChartVeryLongLabel

2022-11-20 Thread Miklos Vajna
Hi,

On Sun, Nov 20, 2022 at 03:06:16PM +0100, Regina Henschel 
 wrote:
> In this case a tolerance is no solution. The text box which is generated by
> the automatic indeed differs between 96 dpi and 120 dpi, see attached
> screenshots. One has six, the other has seven words in the line.
> 
> We can fix the test itself or restrict it to 96dpi. Or fix the automatic
> that layouts labels.
> 
> There exist more of such tests, but I have not made up a list of such test.
> Perhaps something to discuss in ESC, how to treat such dpi depending tests.

My understanding is that file formats deal with logic units most of the
time; so if our output is DPI-dependent, that's a bug to be fixed.

If for some reason there is no time to track down the root of the
problem, adding tolerance or "if (!IsDefaultDPI()) return;" snippets can
work around the problem.

Regards,

Miklos


[Libreoffice-bugs] [Bug 152141] Category's Labels don't work

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152141

--- Comment #3 from Fabio  ---
Created attachment 183688
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183688=edit
I show the problem

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152092] Libreoffice impress freezes when I try to move slides and I'm forced to quit. 'EDITING'

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152092

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
I haven't been able to reproduce with:

Version: 7.3.6.2 / LibreOffice Community
Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: de-DE (en_AU.UTF-8); UI: en-US
Calc: threaded

Or:

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: deb7bc82de19ea8e20c767fdf21f9ba4feb5e9f0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Could you please try:

- Updating to 7.3.7: https://www.libreoffice.org/download/download-libreoffice/
- If that doesn't help, you can try a more recent version, like 7.4 (version
7.3 shoudn't see any more releases)

Does this happen with any document in particular? In that case, it would be
helpful to share a file as an attachment, to help us test.

Thank you!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152150] gtk3: Non-modal dialog on top of modal dialog unusable

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152150

Samuel Mehrbrodt (allotropia)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||8971
 CC||caol...@redhat.com,
   ||samuel.mehrbrodt@allotropia
   ||.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152150] New: gtk3: Non-modal dialog on top of modal dialog unusable

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152150

Bug ID: 152150
   Summary: gtk3: Non-modal dialog on top of modal dialog unusable
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: samuel.mehrbr...@allotropia.de

1. Open Writer
2. File->Export As->Export as PDF
3. Enable "Universal Accessibility (PDF/UA)
4. Export

-> Accessibility Check dialog appears

Expected: Any of the buttons in the dialog can be clicked

Actual: Buttons not clickable

Works with gen, doesn't work with gtk3.

Problem since 1409159d6117d49e61fe5369f858239ff259fc1e

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 38933] python add-in cannot return array in calc in-cell function

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38933

nobu  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #12 from nobu  ---
Version 7.1.2 or later
It has been confirmed that if you write a code that returns the array, you will
return the array as expected.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 127593] [META] Python Macro bugs

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127593
Bug 127593 depends on bug 38933, which changed state.

Bug 38933 Summary: python add-in cannot return array in calc in-cell function
https://bugs.documentfoundation.org/show_bug.cgi?id=38933

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104113] [META] Extension manager dialog bugs and enhancements

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104113
Bug 104113 depends on bug 38933, which changed state.

Bug 38933 Summary: python add-in cannot return array in calc in-cell function
https://bugs.documentfoundation.org/show_bug.cgi?id=38933

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152146] HYPERTEXT() does not work with click or doubleclick.

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152146

Julien Nabet  changed:

   What|Removed |Added

Summary|HYPERTEXT() does not work   |HYPERTEXT() does not work
   |with click ot doubleclick.  |with click or doubleclick.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104980] Notebookbar contextual groups: no indication if document modified/to be saved

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104980

--- Comment #9 from Helmut Leininger  ---
Still present in LO 7.4.3.2

in other bar configurations, a dot is shown on the diskette icon when the
document is modified. This is not the case with notebook bar in Register or
Grouped mode

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149800] Unwanted white border in exported SVG

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149800

László Németh  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
   Assignee|nem...@numbertext.org   |libreoffice-b...@lists.free
   ||desktop.org

--- Comment #4 from László Németh  ---
@Dolon: many thanks for the detailed bug report!

@Buovjaga, Rainer Bielefeld: many thanks for the QA!

Commit description:

tdf#149800 SVG export: remove extra white line of semi-transparent shape

A shape is exported using two svg:paths, first one is for the
fill, and the second one is for the line. Semi-transparency of
shapes enabled the disabled stroke of the first path, resulting
an ~1 pt width extra white line behind the normal line of the
shape. It was visible only, if the normal shape line was thinner
than 1 pt, or if the normal line was semi-transparent or disabled.
The extra line got the same transparency value, as the fill,
so its visibility depended on that, too.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 111450] [META] SVG fileSave filter (Draw/Impress)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=111450
Bug 111450 depends on bug 149800, which changed state.

Bug 149800 Summary: Unwanted white border in exported SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=149800

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113592] LibreLogo: add fallback localization to fix platform issues

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113592

--- Comment #6 from Commit Notification 
 ---
László Németh committed a patch related to this issue.
It has been pushed to "master":

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

tdf#113592 LibreLogo: update fallback localization

It will be available in 7.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113592] LibreLogo: add fallback localization to fix platform issues

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113592

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:6.0.0 target:5.4.4   |target:6.0.0 target:5.4.4
   ||target:7.5.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

2022-11-20 Thread László Németh (via logerrit)
 librelogo/source/LibreLogo/LibreLogo.py |  278 
 1 file changed, 139 insertions(+), 139 deletions(-)

New commits:
commit d687d74a4e3ba70a4e21fcd7db532c3cffc7d4d2
Author: László Németh 
AuthorDate: Sun Nov 20 20:48:58 2022 +0100
Commit: László Németh 
CommitDate: Mon Nov 21 08:09:02 2022 +0100

tdf#113592 LibreLogo: update fallback localization

Follow up to commit d4c92c836c42d8fa7e31657d0534bef3979a03e2
"LibreLogo: add command FONTTRANSPARENCY".

See also commit 5948e2e9f032916e3278f904097eff6b47b869d6
"LibreLogo: fix ast, gug, hsb and sid language support".

Change-Id: I6464091ce66ae302b1f6207f954bf06788bc1e02
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143004
Tested-by: Jenkins
Reviewed-by: László Németh 

diff --git a/librelogo/source/LibreLogo/LibreLogo.py 
b/librelogo/source/LibreLogo/LibreLogo.py
index 2b7af994eb61..bb776ca18c81 100644
--- a/librelogo/source/LibreLogo/LibreLogo.py
+++ b/librelogo/source/LibreLogo/LibreLogo.py
@@ -2103,143 +2103,143 @@ g_exportedScripts = left, right, goforward, 
gobackward, run, stop, home, clearsc
 # vim: set shiftwidth=4 softtabstop=4 expandtab:
 
 __lng_fallback__ = {
-'ORANGE':{'lt': 'oranžinė', 'sid': 'burtukaane', 'fi': 'oranssi', 'ro': 
'orange|portocaliu', 'lv': 'oranžs', 'kn': 'ವ್ಯಾಪ್ತಿ', 'nn': 'oransje|orange', 
'tr': 'turuncu', 'es': 'naranja', 'el': 'πορτοκαλί|orange', 'hr': 'narančasta', 
'cs': 'oranžová', 'sr_Latn': 'narandžasta', 'he': 'כתום', 'nl': 'oranje', 'hu': 
'narancssárga|narancs', 'hi': 'दायरा', 'ml': 'ഓറഞ്ച്', 'gu': 'નારંગી', 'ko': 
'오렌지', 'zh_TW': '橘黃|橙黃|橙|橘|orange', 'mr': 'नारंगी', 'ru': 'оранжевый', 'sl': 
'oranžna', 'bn_IN': 'পরিসর', 'am': 'ብርቱካን', 'et': 'oranž|apelsinikarva', 'uk': 
'оранжевий', 'pt_BR': 'laranja', 'kk': 'қызғылт-сары', 'te': 'ఆరెంజ్', 'br': 
'orañjez', 'is': 'appelsínugult', 'km': '\u200bទឹក\u200bក្រូច', 'bs': 
'narandžasta', 'eu': 'laranja', 'cy': 'oren', 'pa_IN': 'ਰੇਜ਼', 'ast': 
'naranxa', 'gug': 'narã', 'vi': 'phạm vi',
  'as': 'সুমথীৰা', 'gd': 'orains', 'or': 'କମଳା', 'ja': 'オレンジ|オレンジ色|orange', 
'hsb': 'oranžowy', 'nb': 'oransje|orange', 'be': 'аранжавы', 'oc': 'irange', 
'gl': 'laranxa', 'ar': 'برتقالي', 'en_US': 'orange', 'sk': 'oblasť', 'sr': 
'наранџаста', 'zh_CN': '橙色|橙|orange', 'eo': 'oranĝa', 'ta': 'ஆரஞ்சு', 
'ca_valencia': 'taronja', 'ne': 'दायरा', 'ca': 'taronja', 'si': 'පරාසය', 'my': 
'ကန့်သတ်နယ်ပယ်', 'ka': 'ფორთოხლისფერი'},
-'POINT':{'lt': 'skritulys', 'th': 'จุด', 'sid': 'bixxille', 'fi': 'piste', 
'ro': 'point|punct', 'lv': 'punkts', 'kn': 'ಬಿಂದುಗಳು', 'hsb': 'dypk', 'tr': 
'nokta', 'es': 'punto', 'el': 'σημείο|point', 'hr': 'točka', 'cs': 
'bod|puntík', 'de': 'punkt', 'mn': 'цэг', 'he': 'נקודה', 'nl': 'punt', 'hu': 
'pont', 'hi': 'बिंदु', 'ml': 'പോയിന്റ്', 'gu': 'બિંદુ', 'my': 'အမှတ်', 'ko': 
'점', 'zh_TW': '點|point', 'mr': 'बिंदू', 'ru': 'точка', 'sl': 'točka', 'bn_IN': 
'পয়েন্ট', 'am': 'ነጥቦች', 'et': 'punkt', 'uk': 'точка', 'pt_BR': 'ponto', 'kk': 
'нүкте', 'te': 'బిందువు', 'br': 'poent', 'is': 'punktur', 'km': 'ចំណុច', 'bs': 
'tačka', 'eu': 'puntua', 'cy': 'pwynt', 'pa_IN': 'ਬਿੰਦੂ', 'ast': 'puntu', 
'gug': 'kyta', 'vi': 'điểm', 'as': 'বিন্দু', 'gd': 'puing', 'or': 'ବିନ୍ଦୁ', 
'ja': '点|point', 'nn': 'punkt|point', 'nb
 ': 'punkt|point', 'be': 'пункт', 'sq': 'pikë', 'oc': 'punt', 'gl': 'punto', 
'ar': 'نقطة', 'en_US': 'point', 'sk': 'bod', 'zh_CN': '点|point', 'eo': 
'punkto', 'ta': 'புள்ளி', 'ca_valencia': 'punt', 'ne': 'प्वाइन्ट', 'ca': 
'punt', 'si': 'ලක්ෂ්\u200dය', 'ug': 'نۇقتا', 'ka': 'წერტილი'},
-'LEFTSTRING':{'lt': '„|“|‘', 'hsb': '„|‚|"|\'', 'hu': '„', 'fi': '"|\'|”', 
'en_US': '“|‘', 'sk': '„|"', 'nn': '“|‘|«', 'es': '“|‘|«', 'el': '“|‘|"|\'', 
'et': '„', 'zh_TW': '「|『|“|‘', 'cs': '„|"', 'de': '„|‚|"|\'', 'zh_CN': 
'「|『|“|‘'},
-'ABS':{'lt': 'ilgis|abs|modulis', 'sid': 'abse', 'ka': 'ტაბულაციები', 'fi': 
'itseisarvo', 'br': 'dizave', 'pa_IN': 'ਟੈਬ', 'kn': 'ಟ್ಯಾಬ್\u200cಗಳು', 'hsb': 
'absolutny', 'bn_IN': 'ট্যাব', 'el': 'απόλυτο', 'lv': 'modulis', 'tr': 
'Sekmeler', 'vi': 'Tab', 'cs': 'absolutní', 'de': 'betrag', 'he': 'ערך מוחלט', 
'hu': 'abszolútérték|absz?', 'hi': 'टैब्स', 'ar': 'مطلق', 'en_US': 'abs', 'te': 
'టాబ్ లు', 'ko': '탭', 'ne': 'ट्याबहरू', 'zh_TW': '絕對值|abs', 'mr': 'ॲब्स', 'si': 
'පටිති', 'zh_CN': '绝对值|abs', 'ja': '絶対値|abs', 'my': 'အကွက်ခုန်များ', 'am': 
'ፍጹም', 'et': 'absoluutväärtus|abs'},
-'RESUB':{'lt': 'keisk', 'sid': 'cinaancho', 'pt_BR': 'subst', 'fi': 'korvaa', 
'br': 'is', 'uk': 'зам', 'lv': 'aizvietot', 'kn': 'ಉಪ', 'nn': 'byt|byt ut|sub', 
'ja': '文字のおきかえ|置換|sub', 'el': 'αντικατάσταση', 'cs': 'nahraď', 'de': 'ersetzt', 
'nl': 'onderlijn', 'or': 'ଉପ', 'sl': 'zam', 'hsb': 'naruna', 'eu': 'azpi', 
'nb': 'bytt|bytt ut|sub', 'hu': 'cserél', 'ar': 'استبدل', 'gu': 'ઉપ', 'en_US': 
'sub', 'sk': 'nahraď', 'eo': 'anstataŭu|anst', 'zh_TW': '替換|sub', 'mr': 'सब', 
'he': 'שגרה', 'zh_CN': '替换|sub', 'am': 'ንዑስ', 'et': 'asenda'},
-'FILLCOLOR':{'lt': 'spalvinimo.spalva|ssp', 'sid': 

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

2022-11-20 Thread László Németh (via logerrit)
 filter/qa/unit/data/semi-transparent-fill.odg |binary
 filter/qa/unit/svg.cxx|   32 ++
 filter/source/svg/svgwriter.cxx   |6 
 3 files changed, 37 insertions(+), 1 deletion(-)

New commits:
commit 07711c8482714f970c57688629c591f8f3aa135f
Author: László Németh 
AuthorDate: Sun Nov 20 16:18:45 2022 +0100
Commit: László Németh 
CommitDate: Mon Nov 21 08:08:26 2022 +0100

tdf#149800 SVG export: remove extra white line of semi-transparent shape

A shape is exported using two svg:paths, first one is for the
fill, and the second one is for the line. Semi-transparency of
shapes enabled the disabled stroke of the first path, resulting
an ~1 pt width extra white line behind the normal line of the
shape. It was visible only, if the normal shape line was thinner
than 1 pt, or if the normal line was semi-transparent or disabled.
The extra line got the same transparency value, as the fill,
so its visibility depended on that, too.

Change-Id: Idc40971cc73ec9e4f241974ae29c876d06cc0658
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143003
Tested-by: Jenkins
Reviewed-by: László Németh 

diff --git a/filter/qa/unit/data/semi-transparent-fill.odg 
b/filter/qa/unit/data/semi-transparent-fill.odg
new file mode 100644
index ..713f48991bcb
Binary files /dev/null and b/filter/qa/unit/data/semi-transparent-fill.odg 
differ
diff --git a/filter/qa/unit/svg.cxx b/filter/qa/unit/svg.cxx
index a650deb1fc72..824b73383af4 100644
--- a/filter/qa/unit/svg.cxx
+++ b/filter/qa/unit/svg.cxx
@@ -105,6 +105,38 @@ CPPUNIT_TEST_FIXTURE(SvgFilterTest, 
testSemiTransparentLine)
 CPPUNIT_ASSERT_EQUAL(30, nPercent);
 }
 
+CPPUNIT_TEST_FIXTURE(SvgFilterTest, testSemiTransparentFillWithTransparentLine)
+{
+// Load a document with a shape with semi-transparent fill and line
+loadFromURL(u"semi-transparent-fill.odg");
+
+// Export it to SVG.
+uno::Reference xStorable(mxComponent, 
uno::UNO_QUERY_THROW);
+SvMemoryStream aStream;
+uno::Reference xOut = new 
utl::OOutputStreamWrapper(aStream);
+utl::MediaDescriptor aMediaDescriptor;
+aMediaDescriptor["FilterName"] <<= OUString("draw_svg_Export");
+aMediaDescriptor["OutputStream"] <<= xOut;
+xStorable->storeToURL("private:stream", 
aMediaDescriptor.getAsConstPropertyValueList());
+aStream.Seek(STREAM_SEEK_TO_BEGIN);
+
+// Get the style of the group around the actual  element.
+xmlDocUniquePtr pXmlDoc = parseXmlStream();
+OUString aStyle = getXPath(
+pXmlDoc, 
"//svg:g[@class='com.sun.star.drawing.EllipseShape']/svg:g/svg:g", "style");
+CPPUNIT_ASSERT(aStyle.startsWith("opacity: ", ));
+int nPercent = std::round(aStyle.toDouble() * 100);
+// Make sure that the line is still 50% opaque
+CPPUNIT_ASSERT_EQUAL(50, nPercent);
+
+// Get the stroke of the fill of the EllipseShape (it must be "none")
+OUString aStroke = getXPath(
+pXmlDoc, 
"//svg:g[@class='com.sun.star.drawing.EllipseShape']/svg:g/svg:path", "stroke");
+// Without the accompanying fix in place, this test would have failed, as 
the stroke was
+// "rgb(255,255,255)", not "none".
+CPPUNIT_ASSERT_EQUAL(OUString("none"), aStroke);
+}
+
 CPPUNIT_TEST_FIXTURE(SvgFilterTest, testSemiTransparentText)
 {
 // Two shapes, one with transparent text and the other one with
diff --git a/filter/source/svg/svgwriter.cxx b/filter/source/svg/svgwriter.cxx
index ec976ccb6f12..65ccab68bbb0 100644
--- a/filter/source/svg/svgwriter.cxx
+++ b/filter/source/svg/svgwriter.cxx
@@ -3329,7 +3329,11 @@ void SVGActionWriter::ImplWriteActions( const 
GDIMetaFile& rMtf,
 {
 Color aNewLineColor( mpVDev->GetLineColor() ), 
aNewFillColor( mpVDev->GetFillColor() );
 
-aNewLineColor.SetAlpha( 255 - 
sal::static_int_cast( FRound( pA->GetTransparence() * 2.55 ) ) );
+// tdf#149800 do not change transparency of fully 
transparent
+// i.e. invisible line, because it makes it visible,
+// resulting an extra line behind the normal shape line
+if ( aNewLineColor.GetAlpha() > 0 )
+aNewLineColor.SetAlpha( 255 - 
sal::static_int_cast( FRound( pA->GetTransparence() * 2.55 ) ) );
 aNewFillColor.SetAlpha( 255 - 
sal::static_int_cast( FRound( pA->GetTransparence() * 2.55 ) ) );
 
 maAttributeWriter.AddPaintAttr( aNewLineColor, 
aNewFillColor );


[Libreoffice-bugs] [Bug 152138] Internet Options->Email help page is empty on macOS

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152138

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Ever confirmed|0   |1

--- Comment #3 from Buovjaga  ---
Set to NEW.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152108] spell-checking of mixed-language phrases

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152108

Ulrich Windl  changed:

   What|Removed |Added

 CC||ulrich.wi...@rz.uni-regensb
   ||urg.de

--- Comment #3 from Ulrich Windl  ---
(In reply to Stéphane Guillou (stragu) from comment #1)
> A similar report is Bug 131487.

Indeed; to me it seems that any marking for  specific language should override
the built-in word-boundaries.

So for the example (using pseudo-language)"Firewall-Regeln"
there should be two components: "Firewall" Using english language rules) and
"-Regeln" (using default (German) language rules); maybe the leading minus in
"-Regeln" actually causes the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152079

--- Comment #4 from Mike Kaganski  ---
(In reply to Mike Kaganski from comment #1)
> the API, which needs incompatible changes.

I see how I used bad / incorrect wording. Sorry. It's not "incompatible". It's
just a large set of new interfaces/methods, and also large changes (e.g., in
filters code) to use those. But that's all doable, and the scale is expected,
given the task.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152131] Dragging document from window header bar to another location copies wrong document version

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152131

--- Comment #1 from Mike Little  ---
This test was performed on:
Version: 7.4.2.3 / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Mac OS X 13.0; UI render: default; VCL: osx
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded


To reproduce this bug:

1. Create a new text document in LibreOffice Writer. Type "this is the original
document" into the document. 
>>MJL: Done. 

2. Save it under the name "Test.odt".
>>MJL: Done. 

3. Type "And this is an amendment" into the document.
>>MJL: Done. 


4. Save it under the name "Test001.odt".
>>MJL: Done, document saved as Test001.odt as the same path as "Test.odt".


5. Drag the document icon from the title bar of the window to another location
(such as the desktop). You will find that the dragged document is "Test.odt"
and not "Test001.odt". If you open the dragged file, you will see that it does
not contain the words "And this is an amendment". 

>>MJL:  Need to explain “Drag the document icon from the title bar of the 
>>window” … can you provide screen shot?  Which window? The LibreOffice “Start 
>>centre”, or a MacOS Finder window? I am assuming and testing for a MacOS 
>>“Finder” window, and dragging the Test001.odt to the desktop… 

Sorry, I opened the dragged file, and it contained the words “And this is an
amendment” 

>> Conclusion: I was not able to confirm the behaviour. Can you provide screen 
>> shots of the action: “Drag the document icon from the title bar of the 
>> window to another location (such as the desktop)”?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152079

--- Comment #3 from Mike Kaganski  ---
(In reply to Eyal Rozenberg from comment #2)
> Have developers, or the ESC, considered the possibility of maintaining the
> old API via some sort of adaptation layer, allowing for more permissiveness
> in the codebase itself? With the adaptation layer always implemented in
> terms of the more fluid API? And so that you get the old/stable API by
> default, but you can opt-in to the more current one with some preprocessor
> define or extra headers?

Unless that is unavoidable, I don't think it's reasonable; and we don't see a
blocker here yet: it's always easy to introduce a XInterfaceFoo2 over the
former XInterfaceFoo, and provide the new methods/properties there, alongside
with the old methods. This is how we always solve these problems, and this
covers your idea generally.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V4..(same sheet)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152134

--- Comment #2 from wzpd...@gmail.com ---
Correction, function working on Windows8.1 LO version 6.1.0.3 x64 and not v
4.0.
Bug on LO v7.4.2.3 x64 remains. Have since removed LO 7.4 from Windows11 and
installed v 6.1.0.3 x64 in its place and the function works normally as it did
on Windows8.1 so bug is in LO between these two versions..would like to upgrade
to most current version of LO that does not have this bug.. advise?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 109087] [META] Calc sheet header and footer bugs and enhancements

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109087
Bug 109087 depends on bug 145356, which changed state.

Bug 145356 Summary: EDITING: Calc doesn't use custom header font settings
https://bugs.documentfoundation.org/show_bug.cgi?id=145356

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103182
Bug 103182 depends on bug 145356, which changed state.

Bug 145356 Summary: EDITING: Calc doesn't use custom header font settings
https://bugs.documentfoundation.org/show_bug.cgi?id=145356

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 145356] EDITING: Calc doesn't use custom header font settings

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145356

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> ---
(In reply to Tom Williams from comment #3)
> This is working for me in Calc 7.3.7 on Ubuntu Linux. So, this bug report
> can be closed.

Thanks. Closed as WFM

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152138] Internet Options->Email help page is empty on macOS

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152138

--- Comment #2 from Mike Kaganski  ---
Thanks for testing! Just one step was missing:

0. Read and comprehend this report.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151936] Changing text color of form inputfield doesn't work

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151936

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151932] GalleryItem ( XGalleryItem ) wipes some of its properties as soon as it is returned from a function.

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151932

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151928] Installation Wizard is not maximizable and requires UX improvement

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151928

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148454] Crash when I change font size in KDE Plasma 5.22.5

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148454

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148454] Crash when I change font size in KDE Plasma 5.22.5

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148454

--- Comment #3 from QA Administrators  ---
Dear Samantha,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148420] imported scans went white after calling export to pdf

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148420

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 140533] wrong printout for barcode font i2of5txt

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140533

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148420] imported scans went white after calling export to pdf

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148420

--- Comment #3 from QA Administrators  ---
Dear Rikkit,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 140533] wrong printout for barcode font i2of5txt

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140533

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

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 137999] Changing motion path's proportion doesn't change file's "modified" status

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137999

--- Comment #2 from QA Administrators  ---
Dear Ming Hua,

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
https://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://web.libera.chat/?settings=#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] [Bug 137981] Image inside frame still present after cutting frame (but invisible)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137981

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://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://web.libera.chat/?settings=#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] [Bug 104980] Notebookbar contextual groups: no indication if document modified/to be saved

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104980

--- Comment #8 from QA Administrators  ---
Dear Helmut Leininger,

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
https://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://web.libera.chat/?settings=#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] [Bug 145356] EDITING: Calc doesn't use custom header font settings

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145356

--- Comment #3 from Tom Williams  ---
This is working for me in Calc 7.3.7 on Ubuntu Linux. So, this bug report can
be closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151152

Aron Budea  changed:

   What|Removed |Added

 OS|Linux (All) |All

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152148] The Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K()

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152148

Eike Rathke  changed:

   What|Removed |Added

  Component|Calc|Localization

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151152

Aron Budea  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152082] Converting .xlsx to .ods does not correctly convert chosen filtering options

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152082

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||1152

--- Comment #4 from Aron Budea  ---
(In reply to Roman Kuznetsov from comment #3)
> I bisected this one in win64-7.2 bisect repo and got
> 
> https://git.libreoffice.org/core/commit/
> 3069df790cca2917e5aedd87bac1af65f9605d51
That's a backport from 7.3, let's add the original as well. Also, same commit
as identified in bug 151152.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=f6b143a57d9bd8f5d7b29febcb4e01ee1eb2ff1d
author  Balazs Varga 2021-07-02
09:40:32 +0200
committer   László Németh2021-07-07 17:44:46
+0200

tdf#142910 sc filter: fix "greater than" or "smaller than" etc

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151152

Aron Budea  changed:

   What|Removed |Added

   Keywords||bisected
 CC||aron.bu...@gmail.com

--- Comment #3 from Aron Budea  ---
(In reply to Kevin Suo from comment #1)
> The following commit seems related:
> 
> commit f6b143a57d9bd8f5d7b29febcb4e01ee1eb2ff1d
Confirmed by checking this and the predecessor commit in the linux-64-7.3
bibisect repo.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152149] Can't Open "What's New" video to FULLSCREEN

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152149

rwillem...@gmail.com  changed:

   What|Removed |Added

URL||https://www.libreoffice.org
   ||/discover/new-features/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152149] New: Can't Open "What's New" video to FULLSCREEN

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152149

Bug ID: 152149
   Summary: Can't Open "What's New" video to FULLSCREEN
   Product: LibreOffice
   Version: 7.4.2.3 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rwillem...@gmail.com

Description:
On Main Page (www.libreoffice.org)  --> Discover ---> New Features.
On opening the video, the FULLSCREEN button does not work, i.e. clicking the
button does not open the video to full screen. Video plays fine but users will
not be able to read what the video is saying due to the small size of the video
window.  Copying the URL for the video and then playing it allows the user to
go to full screen. 

Steps to Reproduce:
1.Open the above listed web page
2. Start running the video
3. click on the Full Screen button

Actual Results:
Nothing happens

Expected Results:
Video should go to full screen


Reproducible: Always


User Profile Reset: No

Additional Info:
Nothing in help file

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152144] Font color recent list lost after using background fill

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152144

--- Comment #3 from m.a.riosv  ---
I can not get recent list cleared.
For both, when used 'Automatic' or 'Not fill', the default value became the
last on the recent list.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152141] Category's Labels don't work

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152141

--- Comment #2 from m.a.riosv  ---
Attach it here please, not sending a private email. Make it as simple as you
can.
Also to mention, a video, it's not of too much help.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152107] Clicking on a cell shows garbage as the formula

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152107

--- Comment #5 from LeroyG  ---
Related question in the ask site:

https://ask.libreoffice.org/t/disable-calc-automatically-selecting-a-cell-when-clicking-out-of-another-cell/83939

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152148] New: The Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K()

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152148

Bug ID: 152148
   Summary: The Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …)
and MIN.K()
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mand...@o2.pl

Description:
My review concerns the Polish version:
MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K()
1. Syntax error – „K” with „rząd_K” ≠ „K” with „MAKS.K”.
„K” with „MAKS.K” = K
„K” with „rząd_K” = 1, 2, 3...
My proposition - rename the function to:
MAKS.W() from MAKSymalna Wartość
MIN.W() from MINimalna Wartość

2. 2 bugs in feature description  MAKS.K()
„Zwraca K-tą największą wartość zbioru danych.”
1 – the greatest value is only for K=1,
2 – the dataset has no value.
My proposition:
„Zwraca wartości ze zbioru danych - od największej (w kolejności określonej
przez K).”

3. 2 bugs in feature description  MIN.K()
My proposition:
„Zwraca wartości ze zbioru danych - od najmnieszej (w kolejności określonej
przez K).”

4. Unnecessary synonym in the definition 
„Dane oznaczają zakres komórek zawierających dane.”
My proposition:
„dane oznaczają zakres komórek zbioru danych.”

Steps to Reproduce:
1.It's just an opinion.
2.It's just an opinion.
3.It's just an opinion.

Actual Results:
It's just an opinion.

Expected Results:
It's just an opinion.


Reproducible: Always


User Profile Reset: No

Additional Info:
It's just an opinion.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149758] void SwAutoFormat::DelEmptyLine(bool): Assertion `!m_aDelPam.HasMark()' failed.

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149758

Hossein  changed:

   What|Removed |Added

 CC||hoss...@libreoffice.org
 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |hoss...@libreoffice.org
   |desktop.org |

--- Comment #2 from Hossein  ---
Reproduced with the latest LO 7.5 dev master:

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1f9b2a7057a519e0ea750875ac439129f1d3df87
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152138] Internet Options->Email help page is empty on macOS

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152138

--- Comment #1 from Mike Little  ---
1.  Running MacOS…
Version: 7.4.2.3 / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Mac OS X 13.0; UI render: default; VCL: osx
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded


2.  Opened 7.4.2.3-rel, and a Writer application.
3.  Created a test Writer document.
4.  Choose File>Send>Email document
5.  Apple Mail appears, with the test Writer document embedded in the email
body. I have not previously choose the email program from the LibreOffice
Preferences, LibreOffice>Internet> Mail; this was configured by default.

Result: No problems with MacOS.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] help.git: Branch 'feature/cib_contract138e' - CustomTarget_html.mk CustomTarget_imagelist.mk

2022-11-20 Thread Thorsten Behrens (via logerrit)
Rebased ref, commits from common ancestor:
commit f09419188502aeaeaa97ea49930b8d58b8c934ff
Author: Thorsten Behrens 
AuthorDate: Mon Nov 21 00:35:37 2022 +0100
Commit: Thorsten Behrens 
CommitDate: Mon Nov 21 01:37:10 2022 +0100

Revert "Adapt helpcontent2 to var2file rename"

This reverts commit 15deec972f2ea1e2076a74c4d206b49967c68844.

In core: "Resolves: tdf#97046 ensure build system variables start with gb_"

This reverts commit 3829c0c7db8768ca05f148e8f5c271ddb56d5bae.

Change-Id: Ibed2945cbefb73039f2cf44e238a1641f93c68b9

diff --git a/CustomTarget_html.mk b/CustomTarget_html.mk
index 56224a7d90..f66dd95ca1 100644
--- a/CustomTarget_html.mk
+++ b/CustomTarget_html.mk
@@ -42,7 +42,7 @@ $(call 
gb_CustomTarget_get_workdir,helpcontent2/help3xsl)/hid2file.js : \
$(call gb_Helper_abbreviate_dirs,\
( \
echo 'var hid2fileMap = {' \
-   && RESPONSEFILE=$(call gb_var2file,$(shell 
$(gb_MKTEMP)),100,$(foreach module,$(html_TEXT_MODULES),$(addprefix 
$(SRCDIR)/,$(gb_AllLangHelp_$(module)_HELPFILES \
+   && RESPONSEFILE=$(call var2file,$(shell 
$(gb_MKTEMP)),100,$(foreach module,$(html_TEXT_MODULES),$(addprefix 
$(SRCDIR)/,$(gb_AllLangHelp_$(module)_HELPFILES \
&& <"$$RESPONSEFILE" $(if $(filter WNT,$(OS)),tr -d 
'\r' | env -i PATH="$$PATH") xargs -n 1 printf '%s\n' \
| while read xhp; do \
rm -f $@.good && \
@@ -216,7 +216,7 @@ $(call 
gb_CustomTarget_get_workdir,helpcontent2/help3xsl)/%/html.text : \
$(call gb_Helper_abbreviate_dirs,\
cd $(if $(filter en-US,$*),$(SRCDIR),$(call 
gb_HelpTranslatePartTarget_get_workdir,$*))/helpcontent2/source \
&& rm -rf $(dir $@)text \
-   && RESPONSEFILE=$(call gb_var2file,$(shell 
$(gb_MKTEMP)),100,$(foreach module,$(html_TEXT_MODULES),$(patsubst 
helpcontent2/source/%,%,$(gb_AllLangHelp_$(module)_HELPFILES \
+   && RESPONSEFILE=$(call var2file,$(shell 
$(gb_MKTEMP)),100,$(foreach module,$(html_TEXT_MODULES),$(patsubst 
helpcontent2/source/%,%,$(gb_AllLangHelp_$(module)_HELPFILES \
&& <"$$RESPONSEFILE" $(if $(filter WNT,$(OS)),tr -d '\r' | env 
-i PATH="$$PATH") xargs -n 1 printf '%s\n' \
| while read xhp; do \
mkdir -p $$(dirname $(dir $@)$$xhp) && \
@@ -285,7 +285,7 @@ $(call 
gb_CustomTarget_get_workdir,helpcontent2/help3xsl)/%/bookmarks.part : \
$(call gb_ExternalExecutable_get_dependencies,xsltproc)
$(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),XSL,1)
$(call gb_Helper_abbreviate_dirs,\
-   RESPONSEFILE=$(call gb_var2file,$(shell 
$(gb_MKTEMP)),100,$(addprefix $(if $(filter 
en-US,$(HELP_LANG)),$(SRCDIR),$(call 
gb_HelpTranslatePartTarget_get_workdir,$(HELP_LANG)))/,$(gb_AllLangHelp_$(APPDIR)_BOOKMARK_HELPFILES)))
 \
+   RESPONSEFILE=$(call var2file,$(shell 
$(gb_MKTEMP)),100,$(addprefix $(if $(filter 
en-US,$(HELP_LANG)),$(SRCDIR),$(call 
gb_HelpTranslatePartTarget_get_workdir,$(HELP_LANG)))/,$(gb_AllLangHelp_$(APPDIR)_BOOKMARK_HELPFILES)))
 \
&& ( \
<"$$RESPONSEFILE" $(if $(filter WNT,$(OS)),tr -d '\r' | 
env -i PATH="$$PATH") xargs -n 1 printf '%s\n' \
| { rm -f $@.good && while read xhp; do \
diff --git a/CustomTarget_imagelist.mk b/CustomTarget_imagelist.mk
index 86350a530d..06225f121c 100644
--- a/CustomTarget_imagelist.mk
+++ b/CustomTarget_imagelist.mk
@@ -21,7 +21,7 @@ $(call 
gb_CustomTarget_get_workdir,helpcontent2/source/auxiliary)/images_helpimg
| $(call gb_ExternalExecutable_get_dependencies,python)
$(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),PRL,1)
$(call gb_Helper_abbreviate_dirs, \
-   ILSTFILE=$(call gb_var2file,$(shell $(gb_MKTEMP)),100,$(filter 
%.ilst,$^)) && \
+   ILSTFILE=$(call var2file,$(shell $(gb_MKTEMP)),100,$(filter 
%.ilst,$^)) && \
$(call gb_ExternalExecutable_get_command,python) 
$(SRCDIR)/solenv/bin/pack_images.py \
-g $(helpmedia_DIR) -m $(helpmedia_DIR) -c 
$(helpmedia_DIR) \
-l $${ILSTFILE} \


[Libreoffice-commits] core.git: Branch 'feature/cib_contract138e' - helpcontent2

2022-11-20 Thread Thorsten Behrens (via logerrit)
 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit c2167cbdca0390d0386b0b32e2b58af4fc913e71
Author: Thorsten Behrens 
AuthorDate: Mon Nov 21 01:38:08 2022 +0100
Commit: Gerrit Code Review 
CommitDate: Mon Nov 21 01:38:08 2022 +0100

Update git submodules

* Update helpcontent2 from branch 'feature/cib_contract138e'
  to f09419188502aeaeaa97ea49930b8d58b8c934ff
  - Revert "Adapt helpcontent2 to var2file rename"

This reverts commit 15deec972f2ea1e2076a74c4d206b49967c68844.

In core: "Resolves: tdf#97046 ensure build system variables start with 
gb_"

This reverts commit 3829c0c7db8768ca05f148e8f5c271ddb56d5bae.

Change-Id: Ibed2945cbefb73039f2cf44e238a1641f93c68b9

diff --git a/helpcontent2 b/helpcontent2
index a3659faccafe..f09419188502 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit a3659faccafe6eb26822883d3270f988b4ae2a4e
+Subproject commit f09419188502aeaeaa97ea49930b8d58b8c934ff


[Libreoffice-bugs] [Bug 152147] Default keyboard shortcut for non-breaking hyphen does not work

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152147

--- Comment #1 from LeroyG  ---
For me works well, although Ctrl+Shift+- "is not listed as an option" (in the
Shortcut Keys list), so I think that it is not configurable.

- What shortcut do you see in menu Insert - Formatting Mark - Insert
non-breaking hyphen? The same appear in the "Tooltip" when hovering the mouse
pointer over the "Insert non-breaking hyphen" function (menu Tool - Customize -
Keyboard tab)?
- Do you remember the previous version number in which it worked for you?
- What is the "7.4.2-2" within your LibreOffice version information?

With me:
Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: es-MX (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: Changes to 'feature/cib_contract138e'

2022-11-20 Thread Thorsten Behrens (via logerrit)
New branch 'feature/cib_contract138e' available with the following commits:
commit f628a0619863503548a5048aa7d576b1beeb5197
Author: Thorsten Behrens 
Date:   Mon Nov 21 01:28:56 2022 +0100

Make build with Qt5.5

Change-Id: Ic9946cefd4917e764e2f55bb3b6fb158f1629439

commit 77e772c66a6351bed3b9126e323886d9311cb98b
Author: Thorsten Behrens 
Date:   Fri Nov 18 21:58:00 2022 +0100

Revert "tdf#131572 Add java 9 module info for libreoffice.jar"

This reverts commit 941b567a41569260fef14a7337511e8f42337323.

Change-Id: Ic9e0974f2c7800e2c9360fd240abe8d8f692b375

Conflicts:
configure.ac
solenv/gbuild/JavaClassSet.mk

commit 70fc387729695b299b31a5c80866494f74d76f0c
Author: Thorsten Behrens 
Date:   Fri Nov 18 21:55:30 2022 +0100

Revert "tdf#131572 Add java 9 module info for unoloader.jar"

This reverts commit 89cb33dde0c4cd27ca05e31ddea94b7129bc6ebb.

commit 338ed2cbce37e39aba4f6cedbd3b78b678b77896
Author: Thorsten Behrens 
Date:   Fri Nov 18 21:55:18 2022 +0100

Revert "Remove tempfile again"

This reverts commit 8fd8f2ec973b9bdf4ab12056cd37bb817a53edad.

commit a5f937b7481bf569639e0d7076d22134264ce780
Author: Thorsten Behrens 
Date:   Fri Nov 18 21:55:09 2022 +0100

Revert "Resolves: tdf#97046 ensure build system variables start with gb_"

This reverts commit 3829c0c7db8768ca05f148e8f5c271ddb56d5bae.

commit 054d9da2152585e4abf6e33bc9312de67133a254
Author: Thorsten Behrens 
Date:   Fri Nov 18 17:27:09 2022 +0100

Revert "The minimal supported Qt5 version is 5.6"

This reverts commit 81dc2f68dffb9e58e99d5deddb1124f6ec047a25.



[Libreoffice-commits] help.git: Changes to 'feature/cib_contract138e'

2022-11-20 Thread Thorsten Behrens (via logerrit)
New branch 'feature/cib_contract138e' available with the following commits:
commit 414cfe4b952380cca35b27934bff42d5990c6b3a
Author: Thorsten Behrens 
Date:   Mon Nov 21 00:35:37 2022 +0100

Revert "Adapt helpcontent2 to var2file rename"

This reverts commit 15deec972f2ea1e2076a74c4d206b49967c68844.



[Libreoffice-bugs] [Bug 152147] New: Default keyboard shortcut for non-breaking hyphen does not work

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152147

Bug ID: 152147
   Summary: Default keyboard shortcut for non-breaking hyphen does
not work
   Product: LibreOffice
   Version: 7.4.2.3 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: de...@screee.ee

Description:
As stated by the title, the established keyboard shortcut to insert a
non-breaking-hyphen (Ctrl+Shift+Minus) does nothing. This shortcut is mentioned
by the 'Home' extended menu in the 'Tabbed' UI, as well as official
documentation at
https://help.libreoffice.org/latest/en-US/text/shared/guide/space_hyphen.html

It cannot be manually assigned either, because it is currently impossible to
create keyboard shortcuts using the Minus/Plus keys with most modifier
combinations, including Ctrl+Shift. (This probably warrants its own bug
report?)

If this is intended behavior, then at the very least, all mentions of the
shortcut should be removed from the UI and official documentation. Although
reinstating the shortcut would be the better option, if at all possible.

I do not have the time to install and try to reproduce this in earlier versions
of LibreOffice right now, so the version specified is simply the one I
currently have installed. Resetting LibreOffice by removing
$HOME/.config/libreoffice did not resolve the issue.

Steps to Reproduce:
a) Press Ctrl+Shift+Minus inside a document

b) Open the keyboard shortcuts assignment window

Actual Results:
a) Nothing happens

b) Ctrl+Shift+Minus is not listed as an option

Expected Results:
a) A non-breaking hyphen is inserted into the document

b) Ctrl+Shift+Minus is listed as an option, assigned to non-breaking hyphen by
default


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Arch Linux, installed via package: extra/libreoffice-fresh

Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-GB (en_GB.UTF-8); UI: en-US
7.4.2-2
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152146] HYPERTEXT() does not work with click ot doubleclick.

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152146

--- Comment #1 from MARINA-SODA  ---
If you use Ctrl+ to open a hyperlink, this problem also occurs when you try to
open a link while the next cell is selected, for example. Therefore, I set the
link opening method to single click, but even autofill does not work.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152146] New: HYPERTEXT() does not work with click ot doubleclick.

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152146

Bug ID: 152146
   Summary: HYPERTEXT() does not work with click ot doubleclick.
   Product: LibreOffice
   Version: 7.2.3.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: m5382607...@gomen-da.com

Description:
The formula "hypertext()" have many issue.

1.The first time if you wrote the formula is success.
2.The after of over the second time, your hyperlink will not work.

If you click or double click, you can't open the link and if you touch these
cells, you can't see popup message. ---> Click to open hyperlink "c://.".

Steps to Reproduce:
1.There is a list on another sheet. Write a function that creates a link from
the contents of that list to a local folder.
2.For example, if you write in A2 of Sheet2, "Autofill" downwards.
3.Click or double click the A cells. 

Actual Results:
You cant open after A2.

Expected Results:
You can open after A2 too.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Once it happens, the cell will not allow you to open hyperlinks.

Similar to this but different. It has nothing to do with cell properties.
Occurs in autofill even if it's not wrapped.
https://bugs.documentfoundation.org/show_bug.cgi?id=33951

I checked.

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: CL threaded

Version: 7.2.3.2 (x64) / LibreOffice Community
Build ID: d166454616c1632304285822f9c83ce2e660fd92
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 92122] UI: Floating panels cannot be docked, if "Show window contents while dragging" is disabled in Windows visual effects

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92122

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #24 from Regina Henschel  ---
>From the help:
"Docking toolbars and windows by drag-and-drop depends on your system's window
manager settings. You must enable your system to show the full window contents
when you move a window, instead of showing just the outer frame."

It would be an enhancement to enable LibreOffice to drag-and-drop windows if
the system is set to show only the outer frame. The problem is, that windows
are really system windows, not something which LibreOffice has made itself.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 139772] FILEOPEN PDF: Importing results in poor import quality on some pdf files (testfile included)

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139772

V Stuart Foote  changed:

   What|Removed |Added

 CC||ashodnakash...@yahoo.com,
   ||qui...@gmail.com,
   ||vsfo...@libreoffice.org

--- Comment #6 from V Stuart Foote  ---
Hmm, I set the new project provided os/DE environment variable 

PDFIMPORT_RESOLUTION_DPI = 300 (or higher)

But seems like the pdfimport filter still uses the default 96dpi for PDFs like
this composed of raster image pages, and the pixilation noted occurs.

But if I "insert as image" with the pdfium filter, the first page of the PDF
gets rendered to canvas with good quality at the page scale.

@Tomaž, @Ashod shouldn't the environment variable also be affecting the
pdfimport filters? Or am I missing something...

=-ref-=

https://gerrit.libreoffice.org/c/core/+/113223
https://gerrit.libreoffice.org/c/core/+/121087

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 92122] UI: Floating panels cannot be docked, if "Show window contents while dragging" is disabled in Windows visual effects

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92122

--- Comment #23 from V Stuart Foote  ---
Yes this remains an issue on Windows builds. And seemingly other os/DE

On Windows 10, as admin from CLI the "SystemPropertiesPerformance.exe"
'Performance Options' dialog, unchecking the Visual Effects tab 'Show window
contents while dragging' checkbox will no longer expose the docking target
rectangle as the mouse cursor passes over the target.

Checking it enabled restores the drag target.

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

or a current master against 7.5.0
Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bcf09f9a9bde21aac1302cbead2b23822458
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152144] Font color recent list lost after using background fill

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152144

--- Comment #2 from Jonny Grant  ---
Hi miguel, Interestingly the "Recent" list seems to get cleared when changing a
cell to "no fill" unfortunatly too.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107742

Hossein  changed:

   What|Removed |Added

 Depends on||152145


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152145
[Bug 152145] Placeholder text for the content control fields should be exported
to the output
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152145] Placeholder text for the content control fields should be exported to the output

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152145

Hossein  changed:

   What|Removed |Added

 CC||vmik...@collabora.com
 Blocks||107742


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107742
[Bug 107742] [META] Form control bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152145] New: Placeholder text for the content control fields should be exported to the output

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152145

Bug ID: 152145
   Summary: Placeholder text for the content control fields should
be exported to the output
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: hoss...@libreoffice.org

Description:
When exporting/printing a file containing content control fields, the
placeholder text for the fields (those without any selection/editing) should be
exported to the output.

Steps to Reproduce:
1. Open attachment 182846
2. Export the document to PDF

Actual Results:
The placeholder text on page 1 and elsewhere is not exported to PDF.

Expected Results:
The placeholder text should be exported to PDF. Compare page 1 from PDF output
from MS Word (attachment 183511) with the PDF output from LibreOffice 7.5 dev
master (attachment 183512).

Reproducible: Always


User Profile Reset: No


Additional Info:
Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1f9b2a7057a519e0ea750875ac439129f1d3df87
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 102914] Synthetic italic in fonts with partial coverage exported as regular in PDF

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102914

خالد حسني  changed:

   What|Removed |Added

 OS|Linux (All) |All

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 86211] PDF Import: clipping is not implemented

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86211

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99746

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||148526


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148526
[Bug 148526] LibreOffice Draw PDF file displayed incorrectly, visual elements
blocked by unmasked radial gradient
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 82262] Incorrect PDF import into Draw showing layers that should be masked

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82262

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148526] LibreOffice Draw PDF file displayed incorrectly, visual elements blocked by unmasked radial gradient

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148526

V Stuart Foote  changed:

   What|Removed |Added

Summary|LibreOffice Draw | PDF file |LibreOffice Draw PDF file
   |displayed incorrectly | |displayed incorrectly,
   |Visual elements missing |visual elements blocked by
   ||unmasked radial gradient
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=82
   ||262,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=86
   ||211
 Blocks||99746
 CC||vsfo...@libreoffice.org

--- Comment #5 from V Stuart Foote  ---
Remains valid, but this is a masking and clipping issue.

The superfluous radial gradients are fully hidden when using the Insert as
image pdfium import filter.  And, they can be selected and removed from the
Draw canvas otherwise.

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=99746
[Bug 99746] [META] PDF import filter in Draw
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: translations

2022-11-20 Thread Martin Srebotnjak (via logerrit)
 translations |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit deb7bc82de19ea8e20c767fdf21f9ba4feb5e9f0
Author: Martin Srebotnjak 
AuthorDate: Sun Nov 20 22:49:56 2022 +0100
Commit: Gerrit Code Review 
CommitDate: Sun Nov 20 22:49:56 2022 +0100

Update git submodules

* Update translations from branch 'master'
  to 5e9d458209fb3ee168e61c74388f3a0b64f2c12c
  - Updated Slovenian translation

Change-Id: Iaaf4affe6172da08385569d4d158f3e073eb4297

diff --git a/translations b/translations
index 7050fcc7a3b1..5e9d458209fb 16
--- a/translations
+++ b/translations
@@ -1 +1 @@
-Subproject commit 7050fcc7a3b1e899f3d93b6550d96f982809c9b0
+Subproject commit 5e9d458209fb3ee168e61c74388f3a0b64f2c12c


[Libreoffice-commits] translations.git: source/sl

2022-11-20 Thread Martin Srebotnjak (via logerrit)
 source/sl/chart2/messages.po  |  294 
 source/sl/cui/messages.po |  154 
 source/sl/dbaccess/messages.po|   38 
 source/sl/editeng/messages.po |4 
 source/sl/filter/messages.po  |4 
 source/sl/helpcontent2/source/text/sbasic/python.po   |4 
 source/sl/helpcontent2/source/text/sbasic/shared.po   |  216 
 source/sl/helpcontent2/source/text/sbasic/shared/03.po|4 
 source/sl/helpcontent2/source/text/scalc.po   |   16 
 source/sl/helpcontent2/source/text/scalc/00.po|   18 
 source/sl/helpcontent2/source/text/scalc/01.po|   70 
 source/sl/helpcontent2/source/text/scalc/guide.po |   30 
 source/sl/helpcontent2/source/text/schart/01.po   |4 
 source/sl/helpcontent2/source/text/sdatabase.po   |  122 
 source/sl/helpcontent2/source/text/sdraw.po   |   16 
 source/sl/helpcontent2/source/text/sdraw/01.po|4 
 source/sl/helpcontent2/source/text/sdraw/guide.po |4 
 source/sl/helpcontent2/source/text/shared.po  |4 
 source/sl/helpcontent2/source/text/shared/00.po   |  104 
 source/sl/helpcontent2/source/text/shared/01.po   |  112 
 source/sl/helpcontent2/source/text/shared/02.po   |   14 
 source/sl/helpcontent2/source/text/shared/06.po   |   12 
 source/sl/helpcontent2/source/text/shared/autopi.po   |   12 
 source/sl/helpcontent2/source/text/shared/guide.po|   20 
 source/sl/helpcontent2/source/text/shared/optionen.po |   74 
 source/sl/helpcontent2/source/text/simpress.po|   16 
 source/sl/helpcontent2/source/text/simpress/00.po |4 
 source/sl/helpcontent2/source/text/simpress/01.po |  332 
 source/sl/helpcontent2/source/text/simpress/guide.po  |8 
 source/sl/helpcontent2/source/text/smath.po   |   12 
 source/sl/helpcontent2/source/text/swriter.po |   30 
 source/sl/helpcontent2/source/text/swriter/01.po  |   34 
 source/sl/helpcontent2/source/text/swriter/02.po  |   96 
 source/sl/helpcontent2/source/text/swriter/guide.po   |   30 
 source/sl/helpcontent2/source/text/swriter/librelogo.po   |   12 
 source/sl/officecfg/registry/data/org/openoffice/Office/UI.po |   35 
 source/sl/sc/messages.po  |   12 
 source/sl/scaddins/messages.po|4 
 source/sl/sd/messages.po  |   73 
 source/sl/sfx2/messages.po|   65 
 source/sl/svtools/messages.po |  311 
 source/sl/svx/messages.po | 3387 --
 source/sl/sw/messages.po  |  793 +-
 43 files changed, 3387 insertions(+), 3221 deletions(-)

New commits:
commit 5e9d458209fb3ee168e61c74388f3a0b64f2c12c
Author: Martin Srebotnjak 
AuthorDate: Sun Nov 20 22:49:44 2022 +0100
Commit: Andras Timar 
CommitDate: Sun Nov 20 22:49:44 2022 +0100

Updated Slovenian translation

Change-Id: Iaaf4affe6172da08385569d4d158f3e073eb4297

diff --git a/source/sl/chart2/messages.po b/source/sl/chart2/messages.po
index c5e607eb658..6fffca4cef7 100644
--- a/source/sl/chart2/messages.po
+++ b/source/sl/chart2/messages.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 7.5\n"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI\n;
-"POT-Creation-Date: 2022-11-03 11:24+0100\n"
-"PO-Revision-Date: 2022-10-21 12:19+0200\n"
+"POT-Creation-Date: 2022-11-19 09:53+0100\n"
+"PO-Revision-Date: 2022-11-19 10:54+0200\n"
 "Last-Translator: Martin Srebotnjak \n"
 "Language-Team: sl.libreoffice.org\n"
+"Language: sl\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Language: sl\n"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);\n"
 "X-Generator: Virtaal 0.7.1\n"
 "X-Accelerator-Marker: ~\n"
@@ -1883,426 +1883,426 @@ msgctxt "sidebaraxis|checkbutton_show_label"
 msgid "Show labels"
 msgstr "Pokaži oznake"
 
-#: chart2/uiconfig/ui/sidebaraxis.ui:38
+#: chart2/uiconfig/ui/sidebaraxis.ui:40
 msgctxt "sidebaraxis|checkbutton_reverse"
 msgid "Reverse direction"
 msgstr "Nasprotna smer"
 
-#: chart2/uiconfig/ui/sidebaraxis.ui:63
+#: chart2/uiconfig/ui/sidebaraxis.ui:58
 msgctxt "sidebaraxis|label1"
 msgid "_Label position:"
 msgstr "Položaj _oznake:"
 
-#: chart2/uiconfig/ui/sidebaraxis.ui:77
+#: chart2/uiconfig/ui/sidebaraxis.ui:73
 msgctxt "sidebaraxis|comboboxtext_label_position"
 msgid "Near Axis"
 msgstr "Ob os"
 

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

2022-11-20 Thread Stephan Bergmann (via logerrit)
 l10ntools/source/cfgmerge.cxx |   15 +++
 1 file changed, 15 insertions(+)

New commits:
commit cb24017c84efdc91a73d91655664d9ae01a1d6d6
Author: Stephan Bergmann 
AuthorDate: Sun Nov 20 17:52:34 2022 +0100
Commit: Stephan Bergmann 
CommitDate: Sun Nov 20 22:40:27 2022 +0100

Clean up CfgParser::aStack

This is apparently some very old, very poor XML parsing code full of
questionable design decisions.  The silliness of pushing onto the 
opened-element
stack also entities that don't have a closing tag (but which cannot easily 
be
changed, see the added comment about CfgStack::GetAccessPath) caused 
consistent
memory leaks when Executable_cfgex is executed during the build.  While 
those
leaks are harmless, they might cause people to nevertheless try to clean 
them up
in various ways (see the abandoned
 "asan: fix leak in
ExecuteAnalyzedToken/Push"), so just clean up those broken-by-design excess
aStack elements.

Change-Id: I849109906c6b102d9aa90300c2bada360c727d4d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143001
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/l10ntools/source/cfgmerge.cxx b/l10ntools/source/cfgmerge.cxx
index 1e43f3e99394..f07323ef7efd 100644
--- a/l10ntools/source/cfgmerge.cxx
+++ b/l10ntools/source/cfgmerge.cxx
@@ -134,6 +134,21 @@ CfgParser::CfgParser()
 
 CfgParser::~CfgParser()
 {
+// CfgParser::ExecuteAnalyzedToken pushes onto aStack some XML entities 
(like XML and document
+// type declarations) that don't have corresponding closing tags, so will 
never be popped off
+// aStack again.  But not pushing them onto aStack in the first place 
would change the
+// identifiers computed in CfgStack::GetAccessPath, which could make the 
existing translation
+// mechanisms fail.  So, for simplicity, and short of more thorough input 
error checking, take
+// into account here all the patterns of such declarations encountered 
during a build and during
+// `make translations` (some inputs start with no such declarations at 
all, some inputs start
+// with an XML declaration, and some inputs start with an XML declaration 
followed by a document
+// type declaration) and pop any corresponding remaining excess elements 
off aStack:
+if (aStack.size() == 2 && aStack.GetStackData()->GetTagType() == 
"!DOCTYPE") {
+aStack.Pop();
+}
+if (aStack.size() == 1 && aStack.GetStackData()->GetTagType() == "?xml") {
+aStack.Pop();
+}
 }
 
 bool CfgParser::IsTokenClosed(std::string_view rToken)


[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152079

--- Comment #2 from Eyal Rozenberg  ---
(In reply to Mike Kaganski from comment #1)
> There is an option of adopting EMUs (1/36000 mm), which allows for perfect
> integral representation of both tiny fractions of millimeters and inches.
> Using integers as much as possible avoids rounding errors.

Sounds reasonable to me, I didn't mean to suggest an exclusive list of options.

> The problem is not only the file format, but also the API, which needs
> incompatible changes.

Ah. I remember facing very staunch pushback about the "existing API" in the
face of potential changes (bug 150537). That is a separate and more fundamental
discussion than coordinate precision... but I'll just ask: 

Have developers, or the ESC, considered the possibility of maintaining the old
API via some sort of adaptation layer, allowing for more permissiveness in the
codebase itself? With the adaptation layer always implemented in terms of the
more fluid API? And so that you get the old/stable API by default, but you can
opt-in to the more current one with some preprocessor define or extra headers?

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

2022-11-20 Thread Stephan Bergmann (via logerrit)
 l10ntools/source/xmlparse.cxx |   12 +---
 1 file changed, 9 insertions(+), 3 deletions(-)

New commits:
commit e735de2051143347b7283c85ad80b0e2412522dc
Author: Stephan Bergmann 
AuthorDate: Sun Nov 20 17:46:31 2022 +0100
Commit: Stephan Bergmann 
CommitDate: Sun Nov 20 22:39:54 2022 +0100

Avoid some unnecessary, wrong downcasts during `make translations`

> l10ntools/source/xmlparse.cxx:491:51: runtime error: downcast of address 
0x60300610 which does not point to an object of type 'XMLParentNode'
> 0x60300610: note: object is of type 'XMLDefault'
>  00 00 00 00  30 44 a7 dd a0 55 00 00  00 05 10 6e a4 7f 00 00  80 00 00 
00 60 60 00 00  00 00 00 00
>   ^~~
>   vptr for 'XMLDefault'
>  #0 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:491:51
>  #1 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:481:9
>  #2 in HelpParser::CreatePO(rtl::OString const&, rtl::OString const&, 
XMLFile*, std::basic_string_view>) at 
l10ntools/source/helpmerge.cxx:91:20
>  #3 in sal_main_with_args(int, char**) at 
l10ntools/source/helpex.cxx:124:17
>  #4 in main at l10ntools/source/helpex.cxx:47:1

and

> l10ntools/source/xmlparse.cxx:523:44: runtime error: downcast of address 
0x603007c0 which does not point to an object of type 'XMLParentNode'
> 0x603007c0: note: object is of type 'XMLData'
>  00 00 00 00  e0 53 d5 c0 46 56 00 00  d0 00 00 00 40 60 00 00  f0 07 00 
00 30 60 00 00  00 00 00 00
>   ^~~
>   vptr for 'XMLData'
>  #0 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:523:44
>  #1 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:492:80
>  #2 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:481:9
>  #3 in HelpParser::CreatePO(rtl::OString const&, rtl::OString const&, 
XMLFile*, std::basic_string_view>) at 
l10ntools/source/helpmerge.cxx:91:20
>  #4 in sal_main_with_args(int, char**) at 
l10ntools/source/helpex.cxx:124:17
>  #5 in main at l10ntools/source/helpex.cxx:47:1

and

> l10ntools/source/xmlparse.cxx:526:48: runtime error: downcast of address 
0x60300820 which does not point to an object of type 'XMLParentNode'
> 0x60300820: note: object is of type 'XMLComment'
>  00 00 00 00  28 06 92 a9 17 56 00 00  d0 00 00 00 40 60 00 00  40 00 00 
00 20 61 00 00  00 00 00 00
>   ^~~
>   vptr for 'XMLComment'
>  #0 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:523:44
>  #1 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:492:80
>  #2 in XMLFile::CheckExportStatus(XMLParentNode*) at 
l10ntools/source/xmlparse.cxx:481:9
>  #3 in HelpParser::CreatePO(rtl::OString const&, rtl::OString const&, 
XMLFile*, std::basic_string_view>) at 
l10ntools/source/helpmerge.cxx:91:20
>  #4 in sal_main_with_args(int, char**) at 
l10ntools/source/helpex.cxx:124:17
>  #5 in main at l10ntools/source/helpex.cxx:47:1

Change-Id: I1e2c6bf802aa03b5b1eb21532e98fa22d966e683
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143000
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/l10ntools/source/xmlparse.cxx b/l10ntools/source/xmlparse.cxx
index b32ed4f5037a..bcf5d37154cb 100644
--- a/l10ntools/source/xmlparse.cxx
+++ b/l10ntools/source/xmlparse.cxx
@@ -488,8 +488,8 @@ bool XMLFile::CheckExportStatus( XMLParentNode *pCur )
 {
 for ( size_t i = 0; i < GetChildList()->size(); i++ )
 {
-XMLParentNode* pElement = 
static_cast((*GetChildList())[ i ]);
-if( pElement->GetNodeType() ==  XMLNodeType::ELEMENT ) 
CheckExportStatus( pElement );//, i);
+XMLChildNode* pElement = (*GetChildList())[ i ];
+if( pElement->GetNodeType() ==  XMLNodeType::ELEMENT ) 
CheckExportStatus( static_cast(pElement) );//, i);
 }
 }
 }
@@ -520,7 +520,13 @@ bool XMLFile::CheckExportStatus( XMLParentNode *pCur )
 else if ( pElement->GetChildList() )
 {
 for (size_t k = 0; k < pElement->GetChildList()->size(); 
++k)
-CheckExportStatus( 
static_cast((*pElement->GetChildList())[k]) );
+{
+auto const child = (*pElement->GetChildList())[k];
+auto const type = child->GetNodeType();
+if (type != XMLNodeType::DATA && type != 
XMLNodeType::COMMENT) {
+CheckExportStatus( 
static_cast(child) );
+}
+  

[Libreoffice-bugs] [Bug 152143] Provide a mechanism to export PDF to text

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152143

--- Comment #3 from V Stuart Foote  ---
Nope. That in effect is asking for LibreOffice to become a utility for parsing
content of PDF.  We are not a PDF editor, nor do we provide utilities to
manipulate PDF.

We deal in ODF and in external formats via appropriate filters--import and
export.

There is no ODF or project requirement to convert PDF to external text formats.
There is a requirement as for bug 32249 to fully filter parse PDF structure
into useable text runs/sentences/paragraphs.

If you have a requirement--construct it within that context and it would be
valid.

Anything else is OUT OF SCOPE.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152143] Provide a mechanism to export PDF to text

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152143

--- Comment #3 from V Stuart Foote  ---
Nope. That in effect is asking for LibreOffice to become a utility for parsing
content of PDF.  We are not a PDF editor, nor do we provide utilities to
manipulate PDF.

We deal in ODF and in external formats via appropriate filters--import and
export.

There is no ODF or project requirement to convert PDF to external text formats.
There is a requirement as for bug 32249 to fully filter parse PDF structure
into useable text runs/sentences/paragraphs.

If you have a requirement--construct it within that context and it would be
valid.

Anything else is OUT OF SCOPE.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

2022-11-20 Thread Khaled Hosny (via logerrit)
 vcl/source/font/LogicalFontInstance.cxx |7 +++
 1 file changed, 7 insertions(+)

New commits:
commit 1f9b2a7057a519e0ea750875ac439129f1d3df87
Author: Khaled Hosny 
AuthorDate: Sat Nov 19 21:11:22 2022 +0200
Commit: خالد حسني 
CommitDate: Sun Nov 20 22:17:50 2022 +0100

vcl: fix glyph positioning for artificial italic

Let HarfBuzz transform the glyph positions as well, so that e.g.
combining marks get shifted relative to their slanted base glyphs.

Change-Id: Ib399ab462b36effdc21c4bbeba79d65214792f9c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142979
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/vcl/source/font/LogicalFontInstance.cxx 
b/vcl/source/font/LogicalFontInstance.cxx
index d07a8eb9c974..34f05bbe6e33 100644
--- a/vcl/source/font/LogicalFontInstance.cxx
+++ b/vcl/source/font/LogicalFontInstance.cxx
@@ -67,6 +67,13 @@ hb_font_t* LogicalFontInstance::InitHbFont()
 if (!aVariations.empty())
 hb_font_set_variations(pHbFont, aVariations.data(), 
aVariations.size());
 
+#if HB_VERSION_ATLEAST(3, 3, 0)
+// If we are applying artificial italic, instruct HarfBuzz to do the same
+// so that mark positioning is also transformed.
+if (NeedsArtificialItalic())
+hb_font_set_synthetic_slant(pHbFont, ARTIFICIAL_ITALIC_SKEW);
+#endif
+
 ImplInitHbFont(pHbFont);
 
 return pHbFont;


[Libreoffice-bugs] [Bug 112703] [META] ODF (XML) bug tracker

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112703

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||152079


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152079
[Bug 152079] Increase coordinate precision and make it uniform
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152079

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||112703


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=112703
[Bug 112703] [META] ODF (XML) bug tracker
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: vcl/inc vcl/quartz vcl/skia vcl/source vcl/unx

2022-11-20 Thread Khaled Hosny (via logerrit)
 vcl/inc/font/LogicalFontInstance.hxx   |3 +++
 vcl/inc/quartz/salgdi.h|2 --
 vcl/inc/unx/glyphcache.hxx |4 
 vcl/quartz/ctfonts.cxx |   17 ++---
 vcl/quartz/salgdi.cxx  |2 +-
 vcl/skia/osx/gdiimpl.cxx   |2 +-
 vcl/skia/x11/textrender.cxx|4 ++--
 vcl/source/font/LogicalFontInstance.cxx|   10 ++
 vcl/source/gdi/impglyphitem.cxx|4 ++--
 vcl/source/gdi/pdfwriter_impl.cxx  |   11 ++-
 vcl/unx/generic/gdi/cairotextrender.cxx|4 ++--
 vcl/unx/generic/glyphs/freetype_glyphcache.cxx |   15 +--
 vcl/unx/generic/print/genpspgraphics.cxx   |   20 ++--
 13 files changed, 32 insertions(+), 66 deletions(-)

New commits:
commit d4005521e4fe4379381605b63af1950c5aecd798
Author: Khaled Hosny 
AuthorDate: Sun Nov 20 17:45:51 2022 +0200
Commit: خالد حسني 
CommitDate: Sun Nov 20 22:17:22 2022 +0100

vcl: add NeedsArtificialBold/Italic() to LogicalFontInstance

Change-Id: Ie8bab5d7653a22d0f56b4c859fb2260d96e655c5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142998
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/vcl/inc/font/LogicalFontInstance.hxx 
b/vcl/inc/font/LogicalFontInstance.hxx
index 8887a5d77a1d..0b40a9c7d4f7 100644
--- a/vcl/inc/font/LogicalFontInstance.hxx
+++ b/vcl/inc/font/LogicalFontInstance.hxx
@@ -112,6 +112,9 @@ public: // TODO: make data members private
 
 void GetScale(double* nXScale, double* nYScale) const;
 
+bool NeedsArtificialItalic() const;
+bool NeedsArtificialBold() const;
+
 protected:
 explicit LogicalFontInstance(const vcl::font::PhysicalFontFace&,
  const vcl::font::FontSelectPattern&);
diff --git a/vcl/inc/quartz/salgdi.h b/vcl/inc/quartz/salgdi.h
index 4812404bbc6e..8a0fc4cfd3f0 100644
--- a/vcl/inc/quartz/salgdi.h
+++ b/vcl/inc/quartz/salgdi.h
@@ -94,8 +94,6 @@ public:
 float mfFontStretch;
 /// text rotation in radian
 float mfFontRotation;
-/// faux bold - true, if font doesn't have proper bold variants
-bool mbFauxBold;
 
 private:
 explicit CoreTextFont(const CoreTextFontFace&, const 
vcl::font::FontSelectPattern&);
diff --git a/vcl/inc/unx/glyphcache.hxx b/vcl/inc/unx/glyphcache.hxx
index 22e2f0e173d9..9de7bd59fe6c 100644
--- a/vcl/inc/unx/glyphcache.hxx
+++ b/vcl/inc/unx/glyphcache.hxx
@@ -120,8 +120,6 @@ public:
 boolTestFont() const { return mbFaceOk;}
 FT_Face GetFtFace() const;
 const FontConfigFontOptions* GetFontOptions() const;
-boolNeedsArtificialBold() const { return mbArtBold; }
-boolNeedsArtificialItalic() const { return 
mbArtItalic; }
 
 voidGetFontMetric(ImplFontMetricDataRef const &) const;
 
@@ -154,8 +152,6 @@ private:
 mutable std::unique_ptr mxFontOptions;
 
 boolmbFaceOk;
-boolmbArtItalic;
-boolmbArtBold;
 };
 
 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/vcl/quartz/ctfonts.cxx b/vcl/quartz/ctfonts.cxx
index 1f7be532db31..89460c3943a1 100644
--- a/vcl/quartz/ctfonts.cxx
+++ b/vcl/quartz/ctfonts.cxx
@@ -45,7 +45,6 @@ CoreTextFont::CoreTextFont(const CoreTextFontFace& rPFF, 
const vcl::font::FontSe
 : LogicalFontInstance(rPFF, rFSP)
 , mfFontStretch( 1.0 )
 , mfFontRotation( 0.0 )
-, mbFauxBold(false)
 , mpCTFont(nullptr)
 {
 double fScaledFontHeight = rFSP.mfExactHeight;
@@ -63,21 +62,9 @@ CoreTextFont::CoreTextFont(const CoreTextFontFace& rPFF, 
const vcl::font::FontSe
 aMatrix = CGAffineTransformConcat(aMatrix, 
CGAffineTransformMakeScale(mfFontStretch, 1.0F));
 }
 
-// fake bold
-if ( (rFSP.GetWeight() >= WEIGHT_BOLD) &&
- ((rPFF.GetWeight() < WEIGHT_SEMIBOLD) &&
-  (rPFF.GetWeight() != WEIGHT_DONTKNOW)) )
-{
-mbFauxBold = true;
-}
-
-// fake italic
-if (((rFSP.GetItalic() == ITALIC_NORMAL) ||
- (rFSP.GetItalic() == ITALIC_OBLIQUE)) &&
-(rPFF.GetItalic() == ITALIC_NONE))
-{
+// artificial italic
+if (NeedsArtificialItalic())
 aMatrix = CGAffineTransformConcat(aMatrix, CGAffineTransformMake(1, 0, 
ARTIFICIAL_ITALIC_SKEW, 1, 0, 0));
-}
 
 CTFontDescriptorRef pFontDesc = rPFF.GetFontDescriptorRef();
 mpCTFont = CTFontCreateWithFontDescriptor( pFontDesc, fScaledFontHeight, 
 );
diff --git a/vcl/quartz/salgdi.cxx b/vcl/quartz/salgdi.cxx
index a9f879dfea90..661a7e76735e 100644
--- a/vcl/quartz/salgdi.cxx
+++ b/vcl/quartz/salgdi.cxx
@@ -391,7 +391,7 @@ void AquaGraphicsBackend::drawTextLayout(const 
GenericSalLayout& rLayout, bool b
 CGContextSetShouldAntialias(mrShared.maContextHolder.get(), 
!mrShared.mbNonAntialiasedText);
 

[Libreoffice-ux-advise] [Bug 152143] Provide a mechanism to export PDF to text

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152143

Hossein  changed:

   What|Removed |Added

  Component|Writer  |Draw

--- Comment #2 from Hossein  ---
I don't think this is a duplicate of tdf#32249. The title of that one is:

  Bug 32249
  "When importing PDF with text in it , it will be better to have a easy
  and fluent option to edit the imported Text".

So, the above issue is basically talking about being able to edit the text. I
am here talking about being able to export the PDF as a text file. These are
obviously different, even if you discuss about the commonalities in the
implementation.

> So you can already select and consolidate entire pages of imported draw shape
>  textboxes (by glyph index lookup in a ToUinicode CMAP) into a single draw
> shape textbox--a sentence or paragraph of text. And then select that text,
> copy it and paste it as needed. Then correct as lexically necessary.
I disagree. This is not what was intended in this feature request. I have
specifically requested means of exporting the whole PDF document as a text
file, both via UI and command line. The above consolidation feature might help
internally when you want to implement such a feature, but that is not what I
have asked for.

> Also, because PDF provides no lexical sense to the runs in a document (it is 
> a 
> published presentation format)--the discrete imported draw shape text boxes
> *must be selected in sequence* for a manual merge. That would remain the case
> working with draw shape textboxes on the Writer canvas and is a limitation of
> the published rendering encoded into PDF.
I disagree again. We have text boxes in LibreOffice, MS Office and elsewhere,
but we can export the contents to text files. I haven't requested for a smart
software that can understand the meaning of the document. The goal is to export
the contents to a text file.

> Doing more efficient and high fidelity text extraction from PDF into ODF
> paragraphs is the end goal of bug 32249.
>
> Export of lexically correct word, sentence or paragraph to other document
> formats then becomes routine export filtering that is already present. 
Even by accepting this implementation path, it can be said that this feature
request is depending on tdf#32249, not a duplicate of it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 152143] Provide a mechanism to export PDF to text

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152143

Hossein  changed:

   What|Removed |Added

  Component|Writer  |Draw

--- Comment #2 from Hossein  ---
I don't think this is a duplicate of tdf#32249. The title of that one is:

  Bug 32249
  "When importing PDF with text in it , it will be better to have a easy
  and fluent option to edit the imported Text".

So, the above issue is basically talking about being able to edit the text. I
am here talking about being able to export the PDF as a text file. These are
obviously different, even if you discuss about the commonalities in the
implementation.

> So you can already select and consolidate entire pages of imported draw shape
>  textboxes (by glyph index lookup in a ToUinicode CMAP) into a single draw
> shape textbox--a sentence or paragraph of text. And then select that text,
> copy it and paste it as needed. Then correct as lexically necessary.
I disagree. This is not what was intended in this feature request. I have
specifically requested means of exporting the whole PDF document as a text
file, both via UI and command line. The above consolidation feature might help
internally when you want to implement such a feature, but that is not what I
have asked for.

> Also, because PDF provides no lexical sense to the runs in a document (it is 
> a 
> published presentation format)--the discrete imported draw shape text boxes
> *must be selected in sequence* for a manual merge. That would remain the case
> working with draw shape textboxes on the Writer canvas and is a limitation of
> the published rendering encoded into PDF.
I disagree again. We have text boxes in LibreOffice, MS Office and elsewhere,
but we can export the contents to text files. I haven't requested for a smart
software that can understand the meaning of the document. The goal is to export
the contents to a text file.

> Doing more efficient and high fidelity text extraction from PDF into ODF
> paragraphs is the end goal of bug 32249.
>
> Export of lexically correct word, sentence or paragraph to other document
> formats then becomes routine export filtering that is already present. 
Even by accepting this implementation path, it can be said that this feature
request is depending on tdf#32249, not a duplicate of it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149104] Fails to paste images into Writer

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149104

Dieter  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #6 from Dieter  ---
So let's close as RESOLVED WORKSFORME. Feel free to change it back to
UNCONFIRMED, if it happens again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113122] [META] PDF bugs and enhancement

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113122
Bug 113122 depends on bug 144104, which changed state.

Bug 144104 Summary: pdf import into draw and export causes formatting issues
https://bugs.documentfoundation.org/show_bug.cgi?id=144104

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113122] [META] PDF bugs and enhancement

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113122

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||144104


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=144104
[Bug 144104] pdf import into draw and export causes formatting issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 144104] pdf import into draw and export causes formatting issues

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144104

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Blocks||113122
 Status|NEW |RESOLVED
 CC||vsfo...@libreoffice.org

--- Comment #6 from V Stuart Foote  ---
Confirmed

LibreOffice makes no claim that Round trip-- PDF import filter, PDF export
filter --will produce even remotely similar documents.

LibreOffice is not a PDF editor (open the PDF and write changes directly into
it). 

Rather, we read in a PDF stream, we write out a PDF stream within limitations
of the filters and document formats available.

There are specific issues with the filters, and those should be addressed with
specific BZ issues for each (both the import filter, and the export).

*This* issue is not-actionable.

IMHO => INVALID


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=113122
[Bug 113122] [META] PDF bugs and enhancement
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113123] [META] PDF import filter in Writer

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113123

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||151598


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151598
[Bug 151598] Implement  "Consolidate Text" functionality for text boxes in
Writer
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151598] Implement "Consolidate Text" functionality for text boxes in Writer

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151598

V Stuart Foote  changed:

   What|Removed |Added

 Blocks||113123

--- Comment #6 from V Stuart Foote  ---
IMHO this would be a useful tool for folks with workflows directly filter
importing PDF to Write document canvas.  Ability to consolidate the draw shape
textboxes there is a valid requirement, facilitating eventual implementation of
bug 32249

At present, workflows to consolidate text extracted from PDF require taking the
PDF through import to Draw canvas. Merge it there, and then copy the result for
paste to Writer document.

If the draw shape textbox objects can be manipulated in the Writer context then
providing the feature there is reasonable.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=113123
[Bug 113123] [META] PDF import filter in Writer
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99746

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||148826


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148826
[Bug 148826] Automatic Character color for textboxes of imported PDF are not
responding to fixed document canvas color set by LibreOffice Dark color theme
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148826] Automatic Character color for textboxes of imported PDF are not responding to fixed document canvas color set by LibreOffice Dark color theme

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148826

V Stuart Foote  changed:

   What|Removed |Added

Summary|Dark mode makes reading PDF |Automatic Character color
   |text impossible |for textboxes of imported
   ||PDF are not responding to
   ||fixed document canvas color
   ||set by LibreOffice Dark
   ||color theme
 Status|UNCONFIRMED |NEW
 Blocks||99746, 113123
 CC||vsfo...@libreoffice.org
 Ever confirmed|0   |1

--- Comment #4 from V Stuart Foote  ---
On initial import (creation of the textboxes) for imported PDF text runs, the
'Automatic' color of characters in the textboxes does not adjust to the fixed
color set for document background in Application Colors 'LibreOffice Dark'
color theme.

As noted, resolves by selecting the textboxes and reapplying the automatic
theme, i.e. select, apply a color from picker, reselect Automatic.

Windows in DE 'Dark' color theme, with LO Application Colors 'LibreOffice Dark'
color theme selected

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bcf09f9a9bde21aac1302cbead2b23822458
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

As expected, likewise affects PDF filter import to Writer canvas as well


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=99746
[Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=113123
[Bug 113123] [META] PDF import filter in Writer
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113123] [META] PDF import filter in Writer

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113123

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||148826


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148826
[Bug 148826] Automatic Character color for textboxes of imported PDF are not
responding to fixed document canvas color set by LibreOffice Dark color theme
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152142] RTL Text sometimes falls out of the text box

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152142

Regina Henschel  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 CC||rb.hensc...@t-online.de

--- Comment #2 from Regina Henschel  ---
I can confirm that the text box inside the custom shape ha wrong position

I see that the docx-file has left-to-right text directions in Word.

But I see these problems:
The odt-file should have set text direction to "right-to-left" in page style,
but has not. Several default objects have as writing mode "Page", which means
they use the writing mode from the closest object in which they are contained
and which itself has not writing mode "Page". If the page has writing mode not
explicitly set, then (I guess) it takes the writing mode from application
environment. For me that is German with "left-to-right". Has the page style for
You a text direction "right-to-left"?
The result for me is, that the shape has WritingMode=0" and
TextWritingMode="LR_TB" and the paragraph style Frame Content too.

When they do not have the correct text direction, you cannot expect, that the
export to docx, produces correct text directions in Word. Of cause that does
not mean that the export will produce a usable document if they are correct.

So please try the complete process generating the documents with explicitly
setting text directions, so that it is possible to sort out those problems,
which come in because of wrong defaults in text directions.

In regard to the position problem, when I change the anchor of the shape from
"as character" to "to character", the frame jumps to the correct position.

I set it to "New", because there is surely something wrong.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152144] Font color recent list lost after using background fill

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152144

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Seems the 'Recent' it's the same for both.

Version: 7.4.3.1 (x64) / LibreOffice Community
Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL

But I don't know if it was designed to be so, or can be a bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151677] tip on "formula bar" for "formula making" is displaying over the formula itself.

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151677

Rafael Lima  changed:

   What|Removed |Added

 CC||paj...@gmail.com

--- Comment #4 from Rafael Lima  ---
*** Bug 151995 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151995] Formula helper overlaps actual formula when top bars are removed

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151995

Rafael Lima  changed:

   What|Removed |Added

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

--- Comment #1 from Rafael Lima  ---
This is a duplicate of bug 151677.

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 112810] [META] Arabic & Farsi language-specific RTL issues

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112810
Bug 112810 depends on bug 149457, which changed state.

Bug 149457 Summary: Arabic Text Scrambled and Unreadable in PDF Files Opened by 
LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=149457

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

2022-11-20 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104597

--- Comment #98 from V Stuart Foote  ---
*** Bug 149457 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   >