[Bug 146157] Please make the inverted question marks after trailing equality signs optional

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146157

--- Comment #5 from Michael Kogan  ---
The bug is still present at least in 24.2.0, most probably in later versions as
well.

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

[Bug 146157] Please make the inverted question marks after trailing equality signs optional

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146157

--- Comment #4 from QA Administrators  ---
Dear Michael Kogan,

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.

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #14 from Enrique Perez-Terron  ---
The patch looks good to me, except:

Chinese Traditional : Tradisjonell kinesisk

not: Tradisjonelt kinesisk

in lines 12371, 12407, 12431, 12443, 12449, 12467

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

 Whiteboard||target:24.8.0 target:24.2.4

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

[Bug 147463] Clicking on field link scrolls to page, but focuses only 1/3 of the page in question

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147463

--- Comment #7 from Haris  ---
Hi Telesto,

This is still reproducible in 

Stable Build
Version: 24.2.2.2 (AARCH64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Master/Daily Build
Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community
Build ID: c4023d3ec604abfff38be2053e2989c7ec2ba8c1
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
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.

[Bug 147463] Clicking on field link scrolls to page, but focuses only 1/3 of the page in question

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147463

--- 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.

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

Yaroslav Moiko  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

--- Comment #5 from Werner Tietz  ---
@https://bugs.documentfoundation.org/show_bug.cgi?id=160289#c4

there is no logic on Import via GUI, except the __Dialog__ »remembers« the last
settings taken by $USER. (and $User has the Option to change something! )

IMHO it would be a bad idea to apply implicitly such a rule to
Commandline-conversions

my vote: RESOLVED ⇒ NOT A BUG

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

--- Comment #4 from Yaroslav Moiko  ---
(In reply to m_a_riosv from comment #3)
> Maybe in relation with
> https://bugs.documentfoundation.org/show_bug.cgi?id=150714
> default encoded is UTF-8-encoded
> So is needed to put the encoded if it is different. CSV files are plain text
> with no encoded definition.
> 
> >>To work around the issue, specifying the ANSI encoding with the flag 
> >>--infilter="CSV:44,34,ANSI" in the command line enables successful 
> >>conversion of ANSI-encoded files to PDF.
> It is not a workaround, it is part of command line options.
> 
> I think, not a bug.

Thanks for your reply. Why does it work ok, when I load my .csv file via GUI
then?
I thought some logic automatically determines the encoding before loading the
content (which could be broken).

Maybe it's a deluxe request, but I think it would be extremely useful if
converting from csv to pdf via the command line could have identified encoding
automatically (similarly to what is done when opening via UI).

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m_a_riosv  ---
Maybe in relation with
https://bugs.documentfoundation.org/show_bug.cgi?id=150714
default encoded is UTF-8-encoded
So is needed to put the encoded if it is different. CSV files are plain text
with no encoded definition.

>>To work around the issue, specifying the ANSI encoding with the flag 
>>--infilter="CSV:44,34,ANSI" in the command line enables successful conversion 
>>of ANSI-encoded files to PDF.
It is not a workaround, it is part of command line options.

I think, not a bug.

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

--- Comment #2 from Yaroslav Moiko  ---
Created attachment 193216
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193216=edit
Result PDF file that shows the problem with replaced special symbols

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

--- Comment #1 from Yaroslav Moiko  ---
Created attachment 193215
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193215=edit
CSV File in ANSI encoding that contains a special characters. Use it as a
source

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

[Bug 160289] New: Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160289

Bug ID: 160289
   Summary: Converting ANSI encoded CSV file to PDF via command
line results in replacing special characters
(trademark:™,®) with the special question mark
symbol:�
   Product: LibreOffice
   Version: 7.5.0.1 rc
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Printing and PDF export
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: yaroslav.mo...@gmail.com

Description:
When attempting to convert an ANSI-encoded CSV file to PDF via the command line
using LibreOffice, special characters such as ™ and ® are replaced with
question marks � in the resulting PDF file. The command used for conversion is
as follows:
'soffice.exe --headless --convert-to pdf "D:\MyCsvFile.csv" --outdir
"D:\conversionResults"'
This issue does not occur when opening the same file using the LibreOffice GUI
and subsequently exporting it to PDF via Calc. Furthermore, saving the CSV file
in UTF-8 encoding using Notepad++ allows for successful conversion via the
command line, preserving all original content.

To work around the issue, specifying the ANSI encoding with the flag
--infilter="CSV:44,34,ANSI" in the command line enables successful conversion
of ANSI-encoded files to PDF.

>From these observations, it appears that there may be a problem with
identifying the encoding of the source file when it is loaded for conversion
using the command line interface.

Additionally, it's worth noting that this issue is reproducible in all stable
releases following version 7.4.7.2.

Steps to Reproduce:
1. Create a .csv file that contains special characters such as ™ and ® and save
it using ANSI encoding. Or take the .csv file from the attachments.
2. Install any of the affected versions of LibreOffice (any starting from
7.5.0.1 to 7.6.6).
3. Convert the csv file to PDF using the following command line, replacing
paths as necessary: 'soffice.exe --headless --convert-to pdf "D:\MyCsvFile.csv"
--outdir "D:\conversionResults"'.
4. Inspect the result PDF document.

Actual Results:
Special characters such as ™ and ® from the source file are replaced with
question marks � in the result PDF file.

Expected Results:
All the content from the original file is preserved in the resulting PDF
document without any unwanted replacements. All special characters should be
kept.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; 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.

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #13 from Mike Kaganski  ---
https://gerrit.libreoffice.org/c/translations/+/164882 is an attempt to fix it.
I don't know the language. The fix is done mainly by moving wrongly placed
strings to their proper places; but for some, I just copied the missing strings
from the respective nn file.
A review is really needed from someone who reads the language, to make sure
this blind fix makes sense.

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #12 from Mike Kaganski  ---
... and finally, was already in
https://git.libreoffice.org/translations/+/2e55a04c1a0e276ba878f7372ef92467023a23fb%5E%21/translations/source/nb/svx/source/dialog.po

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #11 from Mike Kaganski  ---
Sorry, the problem was as far as in commit
d9a4b60f9ae7e15c44675ea56fe6a06613c419ae (fix of damaged files from beta1,
2012-12-09).

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Mike Kaganski  changed:

   What|Removed |Added

 CC||cl...@documentfoundation.or
   ||g

--- Comment #10 from Mike Kaganski  ---
This is a problem of translation, that was incorrectly updated in commit
a0c08eb77f9fd9e3b53f5c40abb554e83195fa27 (update translations for 6.0 beta1,
2017-11-22).

The problem starts at
https://opengrok.libreoffice.org/xref/translations/source/nb/svx/messages.po?r=c662aec6#12176
:

> 12178 msgid "Arabic (ISO-8859-6)"
> 12179 msgstr "Gresk (ISO-8859-7)"

... and continues through all the rest of RID_SVXSTR_TEXTENCODING_TABLE
entries. This is the entry that the STR uses:

> 12460 msgid "Chinese simplified (EUC-CN)"
> 12461 msgstr "Unicode (UTF-8)"

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Bug 97300] Ill-placed question for updating Link on opening a file with broken conditional formatting

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=97300

--- Comment #12 from Cor Nouws  ---
Created attachment 193112
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193112=edit
screenshot showing the issue

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

[Bug 97300] Ill-placed question for updating Link on opening a file with broken conditional formatting

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=97300

--- Comment #11 from Cor Nouws  ---
Still issue in Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: nl-NL (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Bug 91336] regular expressions list in Help for asterisk or question mark and "zero or"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91336

f...@bger.ch changed:

   What|Removed |Added

   Severity|normal  |trivial

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

[Bug 91336] regular expressions list in Help for asterisk or question mark and "zero or"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91336

f...@bger.ch changed:

   What|Removed |Added

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

--- Comment #6 from f...@bger.ch ---
Note: The list document was already fixed, refering now to "regular expression
term immediately preceding"
There's also a related otpic linked as "Using Regular Expressions in Text
Searches"

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

[Bug 91336] regular expressions list in Help for asterisk or question mark and "zero or"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91336

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.8.0

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

Re: Question about OpenCL VLOOKUP implementation

[Miklos Vajna]

Hi Dhiraj,

On Tue, Jan 23, 2024 at 05:59:06PM -0600, Dhiraj Holden 
 wrote:
> I have a question about the OpenCL implementation of VLOOKUP as given in
> sc/source/core/opencl/op_spreadsheet.cxx. Right now, both the unsorted and
> sorted vlookup both do a linear search to find the right value. I am
> wondering if it would be better to do a binary search for sorted vlookup. I
> could take care of that now that I've wrapped my head around this
> implementation.

Just a general suggestion: make sure that you profile your calculation
cost with callgrind or perf and only optimize this if you see it as a
hotspot.

Also, you might want to consider what the normal (on CPU) calculation
for VLOOKUP does: that is the default, so it typically makes sense to
improve the opencl VLOOKUP if the CPU one already does something
similar, to avoid mismatches and additional complexity.

Regards,

Miklos

Question about OpenCL VLOOKUP implementation

[Dhiraj Holden]

I have a question about the OpenCL implementation of VLOOKUP as given in
sc/source/core/opencl/op_spreadsheet.cxx. Right now, both the unsorted and
sorted vlookup both do a linear search to find the right value. I am
wondering if it would be better to do a binary search for sorted vlookup. I
could take care of that now that I've wrapped my head around this
implementation.

Thanks,
Dhiraj

[Bug 157378] Docx to PDF conversion removes question answers

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157378

--- Comment #3 from Fred Bryan  ---
I just had to share my recent triumph over standing water in a basement. After
some research and a bit of elbow grease, I've conquered the water issue, and my
basement is now bone dry! I started by identifying the source, fixing any
leaks, and investing in a reliable sump pump. Additionally, I improved drainage
around the house. It took some effort, but the peace of mind and a dry basement
are worth it. If you're dealing with standing water, fear not – solutions are
within reach!
https://drainexpress.ca/fix-standing-water-in-a-basement-drain-system/

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

[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||119352
Summary|Save as text with coding|Save as text with coding
   |utf-8 destroys all  |utf-8 destroys all
   |non-ascii characters,   |non-ascii characters,
   |replacing with question |replacing with question
   |mark|mark (Norwegian Norsk
   ||bokmål UI)
 Status|UNCONFIRMED |NEW
Version|7.3.5.2 release |7.2.0.4 release
 Ever confirmed|0   |1
 OS|Windows (All)   |All
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
I reproduced with nb-NO UI on Linux:

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: nb-NO
Calc: threaded

The Byte Order Mark setting was greyed out too.
Already reproduced in 7.2.0.4.

Not reproduced in en-US UI.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=119352
[Bug 119352] [META] Language issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: Question about async methods (related to tdf#158965 "Find Record: Similarities dialog won't appear")

[Julien Nabet]

Thank you Miklos for your feedback!

I've submitted this patch: https://gerrit.libreoffice.org/c/core/+/161664

Re: Question about async methods (related to tdf#158965 "Find Record: Similarities dialog won't appear")

[Miklos Vajna]

Hi Julien,

On Wed, Jan 03, 2024 at 02:01:51PM +0100, Julien Nabet  
wrote:
> I noticed several methods about async:
> 
> 1) from include/vcl/abstdlg.hxx:
> 
> StartExecuteAsync

I think this is the usual codepath for modal dialogs. Some uno command
decides to open a dialog, we call StartExecuteAsync() with a callback to
handle the dialog result and that handler will be executed at some stage
in the future, instead of right now.

> 2) from include/svtools/genericasyncunodialog.hxx
> 
> executedAsyncDialog which seems used only for PDF dialog
> 
> createAsyncDialog  used for PDF dialog but above all in startExecuteModal
> 
> startExecuteModal
> 
> runAsync
> 
> (perhaps I forgot some).
> 
> Is there some plan to unify them (or at least reduce the number of them) or
> each one has its useful role?

This looks like a special case for the situation when an import or
export action wants to show a dialog, as part of a synchronous filter()
API call. In this case you can't move the "rest of the code" to an async
callback, so that needs special handling. Luckily these dialogs are
rather rare.

I fear there is not much you can unify here. Perhaps it's useful to
document which one is the usual case and which one is some special
minority?

Regards,

Miklos

Question about async methods (related to tdf#158965 "Find Record: Similarities dialog won't appear")

[Julien Nabet]

Hello,

I noticed several methods about async:

1) from include/vcl/abstdlg.hxx:

StartExecuteAsync

2) from include/svtools/genericasyncunodialog.hxx

executedAsyncDialog which seems used only for PDF dialog

createAsyncDialog  used for PDF dialog but above all in startExecuteModal

startExecuteModal

runAsync

(perhaps I forgot some).

Is there some plan to unify them (or at least reduce the number of them) 
or each one has its useful role?


I mean noticing tdf#158965 (Find Record: Similarities dialog won't 
appear), I wanted to compare the way the other methods used async to 
understand what caused the assertion in tdf and noticed all these methods.


Julien

[Bug 157378] Docx to PDF conversion removes question answers

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157378

--- Comment #2 from BolotnikovAleksandrin  ---
The process of making an appointment and receiving on-site medical services
from https://valhallamedics.com/ is organized as conveniently as possible for
patients. The clinic provides online appointment systems that allow patients to
easily schedule appointments with doctors, keep track of their schedules and
receive necessary information in real time.

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

Question About Advanced UNO

[Hassan Sajjad]

Hi.

I am reading this link to get an understanding of UNO
https://wiki.documentfoundation.org/Documentation/DevGuide/Advanced_UNO

Close to the end, it is mentioned that "The disadvantage of the above
function is that it must acquire and release the *mutex* every time it is
called. The double-checked locking idiom was developed to reduce the need
for locking, leading to the following modified function. Do not use.:"

But locking is not needed in C++11 https://stackoverflow.com/a/449823.

The documentation mentions that "Implementing a UNO component that is
instantiated on demand from any other language at the global service
manager. In addition to 2) above, a binding must provide the code that
starts up the runtime engine of the target environment. For example, when a
Java UNO component is instantiated by the LibreOffice process, the Java VM
must be loaded and initialized, before the actual component is loaded
(bidirectional binding)"

 Where is the global service manager? Is it in C++? How to implement a UNO
Component in C++? How to instantiate a UNO Component at the global service
manager in C++.

Best,
Hassan Sajjad

[Libreoffice-bugs] [Bug 44448] Option to auto-update Table of Contents, or question offered to update TOC at printing, is missing

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=8

--- Comment #36 from documentfoundat...@jpgeorget.net ---
Is this feature would be great for many users ? The answer often seems to be
"yes".

To add documentation about this feature request:
- discussed 2004-2019, first FR I believe ! ;-) - Table of contents should be
updated before printing (https://bz.apache.org/ooo/show_bug.cgi?id=25710)
- 2004-2015 - Auto updating Table of Content (TOC) (only when not modified
manually (https://bz.apache.org/ooo/show_bug.cgi?id=24593)
- 2011-2018 - Add option for Chapter related Table of Contents update
(https://bugs.documentfoundation.org/show_bug.cgi?id=34121)
- 2012-2023 - This bug

Pros
- Needed by many users
- Needed like every index, not only TOC (eg. figures, tables, etc.)
- As an option so it can be deactivate when not convenient for some long
documents or in special cases

Cons
- Not present in 2023 (libreoffice 7.8.5.2, Debian GNU/Linux, testing/trixie)
- ???

As a workaround, I use:

The following macro:
```

And I assign it to the "Save" event (menu Tools/Macros/Manage macros/Basic then
assign to the event "Save" (the name of the menus/buttons are translate from
french, so it could not be the same in your version).
sub MajIndex
rem define variables
dim document   as object
dim dispatcher as object
rem --
rem get access to the document
document   = ThisComponent.CurrentController.Frame
dispatcher = createUnoService("com.sun.star.frame.DispatchHelper")

rem --
dispatcher.executeDispatch(document, ".uno:GoToStartOfDoc", "", 0, Array())
dispatcher.executeDispatch(document, ".uno:UpdateAllIndexes", "", 0, Array())

end sub
```

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

[Libreoffice-bugs] [Bug 121312] Autofilter "The range does not contain column headers." question is missing in online

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=121312

Timur  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||ti...@libreoffice.org
 Status|NEW |RESOLVED

--- Comment #2 from Timur  ---
WFM. cannot say when added.

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

[Libreoffice-bugs] [Bug 105464] Wrong question in presentation & draw

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=105464

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||102019


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 157530] The bug in question exhibits

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157530

himajin100...@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 157530] The bug in question exhibits

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157530

himajin100...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
  Component|Writer  |deletionRequest

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

[Libreoffice-bugs] [Bug 157530] New: The bug in question exhibits

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157530

Bug ID: 157530
   Summary: The bug in question exhibits
   Product: LibreOffice
   Version: 3.3.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: herdusu...@gufum.com

Description:
Identifying characteristics of the bug include error messages, system crashes,
or incorrect output. Thorough investigation is essential to pinpoint the root
cause, involving steps such as debugging, code review, and possibly
collaboration with development teams. The aim is not only to rectify the
immediate issue but to enhance the overall robustness and reliability of the
software.

Steps to Reproduce:
1.Effective bug descriptions encompass details such as the steps to reproduce
the issue, the expected outcome versus the observed behavior, and any relevant
error messages or logs. Clear communication of these elements facilitates a
smoother debugging process, aiding developers in isolating, understanding, and
resolving the bug efficiently.


2.
3.

Actual Results:
Effective bug descriptions encompass details such as the steps to reproduce the
issue, the expected outcome versus the observed behavior, and any relevant
error messages or logs. Clear communication of these elements facilitates a
smoother debugging process, aiding developers in isolating, understanding, and
resolving the bug efficiently.



Expected Results:
In the ever-evolving landscape of software development, bugs are inevitable but
serve as stepping stones for continuous improvement. Addressing them
systematically ensures a more resilient and optimized software experience for
end-users.







Reproducible: Always


User Profile Reset: No

Additional Info:
Effective bug descriptions encompass details such as the steps to reproduce the
issue, the expected outcome versus the observed behavior, and any relevant
error messages or logs. Clear communication of these https://silex-id.com/
elements facilitates a smoother debugging process, aiding developers in
isolating, understanding, and resolving the bug efficiently.

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

[Libreoffice-bugs] [Bug 157378] Docx to PDF conversion removes question answers

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157378

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||miguelangelrv@libreoffice.o
   ||rg
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from m.a.riosv  ---
Looks like a duplicate of tdf#154876

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

[Libreoffice-bugs] [Bug 157378] New: Docx to PDF conversion removes question answers

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157378

Bug ID: 157378
   Summary: Docx to PDF conversion removes question answers
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: x86-64 (AMD64)
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Printing and PDF export
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rich...@rjriley.info

Created attachment 189755
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189755=edit
Converted docx to pdf with errors

Opensuse 15.4, LibreOffice 7.5.4.1

When converting Docx formatted form to pdf the answers to yes/no questions are
removed and ask the reader to fill in the form.

See attached documents.

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

[Libreoffice-bugs] [Bug 157089] A question about lack of what seems to me a very essential feature for LibreOffice Calcs.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157089

--- Comment #4 from m.a.riosv  ---
Sorry, but doing a test, it is not how Google sheets saves as ods/xlsx file.
"a3:a" -> =SUM(A3:A1000)
"a1:4" -> =SUM(A1:Z4)

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

[Libreoffice-bugs] [Bug 157089] A question about lack of what seems to me a very essential feature for LibreOffice Calcs.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157089

--- Comment #3 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

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

[Libreoffice-bugs] [Bug 157089] A question about lack of what seems to me a very essential feature for LibreOffice Calcs.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157089

--- Comment #2 from ayd...@gmail.com ---
"a3:a" - cells of column "A" beginning from row "3" and below.
"a1:4" - all cells of rows from "1" to "4"

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

[Libreoffice-bugs] [Bug 157089] A question about lack of what seems to me a very essential feature for LibreOffice Calcs.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157089

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from m.a.riosv  ---
And what that ranges it's expected should be?

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

[Libreoffice-bugs] [Bug 157089] New: A question about lack of what seems to me a very essential feature for LibreOffice Calcs.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157089

Bug ID: 157089
   Summary: A question about lack of what seems to me a very
essential feature for LibreOffice Calcs.
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ayd...@gmail.com

Description:
Hello. Without exaggeration it was shocking to me to find that this feature is
not in Calcs. But because this feature seems to me essential i don't think it
was missed but rather there is reason not to support it and im curious about
the reason. 

So in Google Sheets, the product i started my spreadsheet experience with, once
i wanted to  include in my array all cells from columns A, B, C and all rows
beginning from 4 and down. Intuitively i tried "A4:C", and it worked. I did not
read about it anywhere, it just makes sense. Then i was, mildly put, surprised
to find this does not work in LibreOffice Calcs. I was like, there is no way.
Out of curiosity i tried this in other products, WPS Office, OnlyOffice, even
MS Office. It didn't work. Ok, at this point there has to be a reason, can
someone please explain why? btw i tried this a while ago so maybe it is now
supported by some of the products. Thank you. 

Steps to Reproduce:
1.ranges like "a3:a", "a1:4"

Actual Results:
not working

Expected Results:
should be supported


Reproducible: Always


User Profile Reset: No

Additional Info:
No other information

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

Re: Question of Gerrit build

[Miklos Vajna]

Hi Taichi,

On Thu, Aug 31, 2023 at 11:55:58PM +0900, taichi <20001...@ymail.ne.jp> wrote:
> In Gerrit build, Windows builder configuration is only for x86, isn't there 
> one for x86_64 or ARM64?

That's correct. Your trade-off is to have fast CI feedback vs testing
every possible configuration.

The current setup is to test on linux (clang+dbgutil+make check and
gcc+release+a smaller subset of tests), windows, mac and 2 randomly
picked android configs (out of the 4). The jenkins:all label can opt in
to have all android configs.

The rest is covered by tinderboxes (post-submit):

https://ci.libreoffice.org/view/tb%20platform%20status/

There is more there, like wasm and mac vs mac_arm64.

Regards,

Miklos

[Libreoffice-bugs] [Bug 91192] AutoCorrect: Writer not recognizing a URL's trailing carat, hash mark, question mark, backslash, or pipe

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91192

--- Comment #19 from tylergloria  ---
The special characters you mentioned, such as carats (^), hash marks (#),
question marks (?), and backslashes (), are sometimes used in URLs for specific
purposes.
This can lead to issues when the URL contains these characters at the end.
Check this detail https://www.ietf.org/rfc/rfc1738.txt 
Best way to dig this to use browser developer tools to inspect network requests
and redirects or use any online tool like https://redirectchecker.com/  This
can help you to get detail redirection chain and its status code.

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

Question of Gerrit build

[taichi]

Hello.

In Gerrit build, Windows builder configuration is only for x86, isn't there one 
for x86_64 or ARM64?

Regards,
taichi

[Libreoffice-bugs] [Bug 57981] French : spaces before exclamation/question marks in brackets deleted

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=57981

--- Comment #23 from Laurent Balland  ---
Confirmed with Version: 7.5.5.2 (X86_64) / LibreOffice Community
Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 45347] EDITING: AutoCorrect not working if there is a comment on the word in question

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=45347

--- Comment #16 from QA Administrators  ---
Dear olddeath,

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 155612] unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

--- Comment #5 from Tracey  ---
¿enhancement?
A search that fails to find the target formatting?
Minor bug yes, but enhancement?
Thanks, Tracey
BTW Paragraph styles is check/selected.

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

[Libreoffice-bugs] [Bug 57981] French : spaces before exclamation/question marks in brackets deleted

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=57981

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

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 155612] unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

--- Comment #4 from m.a.riosv  ---
That it is not implemented, so could be a request for enhancement?

The trick, in cases like this one, is to search for with the double
underlining, replace with some character not in the text. To after do the
search and replace/modification you need, and search and replace again to
recover from the initial replace.

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

[Libreoffice-bugs] [Bug 155612] unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

Tracey  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 155612] unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

--- Comment #3 from Tracey  ---
Created attachment 188638
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188638=edit
show find/replace dialog

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

[Libreoffice-bugs] [Bug 155612] unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

--- Comment #2 from Tracey  ---
Created attachment 188637
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188637=edit
section of odt

I want to add a print screen png next.

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

Re:Re: Question about linking .so libraries

[Jingze Xu]

Thank you very much!
At 2023-06-20 22:32:05, "Miklos Vajna"  wrote:
>Hi,
>
>On Tue, Jun 20, 2023 at 09:29:03AM +0800, Jingze Xu  
>wrote:
>> Hi, I have a question about linking .so libraries. 
>
>If you want to link to an external library, then you need to bundle it.
>See core.git commit a2ffd71f20e14f797f30223fe29b3ac1e92eafdf (build
>libtiff, 2022-05-19) as a recent example that bundled a new
>non-header-only external.
>
>Regards,
>
>Miklos

Re: Question about linking .so libraries

[Miklos Vajna]

Hi,

On Tue, Jun 20, 2023 at 09:29:03AM +0800, Jingze Xu  
wrote:
> Hi, I have a question about linking .so libraries. 

If you want to link to an external library, then you need to bundle it.
See core.git commit a2ffd71f20e14f797f30223fe29b3ac1e92eafdf (build
libtiff, 2022-05-19) as a recent example that bundled a new
non-header-only external.

Regards,

Miklos

Question about linking .so libraries

[Jingze Xu]

Dear all, 
Hi, I have a question about linking .so libraries. 


-
Question:
I have successfully added a new dialog in Impress according to the steps in 
this tutorial - Development/Create new dialog in Impress - The Document 
Foundation Wiki. Now I wish to call functions in an external library in the 
dialog source file.
I have an external library libxxx containing some C++ header files and a .so 
file. I put the header files in a subfolder in include/ folder and .so file 
outside libreoffice directory. And I include the header files in dialog source 
files located in sd/source/ui/dlg. Then I rerun the autogen.sh with extra 
arguments, trying to let the build system know I have a .so library to link. 


./autogen.sh LDFLAGS=-L/path_to_libxxx LIBS=-lxxx


I rebuild the sd module using make sd, however, it seems the functions in .so 
library is not properly linked. 


"/usr/bin/ld: 
/home/jingze_xu/office/libreoffice-7.6.0.0.beta1/workdir/CxxObject/sd/source/ui/dlg/HelloDialog.o:
 in function `sd::SdHelloDialog::OKHdl(weld::Button&)':
HelloDialog.cxx:(.text+0x36c): undefined reference to 
`Add_FileHeader(std::__cxx11::basic_string, 
std::allocator >, std::__cxx11::basic_string, std::allocator >, unsigned short)'
collect2: error: ld returned 1 exit status
make[1]: *** 
[/home/jingze_xu/office/libreoffice-7.6.0.0.beta1/sd/Library_sdui.mk:10: 
/home/jingze_xu/office/libreoffice-7.6.0.0.beta1/instdir/program/libsduilo.so] 
Error 1
make: *** [Makefile:121: sd] Error 2"


Are there any clues about linking .so libraries in libreoffice codebase?
Thanks!
-




Best wishes,
Jingze Xu

[Libreoffice-bugs] [Bug 155612] unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Please can you attach a sample file?

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

[Libreoffice-bugs] [Bug 155612] New: unable to find/replace a question mark that is not underlined

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155612

Bug ID: 155612
   Summary: unable to find/replace a question mark that is not
underlined
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: traceyad2...@gmail.com

Description:
I tried searching for question marks that were NOT underlined (I underlined
questions, but missed some questions).

I also tried searching for a particular font, which did NOT work, so I had to
add a font size so it would work.

Please do NOT require paragraph styles to be checked when searching for
paragraph styles(it should be understood).

Thanks, Tracey

Steps to Reproduce:
1.Enter multiple questions.
2.Double underline some of the questions.
3.Search for question marks that are not underlined.

Actual Results:
Finds question marks that are underlined.

Expected Results:
Only stop at question marks that are not underlined.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.7.2 (x64) / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 155552] Just trying to ask a question

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=12

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Sorry, but this is not the place.

Please use our forum https://ask.libreoffice.org/c/english/5

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

[Libreoffice-bugs] [Bug 155552] New: Just trying to ask a question

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=12

Bug ID: 12
   Summary: Just trying to ask a question
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ao.techn...@protonmail.com

Description:
Does LibreOffice have some thing like microsoft's Visio? If not, is there
something planned for it in the future?

I would have sent this in through other means but the website does not have a
contact link or email, so I ended up here.

Steps to Reproduce:
1.n/a
2.n/a
3.n/a

Actual Results:
Just read the question

Expected Results:
Just an answer


Reproducible: Always


User Profile Reset: Yes

Additional Info:
n/a

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

[Libreoffice-bugs] [Bug 121221] Formula editor: Upside down question-marks appear for SOME characters in equations

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=121221

--- Comment #3 from Sebastian Lonnberg  ---
https://olmadi-olmuyor1.blogspot.com/
https://olmadi-olmuyor10.blogspot.com/
https://olmadi-olmuyor100.blogspot.com/
https://olmadi-olmuyor101.blogspot.com/
https://olmadi-olmuyor101.blogspot.com/
https://olmadi-olmuyor102.blogspot.com/
https://olmadi-olmuyor103.blogspot.com/
https://olmadi-olmuyor104.blogspot.com/
https://olmadi-olmuyor105.blogspot.com/
https://olmadi-olmuyor106.blogspot.com/
https://olmadi-olmuyor107.blogspot.com/
https://olmadi-olmuyor108.blogspot.com/
https://olmadi-olmuyor109.blogspot.com/
https://olmadi-olmuyor11.blogspot.com/
https://olmadi-olmuyor110.blogspot.com/
https://olmadi-olmuyor111.blogspot.com/
https://olmadi-olmuyor112.blogspot.com/
https://olmadi-olmuyor113.blogspot.com/
https://olmadi-olmuyor114.blogspot.com/
https://olmadi-olmuyor115.blogspot.com/
https://olmadi-olmuyor116.blogspot.com/
https://olmadi-olmuyor117.blogspot.com/
https://olmadi-olmuyor118.blogspot.com/
https://olmadi-olmuyor119.blogspot.com/
https://olmadi-olmuyor12.blogspot.com/
https://olmadi-olmuyor120.blogspot.com/
https://olmadi-olmuyor121.blogspot.com/
https://olmadi-olmuyor122.blogspot.com/
https://olmadi-olmuyor123.blogspot.com/
https://olmadi-olmuyor124.blogspot.com/
https://olmadi-olmuyor125.blogspot.com/
https://olmadi-olmuyor126.blogspot.com/
https://olmadi-olmuyor127.blogspot.com/
https://olmadi-olmuyor128.blogspot.com/
https://olmadi-olmuyor129.blogspot.com/
https://olmadi-olmuyor13.blogspot.com/
https://olmadi-olmuyor130.blogspot.com/
https://olmadi-olmuyor131.blogspot.com/
https://olmadi-olmuyor132.blogspot.com/

https://olmadi-olmuyor133.blogspot.com/
https://olmadi-olmuyor134.blogspot.com/
https://olmadi-olmuyor135.blogspot.com/
https://olmadi-olmuyor136.blogspot.com/
https://olmadi-olmuyor137.blogspot.com/
https://olmadi-olmuyor138.blogspot.com/
https://olmadi-olmuyor139.blogspot.com/
https://olmadi-olmuyor14.blogspot.com/
https://olmadi-olmuyor140.blogspot.com/
https://olmadi-olmuyor141.blogspot.com/
https://olmadi-olmuyor142.blogspot.com/
https://olmadi-olmuyor143.blogspot.com/
https://olmadi-olmuyor144.blogspot.com/
https://olmadi-olmuyor145.blogspot.com/
https://olmadi-olmuyor146.blogspot.com/
https://olmadi-olmuyor147.blogspot.com/
https://olmadi-olmuyor148.blogspot.com/
https://olmadi-olmuyor149.blogspot.com/
https://olmadi-olmuyor15.blogspot.com/
https://olmadi-olmuyor150.blogspot.com/
https://olmadi-olmuyor151.blogspot.com/
https://olmadi-olmuyor152.blogspot.com/
https://olmadi-olmuyor153.blogspot.com/
https://olmadi-olmuyor154.blogspot.com/
https://olmadi-olmuyor155.blogspot.com/
https://olmadi-olmuyor156.blogspot.com/
https://olmadi-olmuyor157.blogspot.com/
https://olmadi-olmuyor158.blogspot.com/
https://olmadi-olmuyor159.blogspot.com/
https://olmadi-olmuyor16.blogspot.com/
https://olmadi-olmuyor160.blogspot.com/
https://olmadi-olmuyor161.blogspot.com/
https://olmadi-olmuyor162.blogspot.com/
https://olmadi-olmuyor163.blogspot.com/
https://olmadi-olmuyor164.blogspot.com/
https://olmadi-olmuyor165.blogspot.com/
https://olmadi-olmuyor166.blogspot.com/
https://olmadi-olmuyor167.blogspot.com/
https://olmadi-olmuyor168.blogspot.com/
https://olmadi-olmuyor169.blogspot.com/
https://olmadi-olmuyor17.blogspot.com/
https://olmadi-olmuyor170.blogspot.com/
https://olmadi-olmuyor171.blogspot.com/
https://olmadi-olmuyor172.blogspot.com/
https://olmadi-olmuyor173.blogspot.com/
https://olmadi-olmuyor174.blogspot.com/
https://olmadi-olmuyor175.blogspot.com/
https://olmadi-olmuyor176.blogspot.com/
https://olmadi-olmuyor177.blogspot.com/
https://olmadi-olmuyor178.blogspot.com/
https://olmadi-olmuyor179.blogspot.com/
https://olmadi-olmuyor18.blogspot.com/
https://olmadi-olmuyor180.blogspot.com/
https://olmadi-olmuyor181.blogspot.com/
https://olmadi-olmuyor182.blogspot.com/
https://olmadi-olmuyor183.blogspot.com/
https://olmadi-olmuyor184.blogspot.com/
https://olmadi-olmuyor185.blogspot.com/
https://olmadi-olmuyor186.blogspot.com/
https://olmadi-olmuyor187.blogspot.com/
https://olmadi-olmuyor188.blogspot.com/
https://olmadi-olmuyor189.blogspot.com/
https://olmadi-olmuyor19.blogspot.com/
https://olmadi-olmuyor190.blogspot.com/
https://olmadi-olmuyor191.blogspot.com/
https://olmadi-olmuyor192.blogspot.com/
https://olmadi-olmuyor193.blogspot.com/
https://olmadi-olmuyor194.blogspot.com/
https://olmadi-olmuyor195.blogspot.com/
https://olmadi-olmuyor196.blogspot.com/
https://olmadi-olmuyor197.blogspot.com/
https://olmadi-olmuyor198.blogspot.com/
https://olmadi-olmuyor199.blogspot.com/
https://olmadi-olmuyor2.blogspot.com/
https://olmadi-olmuyor20.blogspot.com/
https://olmadi-olmuyor200.blogspot.com/
https://olmadi-olmuyor201.blogspot.com/
https://olmadi-olmuyor202.blogspot.com/
https://olmadi-olmuyor203.blogspot.com/
https://olmadi-olmuyor204.blogspot.com/
https://olmadi-olmuyor205.blogspot.com/
https://olmadi-olmuyor206.blogspot.com/
https://olmadi-olmuyor207.blogspot.com/

[Libreoffice-bugs] [Bug 121221] Formula editor: Upside down question-marks appear for SOME characters in equations

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=121221

--- Comment #2 from Sebastian Lonnberg  ---
https://akrep1.blogspot.com/
https://akrep10.blogspot.com/
https://akrep11.blogspot.com/
https://akrep12.blogspot.com/
https://akrep13.blogspot.com/
https://akrep14.blogspot.com/
https://akrep15.blogspot.com/
https://akrep16.blogspot.com/
https://akrep18.blogspot.com/
https://akrep2.blogspot.com/
https://akrep22.blogspot.com/
https://akrep23.blogspot.com/
https://akrep24.blogspot.com/
https://akrep26.blogspot.com/
https://akrep28.blogspot.com/
https://akrep29.blogspot.com/
https://akrep30.blogspot.com/
https://akrep31.blogspot.com/
https://akrep32.blogspot.com/
https://akrep33.blogspot.com/
https://akrep36.blogspot.com/
https://akrep39.blogspot.com/
https://akrep4.blogspot.com/
https://akrep40.blogspot.com/
https://akrep41.blogspot.com/
https://akrep43.blogspot.com/
https://akrep44.blogspot.com/
https://akrep46.blogspot.com/
https://akrep47.blogspot.com/
https://akrep48.blogspot.com/
https://akrep49.blogspot.com/
https://akrep5.blogspot.com/
https://akrep50.blogspot.com/
https://akrep51.blogspot.com/
https://akrep52.blogspot.com/
https://akrep53.blogspot.com/
https://akrep56.blogspot.com/
https://akrep57.blogspot.com/
https://akrep58.blogspot.com/
https://akrep59.blogspot.com/
https://akrep6.blogspot.com/
https://akrep60.blogspot.com/
https://akrep61.blogspot.com/
https://akrep62.blogspot.com/
https://akrep63.blogspot.com/
https://akrep64.blogspot.com/
https://akrep65.blogspot.com/
https://akrep66.blogspot.com/
https://akrep67.blogspot.com/
https://akrep68.blogspot.com/
https://akrep7.blogspot.com/
https://akrep70.blogspot.com/
https://akrep71.blogspot.com/
https://akrep72.blogspot.com/
https://akrep73.blogspot.com/
https://akrep75.blogspot.com/
https://akrep8.blogspot.com/
https://akrep9.blogspot.com/
https://aslanlaar1.blogspot.com/
https://aslanlaar10.blogspot.com/
https://aslanlaar11.blogspot.com/
https://aslanlaar12.blogspot.com/
https://aslanlaar13.blogspot.com/
https://aslanlaar14.blogspot.com/
https://aslanlaar15.blogspot.com/
https://aslanlaar16.blogspot.com/
https://aslanlaar17.blogspot.com/
https://aslanlaar18.blogspot.com/
https://aslanlaar19.blogspot.com/
https://aslanlaar2.blogspot.com/
https://aslanlaar20.blogspot.com/
https://aslanlaar21.blogspot.com/
https://aslanlaar22.blogspot.com/
https://aslanlaar23.blogspot.com/
https://aslanlaar24.blogspot.com/
https://aslanlaar25.blogspot.com/
https://aslanlaar26.blogspot.com/
https://aslanlaar27.blogspot.com/
https://aslanlaar28.blogspot.com/
https://aslanlaar29.blogspot.com/
https://aslanlaar3.blogspot.com/
https://aslanlaar30.blogspot.com/
https://aslanlaar31.blogspot.com/
https://aslanlaar32.blogspot.com/
https://aslanlaar33.blogspot.com/
https://aslanlaar34.blogspot.com/
https://aslanlaar35.blogspot.com/
https://aslanlaar36.blogspot.com/
https://aslanlaar37.blogspot.com/
https://aslanlaar38.blogspot.com/
https://aslanlaar39.blogspot.com/
https://aslanlaar4.blogspot.com/
https://aslanlaar40.blogspot.com/
https://aslanlaar41.blogspot.com/
https://aslanlaar42.blogspot.com/
https://aslanlaar43.blogspot.com/
https://aslanlaar44.blogspot.com/
https://aslanlaar45.blogspot.com/
https://aslanlaar46.blogspot.com/
https://aslanlaar47.blogspot.com/
https://aslanlaar48.blogspot.com/
https://aslanlaar49.blogspot.com/
https://aslanlaar5.blogspot.com/
https://aslanlaar50.blogspot.com/
https://aslanlaar51.blogspot.com/
https://aslanlaar52.blogspot.com/
https://aslanlaar53.blogspot.com/
https://aslanlaar54.blogspot.com/
https://aslanlaar55.blogspot.com/
https://aslanlaar56.blogspot.com/
https://aslanlaar6.blogspot.com/
https://aslanlaar7.blogspot.com/
https://aslanlaar8.blogspot.com/
https://aslanlaar9.blogspot.com/
https://brokoli1.blogspot.com/
https://brokoli10.blogspot.com/
https://brokoli11.blogspot.com/
https://brokoli13.blogspot.com/
https://brokoli15.blogspot.com/
https://brokoli17.blogspot.com/
https://brokoli18.blogspot.com/
https://brokoli19.blogspot.com/
https://brokoli2.blogspot.com/
https://brokoli21.blogspot.com/
https://brokoli3.blogspot.com/
https://brokoli4.blogspot.com/
https://brokoli5.blogspot.com/
https://brokoli6.blogspot.com/
https://brokoli7.blogspot.com/
https://brokoli8.blogspot.com/
https://brokoli9.blogspot.com/
https://civanpercemi1.blogspot.com/
https://civanpercemi10.blogspot.com/
https://civanpercemi11.blogspot.com/
https://civanpercemi12.blogspot.com/
https://civanpercemi13.blogspot.com/
https://civanpercemi14.blogspot.com/
https://civanpercemi15.blogspot.com/
https://civanpercemi16.blogspot.com/
https://civanpercemi17.blogspot.com/
https://civanpercemi18.blogspot.com/
https://civanpercemi19.blogspot.com/
https://civanpercemi2.blogspot.com/
https://civanpercemi20.blogspot.com/
https://civanpercemi21.blogspot.com/
https://civanpercemi22.blogspot.com/
https://civanpercemi23.blogspot.com/
https://civanpercemi24.blogspot.com/
https://civanpercemi25.blogspot.com/
https://civanpercemi26.blogspot.com/

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #8 from Enrique Perez-Terron  ---
I have now tried two more user interface languages: Japanese and Spanish. In
both cases, the file was saved correctly as UTF-8.

Version 7.5.1.2.

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #7 from Enrique Perez-Terron  ---
I changed the UI language in LibreOffice to English (USA), and now the bug is
not there. This was on the first laptop, where I first experienced the bug.

Then I changed the UI language in LibreOffice to Norwegian (Norsk bokmål) on
the third laptop - the one which had English (UK) and which initially did not
manifest the bug - and now the bug is there.

So it now seems like the bug manifests itself only with the UI language
Norwegian. When I find some more time, I may test other UI languages. 

Another hint to the origin of the bug may be that the filter settings dialog
check box for Byte Order Mark is greyed out when the UI language is not
English.

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #6 from Enrique Perez-Terron  ---
Yet another test, with another laptop.

Version: 7.3.5.2 (x64) / LibreOffice Community
Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: nb-NO (nb_NO); UI: nb-NO
Calc: threaded

OS: Operativsystemnavn  Microsoft Windows 10 Home
Versjon 10.0.19045 Bygg 19045

(Norwegian "Bygg" = English "Build")

$ od -c Copyright.txt
000   ?  \n
002

In this case, the bug is present.

What do the laptops have in common, those who manifest the bug?
A: Operating system, B: Windows locale/language, C: Libreoffice User Interface
language
1. The one where I first experienced the bug:
A: Versjon Windows 10 Home
Versjon 22H2
Installert den  ‎12.‎10.‎2020
Operativsystembygg  19045.2604
Opplevelse  Windows Feature Experience Pack 120.2212.4190.0
B: "Norsk Bokmål" (Norwegian)
C: Standard Norsk bokmål

2. The one I am reporting about now:
A:Versjon   Windows 10 Home
Versjon 22H2
Installert den  ‎02.‎11.‎2020
Operativsystembygg  19045.2604
Opplevelse  Windows Feature Experience Pack 120.2212.4190.0
B: "Norsk Bokmål" (Norwegian)
C: Standard Norsk bokmål

3. The laptop that did not manifest the error:
A: Versjon Windows 11 Home
Versjon 22H2
Installert den  ‎04.‎10.‎2022
Operativsystembygg  22621.1265
Opplevelse  Windows Feature Experience Pack 1000.22638.1000.0
B: Two "preferred"languages: Norsk bokmål; English (USA)
C: English (UK) - but Norwegian also available in the drop-down list

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #5 from Enrique Perez-Terron  ---
I tried this on a different laptop running Windows 11, but the bug is absent.

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: nb-NO (nb_NO); UI: en-GB
Calc: CL threaded

In this case, the user interface is English (en-GB). The Ubunutu case also has
English UI (en-US).

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Enrique Perez-Terron  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #4 from Enrique Perez-Terron  ---
I installed

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: nb-NO (nb_NO); UI: nb-NO
Calc: CL threaded

yesterday, and tried again.

I created a new text document with just one character in it, the copyright
mark, Unicode 0xa9. I saved it first as a regular 'odt' file
(C:\cygwin64\tmp\Copyright.odt), then used the menu File->Save a copy, File
type "Text - select coding (txt)". In the coding dialog, UTF8 and LF. The "Byte
order mark" checkbox came with a check mark, but was greyed out and could not
be deselected.

Then:
$ od -c Copyright.txt
000   ?  \n
002

So yes, I am still seeing the error in version 7.5.

What Buovjaga  is getting is a file with the UTF-8-encoded byte order mark
0xFEFF followed by the UTF-8-encoded copyright symbol 0xA9

Another test: I have an Ubuntu Linux with Libreoffice 7.4.4.2. With this
version of Writer, it byte-order mark checkbox can be deselected, and the
resulting file is 
$ od -c Copyright.txt
000 302 251  \n
003

This is the correct outcome. The bug is not present in Ubuntu Libreoffice
Writer  7.4.4.2.

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Buovjaga  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||ilmari.lauhakangas@libreoff
   ||ice.org

--- Comment #3 from Buovjaga  ---
I saved the file in Windows as suggested and tested it on Linux and my result
is

$ od -c copyright.txt 
000 357 273 277 302 251  \n
006

I also got this with version 7.3.

Do you still see this with 7.5?

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED
WORKSFORME, if the problem went away.

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 687b950702c49c90cff9a43655ea97a0343799a0
CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_FI); UI: en-US
Calc: threaded

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

Re: Question re the uno-skeletonmaker'-t' CLI qualifier

[David]

On 25/1/23 20:05, Stephan Bergmann wrote:
> On 25/01/2023 05:14, David [minor edit] wrote:
>> However treating the '-t' option as a service rather than an interface, as 
>> follows, works.  An  directory tree is created in 
>> the directory where the skeletonmaker CLI command was run, and a very 
>> plausible skeleton CalcDL1.java file was created in  though I haven't 
>> been through it in detail.
>> Your comment "[...] So I would assume that -t must specify that interface 
>> type." is what I'd expect too.  That's reinforced by the HELP text which 
>> states:  "-t  specifies a UNOIDL type name, e.g. 
>> com.sun.star.text.XText (can be used more than once". Not much doubt 
>> there... 
> So the uno-skeletonmaker help and diagnostic output apparently uses, somewhat 
> consistently but maybe also somewhat confusingly, the term "type" to mean 
> both UNOIDL interfaces and UNOIDL services. 

That's the problem in a nutshell.

In common programming terminology, the word "type" refers to a single variable 
or symbol.  A strongly-typed language will flag a compilation error if 
incompatible types are used, for example 'i=x' where 'i' is declared to be an 
integer type and 'x' is declared floating-point.  Extending this concept of 
"type" to a complex structure like a UNOIDL interface, which may include many 
different atomic types, makes sense.  But I can't see how it can possibly refer 
to a "service".

An IDL interface and an IDL service are different things entirely, 
conventionally distinguished by prefixing 'X' to interface names.

And in the case of the uno-skeletonmaker 'calc-add-in command', specifying a 
service works but specifying an interface fails.  So I argue that the 
documentation and HELP text are plainly wrong and should be corrected.  After 
all, skeletonmaker is only at version 0.4!

Perhaps it would be worthwhile checking that this inconsistency doesn't hide 
some deeper problem.  It feels to me like the result of a misunderstanding or a 
sudden change of design which may have further ramifications.

D.

Re: Question re the uno-skeletonmaker'-t' CLI qualifier

[Stephan Bergmann]

On 25/01/2023 05:14, David wrote:
Using the three '-l' options shown above and in the following test 
command with *no**'-t' option* results in a skeletonmaker error, 
presumably because '-t' and '-n' are mandatory in the 'calc-add-in' 
command (BUG: the '-t' is displayed in upper case, which can be 
misleading given case-sensitivity):


see  "Fix typo"

However treating the '-t' option as a service rather than an interface, 
as follows, works.  An  directory tree is 
created in the directory where the skeletonmaker CLI command was run, 
and a very plausible skeleton CalcDL1.java file was created in  
though I haven't been through it in detail.

[...]
Your comment "[...] So I would assume that -t must specify that 
interface type." is what I'd expect too.  That's reinforced by the HELP 
text which states:  "-t  specifies a UNOIDL type name, e.g. 
com.sun.star.text.XText (can be used more than once". Not much doubt 
there...


So the uno-skeletonmaker help and diagnostic output apparently uses, 
somewhat consistently but maybe also somewhat confusingly, the term 
"type" to mean both UNOIDL interfaces and UNOIDL services.


There's evidently a discrepancy between the LibreOffice Developer's 
Guide, the skeletonmaker HELP text, introductory comments in the 
skeletonmaker source code, all other API guides which repeat the HELP 
text, and what actually works.


Not sure there's any actual discrepancies here?  (Note how 
 
also states:  "The add-in component has to support two services, the 
com.sun.star.sheet.AddIn service, and an additional service 
that is used to identify the set of functions that the add-in supplies.")

Re: Question re the uno-skeletonmaker'-t' CLI qualifier

[David]

I think we're getting somewhere...!

On 24/1/23 18:03, Stephan Bergmann wrote:
> I don't know much about skeletonmaker or Calc add-ins, but
> 
>  
> <>
>  says "The functions that the add-in component exports to the spreadsheet 
> application have to be defined in a new interface." So I would assume that -t 
> must specify that interface type. And one or more -l will be needed to make 
> available that interface type and all the other UNOIDL entities recursively 
> referenced from it. So if you have your own type com.example.XMyAddIn in your 
> own local mytypes.rdb, you'd probably need something like
>> -t com.example.XMyAddIn -l "$OFFICE_HOME"/program/types.rdb -l 
>> "$OFFICE_HOME"/program/types/offapi.rdb -l mytypes.rdb 

Using the three '-l' options shown above and in the following test command with 
*no**'-t' option* results in a skeletonmaker error, presumably because '-t' and 
'-n' are mandatory in the 'calc-add-in' command (BUG: the '-t' is displayed in 
upper case, which can be misleading given case-sensitivity):

david@anon:~> "$OFFICE_HOME"/sdk/bin/uno-skeletonmaker calc-add-in --java5 -l 
"$OFFICE_PROGRAM_PATH"/types.rdb -l "$OFFICE_HOME"/program/types/offapi.rdb -l 
/home/david/<...path...>/XCalcDL1.rdb -n org.openoffice.adl.util.CalcDL1
        Error: no type is specified, use the -T option at least once

Changing the last '-l' to '-t' results in:
        ERROR: Unknown entity '/home/david/<...path...>/XCalcDL1.rdb'

However treating the '-t' option as a service rather than an interface, as 
follows, works.  An  directory tree is created in the 
directory where the skeletonmaker CLI command was run, and a very plausible 
skeleton CalcDL1.java file was created in  though I haven't been through 
it in detail.

david@anon:~> "$OFFICE_HOME"/sdk/bin/uno-skeletonmaker calc-add-in --java5 -l 
"$OFFICE_PROGRAM_PATH"/types.rdb -l "$OFFICE_HOME"/program/types/offapi.rdb -l 
/home/david/<...path...>/XCalcDL1.rdb -n org.openoffice.adl.util.CalcDL1 -t 
org.openoffice.adl.util.CalcDL1
david@anon:~>

*COMMENTS*

Your comment "[...] So I would assume that -t must specify that interface 
type." is what I'd expect too.  That's reinforced by the HELP text which 
states:  "-t  specifies a UNOIDL type name, e.g. com.sun.star.text.XText 
(can be used more than once".  Not much doubt there...

There's evidently a discrepancy between the LibreOffice Developer's Guide, the 
skeletonmaker HELP text, introductory comments in the skeletonmaker source 
code, all other API guides which repeat the HELP text, and what actually works.

Most of the initial command & option validation seems to be done by 
'skeletonmaker.cxx' which calls generatePackage() in 'javacompskeleton.cxx' to 
do the work.  But as I mentioned in an earlier email, I've come across a 
suggestion somewhere that '-t' defines a service, not an interface; maybe a 
change was made which hasn't been reflected in the Developer's Guide?

I don't have the time and expertise in C to untangle the source code and in any 
case the sources I've looked at are completely devoid of comments (without 
which ongoing maintenance is far more difficult and unreliable!) apart from the 
introduction to skeletonmaker.cxx.  Should I post another bug report in 
Bugzilla?  - the first was marked NOTABUG.

Thanks for your help, Stephan.

_David Lochrin

_

Re: Question re the uno-skeletonmaker'-t' CLI qualifier

[Stephan Bergmann]

On 24/01/2023 01:05, David wrote:
Hello Stephan, Yes, this is a Linux system and I'm invoking 
uno-skeletonmaker thus:


david@anon:~> "$OFFICE_HOME"/sdk/bin/uno-skeletonmaker calc-add-in 
--java5 -l "$OFFICE_PROGRAM_PATH"/types.rdb -n 
org.openoffice.adl.util.CalcDL1 -t CalcDL1

ERROR: Unknown entity 'CalcDL1'
david@anon:~>

I'd already found the '-l' trap for the unwary the hard way (and it also 
occurs in 'javamaker')!  My problem now is that a value for '-t' is 
apparently mandatory for the 'calc-add-in' command but I don't 
understand what to put there.


The uno-skeletonmaker source code, its help text, and every other 
reference have identical wording:  "-t  specifies a UNOIDL type 
name, e.g. com.sun.star.text.XText (can be used more than once)”.


Since '-l' already points to types.rdb you'd think '-t' wouldn't be 
needed. The phrasing "-t CalcDL1" was just a guess as I'd read some 
source code which seemed to imply a service-name was required.


I don't know much about skeletonmaker or Calc add-ins, but 
 
says "The functions that the add-in component exports to the spreadsheet 
application have to be defined in a new interface."  So I would assume 
that -t must specify that interface type.  And one or more -l will be 
needed to make available that interface type and all the other UNOIDL 
entities recursively referenced from it.  So if you have your own type 
com.example.XMyAddIn in your own local mytypes.rdb, you'd probably need 
something like



-t com.example.XMyAddIn -l "$OFFICE_HOME"/program/types.rdb -l 
"$OFFICE_HOME"/program/types/offapi.rdb -l mytypes.rdb

Re: Question re the uno-skeletonmaker'-t' CLI qualifier

[David]

Hello Stephan, Yes, this is a Linux system and I'm invoking uno-skeletonmaker 
thus:

david@anon:~> "$OFFICE_HOME"/sdk/bin/uno-skeletonmaker calc-add-in --java5 -l 
"$OFFICE_PROGRAM_PATH"/types.rdb -n org.openoffice.adl.util.CalcDL1 -t CalcDL1
ERROR: Unknown entity 'CalcDL1'
david@anon:~>

I'd already found the '-l' trap for the unwary the hard way (and it also occurs 
in 'javamaker')!  My problem now is that a value for '-t' is apparently 
mandatory for the 'calc-add-in' command but I don't understand what to put 
there.

The uno-skeletonmaker source code, its help text, and every other reference 
have identical wording:  "-t  specifies a UNOIDL type name, e.g. 
com.sun.star.text.XText (can be used more than once)”.

Since '-l' already points to types.rdb you'd think '-t' wouldn't be needed.  
The phrasing "-t CalcDL1" was just a guess as I'd read some source code which 
seemed to imply a service-name was required.
_
__Regards, David_


On 24/1/23 01:15, Stephan Bergmann wrote:
> On 23/01/2023 03:45, David wrote:
>> According to 
>> https://api.libreoffice.org/docs/tools.html#uno-skeletonmaker the 
>> argument ‘-t’  “specifies a UNOIDL type name, e.g. 
>> com.sun.star.text.XText (can be used more than once)”.  This wording is 
>> the same as both the uno-skeletonmaker command-line ‘help’ and the 
>> introductory comments in the source code for 'skeletonmaker.cxx'.
>>
>> However I don't understand which entity the UNOIDL type name is intended 
>> to qualify.  For example, is it the type of the skeleton code to be 
>> generated (presumably not, since that’s defined by the ‘calc-add-in’ 
>> command), the type of each value returned by the Java methods 
>> implemented in this addIn, or something else? Anything I've tried 
>> results in an "unknown entity" diagnostic.
> uno-skeletonmaker apparently needs to be explicitly told where to find 
> any referenced UNOIDL entities, via the -l option.  So adding something like
>> -l "$OFFICE_HOME"/program/types.rdb -l 
>> "$OFFICE_HOME"/program/types/offapi.rdb
> should work (in an SDK shell, on Linux at least).
>

Re: Question re the uno-skeletonmaker'-t' CLI qualifier

[Stephan Bergmann]

On 23/01/2023 03:45, David wrote:
According to 
https://api.libreoffice.org/docs/tools.html#uno-skeletonmaker the 
argument ‘-t’  “specifies a UNOIDL type name, e.g. 
com.sun.star.text.XText (can be used more than once)”.  This wording is 
the same as both the uno-skeletonmaker command-line ‘help’ and the 
introductory comments in the source code for 'skeletonmaker.cxx'.


However I don't understand which entity the UNOIDL type name is intended 
to qualify.  For example, is it the type of the skeleton code to be 
generated (presumably not, since that’s defined by the ‘calc-add-in’ 
command), the type of each value returned by the Java methods 
implemented in this addIn, or something else? Anything I've tried 
results in an "unknown entity" diagnostic.


uno-skeletonmaker apparently needs to be explicitly told where to find 
any referenced UNOIDL entities, via the -l option.  So adding something like



-l "$OFFICE_HOME"/program/types.rdb -l "$OFFICE_HOME"/program/types/offapi.rdb


should work (in an SDK shell, on Linux at least).

Question re the uno-skeletonmaker'-t' CLI qualifier

[David]

Hello,

I've been referred to this mailing list for an answer to the following 
question, originally posted at 
https://ask.libreoffice.org/t/the-sdk-uno-skeletonmaker-t-argument/86641

According to https://api.libreoffice.org/docs/tools.html#uno-skeletonmaker the 
argument ‘-t’  “specifies a UNOIDL type name, e.g. com.sun.star.text.XText (can 
be used more than once)”.  This wording is the same as both the 
uno-skeletonmaker command-line ‘help’ and the introductory comments in the 
source code for 'skeletonmaker.cxx'.

However I don't understand which entity the UNOIDL type name is intended to 
qualify.  For example, is it the type of the skeleton code to be generated 
(presumably not, since that’s defined by the ‘calc-add-in’ command), the type 
of each value returned by the Java methods implemented in this addIn, or 
something else?  Anything I've tried results in an "unknown entity" diagnostic.

About seven years ago I wrote an addIn which works well, but it was developed 
by hand-coding everything from scratch and modifying the 'make' file given in 
the SDK examples.  My reference document was the "OpenOffice.org 3.1 
Developer's Guide" published by Sun Microsystems in 2009.  I'm now attempting 
to recompile this addIn using the LO SDK toolset before embarking on a new 
project.

I'd be grateful for any light which members of this list can shed.

Regards,
David Lochrin

[Libreoffice-bugs] [Bug 140679] Upside down question markers formula round trip DOCX

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=140679

Rajasekaran Karunanithi  changed:

   What|Removed |Added

 CC||rajasekara...@gmail.com

--- Comment #9 from Rajasekaran Karunanithi  ---
Still presents in LO 7.6 Dev under Windows 10(x64).

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ad387d5b984c906505d25685065f710ed55d
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

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 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #2 from Enrique Perez-Terron  ---
(Continued from the previous comment)

In order to demonstrate what the correct outcome would be, I pasted the
copyright symbol from the Writer document into the following Bash command line:

$ echo '©' | od -t x1
000 c2 a9 0a
003

The bytes C2 A9 are the correct UTF-8 encoding of the code point 0xA9, the
copyright symbol.

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

[Libreoffice-bugs] [Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

--- Comment #1 from Enrique Perez-Terron  ---
A simple test case: 
(Since I have a Norwegian user interface, my English translations of the UI
labels may be inexact.)

1. I opened a new writer document, and
2. selected the copyright symbol by clicking on the "Omega" button in the
'insert' toolbar.
3. Then I saved a copy of the document (File -> Save a copy)
4. navigating to a temporary folder "C:\cygwin64\tmp",
5. naming the file "Copyright" and
6. choosing the format "Text (choose encoding)". 

The coding dialog came up with "Unicode (UTF-8)" and "LF" selected, so I just
clicked on "OK".

I have Cygwin tools installed on my computer.
7. In a Bash command window, I changed to the temporary directory and issued
8. $ od -c Copyright.txt
The output was:
000   ?  \n
002

Notice the question mark.

I will show the expected outcome in the next comment.

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

[Libreoffice-bugs] [Bug 143093] Windows File Explorer created docx file, edited in libreoffice Writer, and Ctrl-S saved, ends up with question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143093

Raghu  changed:

   What|Removed |Added

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

--- Comment #11 from Raghu  ---
I tried with version 7.1.6.2 of LibreOFfice today.
The problem does not occur.
This ticket may be closed.

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

[Libreoffice-bugs] [Bug 151830] New: Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151830

Bug ID: 151830
   Summary: Save as text with coding utf-8 destroys all non-ascii
characters, replacing with question mark
   Product: LibreOffice
   Version: 7.3.5.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: enri...@perezterron.net

My version: 
Version: 7.3.5.2 (x64) / LibreOffice Community
Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: nb-NO (nb_NO); UI: nb-NO
Calc: threaded

I save a file using File->Save as or File->Save a copy, set the File type to
"Text - choose a coding", in the filter selection dialog, I choose encoding
"Unicode (UTF-8)" and line ending "LF". 

Then I inspect the resulting file using od (octal dump) with options to show
byte values as ascii and hex code, (od -c -t x1).

The file begins with these two lines:

Ferden til boplassen
Endelig stod jeg der. Langs den lille kanalen foran meg lå tre små sjøfly.

Notice the three non-ascii characters in the last four words. 

Inspecting the outcome, I find as follows:

$ od -c -t x1 Ren-tekst-versjon.txt | head -30
000   1   .   F   e   r   d   e   n
 20  20  20  20  20  20  20  31  2e  46  65  72  64  65  6e  20
020   t   i   l   b   o   p   l   a   s   s   e   n  \n  \n   E
 74  69  6c  20  62  6f  70  6c  61  73  73  65  6e  0a  0a  45
040   n   d   e   l   i   g   s   t   o   d   j   e   g
 6e  64  65  6c  69  67  20  73  74  6f  64  20  6a  65  67  20
060   d   e   r   .   L   a   n   g   s   d   e   n   l
 64  65  72  2e  20  4c  61  6e  67  73  20  64  65  6e  20  6c
100   i   l   l   e   k   a   n   a   l   e   n   f   o   r
 69  6c  6c  65  20  6b  61  6e  61  6c  65  6e  20  66  6f  72
120   a   n   m   e   g   l   ?   t   r   e   s   m
 61  6e  20  6d  65  67  20  6c  3f  20  74  72  65  20  73  6d
140   ?   s   j   ?   f   l   y   .   T   e   r   m   i   n
 3f  20  73  6a  3f  66  6c  79  2e  20  54  65  72  6d  69  6e

(The first line is a heading, here indented by seven spaces, which I did not
expect. In the original, it is not indented. The second line is part of a
longer paragraph and is saved as a single long line - this is expected and OK.)

The issue in this report is that the characters å and ø are replaced with
question marks. It seems like the file has not been converted to utf-8, but
rather to ascii.

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

[Libreoffice-bugs] [Bug 143093] Windows File Explorer created docx file, edited in libreoffice Writer, and Ctrl-S saved, ends up with question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143093

--- Comment #10 from QA Administrators  ---
Dear Raghu,

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

Re: Question regarding Crazy Ideas List

[Julien Nabet]

Hello,

About Java part, here are some bugtrackers:
Convert Java complex tests to Python 
https://bugs.documentfoundation.org/show_bug.cgi?id=97362


Move Java based API tests to C++
https://bugs.documentfoundation.org/show_bug.cgi?id=45904

Provide Non-Java Database Report Generator for AppStore version (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=151249

BASE reports and wizards still require Java
https://bugs.documentfoundation.org/show_bug.cgi?id=127278

Personnally, when debugging with gdb, I'm quite stuck when code goes in 
to Java. I must add some System.out.println() and some printStacktrace() 
in Java code but it's not ideal.
Perhaps it's possible with an IDE but I just stick to vim, quite light 
and above all no config to do.


Another thing, if I don't misunderstand, using some LO methods from Java 
requires all the UNO stuff, so it's slower.


IMHO, it would be great to be independant from Java.

Julien

Re: Question regarding Crazy Ideas List

[Tomaž Vajngerl]

On Thu, Oct 20, 2022 at 2:33 PM Siddharth Khattar 
wrote:

> Hello,
> So I was going through the crazy ideas list for LibreOffice at
> https://wiki.documentfoundation.org/Development/Crazy_Ideas .
>

Crazy Idea page was first created as a dump of some crazy ideas that the
enthusiastic developers had after LibreOffice was forked (this is why many
ideas are 10+ years old), but has since then evolved into a place where
everyone (but the developers) write their crazy ideas in - so keep that in
mind.

Also they don't mean anything - probably none of them will ever be
implemented.


> When I came to the idea "AOT Compilation for Java Libraries used by
> LibreOffice" , there was this line as the first disadvantage ->
> "Feasibility: Is it even possible to use AOT compiled Java Libraries in a
> C++ compiled executable? Couldn't find a definite answer. "
>
> What does this line mean?
>

Looks like the crazy idea is just by some user thinking aloud.

Can't AOT compilation be used for all Java Libraries?
>

Who knows, probably it's possible with a lot of work but don't think
anybody was looking into that.

Also, does LibreOffice use Java Libraries to further compile their
> functions into C++ executable?
>

No.


> I don't understand what it meant to say at all to be honest.
>

You're free to ignore that - it's not like the crazy ideas page has any
meaning.


> Also, the last disadvantage -> "May reduce motivation to move from Java
> entirely"
>
> Why does LibreOffice want to move on from Java?
>

We want to move away from Java for core stuff as it would require for every
user to have a JVM installed (only Base currently requires a JVM).

We also want to move away from Java during the building of LibreOffice, for
example running tests written in Java, because C++ tests are easier for
most to debug if something goes wrong (as most of core developers are C++
developers).

But we don't want to get rid of Java as a language you can build
LibreOffice extensions in.


> Will it depend entirely on C++ instead then?
>

No, there is still Python that is used for some things (AFAIK) and
StarBasic.

>
> Is this also a crazy/ambitious idea?
>

Not that crazy.


> Is it somewhat related to the "Replace Mozilla Rhino with Mozilla's
> SpiderMonkey or Google's V8" idea as it also wants to remove Java as a
> dependency for executing JavaScript extensions?
>

Well not directly. Rhino JS support isn't the best or fastest, so replacing
that with an up-to-date C++ compatible JS engine that is actually used in a
browser would be much better.

Also no need to have a JVM installed to run JS would make it a much more
interesting language as an alternative scripting language for macros and
extensions.


> Or is that a completely seperate idea?
>

Yes.. and is just a crazy idea.


> Thanks for reading/answering my long question!
>

 Regards, Tomaž

Question regarding Crazy Ideas List

[Siddharth Khattar]

Hello,
So I was going through the crazy ideas list for LibreOffice at
https://wiki.documentfoundation.org/Development/Crazy_Ideas .
When I came to the idea "AOT Compilation for Java Libraries used by
LibreOffice" , there was this line as the first disadvantage ->
"Feasibility: Is it even possible to use AOT compiled Java Libraries in a
C++ compiled executable? Couldn't find a definite answer. "

What does this line mean? Can't AOT compilation be used for all Java
Libraries? Also, does LibreOffice use Java Libraries to further compile
their functions into C++ executable? I don't understand what it meant to
say at all to be honest.

Also, the last disadvantage -> "May reduce motivation to move from Java
entirely"

Why does LibreOffice want to move on from Java? Will it depend entirely on
C++ instead then? Is this also a crazy/ambitious idea? Is it somewhat
related to the "Replace Mozilla Rhino with Mozilla's SpiderMonkey or
Google's V8" idea as it also wants to remove Java as a dependency for
executing JavaScript extensions? Or is that a completely seperate idea?

Thanks for reading/answering my long question!

[Libreoffice-bugs] [Bug 79695] FILEOPEN: MS Word 2013 ODF shows red question marks after formula

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=79695

--- Comment #17 from Roman Kuznetsov <79045_79...@mail.ru> ---
Still repro 

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: threaded

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

[Libreoffice-bugs] [Bug 79695] FILEOPEN: MS Word 2013 ODF shows red question marks after formula

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=79695

--- Comment #16 from QA Administrators  ---
Dear Firas Hanife,

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 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

Mike Kaganski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com
   |desktop.org |
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

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

https://git.libreoffice.org/core/commit/0fa5b4e03ed981cd79ac9af57e616714fc41b685

tdf#150714: [API-CHANGE] change CSV default encoding to UTF-8

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 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.5.0

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

[Libreoffice-bugs] [Bug 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

--- Comment #4 from Eike Rathke  ---
That may be the culprit if it's actually hit for the recovery case. If we
change that also ConvertFrom() needs to be changed and an API change announced,
as these are still (at least per the comments) the defaults for API use without
any parameters.

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

[Libreoffice-bugs] [Bug 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

--- Comment #3 from Mike Kaganski  ---
ScDocShell::ConvertTo seems to use hard-coded RTL_TEXTENCODING_MS_1252

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

[Libreoffice-bugs] [Bug 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

--- Comment #2 from Mike Kaganski  ---
(In reply to Eike Rathke from comment #1)

I suspect hard-coded ISO 8859-1, because for me, the local system codepage is
Windows-1251, that indeed is able to cover Cyrillic characters (but not
extended Western ones).

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

[Libreoffice-bugs] [Bug 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

--- Comment #1 from Eike Rathke  ---
Without looking at code I'd assume the system/thread encoding is used for
recovery, which probably still happens to be some nasty ugly legacy code page
on Windows and not even ISO 8859-1 but Windows-1252 or whatever the regional
system settings offer. Or there's some default forcing ISO 8859-1 that might
originate from legacy reasons.

Sounds sensible to default to UTF-8 instead for CSV recovery if both
save/restore use it.

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

[Libreoffice-bugs] [Bug 150714] DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

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

   What|Removed |Added

 CC||79045_79...@mail.ru
 Blocks||109238, 77999
   Keywords||dataLoss


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=77999
[Bug 77999] [META] Autosave/Autorecovery/Backup copy issues
https://bugs.documentfoundation.org/show_bug.cgi?id=109238
[Bug 109238] [META] CSV bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 150714] New: DATALOSS: saving a recovered CSV converts all non-Western characters to question marks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150714

Bug ID: 150714
   Summary: DATALOSS: saving a recovered CSV converts all
non-Western characters to question marks
   Product: LibreOffice
   Version: unspecified
  Hardware: All
   URL: https://forumooo.ru/index.php?topic=9330
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com

Created attachment 182109
  --> https://bugs.documentfoundation.org/attachment.cgi?id=182109=edit
An UTF-8-encoded CSV

If autorecovery information save is enabled, and a crash happens while editing
a CSV, then opening LibreOffice would offer recovery for the CSV. Performing
the recovery would give the correct data, and saving the recovered data using
File->Save would overwrite the original CSV, but the result would loose all the
non-Western characters, which would only be apparent after reload, at which
point, the non-Western data would be unrecoverable (the autorecovery
information is deleted, and original CSV is overwritten).

Steps to reproduce:
0. Make sure that "Save Autorecovery information" is enabled under
Options->Load/Save->General, and set to some small value (1 minute) for ease of
reproduction.
1. Open the attached CSV, making sure to use UTF-8 encoding (it contains a
string "テストabcабвÀ", which includes Japanese, English, Cyrillic, and extended
Western characters).
2. Make some change to B2, e.g. replace "1" with "2".
3. Wait for automatic save.
4. Kill soffice.bin process.
5. Start LibreOffice, see it offers recovery for the CSV. Confirm the recovery.
Note that no CSV import dialog is shown during the recovery.
6. See that the recovered document looks OK, having the correct string in A2,
and "2" in B2.
7. Press Save toolbar button (or File->Save), confirm saving as CSV.
8. Close and reopen the file.

The text in A2 will be destroyed - both Japanese and Cyrillic characters would
turn to question marks. The Western character "À" will be restored if ISO
8859-1 encoding is selected on import.

Note that if in step #7, you use Save As instead, and select "Edit filter
settings" in the Save As dialog, the settings dialog would offer the last used
encoding, not ISO 8859-1. When saving a new document to CSV, the filter
settings dialog would appear even when "Edit filter settings" is unselected, so
it looks like a problem specific to recovered files.

The origin of the problem seems to be in the fact that autorecovery stores
files in the native ODS format (which is a good thing), but that doesn't keep
the original filter settings in the autorecovery data (see also bug 123877
comment 9). So opening the autorecovery ODS can't provide Calc with the
original encoding, and some internal default is used, which happens to be ISO
8859-1, not even the last-used encoding that is stored in the profile (using
the last-used setting silently would also be incorrect anyway).

The proposal is to make UTF-8 the default encoding for recovered CSV files.
Another option could be to make autorecovered documents have some media flag
set that would force filter settings dialog on save, the same way as when you
save a new document to CSV.
Yet another option is to implement storing original CSV filter settings inside
autorecovery ODS (most complex).

The issue appeared in https://forumooo.ru/index.php?topic=9330.

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