Re: GSoC project to add CPDB support to the LibreOffice print dialog

2024-07-03 Thread Biswadeep Purkayastha
Monthly update: July 2024

Hello everyone,
Last month, I focused on rewriting older code to incorporate CPDB frontend API 
functions and fix the printing process. Now, printing with CPDB works 
seamlessly on the LibreOffice print dialog. During this process, I discovered 
that the printer names in the LibreOffice dialog are static and evaluated at 
startup, unlike CPDB, which periodically refreshes the printer list. 
Consequently, the print dialog had to handle situations where a printer might 
no longer be available even though it is still displayed. I implemented changes 
for dynamically updating the printer lists and to include appropriate error 
handling to address this issue of stale printers while using CPDB. 
Additionally, I modified the functionality of the "Print Directly" button in 
LibreOffice so that with CPDB it now prints to the default printer initially, 
rather than the first available printer as it did previously.

Regards,
Biswadeep



From: LibreOffice on behalf of Michael Weghorn
Sent: Tuesday, May 7, 2024 12:57 PM
To: Biswadeep Purkayastha; libreoffice@lists.freedesktop.org
Subject: Re: GSoC project to add CPDB support to the LibreOffice print dialog

On 2024-05-06 19:22, Biswadeep Purkayastha wrote:> I am Biswadeep
Purkayastha, a GSoC 2024 contributor to OpenPrinting. In
> the upcoming months I'll be working on getting CPDB support into the
> LibreOffice print dialogs. I had previously reached out to the community
> asking for a mentor to help me from the LibreOffice side and I am happy
> to announce that Michael Weghorn will be mentoring me from the
> LibreOffice side on this project. I look forward to working on this
> project with my mentors and being a part of the open-source community.

Thanks for the update and welcome again!
I'm looking forward to working together and hope you'll have a great
GSoC experience!


GSoC Project Introduction: More and Better Tests

2024-05-19 Thread Adam Seskunas
Hello Everyone,

My name is Adam Seskunas and I'm one of the GSoC contributors for
LibreOffice. My project, as the name suggests, is to write more and better
tests for LibreOffice. In particular, I will be focusing on writing filter
tests for writer.  The project will consist of two main parts, the first of
which will be to convert some JUnit tests to CppUnit, and the second part
will consist of writing missing unit tests.  A more detailed description as
well as a link to the project proposal can be found here
https://summerofcode.withgoogle.com/myprojects/details/pUU5JIpy

I'd like to take this opportunity to thank Hossein and Xisco for agreeing
to mentor me through the project. And I'd like to give a big thanks to
Ilmari for helping me get involved with LibreOffice over the past year and
encouraging me to apply for the GSoC. And last of all, a big thanks to all
of the community members, everyone has been welcoming and friendly, it's
been a very positive experience contributing to LibreOffice.

In the next week I will be working on refining the list of tests I will be
working on and gathering information about each test I plan to work on. In
my next update I hope to have a finalized list of tests to publish.

Adam Seskunas


GSoC Project Introduction - .NET Bindings for UNO

2024-05-18 Thread Ritobroto Mukherjee
Hello everyone,

I'm Ritobroto Mukherjee, one of the GSoC contributors for LibreOffice
this year. I'll be working on updating UNO bindings for .NET languages
(C#, F# and VB.NET).

This project aims to update the original .NET Framework compatible
bindings, to use the newer .NET 8 SDK. This would not only make them
cross-platform, but also allow us to introduce newer C# syntax and
features such as generic types. Tests, examples, documentation and a
NuGet package for end users to consume the bindings are also planned.

I am eager to work under the guidance of Mr. Hossein and Mr. Thorsten,
along with the support of the entire LibreOffice community. 

Similar to my peers, I'll be sending weekly updates shortly. Also a big
congratulations to all my peers who were also selected as contributors.

Best regards,
Ritobroto


Re: GSoC project to add CPDB support to the LibreOffice print dialog

2024-05-07 Thread Michael Weghorn
On 2024-05-06 19:22, Biswadeep Purkayastha wrote:> I am Biswadeep 
Purkayastha, a GSoC 2024 contributor to OpenPrinting. In
the upcoming months I'll be working on getting CPDB support into the 
LibreOffice print dialogs. I had previously reached out to the community 
asking for a mentor to help me from the LibreOffice side and I am happy 
to announce that Michael Weghorn will be mentoring me from the 
LibreOffice side on this project. I look forward to working on this 
project with my mentors and being a part of the open-source community.


Thanks for the update and welcome again!
I'm looking forward to working together and hope you'll have a great 
GSoC experience!


OpenPGP_signature.asc
Description: OpenPGP digital signature


GSoC project to add CPDB support to the LibreOffice print dialog

2024-05-06 Thread Biswadeep Purkayastha
Hello,
I am Biswadeep Purkayastha, a GSoC 2024 contributor to OpenPrinting. In the 
upcoming months I'll be working on getting CPDB support into the LibreOffice 
print dialogs. I had previously reached out to the community asking for a 
mentor to help me from the LibreOffice side and I am happy to announce that 
Michael Weghorn will be mentoring me from the LibreOffice side on this project. 
I look forward to working on this project with my mentors and being a part of 
the open-source community.

Regards,
Biswadeep

P.S.: Following is the link to my previous communications: 
https://lists.freedesktop.org/archives/libreoffice/2024-March/091748.html


Re: https://opengrok.libreoffice.org/ has no project "core"

2024-03-29 Thread Regina Henschel

Hi all,
I have written https://redmine.documentfoundation.org/issues/3727

Kind regards,
Regina

Mike Kaganski schrieb am 29.03.2024 um 20:11:

On 29.03.2024 23:31, Regina Henschel wrote:
https://opengrok.libreoffice.org/ has neither in 'Projects' nor in the 
'Repository' list a project 'core'.


Same here.





Re: https://opengrok.libreoffice.org/ has no project "core"

2024-03-29 Thread Mike Kaganski

On 29.03.2024 23:31, Regina Henschel wrote:
https://opengrok.libreoffice.org/ has neither in 'Projects' nor in the 
'Repository' list a project 'core'.


Same here.

--
Best regards,
Mike Kaganski



https://opengrok.libreoffice.org/ has no project "core"

2024-03-29 Thread Regina Henschel

Hi all,

https://opengrok.libreoffice.org/ has neither in 'Projects' nor in the 
'Repository' list a project 'core'.


The direct link https://opengrok.libreoffice.org/xref/core/ works. But 
that does not allow search.


Is it only for me or do you have the same problem?

I have tested Firefox, Chrome and Edge.


Kind regards,
Regina


Outreachy project progress

2024-03-18 Thread khushi gautam
Hi Folks,

The update for the project is that the relative patch of this project has
been +1 verified and covered all the tasks that were mentioned by Jim
before.

Hekio has reviewed the UX and given his comments upon it. I will be working
to address all of them and may be connect with him for some follow up
questions

I am looking to launch this project soon

Thank you,
Khushi


Outreachy project progress.

2024-03-08 Thread khushi gautam
Hi Folks,
I am at the end stage of my project "Sidebar Deck for QuickFind". Past
three months have been pretty much very knowledgeable for me. From starting
with a UI on glade to ending it up with the actual functionality of
searching the keyword in the find bar and making it appear on the quick
find bar panel. My learning graph has made a good inclination with respect
to my career.

Few weeks back I was left with some tasks and I guess almost all of them
are covered now. First, there should be no entry to the search list if
nothing is found. completed the highlighting part of the searched item to
stand out the keyword along with this some more minor prettifying changes
also has been added like, 1. edit view scrolls when a search find entry is
selected, 2. Grab focus to find keywords in the document.
Crash issue is covered. Bringing the find to attention is the one I am
currently working on and about to close in a day or two.

Next, I will be working on improving my Patch to get it merge and taking
approval from my mentors

Working with LO during these months has always been pretty exciting to me.
The amount of learnings I got from here will have a great significance in
my career

Thanks,
Khushi


[outreachy] Project progress (week 6)

2024-01-13 Thread khushi gautam
Hi Folks,

Here comes the 6 weeks report of my project progress. I feel proud to
mention that I am all going according to my project timeline. My mentors
Jim and Heiko are ones who are always available to resolve any issue and
make working in the LO environment much more fun. Learning new things and
encountering such a big codebase is itself a task whenever I initiate any
new milestone per week in the project.

I started this project by making a UI layout of a quick find panel on glade
(using a virtual box for that). Next I integrated the ui with the code to
make the Find Deck icon appear on the sidebar panel. Following up with
that, I spent some more time on glade in figuring out how to expand the
treeview component. This is all about making a structure.

Consequently, I first made the search bar track the keywords on entering
the search field. I connected the entry control to the source and to add an
activate handler for it. Made functions named as FillSearchFindsList().
Sequencing, I built a functionality similar to "Find all" in the quick
search bar. On entering the keyword it highlights corresponding words in
the document. Currently, I am half way on accomplishing the task of
fetching a string of words from the right hand side and left hand side of
the selected word. Once make build stops giving the errors I think I will
be good to go. As Jim said in LO we make change, test it out, think, think,
make change, test until we get a successful outcome.

Here is the link to my current blog that I am maintaining during my whole
outreachy journey : https://khushishikhu.hashnode.dev/outreachy-week-6

Happy Hacking!!

Thank You!!

Khushi Gautam


Outreachy 2 weeks project progress

2023-12-16 Thread khushi gautam
Hi all,
I am currently working on the project "Sidebar deck for quick find". It's
been two weeks since I started my internship here, and I'd like to update
the community about my progress till now. My very first step was to create
a UI for QuickFind using Glade. Initially, I faced challenges operating
Glade on Windows. Fortunately, Heiko, my mentor, helped me by demonstrating
how Glade works on Linux. I promptly installed VirtualBox to run Glade on
Linux, and I was able to create the UI in a short amount of time.

Next, let's talk about the stage where I had to add the 'Find Deck' option
to the sidebar and its corresponding panel. This step took some time from
adding the panel and deck entry in sidebar.xcu file and SwPanelFactory to
achieve a successful build. During this task, Jim Raykowski, my mentor,
cooperated with me so effectively that by the end of the second week, I was
able to accomplish that goal. I appreciate Jim's assistance in making this
task a success.

Thank you!

Regards,

Khushi


[Libreoffice-bugs] [Bug 118277] FILEOPEN XLSX Basic project with VBA Project Password does not work in Calc

2023-07-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118277

--- Comment #7 from QA Administrators  ---
Dear Gabor Kelemen,

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.

GSoC'23 Project - Search Field in Options

2023-05-12 Thread Bayram Çiçek

Hi everyone,

I'm Bayram Çiçek. I was a GSoC 2021 participant at LibreOffice and I 
have a bachelor's degree in computer engineering. I am delighted to 
share with you that I've been given this wonderful opportunity to work 
with LibreOffice as a Google Summer of Code 2023 participant.


I'll be working on "Search Field in Options" project under the 
mentorship of Andreas Heinisch and Heiko Tietze throughout the GSoC 2023 
program.


LibreOffice has a large and growing number of options and sometimes it 
is not easy to find the right one by searching them one by one. 
Throughout the GSoC program, I'll implement a search field/functionality 
to the "Tools > Options..." dialog, so that we can find the right 
options easily.


- Mockup: 
https://bug-attachments.documentfoundation.org/attachment.cgi?id=61600
- Enhancement request on Bugzilla: 
https://bugs.documentfoundation.org/show_bug.cgi?id=49895


I would like to express my gratitude to all mentors and the LibreOffice 
organization for giving us this opportunity.


Thank you.

--

Regards,
Bayram Çiçek


[Libreoffice-bugs] [Bug 154962] New: project files, opening projects with all the files

2023-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154962

Bug ID: 154962
   Summary: project files, opening projects with all the files
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@cspv.hu

it would be great to be able to open "projects", which 
would mean that a couple of files (documents) would open...

or we could add documents to a list which would open together
call them "document lists".. "document groups"

but in NAVIGATOR we could handle it all.. 
like a playlist

just an idea...

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

[Libreoffice-bugs] [Bug 118167] FILESAVE XLSX VBA-Project and Microsoft Excel Objects look different after export

2023-04-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118167

--- Comment #13 from QA Administrators  ---
Dear Gabor Kelemen,

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 154574] Dragging or copying a new JPG image into the project sometimes hides arrows under the image

2023-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

BogdanB  changed:

   What|Removed |Added

Summary|Dragging or copying in new  |Dragging or copying a new
   |Jpg pictures into project   |JPG image into the project
   |sometimes hides Arrows  |sometimes hides arrows
   |under picture.  |under the image

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

[Libreoffice-bugs] [Bug 154574] Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

BogdanB  changed:

   What|Removed |Added

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


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 154574] Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

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

[Libreoffice-bugs] [Bug 154574] Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

--- Comment #4 from lucky  ---
Hello [Jeffry],

Thank you for reporting the bug. I can confirm that the bug is present in
master.

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

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

[Libreoffice-bugs] [Bug 154574] Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

--- 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 154574] Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

--- Comment #2 from Jeffry  ---
Created attachment 186507
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186507=edit
It is a map of the Wilderness area of a NWN Server I play on.

The issues are with the Wilderness Map.

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

[Libreoffice-bugs] [Bug 154574] Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

Buovjaga  changed:

   What|Removed |Added

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

--- Comment #1 from Buovjaga  ---
Please attach an example document.
Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the document.

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

[Libreoffice-bugs] [Bug 154574] New: Dragging or copying in new Jpg pictures into project sometimes hides Arrows under picture.

2023-04-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154574

Bug ID: 154574
   Summary: Dragging or copying in new Jpg pictures into project
sometimes hides Arrows under picture.
   Product: LibreOffice
   Version: 7.5.0.3 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: torchl...@gmail.com

Description:
I'm not really positive what causes the double arrow lines to not work but most
of the time when I drag a new jpg/jpeg picture in that is an update of the same
previous picture the arrows have a tendency of staying hidden behind the
picture when they were intended to be on top of the picture and visible. You
can mitigate this by copying and pasting the arrow again in a different
location, using that one instead of the affected arrow line. 

Thes Pictures were created with Apeaksoft Screenrecorder on Windows 10/ Intel
64 bit system. I'm using Libre Office Calc.


Steps to Reproduce:
1. Delete previous bad picture 
2. Copy or drag the replacement picture from the folder location of the picture
to Libre Office Calc
3. I Hope the double Arrow line doesn't get stuck behind the picture.
4. If it is copying bad double arrow line create a new one.
5. Use the newer unaffected double arrow line instead


Actual Results:
The new picture hides the arrows that previously were on top of it.

Expected Results:
I would think dragging in the new picture would still let the arrows be on top
instead of hidden.


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
None

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

Re: GSoC'23 project

2023-03-28 Thread Ilmari Lauhakangas

On 28.3.2023 18.20, Spruha Thorat wrote:

Hi,
I am Spruha Thorat  from IIIT Vadodara , currently studying in 2nd year 
of B.Tech in CSE.
I want to contribute to the project 'Convert Writer's Java UNO API tests 
to C++'.

I want to know if it's still open for contribution or not ?
  I would like some guidance before starting  with the project.


You can submit proposals until 4 April. Check the deadlines and remember 
to also solve a difficultyInteresting easy hack: 
https://wiki.documentfoundation.org/Development/GSoC/2023#Important_dates


You can keep submitting updated versions of your proposal until the 4 
April deadline, if you want to improve it based on feedback from mentors.


Ilmari


GSoC'23 project

2023-03-28 Thread Spruha Thorat
Hi,
I am Spruha Thorat  from IIIT Vadodara , currently studying in 2nd year of
B.Tech in CSE.
I want to contribute to the project  'Convert Writer's Java UNO API tests
to C++'.
I want to know if it's still open for contribution or not ?
 I would like some guidance before starting  with the project.

Thanks and Regards,
Spruha Thorat.


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2023-03-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Stephan Bergmann  changed:

   What|Removed |Added

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

--- Comment #26 from Stephan Bergmann  ---
Per the comment at

"tdf#38890 Remove hard-coded URLs in source Files":  "So about this bug 149115:
tdf#38890 Remove hard-coded URLs in source Files |
https://gerrit.libreoffice.org/c/core/+/149115, are there no more hardcoded
urls in the source, after grep libreoffice, most outputs are instances of open
office or comments or Test codes"

And I also hardly find anything that looks like it could be another target for
this easyHack when I search now, so lets leave it at that.

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

[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2023-03-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

--- Comment #25 from Commit Notification 
 ---
Adoche Onaji committed a patch related to this issue.
It has been pushed to "master":

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

tdf#38890 Remove hard-coded URLs in source Files

It will be available in 7.6.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 38890] Remove hard-coded project URLs

2023-03-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|reviewed:2022   |reviewed:2022 target:7.6.0

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

[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Buovjaga  changed:

   What|Removed |Added

 CC||dochieon...@gmail.com

--- Comment #24 from Buovjaga  ---
(In reply to Adoche Onaji from comment #23)
> The fail I Saw came in from ww8export3.cxx because it has a block of code in
> there:
> 
> DECLARE_WW8EXPORT_TEST(testHyperLinkURLSaving, "tdf120003.doc")
> {
> OUString URL = getProperty(getShape(1), "HyperLinkURL");
> // Without the fix in place, this test would have failed with
> // - Expected: https://www.libreoffice.org/
> // - Actual  : tps://www.libreoffice.org/
> CPPUNIT_ASSERT_EQUAL(OUString("https://www.libreoffice.org/;), URL);
> }

This is about https://gerrit.libreoffice.org/c/core/+/142005

Undo your changes in the test (qa) directories. The use of www.libreoffice.org
URLs there is just a coincidence and not relevant for this hack.

So undo like

git checkout master -- sw/qa/extras/odfexport/odfexport2.cxx

for each file and update your patch.

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

[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2023-03-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

--- Comment #23 from Adoche Onaji  ---
The fail I Saw came in from ww8export3.cxx because it has a block of code in
there:

DECLARE_WW8EXPORT_TEST(testHyperLinkURLSaving, "tdf120003.doc")
{
OUString URL = getProperty(getShape(1), "HyperLinkURL");
// Without the fix in place, this test would have failed with
// - Expected: https://www.libreoffice.org/
// - Actual  : tps://www.libreoffice.org/
CPPUNIT_ASSERT_EQUAL(OUString("https://www.libreoffice.org/;), URL);
}

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

[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2023-03-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

--- Comment #22 from Adoche Onaji  ---
(In reply to Stephan Bergmann from comment #19)
> (In reply to Björn Michaelsen from comment #0)
> > Background: We still have a number of hardcoded URLs around the place, some
> > of which become visible in the UI. We should have these extracted from a
> > config file instead - preferably a textual 'rc' file (sal has code to parse
> > and use these cf. boots).
> 
> Note that many such URLs are now stored in the configuration, see properties
> "SendFeedbackURL" etc. in
> officecfg/registry/data/org/openoffice/Office/Common.xcu.  That's probably
> the preferred way now.

I am currently working on this bug and have made some progress. I have moved
the URLs to the Common.xcu files and modify neccessary CPPUnitTest files,
running make was successful bug I am getting an error from make check. 
Something of this nature:
[_RUN_] testImageHyperlink::TestBody
image-hyperlink.docx:
/home/samuel/Documents/Dev/libreoffice/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:82:testImageHyperlink::TestBody
equality assertion failed
- Expected: https://libreoffice.org/
- Actual  : http://www.libreoffice.org/

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

GSoC 2023 - Project: Quickly insert brackets

2023-03-12 Thread Bayram Çiçek

Hi LibreOffice Community,

My name is Bayram Çiçek. I have a bachelor's degree in Computer Science 
and I was a GSoC participant for LibreOffice in 2021.


My previous GSoC project was '100 paper cuts' - which is a UI/UX-related 
project. This year, I'd like to apply for a project that is -also- 
related to UI/UX. The project I'm interested in is:


 + Project Name: *Quickly insert brackets*
 + Enhancement request on Bugzilla: 
https://bugs.documentfoundation.org/show_bug.cgi?id=151710

 + Size: 175 hours
 + Difficulty: Easy(?)
 + Potential mentors: Andreas Heinisch, Heiko Tietze

Also, I want to continue to work on LibreOffice development after GSoC.

About me:
 + Website: bayramcicek.com.tr/
 + LinkedIn: linkedin.com/in/bayramcicek/
 + Github: github.com/bayramcicek
 + IRC/Telegram: @bayramcicek
 + GSoC'21 final report (100 Paper Cuts): 
https://bayramcicek.com.tr/libreoffice-dev/2021/08/23/final-report-gsoc.html


Thanks.

--

Regards,
Bayram Çiçek


Re: GSoC Project: Sidebar deck for quick find

2023-02-12 Thread Heiko Tietze

Hi Siddharth,

happy to see your interest in LibreOffice, and in particular in UI topics :-).

Not sure Jim reads the mailing list but I do. He would be the code mentor while 
my contribution could be to test the implementation and to recommend UI solutions.


Jim already created a simple prototype to see how much effort there might be. So 
if the project has any blockers I'd expect it on the UI/UX side. Meaning some 
complexity with replacement functionality (personally, I'd would keep things 
simple and not abuse the sidebar as dialog replacement). Some discussion has 
been done on the ticket.


As always, we request students to proof skills by solving easy hacks. Ask in 
private, if you don't find an appropriate ticket.


Looking forward to work with you,
Heiko

On 11.02.23 19:54, Siddharth Khattar wrote:

Hello,

I was recently taking a look again at the GSoC ideas list and I found out that 
it had been updated a bit since I last took a look at it a couple of weeks ago. 
I, unfortunately, wasn't able to find a mentor to help me with the previous idea 
(Improving Zoner Draw Filter), and also couldn't find a copy of Zoner Draw 2 for 
testing, which I was researching to implement so I went to look at the list 
again for inspiration. Then, the idea to implement Quick Find as a sidebar deck 
interested me. As I researched the idea further, I read through the discussion 
and implementation regarding this idea at: 
https://bugs.documentfoundation.org/show_bug.cgi?id=95405 
<https://bugs.documentfoundation.org/show_bug.cgi?id=95405>. I also looked at 
the mock-up at: 
https://bug-attachments.documentfoundation.org/attachment.cgi?id=184862 
<https://bug-attachments.documentfoundation.org/attachment.cgi?id=184862> & 
thought that it was pretty close to my view of the project as well. The 
implementation of the idea seems pretty doable for a beginner like me who is new 
to open-source development as a whole. In the meanwhile, I've looked into the 
files srchdlg.cxx and navigatorpanel.ui for an initial idea of the 
implementation of the project.


I think the ideal implementation of this idea would be to -
1) Create an additional find/replace section in sidebar
2) Leave the current find/replace dialogue in place (for the sake of user 
choice)
3) Show multiple matches of the searched keyword from the content in the sidebar 
and highlight them alongside with a yellow font color in the file, also allowing 
the user to cycle through them with a button click


Firstly (and most importantly), Are there please any potential mentors who are 
willing to help me with this project? The GSoC ideas page mentioned potential 
mentors as /Jim Raykowski and //Heiko Tietze, /can somebody please contact them 
and ask if they're interested in this project?

Are there any foreseeable roadblocks or challenges to the execution of this 
idea?
In which area should I start focusing my research to start working on the 
document to successfully implement this idea as part of GSoC 2023?
Is anyone else currently aiming to implement this idea at LibreOffice or in the 
LibreOffice open-source community?
Lastly, are there any other tips or thoughts regarding this that you would like 
to give me?


Thanking for your time and consideration,
Siddharth K


--
Dr. Heiko Tietze, UX-Designer and UX-Mentor
Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint


OpenPGP_signature
Description: OpenPGP digital signature


GSoC Project: Sidebar deck for quick find

2023-02-11 Thread Siddharth Khattar
Hello,

I was recently taking a look again at the GSoC ideas list and I found out
that it had been updated a bit since I last took a look at it a couple of
weeks ago. I, unfortunately, wasn't able to find a mentor to help me with
the previous idea (Improving Zoner Draw Filter), and also couldn't find a
copy of Zoner Draw 2 for testing, which I was researching to implement so I
went to look at the list again for inspiration. Then, the idea to implement
Quick Find as a sidebar deck interested me. As I researched the idea
further, I read through the discussion and implementation regarding this
idea at: https://bugs.documentfoundation.org/show_bug.cgi?id=95405. I also
looked at the mock-up at:
https://bug-attachments.documentfoundation.org/attachment.cgi?id=184862 &
thought that it was pretty close to my view of the project as well. The
implementation of the idea seems pretty doable for a beginner like me who
is new to open-source development as a whole. In the meanwhile, I've looked
into the files srchdlg.cxx and navigatorpanel.ui for an initial idea of the
implementation of the project.

I think the ideal implementation of this idea would be to -
1) Create an additional find/replace section in sidebar
2) Leave the current find/replace dialogue in place (for the sake of user
choice)
3) Show multiple matches of the searched keyword from the content in the
sidebar and highlight them alongside with a yellow font color in the file,
also allowing the user to cycle through them with a button click

Firstly (and most importantly), Are there please any potential mentors who
are willing to help me with this project? The GSoC ideas page mentioned
potential mentors as *Jim Raykowski and **Heiko Tietze, *can somebody
please contact them and ask if they're interested in this project?
Are there any foreseeable roadblocks or challenges to the execution of this
idea?
In which area should I start focusing my research to start working on the
document to successfully implement this idea as part of GSoC 2023?
Is anyone else currently aiming to implement this idea at LibreOffice or in
the LibreOffice open-source community?
Lastly, are there any other tips or thoughts regarding this that you would
like to give me?

Thanking for your time and consideration,
Siddharth K


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2022-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Adoche Onaji  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

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

[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2022-08-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Hossein  changed:

   What|Removed |Added

 Whiteboard||reviewed:2022

--- Comment #21 from Hossein  ---
Re-evaluating the EasyHack in 2022

This enhancement is still relevant. Some hard-coded project URLs are still in
the code.

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

[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2022-05-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Xisco Faulí  changed:

   What|Removed |Added

   Assignee|rasheshpadia...@gmail.com   |libreoffice-b...@lists.free
   ||desktop.org
 Status|ASSIGNED|NEW

--- Comment #20 from Xisco Faulí  ---
Dear  Padia Rashesh,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.

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

Re: Redirecting conversation regarding GSoC Project to Mailing List

2022-04-11 Thread Eike Rathke
Hi Heiko,

On Monday, 2022-04-11 10:34:13 +0200, Heiko Tietze wrote:

> TS are not only relevant on Calc but also (and probably more aware to users)
> in Writer.

I'd rather not mix in anything Writer but keep this Calc focused.
The implementation will be completely different, though the actual
styles and design view of Impress could be similar if not identical (I
hope the styles themselves were defined such that they are usable
everywhere..).

  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


signature.asc
Description: PGP signature


GSoC Calc Table Styles (was: Redirecting conversation regarding GSoC Project to Mailing List)

2022-04-11 Thread Eike Rathke
Hi Sarrah,

On Friday, 2022-04-08 16:51:34 +0530, Sarrah Bastawala wrote:

> Based on what I have understood so far, here is the functionality we are
> looking to implement in Table Styles
> 
>We want to visually make it similar to the tables currently present in
>autoformat, however it should be able to apply the same attribute to
>multiple cells changing as more data is entered

That's right. It should be one attribute with a table style ID applied
to a cell range, and that table style should handle all the necessary
settings like whether or not header row or total row is present, left
and right column, banded rows, banded columns, and so on, and how a cell
with its offset within such table should effectively be displayed. The
effective display attribute is not tied to a particular cell/row/column,
also for example, banded rows and columns should continue alternating in
the view if rows or columns are hidden. Which is something that
completely does not work with current AutoStyles.


>The functionality for this could be referred to from the present table
>styles in Impress and the functionality for sorting, filters, etc from
>existing code for pivot tables in calc, if I’m not wrong. ( I would
>appreciate if you could give me the code pointers for these to refer
>directly)

Sorting and filters or pivot tables are not directly related. A table
style applies to the current view of a table cell range. It should
however be related to defined database ranges (Data -> Define Range), as
those already have properties for column labels (header row) and totals
row and are used with Table References in formulas as well. I'm not sure
if Impress table styles are actually helpful here, though the
functionality in Table Design of sidebar looks very much like what is
needed. I don't know their implementation details yet though.


>Also, as the bug [#132780](
>https://bugs.documentfoundation.org/show_bug.cgi?id=132780) talks about
>in detail, it also includes that the functionality is present identically
>in openoffice with a GPL3 license,

If you meant
https://bugs.documentfoundation.org/show_bug.cgi?id=132780#c7
that's not OpenOffice but OnlyOffice. And no, we can't use GPL code so
that comment is off.

That bug also is more about the functionality of tables, like behaviour
when new rows are added copying formulas of the row above and such.
Let's focus here on the Table Styles.


>I’m not extremely well versed in this, but I assume apart from the
>hindrance to user of formatting added data manually in Autoformat styles,
>the main difference of table styles to that would be that instead of
>applying the attributes cell by cell, they would be applied directly to the
>entire table.

That's correct. (which effectively means that one table style attribute
will be applied to a range of rows per column).

>I believe this would require some concepts of Object-Oriented
>programming to increase the efficiency, and I think I could understand
>better from how it is already implemented in Impress.

Try to work through, maybe it's helpful for ideas. Note though that
Calc's attribution handling works quite different.


>Lastly, I see that suggestions include asking users to use pivot tables
>for functionalities such as creating charts from tables etc., so if we do
>implement table styles, I assume we would merge it with pivot tables.
>Please feel free to correct me if I’m wrong anywhere and guide me on how to
>proceed further with this project and what resources would I need to study?

As said, the table style view should be completely independent of any
pivot table functionality.


The current attribution of cells has 3 levels, ordered in precedence
(top items override lower items):

1. conditional format
2. hard attribution
3. cell style

Table styles would go between hard attribution and cell style, yielding
a precedence of

1. conditional format
2. hard attribution
3. table style
4. cell style

So all methods asking for cell atributes that currently evaluate styles,
hard attribution and conditional formatting would have to evaluate table
styles as well to determine the final attributes relevant to display
a cell.

Some code pointers:

sc/source/core/data/attarray.cxx
Does all the applying an attribute to a range of rows within a column
and obtaining attributes. Probably adding/removing table styles could be
similar to ScAttrArray::AddCondFormat() and
ScAttrArray::RemoveCondFormat(), just an idea.

sc/source/core/data/documen4.cxx
* ScDocument::GetEffItem()
  * Obtains the effective item for an attribute (per WhichId), i.e.
overriding with a conditional format if present. That should handle
table styles as well in the correct order.
* ScDocument::GetCondFormat()
  * Check places where this is called, they'll likely need handling

Re: Redirecting conversation regarding GSoC Project to Mailing List

2022-04-11 Thread Heiko Tietze

Hi Sarrah,

Replying from the UX/design POV, so maybe not really answering your questions.

The table style (TS) feature is supposed to supersede the AutoFormat dialog. TS 
are not only relevant on Calc but also (and probably more aware to users) in 
Writer. And access from the Stylist at the sidebar is possible there though it 
lacks a preview like in Draw/Impress. And the UI is missing to edit the TS. But 
the top PITA is this binary format.


* bug 49437: Writer/Calc: Use XML for serializing table autoformats instead of 
the current brittle binary format

* bug 105933: Means to modify existing table styles in a dialog
* bug 101802: Consolidate Writer and Draw/Impress sidebar table design content 
panel

The META ticket lists a gazillion internal issues that are also highly relevant
* https://bugs.documentfoundation.org/show_bug.cgi?id=101756

Previous GSoC project is documented at 
https://gist.github.com/ubap/55d22ef9b2e00347a2dc58ca4cb8b0ea


UI proposal by the design team at 
https://design.blog.documentfoundation.org/2015/12/13/style-your-tables/


Hope that helps,
Heiko

On 08.04.22 13:21, Sarrah Bastawala wrote:

Hello All,

Continuing here the conversation with Eike Rathke as instructed by him in the 
previous email :


However, I'd like to keep further dev-related and specifically GSoC
discussion on our mailing list libreoffice@lists.freedesktop.org
<mailto:libreoffice@lists.freedesktop.org> and
continue things there, so everyone can benefit.

That being said, do you already have ideas what would be required for
a solution?

Thank you for replying to me! I would definitely be glad to solve an interesting 
problem with your mentorship.


Based on what I have understood so far, here is the functionality we are looking 
to implement in Table Styles



  *

We want to visually make it similar to the tables currently present in
autoformat, however it should be able to apply the same attribute to
multiple cells changing as more data is entered

  *

The functionality for this could be referred to from the present table
styles in Impress and the functionality for sorting, filters, etc from
existing code for pivot tables in calc, if I’m not wrong. ( I would
appreciate if you could give me the code pointers for these to refer 
directly)

  *

Also, as the bug
[#132780](https://bugs.documentfoundation.org/show_bug.cgi?id=132780
<https://bugs.documentfoundation.org/show_bug.cgi?id=132780>) talks about in
detail, it also includes that the functionality is present identically in
openoffice with a GPL3 license, so I do not know exactly how that can be
used and how it would fall within the scope of this project, and hence would
appreciate pointers from you.

  *

I’m not extremely well versed in this, but I assume apart from the hindrance
to user of formatting added data manually in Autoformat styles, the main
difference of table styles to that would be that instead of applying the
attributes cell by cell, they would be applied directly to the entire table.
I believe this would require some concepts of Object-Oriented programming to
increase the efficiency, and I think I could understand better from how it
is already implemented in Impress.

  *

Lastly, I see that suggestions include asking users to use pivot tables for
functionalities such as creating charts from tables etc., so if we do
implement table styles, I assume we would merge it with pivot tables. Please
feel free to correct me if I’m wrong anywhere and guide me on how to proceed
further with this project and what resources would I need to study?


Sincerely,
Sarrah










--
Dr. Heiko Tietze, UX-Designer and UX-Mentor
Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint


OpenPGP_signature
Description: OpenPGP digital signature


Redirecting conversation regarding GSoC Project to Mailing List

2022-04-08 Thread Sarrah Bastawala
Hello All,

Continuing here the conversation with Eike Rathke as instructed by him in
the previous email :

> However, I'd like to keep further dev-related and specifically GSoC
> discussion on our mailing list libreoffice@lists.freedesktop.org and
> continue things there, so everyone can benefit.
>
> That being said, do you already have ideas what would be required for
> a solution?

Thank you for replying to me! I would definitely be glad to solve an
interesting problem with your mentorship.

Based on what I have understood so far, here is the functionality we are
looking to implement in Table Styles


   -

   We want to visually make it similar to the tables currently present in
   autoformat, however it should be able to apply the same attribute to
   multiple cells changing as more data is entered
   -

   The functionality for this could be referred to from the present table
   styles in Impress and the functionality for sorting, filters, etc from
   existing code for pivot tables in calc, if I’m not wrong. ( I would
   appreciate if you could give me the code pointers for these to refer
   directly)
   -

   Also, as the bug [#132780](
   https://bugs.documentfoundation.org/show_bug.cgi?id=132780) talks about
   in detail, it also includes that the functionality is present identically
   in openoffice with a GPL3 license, so I do not know exactly how that can be
   used and how it would fall within the scope of this project, and hence
   would appreciate pointers from you.
   -

   I’m not extremely well versed in this, but I assume apart from the
   hindrance to user of formatting added data manually in Autoformat styles,
   the main difference of table styles to that would be that instead of
   applying the attributes cell by cell, they would be applied directly to the
   entire table. I believe this would require some concepts of Object-Oriented
   programming to increase the efficiency, and I think I could understand
   better from how it is already implemented in Impress.
   -

   Lastly, I see that suggestions include asking users to use pivot tables
   for functionalities such as creating charts from tables etc., so if we do
   implement table styles, I assume we would merge it with pivot tables.
   Please feel free to correct me if I’m wrong anywhere and guide me on how to
   proceed further with this project and what resources would I need to study?


Sincerely,
Sarrah


[Libreoffice-bugs] [Bug 143120] After deleting a row in a Calc project, crash occurs when I attempt to FILESAVE the changes.

2022-04-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143120

--- Comment #4 from QA Administrators  ---
Dear h6...@comcast.net,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 143120] After deleting a row in a Calc project, crash occurs when I attempt to FILESAVE the changes.

2022-04-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143120

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 143120] After deleting a row in a Calc project, crash occurs when I attempt to FILESAVE the changes.

2022-03-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143120

--- Comment #3 from QA Administrators  ---
Dear h6...@comcast.net,

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 143120] After deleting a row in a Calc project, crash occurs when I attempt to FILESAVE the changes.

2021-09-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143120

Timur  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #2 from Timur  ---
Please: 
1. try with User Profile Reset or  Menu/Help/Restart in Safe Mode
2. attach sample file and write exact steps.

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

[Libreoffice-bugs] [Bug 118277] FILEOPEN XLSX Basic project with VBA Project Password does not work in Calc

2021-07-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118277

NISZ LibreOffice Team  changed:

   What|Removed |Added

 Blocks||143335


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=143335
[Bug 143335] [META] XLSX (OOXML) document protection issues
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 143120] After deleting a row in a Calc project, crash occurs when I attempt to FILESAVE the changes.

2021-06-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143120

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Please test with a clean profile, Menu/Help/Restart in Safe Mode

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


[Libreoffice-bugs] [Bug 143120] New: After deleting a row in a Calc project, crash occurs when I attempt to FILESAVE the changes.

2021-06-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143120

Bug ID: 143120
   Summary: After deleting a row in a Calc project, crash occurs
when I attempt to FILESAVE the changes.
   Product: LibreOffice
   Version: 7.1.4.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: h6...@comcast.net

Description:
I have a Calc sheet containing cells with text and cells with images set to
conform to the cell size to which the image is anchored. When I first delete
the contents of the image cell, then delete the row containing the image, all
operations complete without error. Then when I attempt to save the project
after the deletions, the crash occurs.

Steps to Reproduce:
1.Delete an anchored image in a cell.
2.Select the row containing the (now) deleted image. 
3.Delete the selected row.
4.Save (or Save As) the sheet after the deletions have been made.
5.Crash occurs and Calc closes.

Actual Results:
When the recovery process finishes, the loaded sheet displays the entire
project including the (failed attempt) deleted row with the deleted image.

Expected Results:
After the recovery operation (which runs when I attempt to reload the project)
I would expect the project to be displayed without the row I attempted to
delete. Neither the crash nor the recovery should be necessary.


Reproducible: Always


User Profile Reset: No



Additional Info:
I delete the image from its cell BEFORE deleting the row. Otherwise the row is
deleted but the anchored image (which should have been deleted along with the
other cells in the row)remains in place. Then when the rows below move up, the
image no longer coincides with the text information contained within the other
cells in the row.

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-06-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Padia Rashesh  changed:

   What|Removed |Added

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

--- Comment #17 from Padia Rashesh  ---
Basically I have to create a .rc file which contains all the URLs and somehow
read it with help of bootstrap.hxx at runtime 
But I am confused on the following points:

1) grep for libreoffice.org - BEWARE - many instances of openoffice.org are
standards related around ODF and other XML file formats - these must -not- be
changed (obviously). But ones that point to simple web pages make good targets
for clean configurability. 

I don't understand what you are trying to say, can you explain with example?

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


Re: Weekly Progress of GSoC project

2021-06-06 Thread Ilmari Lauhakangas

On 6.6.2021 9.49, Regis Perdreau wrote:

On 05.06.21 21:07, anshu khare wrote:
 > Hi
 >
 > My GSoC project can be viewed here :
 >

https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/

<https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/>

 >

<https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/

<https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/>>
 >
 > In my first week, I made a good connection with my mentors. We
came out with
 > different ways of communication. I really enjoyed talking to them
and discussing
 > different ideas and approaches for the project.
 > In the technical aspect, I made a treeview and loaded Character
Styles in that
 > treeview..
 >
 > My patch can be found here :
https://gerrit.libreoffice.org/c/core/+/116340
<https://gerrit.libreoffice.org/c/core/+/116340>
 > <https://gerrit.libreoffice.org/c/core/+/116340
<https://gerrit.libreoffice.org/c/core/+/116340>>
 >
 > Looking forward to implement many more ideas in the next week :)
 >
 > Thanks
 > Regards
 > Anshu
 >

>
> Le dim. 6 juin 2021 à 08:40, Heiko Tietze
>  <mailto:heiko.tie...@documentfoundation.org>> a écrit :
>
> Actually it was week zero - the real coding period begins tomorrow
> Jul/07 and
> lasts until Aug/16. Google's idea of the current "bonding" is to
> make yourself
> familiar with code and community, which you did greatly.
>
> Cheers,
> Heiko
>
>
> Hi,
>
> I'm trying to follow progress about this Gsoc and others, so it's nice
> to have little thinkings about before.
>
> We have error 500 when following the link above.
> 
(https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/ 

> 
<https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/>)

>
> Cheers,
>
> Régis Perdreau
>

Public link:

https://summerofcode.withgoogle.com/projects/#5869092168269824

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


Re: Weekly Progress of GSoC project

2021-06-06 Thread Regis Perdreau
Hi,

I'm trying to follow progress about this Gsoc and others, so it's nice to
have little thinkings about before.

We have error 500 when following the link above. (
https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/
)

Cheers,

Régis Perdreau



Le dim. 6 juin 2021 à 08:40, Heiko Tietze <
heiko.tie...@documentfoundation.org> a écrit :

> Actually it was week zero - the real coding period begins tomorrow Jul/07
> and
> lasts until Aug/16. Google's idea of the current "bonding" is to make
> yourself
> familiar with code and community, which you did greatly.
>
> Cheers,
> Heiko
>
> On 05.06.21 21:07, anshu khare wrote:
> > Hi
> >
> > My GSoC project can be viewed here :
> >
> https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/
> > <
> https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/
> >
> >
> > In my first week, I made a good connection with my mentors. We came out
> with
> > different ways of communication. I really enjoyed talking to them and
> discussing
> > different ideas and approaches for the project.
> > In the technical aspect, I made a treeview and loaded Character Styles
> in that
> > treeview..
> >
> > My patch can be found here :
> https://gerrit.libreoffice.org/c/core/+/116340
> > <https://gerrit.libreoffice.org/c/core/+/116340>
> >
> > Looking forward to implement many more ideas in the next week :)
> >
> > Thanks
> > Regards
> > Anshu
> >
> >
> >
> >
> >
> >
> >
> > ___
> > LibreOffice mailing list
> > LibreOffice@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/libreoffice
> >
>
> --
> Dr. Heiko Tietze, UX-Designer and UX-Mentor
> Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
> The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
> Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
> Legal details: https://www.documentfoundation.org/imprint
>
> ___
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice
>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Weekly Progress of GSoC project

2021-06-06 Thread Heiko Tietze
Actually it was week zero - the real coding period begins tomorrow Jul/07 and 
lasts until Aug/16. Google's idea of the current "bonding" is to make yourself 
familiar with code and community, which you did greatly.


Cheers,
Heiko

On 05.06.21 21:07, anshu khare wrote:

Hi

My GSoC project can be viewed here : 
https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/ 
<https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/>


In my first week, I made a good connection with my mentors. We came out with 
different ways of communication. I really enjoyed talking to them and discussing 
different ideas and approaches for the project.
In the technical aspect, I made a treeview and loaded Character Styles in that 
treeview..


My patch can be found here : https://gerrit.libreoffice.org/c/core/+/116340 
<https://gerrit.libreoffice.org/c/core/+/116340>


Looking forward to implement many more ideas in the next week :)

Thanks
Regards
Anshu







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



--
Dr. Heiko Tietze, UX-Designer and UX-Mentor
Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint



OpenPGP_signature
Description: OpenPGP digital signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Weekly Progress of GSoC project

2021-06-05 Thread anshu khare
Hi

My GSoC project can be viewed here :
https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/

In my first week, I made a good connection with my mentors. We came out
with different ways of communication. I really enjoyed talking to them and
discussing different ideas and approaches for the project.
In the technical aspect, I made a treeview and loaded Character Styles in
that treeview..

My patch can be found here : https://gerrit.libreoffice.org/c/core/+/116340

Looking forward to implement many more ideas in the next week :)

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


Re: GSOC Project - "Write Missing Unit Tests"

2021-06-02 Thread Xisco Fauli
Hi Shubham,

Welcome aboard!

On 28/5/21 22:17, Shubham Jain wrote:
> Hi everyone!
> I am Shubham Jain. I am an ungrad student from India. I am very happy
> to get to work at an esteemed organisation like LibreOffice for the
> summer. 
>
> I am selected for the GSOC project - "Write Missing Unit Tests". I'll
> be working under the mentorship of Mr. Xisco Fauli and Mr. Ilmari
> Lauhakangas. My main goal will be to extend the test coverage for all
> the modules present in LO.
>
> Looking forward to connecting with all the mentors and other participants.
> Shubham Jain
>
>
>
> ___
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice

-- 
Xisco Faulí
LibreOffice QA Team
IRC: x1sc0

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


GSOC Project - "Write Missing Unit Tests"

2021-05-29 Thread Shubham Jain
Hi everyone!
I am Shubham Jain. I am an ungrad student from India. I am very happy
to get to work at an esteemed organisation like LibreOffice for the summer.

I am selected for the GSOC project - "Write Missing Unit Tests". I'll be
working under the mentorship of Mr. Xisco Fauli and Mr. Ilmari Lauhakangas.
My main goal will be to extend the test coverage for all the modules
present in LO.

Looking forward to connecting with all the mentors and other participants.
Shubham Jain
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-05-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Buovjaga  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #16 from Buovjaga  ---
(In reply to rino19ny from comment #15)
> wow more than 4 years!
> 
> someone still working on this?
> 
> by "..around the place.." meaning most source files still have hardcoded
> URLs??

Please don't change the status to needinfo:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO
Needinfo reports will be automatically closed after some time, so you don't
want to do that here.

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-05-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

rino1...@gmail.com changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #15 from rino1...@gmail.com ---
wow more than 4 years!

someone still working on this?

by "..around the place.." meaning most source files still have hardcoded URLs??

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


GSoC Project - "Tests for the VCL graphics backend"

2021-05-28 Thread Mind Baffler
Hi everyone,
I'm Akshit, a student and a newbie contributor to LibreOffice. I am
delighted to share with you that I've been given this wonderful opportunity
to work with LibreOffice during this GSoC under the mentorship of Tomaž
Vajngerl and Luboš Luňák. My project's titled *Tests for the VCL graphics
backend* and its main focus is to prevent any irregular user experience
that might show up in any graphics backend. The main objectives of my
project are:

   1. To run the pre-existing tests when the user first installs
   LibreOffice or Upgrades it and also to provide a UI functionality to the
   user to test the tests on his/her own will enabling him/her to present any
   graphics related issue to the community easily if present.
   2. Adding more test cases to refine the pre-existing test cases thereby
   covering almost every graphics feature used in LibreOffice.

I'm really excited to work on this project and to make a difference to the
LibreOffice codebase for good with the help of my brilliant mentors.

Yours Sincerely,
Akshit
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Request for information about LibreOffice for university project

2021-05-28 Thread sophi
Hi,
Le 27/05/2021 à 21:04, Alberto a écrit :
> Greetings,
> 
> My name is Alberto Dorizza and I’m writing for a group of Software
> Engineering students at University of Padova (Italy) conducting research
> that involves the analysis of the development process of a software of our
> choosing.
> 
> Therefore we would like to conduct this research on LibreOffice, on which
> we thought you might be able to enlighten us.
> 
> 
> Our research is based on a few points, that is the focus and purpose of
> this software, the development strategies and models applied, the software
> requirements, the update commit frequency and if possible a history of such
> updates.
> 
> We want to enforce the purely informative purpose of this research.

In addition to Marco's answer, you'll find several information on the
project here:
https://dashboard.documentfoundation.org/

Kind regards
Sophie

-- 
Sophie Gautier so...@libreoffice.org
GSM: +33683901545
IRC: sophi
Foundation coordinator
The Document Foundation
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Request for information about LibreOffice for university project

2021-05-27 Thread Marco Marinello
Dear Alberto,


please, try to post here on the ML a list of questions you would ask
regarding our development process so that (different) devs and
contributors can try to answer as best as we can.


Nice project, indeed (is it a thesis?)

All the best,

Marco Marinello


Il 27/05/21 21:04, Alberto ha scritto:
>
> Greetings,
>
>
> My name is Alberto Dorizza and I’m writing for a group of Software
> Engineering students at University of Padova (Italy) conducting
> research that involves the analysis of the development process of a
> software of our choosing.
>
> Therefore we would like to conduct this research on LibreOffice, on
> which we thought you might be able to enlighten us.
>
> Our research is based on a few points, that is the focus and purpose
> of this software, the development strategies and models applied, the
> software requirements, the update commit frequency and if possible a
> history of such updates.
>
> We want to enforce the purely informative purpose of this research.
>
> We are very much open to fix an appointment with yourself, or with
> whom this might be of concern, to discuss in more details our
> requests, if needed.
>
> Should our project meet your interest, we would respectfully ask of
> you a rather quick response so that we might close in well on our
> strict deadline.
>
> I give you our utmost thanks for your helpfulness.
>
>
> Sincerely,
>
> Alberto Dorizza
>
>
>
> ___
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Request for information about LibreOffice for university project

2021-05-27 Thread Alberto
Greetings,

My name is Alberto Dorizza and I’m writing for a group of Software
Engineering students at University of Padova (Italy) conducting research
that involves the analysis of the development process of a software of our
choosing.

Therefore we would like to conduct this research on LibreOffice, on which
we thought you might be able to enlighten us.


Our research is based on a few points, that is the focus and purpose of
this software, the development strategies and models applied, the software
requirements, the update commit frequency and if possible a history of such
updates.

We want to enforce the purely informative purpose of this research.


We are very much open to fix an appointment with yourself, or with whom
this might be of concern, to discuss in more details our requests, if
needed.

Should our project meet your interest, we would respectfully ask of you a
rather quick response so that we might close in well on our strict deadline.

I give you our utmost thanks for your helpfulness.

Sincerely,

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


[Libreoffice-bugs] [Bug 107146] "Project Open Thesauri"

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

Aron Budea  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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


[Libreoffice-bugs] [Bug 107146] "Project Open Thesauri"

2021-05-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107146

--- Comment #4 from Fenske  ---
Total result Paris

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


[Libreoffice-bugs] [Bug 118167] FILESAVE XLSX VBA-Project and Microsoft Excel Objects look different after export

2021-04-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118167

--- Comment #12 from QA Administrators  ---
Dear Gabor Kelemen,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-03-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

Buovjaga  changed:

   What|Removed |Added

 Status|ASSIGNED|NEW

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-03-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

adityapratapsing...@gmail.com changed:

   What|Removed |Added

   Assignee|adityapratapsingh51@gmail.c |libreoffice-b...@lists.free
   |om  |desktop.org

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-03-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

adityapratapsing...@gmail.com changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |adityapratapsingh51@gmail.c
   |desktop.org |om

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-03-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

--- Comment #14 from Buovjaga  ---
(In reply to adityapratapsingh51 from comment #13)
> Could you explain what "...and use these cf. boots..." means?

cf. means comparison. Note comment 5

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


[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs

2021-03-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38890

--- Comment #13 from adityapratapsing...@gmail.com ---
(In reply to Björn Michaelsen from comment #0)
> Remove hard-coded project URLs
> 
> Background: We still have a number of hardcoded URLs around the place, some
> of which become visible in the UI. We should have these extracted from a
> config file instead - preferably a textual 'rc' file (sal has code to parse
> and use these cf. boots). To find many instances of hard-coded URLs use:
> 
> bin/g grep '"http://' | grep '\.[ch]xx:'
> 
> or grep for libreoffice.org - BEWARE - many instances of openoffice.org are
> standards related around ODF and other XML file formats - these must -not-
> be changed (obviously). But ones that point to simple web pages make good
> targets for clean configurability.
> 
> Skills: git grep, simple C++ programming

Could you explain what "...and use these cf. boots..." means?

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


Re: Gsoc 2021 project Discussion

2021-03-10 Thread Ilmari Lauhakangas

On 10.3.2021 13.32, Kunal Singh wrote:

Hello Mentors,
I am Kunal Singh 2nd year UG at computer science department IIT 
kharagpur , I am proficient in c++ and have good knowledge of object 
oriented programming in c++ and Python
I was seeing the Ideas page and found some good projects and I want some 
lead on write missing unit tests 
<https://wiki.documentfoundation.org/Development/GSoC/Ideas> project .


I have invited you to an orienting interview.

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


Gsoc 2021 project Discussion

2021-03-10 Thread Kunal Singh
Hello Mentors,
I am Kunal Singh 2nd year UG at computer science department IIT kharagpur ,
I am proficient in c++ and have good knowledge of object oriented
programming in c++ and Python
I was seeing the Ideas page and found some good projects and I want some
lead on write missing unit tests
<https://wiki.documentfoundation.org/Development/GSoC/Ideas> project .

-- 


[image: Image result for iit kgp logo]

Kunal Singh

Second Year Undergraduate Student

Computer Science and Engineering

Indian Institute of Technology,

Kharagpur

Github <https://github.com/kunalsingh2002>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice-bugs] [Bug 135405] Dictionaries: Add Korean(ko_KR) spellcheck dictionary from existing hunspell Korean dictionary project

2020-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135405

Xisco Faulí  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |ju.il...@gmail.com
   |desktop.org |
 CC||xiscofa...@libreoffice.org

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


[Libreoffice-bugs] [Bug 135405] Dictionaries: Add Korean(ko_KR) spellcheck dictionary from existing hunspell Korean dictionary project

2020-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135405

--- Comment #8 from Commit Notification 
 ---
Ilkyu Ju committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/dictionaries/commit/975046e0970d4300bb229fb0cbe3d5d0afec8c8f

tdf#135405 Add Korean(ko_KR) spellcheck dictionary

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


[Libreoffice-bugs] [Bug 135405] Dictionaries: Add Korean(ko_KR) spellcheck dictionary from existing hunspell Korean dictionary project

2020-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135405

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.1.0

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


[Libreoffice-bugs] [Bug 99054] Distribution on Windows Store using "Project Centennial"

2020-10-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99054

--- Comment #5 from Claudius Ellsel  ---
Thanks for updating this issue.

Unfortunately I don't share your viewpoints on this topic.

While the work might have been "non-trivial", it is most likely not too hard,
either.

The "automatic update functionality and the convenience it provides to users"
is mainly provided by Microsoft's ecosystem, not Collabora or CIB by the way.
Using that as an argument is thus a bit flawed.

Also note that there is a long-standing bug report about making the auto update
on Windows work again:
https://bugs.documentfoundation.org/show_bug.cgi?id=68274

I don't like having to rely on third companies for continued support of this
software. It does not look convincing to me that the support is split in
between companies for different platforms, either. If at least all
infrastructure and resources needed for building and publishing would be at the
hands of the document foundation that would ensure some trust.

This current situation is rather frustrating for me, though.

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


[Libreoffice-bugs] [Bug 99054] Distribution on Windows Store using "Project Centennial"

2020-10-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99054

Adolfo Jayme  changed:

   What|Removed |Added

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

--- Comment #4 from Adolfo Jayme  ---
The “LibreOffice Vanilla” builds that you see in Microsoft Store and macOS’ App
Store are official LibreOffice builds and identical to the ones you can
download from The Document Foundation websites.

Since Collabora and CIB provided the (non-trivial) work needed to build and
publish these, we believe it’s fair that they are paid in exchange for the
automatic update functionality and the convenience it provides to users
(similar to the paint.net model). Collabora and CIB are companies that play an
important part in our development ecosystem, and they employ the people that
develop LibreOffice, so buying LibreOffice Vanilla is a way to support the
LibreOffice project.

This is the reason why we don’t plan to make those builds gratis. Of course,
you can always download LibreOffice for free at our website.

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


[Libreoffice-bugs] [Bug 99054] Distribution on Windows Store using "Project Centennial"

2020-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99054

Claudius Ellsel  changed:

   What|Removed |Added

 CC||claudius.ell...@live.de

--- Comment #3 from Claudius Ellsel  ---
There is apparently a version now on the Store:
https://www.libreoffice.org/download/libreoffice-from-microsoft-and-mac-app-stores/

Unfortunately that is not from The Document Foundation and paid. Not really
what I expected and rather frustrating.

I hope there can be an official free version soon!

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

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

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEEDINFO|RESOLVED

--- Comment #8 from Roman Kuznetsov <79045_79...@mail.ru> ---
So let's close it as WF

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

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

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEEDINFO|RESOLVED

--- Comment #8 from Roman Kuznetsov <79045_79...@mail.ru> ---
So let's close it as WF

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #7 from Mike Kaganski  ---
The specific task that ODM solves for Writer documents, which can't be solved
by OLE, is central management/redefinition of styles: a style definition in
master document overrides same-name style in linked documents.

This is not applicable to proposed mixed-type content. Better link management
is a different problem, and needs own improvement to eliminate the reason
mentioned here ("dynamic links between files can be broken with change of
computer or change of document places").

So WF from my PoV.

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #7 from Mike Kaganski  ---
The specific task that ODM solves for Writer documents, which can't be solved
by OLE, is central management/redefinition of styles: a style definition in
master document overrides same-name style in linked documents.

This is not applicable to proposed mixed-type content. Better link management
is a different problem, and needs own improvement to eliminate the reason
mentioned here ("dynamic links between files can be broken with change of
computer or change of document places").

So WF from my PoV.

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #6 from Heiko Tietze  ---
So my take: WONTFIX.

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #6 from Heiko Tietze  ---
So my take: WONTFIX.

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #5 from Regina Henschel  ---
(In reply to Heiko Tietze from comment #3) 
> Regina, are there any plans to pack various files into a container?

No. If you not use the flat format but the usual package format, then a .odg
file for example, is already a container. You can add files to that packages,
if you list them in the manifest.xml in folder META-INF.

A different question is, how to access additional content from within the main
document. For all of our own file formats, it works with OLE, not only on
Windows, but on other supported operating systems too.

For linking to other content we have already solutions. You can include linked
text content in Writer via "section". You have a similar mechanism in Calc to
integrate other table-like content as link and in Draw/Impress to integrate
other drawing content as link. I see no need to integrate mixed content beyond
the already existing OLE mechanism.

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #5 from Regina Henschel  ---
(In reply to Heiko Tietze from comment #3) 
> Regina, are there any plans to pack various files into a container?

No. If you not use the flat format but the usual package format, then a .odg
file for example, is already a container. You can add files to that packages,
if you list them in the manifest.xml in folder META-INF.

A different question is, how to access additional content from within the main
document. For all of our own file formats, it works with OLE, not only on
Windows, but on other supported operating systems too.

For linking to other content we have already solutions. You can include linked
text content in Writer via "section". You have a similar mechanism in Calc to
integrate other table-like content as link and in Draw/Impress to integrate
other drawing content as link. I see no need to integrate mixed content beyond
the already existing OLE mechanism.

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #4 from paulyste...@web.de ---
dynamic links between files can be broken with change of computer or change of
document places.
so in LO writer document there are calc parts, formulas, draws and so on
In a container all is in one place with direct link without file system
problems.

Or is this perfect solved in LO?

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #4 from paulyste...@web.de ---
dynamic links between files can be broken with change of computer or change of
document places.
so in LO writer document there are calc parts, formulas, draws and so on
In a container all is in one place with direct link without file system
problems.

Or is this perfect solved in LO?

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #3 from Heiko Tietze  ---
Paul, what problem do you want to solve with such a container? What is the use
case?

Regina, are there any plans to pack various files into a container?

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #3 from Heiko Tietze  ---
Paul, what problem do you want to solve with such a container? What is the use
case?

Regina, are there any plans to pack various files into a container?

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> ---
I disagree with this idea and don't see any problem with current file
extensions by its modules

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

--- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> ---
I disagree with this idea and don't see any problem with current file
extensions by its modules

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


[Libreoffice-ux-advise] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

V Stuart Foote  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||rb.hensc...@t-online.de,
   ||vstuart.fo...@utsa.edu

--- Comment #1 from V Stuart Foote  ---
Thank you for the suggestion.

LibreOffice is OASIS ODF standards driven. ODF Master documents are provided
for in the ODF 1.2/1.3 standard.

You can already insert content from any LO module as OLE object into any
subdocument.

And no single moudule other than Writer benefits from the organization
complexity that the Writer centric ODF Master document provides.

IMHO => WF

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


[Libreoffice-bugs] [Bug 137207] there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

V Stuart Foote  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||rb.hensc...@t-online.de,
   ||vstuart.fo...@utsa.edu

--- Comment #1 from V Stuart Foote  ---
Thank you for the suggestion.

LibreOffice is OASIS ODF standards driven. ODF Master documents are provided
for in the ODF 1.2/1.3 standard.

You can already insert content from any LO module as OLE object into any
subdocument.

And no single moudule other than Writer benefits from the organization
complexity that the Writer centric ODF Master document provides.

IMHO => WF

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


[Libreoffice-bugs] [Bug 137207] New: there is no project container for combination of all LO-formats, odm is limited to writer

2020-10-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137207

Bug ID: 137207
   Summary: there is no project container for combination of all
LO-formats, odm is limited to writer
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: paulyste...@web.de

odm is a first trial for complex projects with writer.

But more is necessary in projects with more parts of LO.

A super global document with all parts of LO is my idea.

In a main menu the parts are referenced and sorted.

All part documnents of libre office are possible parts. 

Writer, impress, calc, draw, base, formula documents with full possibilities
are grouped in super global document.
The parts are worked in the part programs.

So links in documents are nor lost with change of file system position.

I hope this idea is understood and good enough.

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


[Libreoffice-bugs] [Bug 135405] Dictionaries: Add Korean(ko_KR) spellcheck dictionary from existing hunspell Korean dictionary project

2020-09-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135405

--- Comment #7 from DaeHyun Sung  ---
(In reply to DaeHyun Sung from comment #6)
> Created attachment 164173 [details]
> Example of Huspell-ko dictionary on LibreOffice.
> 
> Example of Huspell-ko dictionary on LibreOffice.
> 어루만자기(incorrect) to 어루만지기(correct)

I tested it on my laptop both  openSUSE Tumbleweeds and Windows 10. 

Linux
Version: 7.1.0.0.alpha0+
Build ID: 6935dcd80f1677a293a412da3d94afd1217c0bd1
CPU threads: 16; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: ko-KR (ko_KR.UTF-8); UI: ko-KR
Calc: threaded

Windows
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 6935dcd80f1677a293a412da3d94afd1217c0bd1
CPU threads: 6; OS: Windows 10.0 Build 19041; UI render: default; VCL: win
Locale: ko-KR (ko_KR); UI: ko-KR
Calc: threaded

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


[Libreoffice-bugs] [Bug 118277] FILEOPEN XLSX Basic project with VBA Project Password does not work in Calc

2020-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118277

Aron Budea  changed:

   What|Removed |Added

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108914
[Bug 108914] [META] Password protected file bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118277] FILEOPEN XLSX Basic project with VBA Project Password does not work in Calc

2020-08-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118277

Mike Kaganski  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 135405] Dictionaries: Add Korean(ko_KR) spellcheck dictionary from existing hunspell Korean dictionary project

2020-08-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135405

--- Comment #6 from DaeHyun Sung  ---
Created attachment 164173
  --> https://bugs.documentfoundation.org/attachment.cgi?id=164173=edit
Example of Huspell-ko dictionary on LibreOffice.

Example of Huspell-ko dictionary on LibreOffice.
어루만자기(incorrect) to 어루만지기(correct)

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


[Libreoffice-bugs] [Bug 135405] Dictionaries: Add Korean(ko_KR) spellcheck dictionary from existing hunspell Korean dictionary project

2020-08-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135405

--- Comment #5 from DaeHyun Sung  ---
Created attachment 164171
  --> https://bugs.documentfoundation.org/attachment.cgi?id=164171=edit
Example of Huspell-ko dictionary on LibreOffice

Example of Huspell-ko dictionary on LibreOffice.
숫닭(incorrect) to 수탉(correct)

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


  1   2   3   4   5   6   >