Re: Forums and FAQ
Am 16.05.22 um 20:45 schrieb Dave Fisher: We don’t have the German Forum on forum.openoffice.org - we link to here: https://www.openoffice.org/de/foren.html and that links to here: https://www.openoffice-forum.de so, we don't need the strings in German as they won't show up, right? Thanks Marcus On May 16, 2022, at 10:37 AM, Marcus wrote: Am 10.05.22 um 02:25 schrieb Dave Fisher: We need versions of the following strings to add for each language: ./language/en/help/faq.php 'HELP_FAQ_AOO_SPECIFIC' => 'OpenOffice.org Community Forum Specific Issues', 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => 'Where can I find FAQs relating specifically to OpenOffice.org products?', 'HELP_FAQ_AOO_WHERE'=> 'We don\'t maintain an FAQ per se, but you is you start with our Survival Guide, this will explain how to go about using the forum. You will also find specific tutorials in the Tutorials forum. You can also use the https://wiki.openoffice.org/wiki/;>OpenOffice wiki as a knowledge source.', 'HELP_FAQ_AOO_HOW_TO_ASK' => ‘ How do I ask a question?', 'HELP_FAQ_AOO_HOW' => 'Please read the Survival Guide before you post. These guidelines and rules help the community to make the most of this forum. The remainder of this FAQ coverts general issues to do with the using phpBB3.', Here’s where the strings are used. ./phpbb/help/controller/faq.php 'HELP_FAQ_AOO_SPECIFIC', 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => 'HELP_FAQ_AOO_WHERE', 'HELP_FAQ_AOO_HOW_TO_ASK' => 'HELP_FAQ_AOO_HOW', can someone show me where the German strings would show up in the forum? For a (still needed ?) translation I need a bit context. Thanks Marcus On May 9, 2022, at 10:33 AM, Bidouille wrote: Hello, Small problem with FAQ on all forums except EN https://forum.openoffice.org/fr/forum/download/file.php?id=145454 I don't know how these strings has been added. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Forums and FAQ
Am 10.05.22 um 02:25 schrieb Dave Fisher: We need versions of the following strings to add for each language: ./language/en/help/faq.php 'HELP_FAQ_AOO_SPECIFIC' => 'OpenOffice.org Community Forum Specific Issues', 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => 'Where can I find FAQs relating specifically to OpenOffice.org products?', 'HELP_FAQ_AOO_WHERE'=> 'We don\'t maintain an FAQ per se, but you is you start with our Survival Guide, this will explain how to go about using the forum. You will also find specific tutorials in the Tutorials forum. You can also use the https://wiki.openoffice.org/wiki/;>OpenOffice wiki as a knowledge source.', 'HELP_FAQ_AOO_HOW_TO_ASK' => ‘ How do I ask a question?', 'HELP_FAQ_AOO_HOW' => 'Please read the Survival Guide before you post. These guidelines and rules help the community to make the most of this forum. The remainder of this FAQ coverts general issues to do with the using phpBB3.', Here’s where the strings are used. ./phpbb/help/controller/faq.php 'HELP_FAQ_AOO_SPECIFIC', 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => 'HELP_FAQ_AOO_WHERE', 'HELP_FAQ_AOO_HOW_TO_ASK' => 'HELP_FAQ_AOO_HOW', can someone show me where the German strings would show up in the forum? For a (still needed ?) translation I need a bit context. Thanks Marcus On May 9, 2022, at 10:33 AM, Bidouille wrote: Hello, Small problem with FAQ on all forums except EN https://forum.openoffice.org/fr/forum/download/file.php?id=145454 I don't know how these strings has been added. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [IMPORTANT] Scheduling Maintenance for our Forum
Also from me a big thank you for this even bigger work.
It's very much appreciated. :-)
Marcus
Am 05.05.22 um 13:02 schrieb Dick Groskamp:
Thanks for the update Dave. Much appreceated.
Dutch forum looks good.
On 2022/05/04 23:06:54 Dave Fisher wrote:
Maintenance on the Forums is completed!
The Forums are now at phpBB 3.3.7 which was released March 17, 2023. The prior
version was 3.0.9 released July 10, 2011.
Very, very happy. Future updates should be much easier. I will follow up with
the Forum sysadmins on these issues:
1. The Italian Forum has a weird display issues. I think that a post will need
to be regenerated.
2. We need to find forum administrators to replace imacat for each forum.
3. I will need to document the process, customizations and migration steps.
But I’ll need a few days away.
ATB,
Dave
On May 4, 2022, at 7:38 AM, Dave Fisher wrote:
Https://forum.openoffice.org is now offline with a simple page to checkbook
later..
On May 4, 2022, at 7:04 AM, Dave Fisher wrote:
On May 4, 2022, at 1:14 AM, David Robley wrote:
Registration works OK; I registered a new user, got the activation email and
activated the account. Then posted a first message and (as moderator) approved
it, but I _did not_ get the email advising of approval although the post was
cleared. I did check junk as that was where the activation email ended up :-).
There is an apparent inconsistency on the mod control panel; some recent events
that are displayed under the Moderator Logs tab do not appear under the Main
tab.
While I'm on the topic, is there any chance the change to the search page I
mentioned at
https://forum.openoffice.org/en/forum/viewtopic.php?t=105949#p515320 might be
implemented?
Done! Try it on the EN forum and I’ll propagate to the others.
And, pushing my (our?) luck even more, the extensions Banhammer and stopforumspam
mentioned in
https://forum.openoffice.org/en/forum/viewtopic.php?f=104=96141#p513871
We’re going to need to take full control of the forum sysadmin role once the
migration is completed.
On 5/2/22 17:28, Dave Fisher wrote:
The en and fr forums are available to test:
https://openoffice-vm1-lw-us.apache.org/
Please test these forums.
Known work to do:
- Restore the Apache Open Office logo in the header
- Return the Apache and Get OpenOffice information in the footer
- Avatars have moved in 3.3.7 need to determine how to move them.
The automatic mySQL migration from 3.0.9 seems to work but takes quite some
time.
ATB,
Dave
On May 1, 2022, at 11:16 AM, Dave Fisher wrote:
Apologies for the late communication.
The forums are being updated from phpBB 3.0.9 to 3.3.7.
Differences so far:
1. The subsilver2 theme is no longer available.
2. Analytics are removed due to new ASF privacy policies. We can add back
analytics that are compliant in the next weeks.
3. Search Display code is changed and I could not see how add
({NEW_POST_COUNT}) into styles/prosilver/template/index_body.html
4. /style.php is no longer included.
5. /app.php is new.
6. /includes/ucp/ucp_register.php will need to be tested on the French forum.
7. /feed.php is reorganized and it was not clear how to add the customized
rel=“alternate” to one of the links.
This doesn’t seem bad.
Language packs were found and AOO customizations are added.
I expect to finish late tonight - when ready there will be a test url.
Once the forums are put into maintenance the following will happen:
1. Make sure all the files and images that have been uploaded are copied.
2. Dumps of the mysql databases will be copied over.
3. Forum databases will be updated
4. Forum admins will have a chance to test.
5. Once live we’ll triage any issues.
Bidouille has access to the VM … any other forum admins who are already
OpenOffice committers may request access.
A warning - this same VM hosts the wiki and the mysql databases.
I’ll be offline for a few hours before returning to this work and to answer any
questions.
ATB,
Dave
On May 1, 2022, at 10:43 AM, Peter Kovacs wrote:
Am 01.05.22 um 15:59 schrieb Rory O'Farrell:
On Sun, 1 May 2022 15:53:47 +0200
Peter Kovacs wrote:
Hello all,
please note, that we schedule a maintenance for the Forum in order to
move database and content to a new machine. This maintenance tasks
includes also a phpBB updates to a recent version, with all the Forum
Modification ported.
The downtime will take place from Monday, 2nd March 2022 1800 UTC until
the end of the same day.
All the best
Peter
Possible typo? March in place of May?
Thanks Rory, It is May. My mistake.
Rory
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Cheers
--
David Robley
Almost went crazy. Would have been a real short trip.
-
To unsubscribe, e-mail: dev-unsubscr
Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)
Am 27.04.22 um 17:44 schrieb Matthias Seidel:
Sounds great!
I also think that it's a great progress.
As none-developer I cannot really judge how good and valuable the
changes are. But all in all I'm happy to see this refactored to have
less problems.
Well done. :-)
Marcus
Am 26.04.22 um 19:56 schrieb Damjan Jovanovic:
On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski <mailto:j...@jagunet.com>> wrote:
I'm gonna look into the serf->(lib)curl option... Since we don't
use any of the fancy features of serf, I'm thinking that the easy
option might be best
Hi
I've ported our WebDAV content provider module from Serf to Curl.
While it ended well, and several other bugs were found and fixed, it
definitely wasn't the "easy option" Jim ;). Starting with conservative
changes, it ended up needing total restructuring, and became more of a
rewrite. The crashes were frequent and hung connections many, and I
had to read up on the HTTP protocol, and read Curl and Serf's source
code, but eventually I prevailed, and a clean elegant stable Curl
WebDAV module emerged.
The huge patch is attached for anyone wishing to review and test.
Unless there are major objections, I'll push it in a couple of days.
STATUS
It builds and works well on FreeBSD and Windows.
Most of the code was reused, and all the operations and semantics
previously present with Serf, should have been preserved.
Browsing WebDAV files and directories, loading files, overwriting them
("Save"), creating them ("Save As"), renaming and deleting them, all
works.
HTTP and HTTPS proxies work. Unlike Serf, Curl could also support
SOCKS proxies (with minimal further changes), but AOO lacks that
setting in the proxy UI and configuration.
Authentication works, both to the destination server and to the proxy
server. I've successfully tested Basic and Digest authentication. Curl
supports every authentication method Serf does and more.
HTTPS works, with a custom certificate verification function, using
our own certificate store from NSS and its API (like the Serf code
used). A bug was discovered (which is in the Serf implementation too)
where self-signed certificates were being unconditionally rejected;
apparently NSS wants to see that a copy of that certificate in its
certificate chain parameter too. Now they work, and the user gets
prompted to allow access.
HTTPS and authentication can be used together on the same connection
and work well, both bringing up their UI dialogs as needed.
A bug was fixed where when username and password were both present in
the URL (dav://user:pass@host/path), the code was trying to split them
at the "@" instead of ":".
Unnecessary base64 encoding and decoding was removed, when importing
the TLS connection's certificates into our XSecurityEnvironment. They
now come in directly as ASN.1 DER, and still work.
The code was greatly restructured and cleaned up, as Curl's API is
synchronous and blocking, with parameters set in advance instead of
through many callbacks, which has allowed using short clear methods,
and clean separation between the session and request classes. The
WebDAV content provider has shrunk from 35 to 21 C++ files, 43 to 29
header files, and 19129 to 15991 lines of code. With WebDAV methods
centralized and refactored into only 10-20 lines of code each, instead
of scattered across 4 files, it is much more understandable and
maintainable now.
Curl is vastly more portable than Serf. We should build easily now
even on OS/2. We can remain with existing build tools instead of
needing scons or cmake just to build Serf.
3 now unused dependencies were removed: apr, apr-util, and serf. Serf
isn't so bad. APR's pool idea is an ingenious way of doing resource
management in C. However Curl has excellent documentation, guides,
examples, and detailed explanations and even example code for each
setting, while Serf has no documentation. Serf might be worth it in a
project that already uses APR a lot, but we don't.
Instead of the historical, crippled forms of logging like OSL_TRACE(),
which don't appear in release builds, I've made it use the newer
com.sun.star.logging UNO component (wrapped in
comphelper::EventLogger), which was inspired by java.util.logging,
with configurable verbosity levels, handlers (file and console) and
output formats (plain, csv), and importantly, which produces output in
release builds too. I've also made it so that on LogLevel::FINEST,
Curl's verbose mode is enabled and Curl's debug output is also logged
through us, with descriptions of what Curl is doing, and logs of all
HTTP traffic including headers and bodies, before encryption and after
decryption in the case of HTTPS, giving us tremendous detail that can
be used for troubleshooting problems.
CURL CHANGED TO USE OPENSSL AND ZLIB
Curl only supports the custom TLS certificate verification fun
Re: [VOTE] Release AOO 4.1.12-RC1 as GA
Am 21.04.22 um 19:59 schrieb Pedro Lino: FYI there are 6 binding votes https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.12#AOO4.1.12-VoteResolution right, for voting we don't need more time as we have enough. We need at least 3 +1 votes but we have already 7 votes (6 of them are binding). So, do you see any need or additional benefit for more testing (except that more in general is of course always good ;-) )? No criticism, just asking. Thanks Marcus On 04/21/2022 3:02 PM Jim Jagielski wrote: I'll keep this open for a few more days to allow for more testing and voting... On Apr 21, 2022, at 1:36 AM, Don Lewis wrote: On 13 Apr, Jim Jagielski wrote: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.12-RC1 as GA. These artifacts can be found at: https://dist.apache.org/repos/dist/dev/openoffice/4.1.12-RC1/ Please cast your vote: The Release Candidate is good for production/GA: [X] yes / +1 [ ] no / -1 My vote is based on [ ] binding (member of PMC) [X] I have built and tested the RC from source on platform [FreeBSD] [ ] I have tested the binary RC on platform [ ] I tested the source tarball checksum. Opening, editing, saving existing calc and writer docs works. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla list_id parameter in URL question
Am 21.04.22 um 23:43 schrieb Carl Marcum: On 4/21/22 4:15 PM, Marcus wrote: Am 21.04.22 um 14:57 schrieb Carl Marcum: Does anyone know what the list_id parameter is for in the URL after a search? [...] I did a quick search with Google (bugzilla url list_id) and found this as first hit: https://support-bugzilla.mozilla.narkive.com/jXnwYmle/purpose-of-list-id-url-parameter So it seems the list_id may be a saved result, meaning if something happens to an issue that would change the search result list it would not be updated when using the list_id in a URL. You have to do a new search or not include the list_id in the URL to get the current results. At least that is the way I'm understanding it. Now my questions is: When we provide a URL like this in a release blog post or announcement should we do a new search and use the list_id in the URL so we have a snapshot in time or not include it so each user gets an up-to-date result? For example, if an issue is changed from fixed to reopened, do we want that issue to appear in the list after that or not? It might be easier on the database if we use the list_id at release time so everyone that follows the link isn't creating a new entry as long as we're okay with the snapshot in time list. as we present a software release which is fix when published, so it cannot be changed afterwards, I would prefer to deliver a list of its issues which is also fixed. So, let's include (and just keep) the URL paramter. My 2ct. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla list_id parameter in URL question
Am 21.04.22 um 14:57 schrieb Carl Marcum: Does anyone know what the list_id parameter is for in the URL after a search? [...] I did a quick search with Google (bugzilla url list_id) and found this as first hit: https://support-bugzilla.mozilla.narkive.com/jXnwYmle/purpose-of-list-id-url-parameter HTH Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release AOO 4.1.12-RC1 as GA
Am 13.04.22 um 15:54 schrieb Jim Jagielski: [X] yes / +1 [ ] no / -1 My vote is based on [X] binding (member of PMC) [ ] I have built and tested the RC from source on platform [ ] [X] I have tested the binary RC on platform [ ] tested on: - Windows 10 Home 64-bit 21H2 Build 19044.1415 - Installed AOO 4.1.12m1 (Build 9809 - Rev. 60e0a1c111) - First with "en-US" full install - Then "de" langpack - Then "es" langpack - Then switched the UI languages Checksums: - Tested checksums for all source tarballs - Tested checksums for the install files en-US, de, es Document tests: - Existing, older DOC, XLS, PPT documents - Existing, older DOCX, XLSX, PPTX documents - Created a new docs for Writer, Calc, Impress and opened / edited the saved file with all languages Everything without problems. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1.12-dev developer test builds...
Am 09.04.22 um 19:59 schrieb Matthias Seidel: Am 07.04.22 um 21:53 schrieb Marcus: Am 07.04.22 um 11:21 schrieb Matthias Seidel: Am 05.04.22 um 14:44 schrieb Jim Jagielski: Are we ready for a RC1? So, basically only three person are interested in a new release... :-( Still, we should just go ahead and build RC1. count me in. Great! The Release Schedule is here: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.12 I've added my name to the ususal items. Marcus On Mar 27, 2022, at 9:44 AM, Matthias Seidel wrote: Hi Jim, Am 25.03.22 um 13:24 schrieb Jim Jagielski: ... Are available at http://home.apache.org/~jim/AOO-builds/ Thanks! I tested your builds on Ubuntu 16.04 (64bit) and macOS 12. Working as expected. Assuming these look good, we can progress to an RC1 Given that there was not so much response until now I would propose to wait some more days... That way people get the opportunity to test the builds and we also could integrate the latest English dictionary on Tuesday(?). My latest build for Windows can be found here: https://home.apache.org/~mseidel/Apache_OpenOffice_4.1.12_Win_x86_install_en-US_Test.exe Looking forward to more feedback! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1.12-dev developer test builds...
Am 07.04.22 um 11:21 schrieb Matthias Seidel: Am 05.04.22 um 14:44 schrieb Jim Jagielski: Are we ready for a RC1? So, basically only three person are interested in a new release... :-( Still, we should just go ahead and build RC1. count me in. Marcus On Mar 27, 2022, at 9:44 AM, Matthias Seidel wrote: Hi Jim, Am 25.03.22 um 13:24 schrieb Jim Jagielski: ... Are available at http://home.apache.org/~jim/AOO-builds/ Thanks! I tested your builds on Ubuntu 16.04 (64bit) and macOS 12. Working as expected. Assuming these look good, we can progress to an RC1 Given that there was not so much response until now I would propose to wait some more days... That way people get the opportunity to test the builds and we also could integrate the latest English dictionary on Tuesday(?). My latest build for Windows can be found here: https://home.apache.org/~mseidel/Apache_OpenOffice_4.1.12_Win_x86_install_en-US_Test.exe Looking forward to more feedback! Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.1.12?
Am 16.03.22 um 16:40 schrieb Jim Jagielski: Thanks! I volunteer to RM. Is that OK? yes, absolutely. :-) Thanks Marcus On Mar 15, 2022, at 6:43 PM, Matthias Seidel wrote: Just FYI, I created a Release Schedule for AOO 4.1.12: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.12 Feel free to update! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Is the enclosed still true for AOO 4.1.x Impress
Am 09.03.22 um 22:45 schrieb Keith N. McKenna: The Chapter on Impress in the Getting Started Guide contains the following note for using media files in Linix based systems: In Linux-based systems such as Ubuntu, media files do not work straight out of the box. You need to download the Java Media Framework API (JMF) and add the path to jmf.jar to the Class Path in Tools > Options > OpenOffice > Java. Is this still true for 4.1.x versions of AOO. unfortunately, I've no experience with video or sound files in presentations on Linux. Maybe other people can tell their experiences? Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Is certificate from https:/translate.apache.org expired ?
Am 15.03.22 um 17:01 schrieb Dick Groskamp: Tried to log in on the Pootle server at https://translate.apache.org. Firefox can't connect me, indicating that the certifcate for the server might be expired or my computerclock is off. The latter is OK. Could someone check ? yes, Firefox tells me that the certificte is expired at Sun, 06 Mar 2022 12:59:01 GMT. It seems Infra has to renew it. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Am 10.03.22 um 18:21 schrieb Matthias Seidel: Am 10.03.22 um 17:52 schrieb Pedro Lino: Yes, it was updated on March 1st Thanks to Andrea's clear instructions we now have one more trained "staff" to do this update ;) I can confirm that it also works perfectly under Linux using the 4.1.12 Nightly builds Good to hear! Maybe this is a good enough motive to release 4.1.12 to all? This and some other goodies. I think we can plan the release at this point, so maybe we have something ready in April? the more important thing is what we want to have ready for 4.1.2. But this is not a topic for this thread. ;-) Marcus On 03/10/2022 4:10 PM Matthias Seidel wrote: Hi Pedro, all, Am 19.02.22 um 17:56 schrieb Pedro Lino: Hi Andrea, all On 02/13/2022 10:11 PM Andrea Pescetti wrote: I'm assuming lazy consensus on giving you permissions on the Extensions site (not the site itself, actually, but the shell access). You should post here your SourceForge username for you to be added. Once we are ready with permissions we can then get into details of how the feed works. One week later, I assume no one opposes that I have permissions on the Extensions shell access? Who can handle this so you can teach me further steps? At least on Windows I now get an update notification for the English dictionary. So it seems to work again? Many thanks for that! Looking at: https://sourceforge.net/projects/aoo-extensions/files/17102/75/dict-en-20220301_aoo.oxt/stats/timeline the download numbers increase now! Note: With the next AOO release the update notifications should also work for macOS/Linux again. Regards, Matthias Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice-org] branch main updated: Updated download numbers for February and March
Am 08.03.22 um 19:26 schrieb Matthias Seidel: Am 08.03.22 um 19:15 schrieb mar...@apache.org: 2022-02-12,35366,325133641 2022-02-13,36749,325133641 There seems to be something wrong? Also: 2022-02-06,38938,324873405 2022-02-07,48470,324922560 right, with a new commit it will be fixed. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: calc date search issue 60307 in AOO41X
Am 18.02.22 um 00:15 schrieb Carl Marcum: [...] It looks like in 2015 Damjan provided one line fix and BVT test in AOO42X and trunk with git commit 2e4d2335e [2] but it never made it to the AOO41X branch. I'm running a build of AOO41X with this fix included and if it's successful and the tests pass I'll submit a PR. sure, it's great to see that this is the only difference between all branches. Please commit when you see that the fix is working. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Am 11.02.22 um 02:34 schrieb Jean-Christophe Helary: On Feb 11, 2022, at 9:36, Matthias Seidel wrote: Am 11.02.22 um 00:07 schrieb Marcus: Am 10.02.22 um 23:08 schrieb Matthias Seidel: Am 10.02.22 um 23:06 schrieb Marcus: Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Did you read the mail?! OK, I'm trying a thought. I don't know which content and how it was on the webpage that is now gone. So, maybe it's rubish. - Download all extensions - Extract the pure dictionary files - Put them on a new webpage - Exchange the old URL to this new one in OmegaT Can this work? BTW: When I look at the SSL certificate for "https://download.services.openoffice.org/; (yes, with HTTPS) I've the feeling that the page was not under our control. You are right! This site was probably never under our control! The invalid certificate refers to some domains (e.g. https://www.ammec.de). Does anyone know "Marco Skambraks"? @Jean-Christophe: It looks like OmegaT points to a download page that was not from the OpenOffice project. In what format does OmegaT expect the dictionaries? I installed the Windows version and it does not seem to accept OXT, which is the only format we offer. Regards, Matthias Thank you both so much for looking into this. I'm putting Aaron Madlon-Kay, who is the OmegaT project coordinator in Cc. The process was transparent to the user so it's hard to see what was hosted/expected from the site, but from reading the OmegaT code it looks like the site hosted a number of zipped .aff + .dic pairs for each language. https://sourceforge.net/p/omegat/code/ci/master/tree/src/org/omegat/core/spellchecker/DictionaryManager.java OmegaT displayed the language code, the user selected a language and OmegaT downloaded the zip, unzipped it in a dedicated folder and that was it. Marco Skambraks seems to have been working on accessibility in Linux. https://wiki.linuxfoundation.org/accessibility/charter_v1.0 https://www.knopper.net/knoppix-adriane/index-en.html https://www.suse.com/c/the-brains-behind-the-books-part-ix-meike-chabowski/ He seems to be heading this company http://www.ammec.de/ So I guess the belief that we were using an OOo repository was wrong and I'm sorry I bothered you. LibreOffice seems to have a github repository with the unzipped files at https://github.com/LibreOffice/dictionaries Either way, we'll have to implement a new solution. Thank you again for all the work you do on OOo. don't worry, it's nice to see that we could help to see the problem behind the problem. :-) Good luck that you don't have to change much for the solution. Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Am 10.02.22 um 23:08 schrieb Matthias Seidel: Am 10.02.22 um 23:06 schrieb Marcus: Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Did you read the mail?! OK, I'm trying a thought. I don't know which content and how it was on the webpage that is now gone. So, maybe it's rubish. - Download all extensions - Extract the pure dictionary files - Put them on a new webpage - Exchange the old URL to this new one in OmegaT Can this work? BTW: When I look at the SSL certificate for "https://download.services.openoffice.org/; (yes, with HTTPS) I've the feeling that the page was not under our control. Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Am 10.02.22 um 20:12 schrieb Arrigo Marchiori: Hello Carl, On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: Hi Arrigo, On 2/10/22 11:00 AM, Arrigo Marchiori wrote: Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. On Feb 8, 2022, at 6:06 AM, Matthias Seidel wrote: Hi Arrigo, No need to apologize. ;-) But I think, before we begin to think about upgrading serf we need to make sure that AOO41X is able to build successfully on all platforms. Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. What is the architecture of the Mac Mini? % uname -a Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64 Asul has x86-64 JDK's available for Java 7 but that's all. https://www.azul.com/downloads/?version=java-7-lts=macos=jdk I will try that! Please allow me to state I had no intention to ``subvert'' current versions of Java or whatever. For what I understand, Catalina and the XCode versions installed in our Mac mini do not match the reference macOS version and tools for our AOO41X builds, and this is absolutely fine for me, as long as there is someone else who has a system with the ``official'' architecture and is able to use it. I am just trying to have a (whatever version of) macOS building AOO, so that when I commit something, I can test on that architecture as well. And possibly lower the barriers to entry for others. So if any of my edits break the builds on ``official machines'', please let us just revert them. The Java version change was not even committed anywhere. ;-) Thank you for reading through my disclaimer. ;-) Don't worry. I don't see a problem for now. Great that you experiment with a different setup to see how it works then. For the AOO41X release branch we really should try as best and long as possible to keep the setup the same like the past releases to give a (kind of) guarantee that a new release would run also in the same PC environment. So, the next step is to see if the build is also successful with Java 7. But as I see this already in progress . :-) All fine Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: RV: Aranese Spell Checking in libreoffice
Am 10.02.22 um 21:20 schrieb Matthias Seidel:
Anyone else?!
This issue is almost 7 years old now...
unfortunately, I'm not a core developer and I don't know anything about
how to integrate new languages for spell checking.
Marcus
Am 08.02.22 um 19:09 schrieb Peter Kovacs:
On 07.02.22 21:17, Matthias Seidel wrote:
Hi all,
Anyone who can help here?
Currently no clue. sorry.
Regards,
Matthias
Am 30.01.22 um 12:01 schrieb Javier T:
Hi Matthias
I have been looking at the LibreOffice code and the Aranese language
is partially defined.
Is already defined
FILE ./svtools/inc/langtab.hrc
{ NC_("STR_ARR_SVT_LANGUAGE_TABLE", "Aranese") ,
LANGUAGE_USER_OCCITAN_ARANESE },
FILE ./include/i18nlangtag
#define LANGUAGE_USER_OCCITAN_ARANESE LanguageType(0x8082)
Remains to be defined
FILE ./i18nlangtag/source/isolang
{ LANGUAGE_USER_OCCITAN_ARANESE, "oc", "ES", k0 },
FILE ./i18npool/Library_localedata_es.mk
CustomTarget/i18npool/localedata/localedata_oc_ES \
FILE ./i18npool/source/localedata/localedata.cxx
{ "oc_ES", lcl_DATA_ES },
add the file
/i18npool/source/localedata/data/oc_ES.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=147053
De: Matthias Seidel
Enviado: Jueves, 27 de Enero de 2022 23:56
Para: dev@openoffice.apache.org
Asunto: Re: RV: Aranese Spell Checking in libreoffice
Hi Javier,
My impression is that LO did somehow enable Aranese for spellchecking.
They never added your localedata (oc_ES.xml), at least I can't find
it in their code.
I am not sure what to think of that, maybe others here have an opinion?
Regards,
Matthias
Am 23.01.22 um 21:44 schrieb Javier T:
Hi Matthias
I have found the mail that I sent them with the modified file that
they indicated to me.
If I remember correctly this was added by the version of libreoffice
5.1
When you open a new document in libreoffice if you select the text,
it lets you define the language of the text or paragraph and
"Aranese" appears there.
When you want to define a language for the document it does not
appear or I know why.
Attached capture and the mail that I tell you.
Thank you.
[cid:part1.65E0CAD6.8A86E85D@hamburg.de]
De: Javier <mailto:javierd...@hotmail.com>
Enviado: miércoles, 13 de mayo de 2015 22:12
Para: jonathon <mailto:toki.kant...@gmail.com>
Asunto: RE: Aranese Spell Checking
Occitan is composed by these diferent variants.
Alvernès
Bearnès
Creixent
Gascó
Judeoprovençal
Llenguadocià
Montpellerenc (subdialecte)
Niçard
Occità llemosí
Provençal
Vivaroalpí
Aranese is a Gascon dialect spoken in Aran Valley (Spain)
I think that ISO 639 is a realy bad system to define languages an
their dialects.
Nowadays exists 2 spell checkers for libreoffice
oc_FR - I think that is Llenguadocian (but I'm not sure)
gsc_FR - A gascon dialect spell checker.
The correct definition maybe can be
FR_oci_leng
FR_oci_gsc
But this isn't a ISO 639 code. Really I don't have a good solution
for that and I'm not sure what are the diferences between the
diferent dialects.
If you defines a code OCI_fr you need to update the oc_FR spell
checker.
In my case I prefer use oc_ES to standarize with the old
aplications. But I'm not sure what is the best choice to define it
in libreoffice.
You can decide at your own criterion, oc_ES or oci_ES. Really is not
a problem for me, because Aran Valley is the only region in Spain
where people speaks occitan. I need just a code.
I send you the locale file.
Thanks
From: toki.kant...@gmail.com<mailto:toki.kant...@gmail.com>
Date: Tue, 28 Apr 2015 19:00:18 +
To: javierd...@hotmail.com<mailto:javierd...@hotmail.com>
Subject: Aranese Spell Checking
Javier:
I saw your request for support of Aranese in Apache OpenOffice.
I don't how difference Aranese is from Gascon, nor how different
either
of those are from Occitan.
The primary issue is ISO 639-3 Code OCI, which is for Occitan, and the
various dialects. A spell checker for Aranese will conflict with a
spell
checker for Occitan.
(I am saying that, based on working with spell checkers for various
languages of Southern Africa.)
LibreOffice currently supports Occitan as a language/local.
My suggestion is creating OCI_fr, OCI_ad, OCI_es, and maybe OCI_it as
locales. Get together with users of other dialects/languages that are
classified under OCI, and work up something that is acceptable to
everybody, but still allows them to use the grammar and spell
checkers.
Go to http://www.it46.se/localegen/select_lang.php to create the
locales.
Then either go to https://bugs.documentfoundation.org/buglist.cgi and
file a bug requesting creation of the respective locales, or email the
xml, and I'll do that.
The _only_ reason I'm not creat
Re: AOO available in the Microsoft Store app (background information)
Am 15.01.22 um 15:05 schrieb Matthias Seidel: Since there were no public information from me until this "project" was successfully launched on the last minute in parallel with Windows 11, I want to give some details (now that I have time): Microsoft introduced the possibility to publish "classic" Windows programs via their Microsoft Store app. This was a new feature for Windows 11 and is now also available for some time on Windows 10. So what you download and install via Microsoft Store app is an unmodified binary, identical to what we distribute via SourceForge. The only requirement from Microsoft were to install AOO totally "silent". This needed some parameters [1] and a minor change in the installation of the MSVC runtimes [2]. Downloads point to the Apache Download server [3] because we had issues with the SourceForge mirrors. After all, this was technically no big problem but required some "struggle" with the Microsoft Developer Network. My thanks go to Santhosh Panchapagesam from Microsoft and to Ross Gardler (ASF) who made the initial contact. [1] https://svn.apache.org/repos/asf/openoffice/devtools/Microsoft%20Store/Parameters.txt [2] https://github.com/apache/openoffice/commit/908cc4a92408d9aa3bc9d002845a580a2175543f [3] https://downloads.apache.org/openoffice/4.1.11/binaries/ thanks for the background information. Let's see if we can see or feel one day the increased downloads. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Happy new year!
Am 15.01.22 um 00:45 schrieb Keith N. McKenna: On Tue, 04 Jan 2022 17:04:40 +0100, Matthias Seidel wrote: I almost forgot to wish everyone here a happy new year 2022! Happy New Year to all. happy new year also to you. :-) What is your new years resolution? Mine is still 1366x768! ;-) Mine is to return to a more active status with the project and again start moving the User Guides along. Do you have the plan to public them a browsable webpages or PDF files? Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Project Planning page on cwiki
Am 07.01.22 um 12:32 schrieb Arrigo Marchiori:
On Wed, Jan 05, 2022 at 07:03:47PM +0100, Marcus wrote:
Am 05.01.22 um 10:09 schrieb Arrigo Marchiori:
On Sat, Nov 06, 2021 at 11:57:14AM +0100, Marcus wrote:
Am 24.10.21 um 16:27 schrieb Peter Kovacs:
On 24.10.21 16:13, Arrigo Marchiori wrote:
this may have been raised many other times... but why do we keep
publishing release notes under the "Project Planning" cwiki page [1]
when that page starts with a big warning that is only for the
incubation phase? :-)
I think there are a lot of old an new stuff intermixed. We have left the
existing stuff as is and added the new stuff.
My humble suggestion, given the fact that the section contains updated
information, is to create a subpage "Incubation" and then move under
it all subpages related to the incubation period.
I am available to do this work, if no one else has either better ideas
or good reasons not to do so.
Sounds like an improvement. I have no objection. :)
[1]:
https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Planning
indeed. In the meantime outdated and it could be improved.
As a first step I've deleted the warning.
When you have some concret points that should be improved just tell here or
start in Confluence and we can talk about it.
I suggest we create an "Incubation" subpage of "Project planning" and
move ("reparent"?) into there:
sounds good. We should add a short explaintion text, so tht everyone knows
what can be expected on this and all subpages.
- Site-PPMC-Plan
- Site-QA-Plan
- Site-Dev-Plan
- IP_Clearance
- Assigned issues to former Oracle employee
- ...all other pages explicitly referring to the OpenOffice.org migration
I understand these are somewhat major changes so I want to make sure
no one has objections before starting to implement them.
Thanks for asking. If you need help in or with Confluence please don't
hesitate to ask.
Thank you. I am done now.
The "older" pages are now under
https://cwiki.apache.org/confluence/display/OOOUSERS/Incubation
oh, that was fast.
I've add a sentence that the Incubation phase is already finished.
Marcus
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Project Planning page on cwiki
Am 05.01.22 um 10:09 schrieb Arrigo Marchiori:
On Sat, Nov 06, 2021 at 11:57:14AM +0100, Marcus wrote:
Am 24.10.21 um 16:27 schrieb Peter Kovacs:
On 24.10.21 16:13, Arrigo Marchiori wrote:
this may have been raised many other times... but why do we keep
publishing release notes under the "Project Planning" cwiki page [1]
when that page starts with a big warning that is only for the
incubation phase? :-)
I think there are a lot of old an new stuff intermixed. We have left the
existing stuff as is and added the new stuff.
My humble suggestion, given the fact that the section contains updated
information, is to create a subpage "Incubation" and then move under
it all subpages related to the incubation period.
I am available to do this work, if no one else has either better ideas
or good reasons not to do so.
Sounds like an improvement. I have no objection. :)
[1]:
https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Planning
indeed. In the meantime outdated and it could be improved.
As a first step I've deleted the warning.
When you have some concret points that should be improved just tell here or
start in Confluence and we can talk about it.
I suggest we create an "Incubation" subpage of "Project planning" and
move ("reparent"?) into there:
sounds good. We should add a short explaintion text, so tht everyone
knows what can be expected on this and all subpages.
- Site-PPMC-Plan
- Site-QA-Plan
- Site-Dev-Plan
- IP_Clearance
- Assigned issues to former Oracle employee
- ...all other pages explicitly referring to the OpenOffice.org migration
I understand these are somewhat major changes so I want to make sure
no one has objections before starting to implement them.
Thanks for asking. If you need help in or with Confluence please don't
hesitate to ask.
Marcus
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Marketing > Referenzkunden
Hi Martin, happy new year. :-) Thanks for your mail. I've add an entry for you / your company. Please check on the test webpage if all is correct or something has to / should be changed: https://openoffice-org.staged.apache.org/de/marketing/referenzkunden.html Thanks Marcus Am 03.01.22 um 15:06 schrieb Martin Bauer: If you like, you can add our statement to the list https://openoffice-org.staged.apache.org/de/marketing/referenzkunden.html Als Content Marketing Agentur nutzen wir OpenOffice für die Erstellung sämtlicher Texte. Danke für die super Funktionalitäten! www.coco-content-marketing.de - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Happy new year!
Am 04.01.22 um 17:04 schrieb Matthias Seidel: I almost forgot to wish everyone here a happy new year 2022! I also wish all of us a happy, healthy and peaceful new year. What is your new years resolution? Mine is still 1366x768! ;-) Both monitor are still running with 1920 x 1080. Not really new. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Translate certificate expired
Am 06.12.21 um 08:21 schrieb Arrigo Marchiori: On Fri, Dec 03, 2021 at 09:00:27PM +0100, Arrigo Marchiori wrote: On Fri, Dec 03, 2021 at 05:33:51PM +0100, Matthias Seidel wrote: I don't have the time to do it. Anyone else? https://issues.apache.org/jira/browse/INFRA-22581 I was told I should contact sysad...@openoffice.apache.org. It is in Cc to this message. Who reads that mailbox? only project internal people. So IMHO it doesn't make sense. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Translate certificate expired
Am 02.12.21 um 13:34 schrieb Matthias Seidel: Our certificate on: https://translate.apache.org/projects/ expired on 28. November 2021. can we do something to renew it? I don't think so, maybe a task for the Infra team? Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice available in the Microsoft Store on Windows 10
Am 22.11.21 um 17:31 schrieb Matthias Seidel: Am 19.11.21 um 00:53 schrieb Marcus: Am 18.11.21 um 21:51 schrieb Matthias Seidel: Apache OpenOffice has already been available in the new Microsoft Store on Windows 11 since October. With the latest App update, the new store is also coming to Windows 10. Users can now install the latest OpenOffice version with a single click! The Store Listings are localized in English, German, Italian, Polish and Portuguese. Feel free to contact me if you want to add more languages or if you have any questions. great news. :-) Then the new version was worth it to release at this point of time - to be ready for the Win 10 store. Yes, I have now tested the store on every Windows PC I got my hands on. Absolutely no problems so far... The next task will be to get rid of all these unofficial OpenOffice offers. ;-) Do we want to make an announcement? I would say let's involve someone who has hopefully more knowledge about such kind of things. Michael, do you have time to speak about it? Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice available in the Microsoft Store on Windows 10
Am 18.11.21 um 21:51 schrieb Matthias Seidel: Apache OpenOffice has already been available in the new Microsoft Store on Windows 11 since October. With the latest App update, the new store is also coming to Windows 10. Users can now install the latest OpenOffice version with a single click! The Store Listings are localized in English, German, Italian, Polish and Portuguese. Feel free to contact me if you want to add more languages or if you have any questions. great news. :-) Then the new version was worth it to release at this point of time - to be ready for the Win 10 store. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 10.11.21 um 11:36 schrieb Dave Barton: On 09/11/2021 23:48, Marcus wrote: However, I'm curious to know what you mean with "... why moderators should hold any more of an exclusive or covert role within the ASF ..." and why you think there is something secret? The answer to that "baited" question is: Everybody with any kind of role within the ASF can be identified, EXCEPT MODERATORS, Unidentified = Hidden = Secret. a last attempt: https://whimsy.apache.org/roster/committee/openoffice#mail After login you can see all mailing lists with their moderators. Marcus On 10/11/2021 04:25, Dave Fisher wrote That’s ok as long as it is made clear NOT to ever contact moderator directly about the mailing list>>> I hope you see the conundrum being presented. The inbox of all moderators receive posts to owner-, which effectively is direct contact, but if it is a matter of concern, let's leave the status quo. I really would like to end my involvement in this thread now. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 10.11.21 um 05:25 schrieb Dave Fisher: On Nov 9, 2021, at 3:48 PM, Marcus wrote: Am 07.11.21 um 21:18 schrieb Dave: On 07/11/2021 19:42, Dave Fisher wrote: Sorry to put it this way Dave, but this is the same answer that I have had received from you and other PMC members previously. If your statement is true, then we and the ASF have a very serious and extreme privacy challenge here: https://people.apache.org/committers-by-project.html#openoffice In my view anyone who "steps up to he plate" for ANY role in an OPEN source project should not have any concerns about being identified a contributor and their role that project. I am not ashamed of being identified as a (very small, relatively unimportant) contributor to the AOO project and I suggest that ANYONE who is wishes to adopt this underhanded, secretive approach, should step away from the project. I agree about every role except moderation. I moderate 27 different Apache Mailing Lists only one of which is an AOO list. If the community wishes to disclose all of the moderators that would be an acceptable outcome. I read your words, which are the same as you and other PMC members have previously stated, but I still do not read any explanation as to the rational of why moderators should hold any more of an exclusive or covert role within the ASF. Let's just put this down to my natural stupidity and end this thread, because there is nothing to be gained by perusing the subject. normally I would agree. However, I'm curious to know what you mean with "... why moderators should hold any more of an exclusive or covert role within the ASF ..." and why you think there is something secret? A moderator is just a committer as you and me. Some are also a PMC member or maybe also supporter/committer/member of other ASF projects. But thats it. I volunteer to create a Wiki page to show who is moderating which mailing list(s) - if the community think it has a value. That’s ok as long as it is made clear NOT to ever contact moderators directly about the mailing list. sure, that and ... I hope you see the conundrum being presented. ... I won't add any mail address. Names only. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 07.11.21 um 21:18 schrieb Dave: On 07/11/2021 19:42, Dave Fisher wrote: Sorry to put it this way Dave, but this is the same answer that I have had received from you and other PMC members previously. If your statement is true, then we and the ASF have a very serious and extreme privacy challenge here: https://people.apache.org/committers-by-project.html#openoffice In my view anyone who "steps up to he plate" for ANY role in an OPEN source project should not have any concerns about being identified a contributor and their role that project. I am not ashamed of being identified as a (very small, relatively unimportant) contributor to the AOO project and I suggest that ANYONE who is wishes to adopt this underhanded, secretive approach, should step away from the project. I agree about every role except moderation. I moderate 27 different Apache Mailing Lists only one of which is an AOO list. If the community wishes to disclose all of the moderators that would be an acceptable outcome. I read your words, which are the same as you and other PMC members have previously stated, but I still do not read any explanation as to the rational of why moderators should hold any more of an exclusive or covert role within the ASF. Let's just put this down to my natural stupidity and end this thread, because there is nothing to be gained by perusing the subject. normally I would agree. However, I'm curious to know what you mean with "... why moderators should hold any more of an exclusive or covert role within the ASF ..." and why you think there is something secret? A moderator is just a committer as you and me. Some are also a PMC member or maybe also supporter/committer/member of other ASF projects. But thats it. I volunteer to create a Wiki page to show who is moderating which mailing list(s) - if the community think it has a value. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl
Am 09.11.21 um 22:31 schrieb Matthias Seidel: Am 09.11.21 um 21:50 schrieb Jim Jagielski: I've recently folded in openssl-1.1 to trunk and all branches, but this gets us in a corner. To support this version of openssl, we need to upgrade Serf. This means that we need to also update apr and apr-util as well as include a requirement that the build server also as SCons installed. This could be problematic, esp for those older, legacy systems that we want to continue to support. One alternative is to simply drop Serf completely; we already require curl, and we could start using curl for the WebDav functionality instead of it being the (sole, afaict) reason for Serf. +1 simply for reducing the dependencies on those various libraries. If it can be done with curl we should try it. yes, please try it. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 09.11.21 um 13:13 schrieb Matthias Seidel: I am SO sick of these toxic threads of a certain person... I don't want to read his conspiracy theories anymore I also think I can say what I want. It's always understood differently and not trying to think about any attempt to change it. Let's stop this and go back to work and move on with the project instead of harming it. Good point. :-) Marcus Am 09.11.21 um 10:58 schrieb Dr. Michael Stehmann: Hello, Am 08.11.21 um 20:13 schrieb Jörg Schmidt: I'm afraid, Marcus, we have a problem of understanding what "all" means. For me, this is the community and not a few privileged people who are in PMC. Maybe some may see it as a privilege. I see it as a (little) burden I bear voluntarily. The PMC is not any kind of peerage or order. It's a necessary working group. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 08.11.21 um 20:13 schrieb Jörg Schmidt: Hello Marcus, -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Monday, November 08, 2021 5:57 PM To: dev@openoffice.apache.org Subject: Re: Who moderates users...@openoffice.apache.org? Am 08.11.21 um 07:33 schrieb Jörg Schmidt: -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Sunday, November 07, 2021 7:48 PM To: dev@openoffice.apache.org Subject: Re: Who moderates users...@openoffice.apache.org? when you want to talk about this with names then I invite you to discuss this via private@. with pleasure, but not on private@, but by PM. sorry but please write to private@, so that we *all* can have the same information and can discuss it. I'm afraid, Marcus, we have a problem of understanding what "all" means. For me, this is the community and not a few privileged people who are in PMC. I don't know in which circle you see a PMC. It's not a club of old men or a secret organization like Illuminati or any other voodoo. Please see the mail from Dave Fisher he posted on Nov, 07th. Why I no longer want to write to private@, namely because my experiences with requests to private@ are negative, I told you by PM. For me, the greatest possible openness has always been a 'trademark' of the ASF, but with AOO I experience that the PMC tries to build up more insider knowledge than is necessary. Knowledge that should actually be known and discussed within the entire community. Sorry I don't know what you mean with "inside knowledge". Some tasks have to be handled by the PMC only (e.g., people issues, binding release voting, trademark) . This is the rule that comes from the ASF itself. So please excuse me, but I am not interested in secret talks with the PMC. And I've no interest to talk to you in private about topic(s) that affects actually more people. Or what do you expect from me? We both talk and I take it further to someone else, then further and further? I hope that this is not the thing you have in mind. Finally: When you have a topic to discuss that affects the PMC, then you have to talk with the PMC. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 08.11.21 um 07:33 schrieb Jörg Schmidt: -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Sunday, November 07, 2021 7:48 PM To: dev@openoffice.apache.org Subject: Re: Who moderates users...@openoffice.apache.org? when you want to talk about this with names then I invite you to discuss this via private@. with pleasure, but not on private@, but by PM. sorry but please write to private@, so that we *all* can have the same information and can discuss it. PS: I'm writing this here, so that you know why I don't answer your PM. Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 07.11.21 um 13:38 schrieb Jörg Schmidt: -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Sunday, November 07, 2021 12:22 PM To: dev@openoffice.apache.org Subject: Re: Who moderates users...@openoffice.apache.org? I wonder who you want to delete from the list *). It is the normal way that over the time a person earns merit and therefor gets the committer - and maybe also PMC - status when the contributions are good and qualifies for it. Why do we not see this way, but have to realise that some people work actively for OpenOffice for many, many years and are denied membership in the PMC, while other new project members are promoted to the PMC within a few months? when you want to talk about this with names then I invite you to discuss this via private@. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 06.11.21 um 22:34 schrieb Dave:
On 06/11/2021 19:26, Dave Fisher wrote:
On Nov 6, 2021, at 3:45 AM, Dave wrote:
On 06/11/2021 10:30, Marcus wrote:
Am 06.11.21 um 10:16 schrieb Jörg Schmidt:
following Dave's advice {1], I contacted one moderator of the list
users...@openoffice.apache.org I know and was promised that spam
emails would be rejected in future - unfortunately, however, no action
was taken, because there is spam again from the sender on the list
that I had specifically pointed out.
Can someone please tell me who moderates this list? I would then try
to write to another moderator and ask for help.
[1]
see the thread "How to delete a wrong email list subscription?"
I can see that Michael and Dave could be moderators of the list. But
maybe it's a bit outdated.
I have been a moderator for some of our English lists since the
project's poddling days. Unfortunately, my knowledge of German is not
very good, so I would not be of much help for the German users list.
I have asked before why the PMC does not wish moderators to be
identified, but never received any rational answer.
Providing a clear identification of moderators would be a privacy challenge.
The mechanism to contact moderators is to send an email to
users-de-own...@openoffice.apache.org
As a separate issue, the above mentioned link is seriously in need of
review and update, because many of the people mentioned are no longer
active in, or have resigned from the positions listed.
I wonder who you want to delete from the list *).
It is the normal way that over the time a person earns merit and
therefor gets the committer - and maybe also PMC - status when the
contributions are good and qualifies for it.
However, merit lies with the individual and does not expire. It's not
normal to remove this status just because of inactivity [1].
Also one person listed regrettably passed away last month.
OK, here you are right. However, this page is not under our control and
has to be updated by the ASF.
[1] https://infra.apache.org/committers.html
see "Is there a set term for acting as a Committer? Will I have to be
elected again?"
Marcus
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 06.11.21 um 21:11 schrieb Dr. Michael Stehmann: Am 06.11.21 um 20:26 schrieb Dave Fisher: The mechanism to contact moderators is to send an email to users-de-own...@openoffice.apache.org I've gotten one from Marcus, but it was really empty. I've just tried to find out who the moderators of the list are. It was not working as I thought. ;-) Then I found the info via Whimsy. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 06.11.21 um 12:36 schrieb Dr. Michael Stehmann:
I'm one of the moderators of users-de. IMO I'm not the only one.
I have gotten some of the spam postings in the past and rejected them.
But it seems so, I got not all.
There should be a ban for some email addresses, but I'm busy at the
moment. Because it's not trivial it would take some time. There was no
need for a ban in past. So it would be the first time for me to do such
a job.
I've tried to unsubscribe the mail address. But maybe it was not
successful as I'm not a moderator for that list.
BTW:
It's the default contact address from a German bank. IMHO it is obvious
that this is not really used for sending / getting mails about OpenOffice.
Marcus
Am 06.11.21 um 10:16 schrieb Jörg Schmidt:
following Dave's advice {1], I contacted one moderator of the list
users...@openoffice.apache.org I know and was promised that spam
emails would be rejected in future - unfortunately, however, no action
was taken, because there is spam again from the sender on the list
that I had specifically pointed out.
Can someone please tell me who moderates this list? I would then try
to write to another moderator and ask for help.
[1]
see the thread "How to delete a wrong email list subscription?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Project Planning page on cwiki
Am 24.10.21 um 16:27 schrieb Peter Kovacs: On 24.10.21 16:13, Arrigo Marchiori wrote: this may have been raised many other times... but why do we keep publishing release notes under the "Project Planning" cwiki page [1] when that page starts with a big warning that is only for the incubation phase? :-) I think there are a lot of old an new stuff intermixed. We have left the existing stuff as is and added the new stuff. My humble suggestion, given the fact that the section contains updated information, is to create a subpage "Incubation" and then move under it all subpages related to the incubation period. I am available to do this work, if no one else has either better ideas or good reasons not to do so. Sounds like an improvement. I have no objection. :) [1]: https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Planning indeed. In the meantime outdated and it could be improved. As a first step I've deleted the warning. When you have some concret points that should be improved just tell here or start in Confluence and we can talk about it. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Who moderates users...@openoffice.apache.org?
Am 06.11.21 um 10:16 schrieb Jörg Schmidt:
following Dave's advice {1], I contacted one moderator of the list
users...@openoffice.apache.org I know and was promised that spam emails would
be rejected in future - unfortunately, however, no action was taken, because
there is spam again from the sender on the list that I had specifically pointed
out.
Can someone please tell me who moderates this list? I would then try to write
to another moderator and ask for help.
[1]
see the thread "How to delete a wrong email list subscription?"
I can see that Michael and Dave could be moderators of the list. But
maybe it's a bit outdated.
Marcus
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Registration on Bugzilla
Am 29.10.21 um 15:10 schrieb Bidouille: - Mail original - but it's not your mail address I would send the respone to. I'm confused. Just to have a response sample to illustrate the tutorial. A delay that a human simply needs. He is doing the works when he is doing it. ;-) Again, it's just to give a correct information in the tutorial Some end users are rushed ;-) ah OK, but then it would be better to just ask what the process looks like and what will happen for the user. Here is the process: When a request is coming to sysadmin@ we check for which tool the request is (the mail address is also used for others) and which name and mail address. If this not clear we ask and wait for the answer. So, when users wish to have an acount for BZ, they should write: - that it is for Bugzilla - which mail address should be used as login name - and their real name When we have the information, we create a new BZ account and give a response on sysadmin@, so all admins knows. The account details incl. the password will be send to the user only. And with the request to change it with first login. That's it. I hope this helps. :-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Registration on Bugzilla
Am 29.10.21 um 13:45 schrieb Bidouille: We have received a request without any name but with "club.acsi" in the mail address. Is this the user you are asking for? Yes it was a test Could you send me a response? On french forum, we have a tutorial to submit issues on Bugzilla. I must to update it with new informations but it's not your mail address I would send the respone to. I'm confused. And they are sometimes not the fastest workers. ;-) A human process means which delay to enable an account? A delay that a human simply needs. He is doing the works when he is doing it. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Registration on Bugzilla
Am 29.10.21 um 09:22 schrieb Bidouille: Account registration has been disabled for spamming cause In https://bz.apache.org/ooo/createaccount.cgi I read that: "New accounts must be created by an administrator. The maintainer is aoo-bugzilla-ad...@apache.org" But if I send an e-mail, I get an automated response with: "To request an account please send an email to sysad...@openoffice.apache.org" I send a new e-mail to this address but no response since 24hrs. This registration process is it correct? yes, but it's not automated. So, a humans have to create the account. And they are sometimes not the fastest workers. ;-) We have received a request without any name but with "club.acsi" in the mail address. Is this the user you are asking for? Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Happy Anniversary (9 years as TLP)
Am 17.10.21 um 12:04 schrieb Matthias Seidel: On this day, 9 years ago Apache OpenOffice became an Apache Top Level Project (TLP). Thanks to all the volunteers who made that happen and spent their private time since then! I also want to say thank you to all users, committers, supports, friends for improving OpenOffice in so many ways. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Am 18.10.21 um 08:07 schrieb Arrigo Marchiori: replying to myself as a correction. On Thu, Oct 14, 2021 at 07:08:25PM +0200, Arrigo Marchiori wrote: [...] Those pages should be generated by Autodoc, for what I understand. Are there any scripts that do this? Or any policies on how and when to update the API documentation? For example, I would suggest that each new release would be a good time to update the API. I should have written "API documentation" instead of API. I apologize. ah, that is changing the game. ;-) I agree that changing the API is a ``big thing'', that we shall be very careful, and I understand Jörg's and Marcus' concern while reading my paragraph above! I suggest we update the _documentation_ whenever possible because IMHO that can be helpful for developers. The details can and should be discussed when it comes to updates. But in general I agree. I hope I could clarify my proposal now. Yes, thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Am 15.10.21 um 10:15 schrieb Jörg Schmidt: -Original Message- From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] Sent: Thursday, October 14, 2021 7:08 PM To: dev@openoffice.apache.org Subject: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] the API doc is (somehow) part of the website. And what you are looking for is maybe here: https://github.com/apache/openoffice-org/blob/main/part2/conte nt/api/docs/common/ref/com/sun/star/office/module-ix.html Thank you! That is what I meant. Those pages should be generated by Autodoc, for what I understand. Are there any scripts that do this? Or any policies on how and when to update the API documentation? For example, I would suggest that each new release would be a good time to update the API. please not really for each release. We should provide our users with a stable API at least for the 4.1.x release branch. Maybe also for 4.x.y. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Accessing the comment object (annotation) in Draw/Impress via API
Am 12.10.21 um 22:06 schrieb Arrigo Marchiori: On Mon, Oct 11, 2021 at 04:53:56PM +0200, Czesław Wolański wrote: Recently a user on the English forum inquired how one can change the font size in a comment box in Draw [1]. He was given the obvious workaround tip and then the discussion started on how to access the comment object via API. Though the AOO's IDL reference says nothing in this regard, it turned out the annotation can be handled programmatically (at least in OpenOffice Basic). Hence my questions: 1. Is the API in terms of annotations' handling fully operational? 2. Should the relevant AOO's IDL reference be amended? see: https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html I guess that the "API documentation" is extracted from autodoc or something like that... how can we update it on our web site? Are there any scripts or procedures? Thank you in advance for any pointers, the API doc is (somehow) part of the website. And what you are looking for is maybe here: https://github.com/apache/openoffice-org/blob/main/part2/content/api/docs/common/ref/com/sun/star/office/module-ix.html HTH Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Packages from Unofficial Apache OO Debian repository updated to version 4.1.11
Am 10.10.21 um 16:22 schrieb Marcelo Santana: On Sun, 10 Oct 2021 10:13:13 +0200, Marcus wrote: Am 10.10.21 um 01:08 schrieb Marcelo Santana: [...] BTW: Is there anything we can or should improve with our DEB files? I'm wondering of the reason for a second repository. Well, as far as I've seen, at least to have it in the Debian repositories, there are many things but I don't have time to do it according to the DFSG guidelines. So, I've been maintaining the repository (almost 10 years now) to make it easier for sysadmins to maintain their groups of desktops updated. Remember, it's simple to update your AOO just downloading the new version and typing "dpkg -i *.deb", but it's more complicated when you have one group of desktops to be updated. I understand. Thanks for your explaination. Anyway, if the fact of having a second repository bothers the Apache OpenOffice project, I have no problem ending it up. No, that was not the intention behind my question. I just asked of curiosity. Not more. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Packages from Unofficial Apache OO Debian repository updated to version 4.1.11
Am 10.10.21 um 01:08 schrieb Marcelo Santana: The unofficial Apache OO Debian repository was updated and from now it provides the version 4.1.11 of Apache Openoffice with all available languages. All information needed for new installation or upgrade are available in the README file[1]. [1]https://sourceforge.net/projects/apacheoo-deb/files/debian/ thanks for your service. Please correct a link on top of the "REAME.md" file. "https://www.openoffice.org/download/other.html; is no longer existing. Please refer always and only to "https://www.openoffice.org/download/;. BTW: Is there anything we can or should improve with our DEB files? I'm wondering of the reason for a second repository. Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release announce to Apache moderated due to source link
Am 08.10.21 um 19:18 schrieb Dave Fisher: On Oct 8, 2021, at 10:14 AM, Matthias Seidel wrote: I asked Infra to distribute our source packages via ASF mirrors, but that ticket was closed today: https://issues.apache.org/jira/browse/INFRA-21497?focusedCommentId=17338060=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17338060 It’s good because it is on the cdn. https://www.apache.org/dyn/closer.lua/openoffice/4.1.11/source/ Gave me https://dlcdn.apache.org/openoffice/4.1.11/source/ which is the cdn. “Mirror" We are good. nice when it is working now. Last time it was not. @Carl: When you use the "closer.lua" link in the mail then it should work. Marcus Am 08.10.21 um 19:04 schrieb Dave Fisher: That will probably be kicked back too On Oct 8, 2021, at 9:57 AM, Carl Marcum wrote: My Apache announce email got kicked back due to the link to the source not using the mirror system. "Source releases MUST use the ASF mirror system." I used: https://openoffice.apache.org/downloads.html So I guess I need to use: https://downloads.apache.org/openoffice/4.1.11/source/ Our download page is wrong. See https://infra.apache.org/release-download-pages.html#download-page I'll send a new one in a while. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release announce to Apache moderated due to source link
Am 08.10.21 um 19:04 schrieb Dave Fisher: That will probably be kicked back too On Oct 8, 2021, at 9:57 AM, Carl Marcum wrote: My Apache announce email got kicked back due to the link to the source not using the mirror system. "Source releases MUST use the ASF mirror system." I used: https://openoffice.apache.org/downloads.html So I guess I need to use: https://downloads.apache.org/openoffice/4.1.11/source/ Our download page is wrong. See https://infra.apache.org/release-download-pages.html#download-page we use already a ASF server. But it has to be also the download system. I had the same problem with the AOO 4.1.10 release. However, it's not a big loss when the mail is not accepted. So, don't waste any time for this. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Open Office Suggestion
Adding John as he is not subscribed to this mailing list. Am 07.10.21 um 21:12 schrieb Bidouille: Feature already reported: https://bz.apache.org/ooo/show_bug.cgi?id=10864 You can vote for this. - Mail original - De: "Heroes Outreach Program Administrator" À: dev@openoffice.apache.org Envoyé: Jeudi 7 Octobre 2021 16:19:56 Objet: Open Office Suggestion I use OpenOffice Calc to track my personal budget, as well as items and budgets for our nonprofit, Heroes Outreach Program. There is one feature that I would find very useful and that would save me a lot of time. When selecting the cell background color or font color, I would like it if when you clicked on the button that it would color the box in the last color selected rather than having to go into the drop down and selecting the same color cell after cell. This function is available in Microsoft Excel and I find it very useful and would find it just as useful in Open Office Calc. I prefer to use open source software rather than feeding Microsoft. Thank you for your time. -- John L. Morlock - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 20:55 schrieb Marcus: Am 06.10.21 um 20:17 schrieb Marcus: Am 06.10.21 um 20:11 schrieb Carl Marcum: On 10/6/21 1:41 PM, Marcus wrote: Am 06.10.21 um 19:37 schrieb Carl Marcum: On 10/6/21 1:15 PM, Marcus wrote: Am 06.10.21 um 19:06 schrieb Carl Marcum: On 10/6/21 12:37 PM, Marcus wrote: Am 06.10.21 um 18:31 schrieb Matthias Seidel: Am 06.10.21 um 18:26 schrieb Dave Fisher: On Oct 6, 2021, at 9:22 AM, Matthias Seidel wrote: Am 06.10.21 um 18:19 schrieb Dave Fisher: On Oct 6, 2021, at 8:16 AM, Matthias Seidel wrote: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! I don’t see the files here: https://sourceforge.net/projects/openofficeorg.mirror/files/ The directory is staged (invisible) until we do the release. Great. Just checking. BTW - What time will the “release” happen? Today or tomorrow morning? I need to ask security to publish the two CVEs and plan to be out this afternoon and evening. I would prefer later today (European time). Marcus, what do you think? I don't care. My preparations are nearly finished. I can commit the changes whenever we want. :-) However, more important is that the blog announcement and release notes are also ready. I can take care for the release notes. I filled in some improvement bullet points but feel free to add/change as needed. I've finished (so far) the release notes. You can copy & paste the bugfixes and enhancements from there: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.11+Release+Notes We have these two that are already public and could be listed. CVE-2021-33035 Buffer overflow from a crafted DBF file CVE-2021-40439 Billion Laughs CVE 2021-30245 - Code execution in Apache OpenOffice via non-http(s) schemes in Hyperlinks We fixed in 4.1.10 although a little to aggressively and improved the handling in this one. Should we list it again? please reload the page. I've updated exactly this section. ;-) I'm about to send the announce email. Do you want to pull the draft notice down from the release notes now? I've published the blog great, then I'll change the blue headlines to the new announcement. short status: Main download page - updated Blue headline - updated Default download on sourceforge - changed Project page - updated Release notes - done Blog post with announcment - done Localized download pages - coming next Mail with announcement - coming next new status: Localized download pages - done Mail with AOO announcement - done Mail with Apache announcement - coming next Press Release - coming next Security texts - coming next Marcus I saw the date for Patricia joining the project was missing. I searched the archives and came up with a this post as about the oldest I could find so I used that year. https://lists.apache.org/thread.html/9f5c7bbe9c2e46b800ad1dda5a1068a64ff26ab830ff9a9134c3b398%401446081722%40%3Cdev.openoffice.apache.org%3E Ah, great. And of cause the security texts and webpages. I can also take over this but need the texts. Dave, can you please help with the texts? Carl, can you please finalize the blog post? If were good with the text I'm ready to publish. Just say the word. Also on the announce email draft I'm ready if nobody wants a change.. What time are we thinking? Let's say at 20:00 CET which is in ~ 45 minutes. Is this OK for all? Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 20:17 schrieb Marcus: Am 06.10.21 um 20:11 schrieb Carl Marcum: On 10/6/21 1:41 PM, Marcus wrote: Am 06.10.21 um 19:37 schrieb Carl Marcum: On 10/6/21 1:15 PM, Marcus wrote: Am 06.10.21 um 19:06 schrieb Carl Marcum: On 10/6/21 12:37 PM, Marcus wrote: Am 06.10.21 um 18:31 schrieb Matthias Seidel: Am 06.10.21 um 18:26 schrieb Dave Fisher: On Oct 6, 2021, at 9:22 AM, Matthias Seidel wrote: Am 06.10.21 um 18:19 schrieb Dave Fisher: On Oct 6, 2021, at 8:16 AM, Matthias Seidel wrote: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! I don’t see the files here: https://sourceforge.net/projects/openofficeorg.mirror/files/ The directory is staged (invisible) until we do the release. Great. Just checking. BTW - What time will the “release” happen? Today or tomorrow morning? I need to ask security to publish the two CVEs and plan to be out this afternoon and evening. I would prefer later today (European time). Marcus, what do you think? I don't care. My preparations are nearly finished. I can commit the changes whenever we want. :-) However, more important is that the blog announcement and release notes are also ready. I can take care for the release notes. I filled in some improvement bullet points but feel free to add/change as needed. I've finished (so far) the release notes. You can copy & paste the bugfixes and enhancements from there: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.11+Release+Notes We have these two that are already public and could be listed. CVE-2021-33035 Buffer overflow from a crafted DBF file CVE-2021-40439 Billion Laughs CVE 2021-30245 - Code execution in Apache OpenOffice via non-http(s) schemes in Hyperlinks We fixed in 4.1.10 although a little to aggressively and improved the handling in this one. Should we list it again? please reload the page. I've updated exactly this section. ;-) I'm about to send the announce email. Do you want to pull the draft notice down from the release notes now? I've published the blog great, then I'll change the blue headlines to the new announcement. short status: Main download page - updated Blue headline - updated Default download on sourceforge - changed Project page - updated Release notes - done Blog post with announcment - done Localized download pages - coming next Mail with announcement - coming next Marcus I saw the date for Patricia joining the project was missing. I searched the archives and came up with a this post as about the oldest I could find so I used that year. https://lists.apache.org/thread.html/9f5c7bbe9c2e46b800ad1dda5a1068a64ff26ab830ff9a9134c3b398%401446081722%40%3Cdev.openoffice.apache.org%3E Ah, great. And of cause the security texts and webpages. I can also take over this but need the texts. Dave, can you please help with the texts? Carl, can you please finalize the blog post? If were good with the text I'm ready to publish. Just say the word. Also on the announce email draft I'm ready if nobody wants a change.. What time are we thinking? Let's say at 20:00 CET which is in ~ 45 minutes. Is this OK for all? Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice-org Staging Site Published
Am 06.10.21 um 20:23 schrieb Dave Fisher: This build has strange issues and inserted an extra layer of content. Do not publish. it is already published. But I cannot see any extra content. Can you point me to what you see? Thanks Marcus On Oct 6, 2021, at 11:17 AM, Apache Jenkins Server wrote: OpenOffice » OpenOffice-org-Staging-Site-Build - Build # 494 - Successful: Check console output at https://ci-builds.apache.org/job/OpenOffice/job/OpenOffice-org-Staging-Site-Build/494/ to view the results. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 20:11 schrieb Carl Marcum: On 10/6/21 1:41 PM, Marcus wrote: Am 06.10.21 um 19:37 schrieb Carl Marcum: On 10/6/21 1:15 PM, Marcus wrote: Am 06.10.21 um 19:06 schrieb Carl Marcum: On 10/6/21 12:37 PM, Marcus wrote: Am 06.10.21 um 18:31 schrieb Matthias Seidel: Am 06.10.21 um 18:26 schrieb Dave Fisher: On Oct 6, 2021, at 9:22 AM, Matthias Seidel wrote: Am 06.10.21 um 18:19 schrieb Dave Fisher: On Oct 6, 2021, at 8:16 AM, Matthias Seidel wrote: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! I don’t see the files here: https://sourceforge.net/projects/openofficeorg.mirror/files/ The directory is staged (invisible) until we do the release. Great. Just checking. BTW - What time will the “release” happen? Today or tomorrow morning? I need to ask security to publish the two CVEs and plan to be out this afternoon and evening. I would prefer later today (European time). Marcus, what do you think? I don't care. My preparations are nearly finished. I can commit the changes whenever we want. :-) However, more important is that the blog announcement and release notes are also ready. I can take care for the release notes. I filled in some improvement bullet points but feel free to add/change as needed. I've finished (so far) the release notes. You can copy & paste the bugfixes and enhancements from there: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.11+Release+Notes We have these two that are already public and could be listed. CVE-2021-33035 Buffer overflow from a crafted DBF file CVE-2021-40439 Billion Laughs CVE 2021-30245 - Code execution in Apache OpenOffice via non-http(s) schemes in Hyperlinks We fixed in 4.1.10 although a little to aggressively and improved the handling in this one. Should we list it again? please reload the page. I've updated exactly this section. ;-) I'm about to send the announce email. Do you want to pull the draft notice down from the release notes now? I've published the blog great, then I'll change the blue headlines to the new announcement. Marcus I saw the date for Patricia joining the project was missing. I searched the archives and came up with a this post as about the oldest I could find so I used that year. https://lists.apache.org/thread.html/9f5c7bbe9c2e46b800ad1dda5a1068a64ff26ab830ff9a9134c3b398%401446081722%40%3Cdev.openoffice.apache.org%3E Ah, great. And of cause the security texts and webpages. I can also take over this but need the texts. Dave, can you please help with the texts? Carl, can you please finalize the blog post? If were good with the text I'm ready to publish. Just say the word. Also on the announce email draft I'm ready if nobody wants a change.. What time are we thinking? Let's say at 20:00 CET which is in ~ 45 minutes. Is this OK for all? Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 19:37 schrieb Carl Marcum: On 10/6/21 1:15 PM, Marcus wrote: Am 06.10.21 um 19:06 schrieb Carl Marcum: On 10/6/21 12:37 PM, Marcus wrote: Am 06.10.21 um 18:31 schrieb Matthias Seidel: Am 06.10.21 um 18:26 schrieb Dave Fisher: On Oct 6, 2021, at 9:22 AM, Matthias Seidel wrote: Am 06.10.21 um 18:19 schrieb Dave Fisher: On Oct 6, 2021, at 8:16 AM, Matthias Seidel wrote: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! I don’t see the files here: https://sourceforge.net/projects/openofficeorg.mirror/files/ The directory is staged (invisible) until we do the release. Great. Just checking. BTW - What time will the “release” happen? Today or tomorrow morning? I need to ask security to publish the two CVEs and plan to be out this afternoon and evening. I would prefer later today (European time). Marcus, what do you think? I don't care. My preparations are nearly finished. I can commit the changes whenever we want. :-) However, more important is that the blog announcement and release notes are also ready. I can take care for the release notes. I filled in some improvement bullet points but feel free to add/change as needed. I've finished (so far) the release notes. You can copy & paste the bugfixes and enhancements from there: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.11+Release+Notes We have these two that are already public and could be listed. CVE-2021-33035 Buffer overflow from a crafted DBF file CVE-2021-40439 Billion Laughs CVE 2021-30245 - Code execution in Apache OpenOffice via non-http(s) schemes in Hyperlinks We fixed in 4.1.10 although a little to aggressively and improved the handling in this one. Should we list it again? please reload the page. I've updated exactly this section. ;-) Marcus I saw the date for Patricia joining the project was missing. I searched the archives and came up with a this post as about the oldest I could find so I used that year. https://lists.apache.org/thread.html/9f5c7bbe9c2e46b800ad1dda5a1068a64ff26ab830ff9a9134c3b398%401446081722%40%3Cdev.openoffice.apache.org%3E Ah, great. And of cause the security texts and webpages. I can also take over this but need the texts. Dave, can you please help with the texts? Carl, can you please finalize the blog post? If were good with the text I'm ready to publish. Just say the word. Also on the announce email draft I'm ready if nobody wants a change.. What time are we thinking? Let's say at 20:00 CET which is in ~ 45 minutes. Is this OK for all? Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 19:06 schrieb Carl Marcum: On 10/6/21 12:37 PM, Marcus wrote: Am 06.10.21 um 18:31 schrieb Matthias Seidel: Am 06.10.21 um 18:26 schrieb Dave Fisher: On Oct 6, 2021, at 9:22 AM, Matthias Seidel wrote: Am 06.10.21 um 18:19 schrieb Dave Fisher: On Oct 6, 2021, at 8:16 AM, Matthias Seidel wrote: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! I don’t see the files here: https://sourceforge.net/projects/openofficeorg.mirror/files/ The directory is staged (invisible) until we do the release. Great. Just checking. BTW - What time will the “release” happen? Today or tomorrow morning? I need to ask security to publish the two CVEs and plan to be out this afternoon and evening. I would prefer later today (European time). Marcus, what do you think? I don't care. My preparations are nearly finished. I can commit the changes whenever we want. :-) However, more important is that the blog announcement and release notes are also ready. I can take care for the release notes. I filled in some improvement bullet points but feel free to add/change as needed. I've finished (so far) the release notes. You can copy & paste the bugfixes and enhancements from there: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.11+Release+Notes I saw the date for Patricia joining the project was missing. I searched the archives and came up with a this post as about the oldest I could find so I used that year. https://lists.apache.org/thread.html/9f5c7bbe9c2e46b800ad1dda5a1068a64ff26ab830ff9a9134c3b398%401446081722%40%3Cdev.openoffice.apache.org%3E Ah, great. And of cause the security texts and webpages. I can also take over this but need the texts. Dave, can you please help with the texts? Carl, can you please finalize the blog post? If were good with the text I'm ready to publish. Just say the word. Also on the announce email draft I'm ready if nobody wants a change.. What time are we thinking? Let's say at 20:00 CET which is in ~ 45 minutes. Is this OK for all? Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 18:31 schrieb Matthias Seidel: Am 06.10.21 um 18:26 schrieb Dave Fisher: On Oct 6, 2021, at 9:22 AM, Matthias Seidel wrote: Am 06.10.21 um 18:19 schrieb Dave Fisher: On Oct 6, 2021, at 8:16 AM, Matthias Seidel wrote: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! I don’t see the files here: https://sourceforge.net/projects/openofficeorg.mirror/files/ The directory is staged (invisible) until we do the release. Great. Just checking. BTW - What time will the “release” happen? Today or tomorrow morning? I need to ask security to publish the two CVEs and plan to be out this afternoon and evening. I would prefer later today (European time). Marcus, what do you think? I don't care. My preparations are nearly finished. I can commit the changes whenever we want. :-) However, more important is that the blog announcement and release notes are also ready. I can take care for the release notes. And of cause the security texts and webpages. I can also take over this but need the texts. Dave, can you please help with the texts? Carl, can you please finalize the blog post? Thanks Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] Re: [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Am 06.10.21 um 17:16 schrieb Matthias Seidel: Uploads are complete and files are on at least 20 mirrors. SourceForge is ready to go! OK, then I'll continue the release process now for the website. Marcus Am 05.10.21 um 20:58 schrieb Matthias Seidel: Hi Jim, Uploads to SourceForge are running. Regards, Matthias Am 05.10.21 um 13:14 schrieb Jim Jagielski: The vote on releasing AOO 4.1.11-RC1 as GA is CLOSED. The vote has PASSED. On Oct 4, 2021, at 12:01 PM, Matthias Seidel wrote: Hi Jim, Am 04.10.21 um 13:09 schrieb Jim Jagielski: Agreed! Marcus already casted his vote. Maybe it is time to close the vote and move on? Regards, Matthias On Oct 1, 2021, at 2:45 PM, Marcus wrote: Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release AOO 4.1.11-RC1 as GA
Am 30.09.21 um 12:37 schrieb Jim Jagielski: [X] yes / +1 [ ] no / -1 My vote is based on [X] binding (member of PMC) [ ] I have built and tested the RC from source on platform [ ] [X] I have tested the binary RC on platform [ ] Tested on: - Windows 10 Home 64-bit 20H2 Build 19042.1237 - Installed AOO 4.1.11m1 (Build 9808 - Rev. bdb20b2a64) - First with "en-US" full install - Then "de" langpack - Then "pt" langpack - Then switched the UI languages Checksums: - Tested checksums for all source tarballs - Tested checksums for the install files en-US, de, pt Document tests: - Existing, older DOC, XLS, PPT documents - Existing, older DOCX, XLSX, PPTX documents - Created a new text doc and opened / edited the saved file with all languages Everything without problems. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS][VOTE] Release AOO 4.1.11-RC1 as GA
Jim, is it possible to extent the vote for 12 hours (which will be Midnight European time)? Then I've a much better chance with testing *and* to take part of this vote. Thanks Marcus Am 30.09.21 um 12:37 schrieb Jim Jagielski: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.11-RC1 as GA. [...] This vote will be open for the normal 72hrs. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice on Xing
Am 30.09.21 um 13:12 schrieb Matthias Seidel: On Xing Jürgen Schmidt is looking for a new moderator (German speaking) for the Apache OpenOffice group: https://www.xing.com/communities/posts/neuer-moderator-gesucht-1022924323?cce=emaaa97608.%3ADuB0OsqNVnj2CFA0144fAI Any volunteers? IMHO this is best discussed on the dev-de@ mailing list - btw it is already running - as it is German only business. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [QA AUTOMATION] Standalone Tests now available in standalone-test branch
Am 30.09.21 um 04:02 schrieb Carl Marcum: Just an FYI on the status of my work on allowing the automated test suites to compile and run tests without a working AOO build environment. I've started a new branch standalone-test [1] with a README file explaining the usage. [...] thanks for your work. That this test suite is now more modern but first of all usable with a fresh build AOO is a really great improvement. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO41X: Time for RC1?
Am 16.09.21 um 11:57 schrieb Matthias Seidel: I just did a full build of AOO41X for Windows. Everything fine! IMHO this could be the base for AOO 4.1.11-RC1? (This is #55779ad04e) was everything backported to the AOO41X branch that should be included also here? If yes, then we should start the process. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: LAZY CONSENSUS: change IRC links from Freenode to Libera.Chat
Am 12.08.21 um 16:26 schrieb Arrigo Marchiori: sorry I am a bit absent in these days. Edits are "on stage": https://openoffice-org.staged.apache.org/ Can someone push them into production, please, if they look good? (they do IMHO) done, thanks for taking care. Marcus On Tue, Aug 10, 2021 at 03:03:24AM +0200, australia.student@tutanota.com.INVALID wrote: +0.10 Here is the background about freenode to libera.chat https://kline.sh/ Great to see the updated links Aug 6, 2021, 16:58 by o...@mechtilde.de: +1 Am 06.08.21 um 00:35 schrieb Carl Marcum: Hi Arrigo, On 8/5/21 4:44 PM, Dave Fisher wrote: On Aug 5, 2021, at 1:11 PM, Arrigo Marchiori wrote: Hello All, following Carl's very good advice, here is my proposal: I will merge https://github.com/apache/openoffice-org/pull/57 consisting of changing IRC links from Freenode into Libera Chat, if no one objects within August 10th. Nicely done! I don’t see any reason to wait. We aren’t going back to Freenode … Make it so! I also agree. Best regards, Carl Regards, Dave Thank you and best regards, - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: devtools
Am 14.08.21 um 13:33 schrieb Peter Kovacs: Last discussion on this topic is at [1] [1] https://lists.apache.org/thread.html/r64090cf9de98c0147098b5d7d58b5f248c71b42e06d3dcb1c536bc88%40%3Cdev.openoffice.apache.org%3E +1 to move to git. I would separate each tool in an own repository. But as long as it is done I would agree to a devtools repository. To migrate it back into OpenOffice.git I am at -1 because OpenOffice Code + Build environment is already hard to learn. Especially for new commers. It is better to cluster by topics. I also think that code and tools should be separated. We have the following tools (or maybe also some more): aoo-stats bootstrap-connector build-scripts bz-tools genUpdateFeed guno-extension hg2svn lazybones-templates list-stats release-scripts scripts sdk-examples svn-stats updateVersion I don't think that we should create an own repo for each of them. This would be too much overhead. Please let us keep all tools in 1 repo together. It's just 25 MB of space or a few MBs more. Marcus On 12.08.21 18:00, Jim Jagielski wrote: Any other opinions or comments? On Aug 6, 2021, at 12:52 PM, Jim Jagielski wrote: To me, it being within OpenOffice.git makes the most sense... but I'm fine either way On Aug 6, 2021, at 12:49 PM, Dave Fisher wrote: Within /Apache/OpenOffice.git repository? Or a new /Apache/OpenOffice-devtools.git? +1, especially if history is preserved. Of course there would be wiki and webpages to update. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Am 30.06.21 um 23:47 schrieb Carl Marcum:
I think it looks great!
I've tested mobile with Firefox's developer tools and my iPhone 11 with
Firefox and that looks great too.
I had a look on my desktop with Firefox and the difference now -
compared with the first steps - is increadible.
The menu / nav now looks more sorted and clear. The menu items are well
aligned and personally I don't miss any icons for them.
Maybe you can reduce the font size and margins a bit as currently less
content is fitting on the page than before without the need to scroll.
Thanks for your work on this!
Yes, thanks a lot for making this possible.
Marcus
On 6/30/21 5:13 PM, Dave Fisher wrote:
Hi -
I like where everything is now. When I run google’s Lightroom tool in
a Chrome Incognito window I get scores of 94, 97, 100, and 100.
On Jun 30, 2021, at 1:40 PM, Peter Kovacs wrote:
On 30.06.21 20:17, Dave Fisher wrote:
On Jun 30, 2021, at 11:12 AM, Peter Kovacs wrote:
On 30.06.21 19:25, Dave Fisher wrote:
I like the look at https://openoffice-refresh.staged.apache.org/.
Please review.
+1, maybe can we have some icons in front of a menu point? like the
ASF feather in front of the ASF?
The feather in front of “The ASF” is possible.
And maybe an indication which menu point we currently see. Maybe an
arrow? (if you visit the link and you click on General you would
see a -> in front of the menu point "About".)
I’m counting on bootstrap for the nav menus and I don’t think that
is at all easy. It would likely require keeping information about
what menu a page is part of in the page along with making sure that
the page is on the menu.
I thought of something like this pseudocode:
if (window.location.href = this.dropdown-item.href) then this.css =
"selected" else this.css = "unselected"?
I get your idea and it could be a way to do it and there is a way to
make bootstrap menu items inactive.
There may be some issues with the comparison as the
window.location.href is fully qualified while we do not want to use
fully qualified urls for the dropdown-item hrefs (makes testing the
site painful.)
Hmm, bummer seems not that easy.
So maybe something like:
const boxes =
documentui.dropdown-menu.show.querySelectorAll('#dropdown-item');
boxes.forEach(box => {
if (window.location.href = box.dropdown-item.href) then box.css =
"selected" else box.css = "unselected"?
}
Well something along those lines. I really suck at JS, i just try to
write something so you have a better Idea what I thought of. Could
well (likely) be this is rubbish.
So for the pages I tried this approach seem to be pretty neat. Pages
that are not listed on the menue, maybe it is the qwuestion where
they belong, anyhow.
Actually, I would want to learn how to customize Bootstrap 5 first,
but I’m not going to do that right now.
There were numerous tweaks needed. The current site did not catch
the rename of volunteer@ to recruitment@.
Unless there are objections I plan to squash & merge after I get
the mobile view better.
I tried earlier today on my phone and it did look promising
already. The Desktop does also look great.
Do you have an android phone, or iPhone?
I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to
be exact. I use a Firefox browser.
Now I see a hamburger menu, nice. However the feather makes the menu
look unaligned. it is great on the desktop.
I am not a gui developer so I am not sure what is state of the art on
hamburger menus is, but i would intend the other menus, with the goal
that the text starts always at same point.
IMO the feather is good in the hamburger menu. All of the ASF menu
items leave the site.
I’m done with UI work for now. It is time to update content. See
https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
All The Best,
Dave
I really like the fact that it incorporates the UI approach we are
using.
Thanks!
Dave
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Am 29.06.21 um 18:57 schrieb Dave Fisher:
On Jun 29, 2021, at 9:48 AM, Marcus wrote:
Am 28.06.21 um 23:44 schrieb Dave Fisher:
I’ve created a feature branch of the project website at
https://github.com/apache/openoffice-project/tree/preview/refresh
I’ve updated it to use the ASF Pelican features as developed for the CMS
Migration of www.apache.org and ten project websites just being completed.
One feature that returns is {#elementid} and permalink support.
Intermediate results are here: https://openoffice-refresh.staged.apache.org
when comparing this with "https://openoffice.apache.org/; I don't see any
changes. Are there already changes to be noticed?
The only changes to be noticed is the formatting for the three [TOC]
after you last changes I can see now more.
In general, the vertical margins between headlines are wider.
Thanks
I plan to swap from left navigation to top navigation next along with other
enhancements.
That means all links under General, Community, Develoment ... are horizontal
links, right?
Yes, and they will collapse to a menu on narrow screens / mobile
OK, then the number of items doesn't matter.
On the example page "https://template.staged.apache.org/; I can see how it can
look like. However, we have a lot of links more, so how would it look like for us?
Two things.
(1) That’s a limited sample. Each menu will have however many menu items we
want.
(2) I think we should revisit the menus on a case by case and page by page
basis.
We have 46 pages:
[...]
Some of these are obsolete and many could use a review.
We might want to add an “Orientation” menu.
I think my next step is to make a table of the pages.
Yes, even with only 46 pages an update sounds reasonable.
Marcus
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Am 28.06.21 um 23:44 schrieb Dave Fisher:
I’ve created a feature branch of the project website at
https://github.com/apache/openoffice-project/tree/preview/refresh
I’ve updated it to use the ASF Pelican features as developed for the CMS
Migration of www.apache.org and ten project websites just being completed.
One feature that returns is {#elementid} and permalink support.
Intermediate results are here: https://openoffice-refresh.staged.apache.org
when comparing this with "https://openoffice.apache.org/; I don't see
any changes. Are there already changes to be noticed?
Thanks
I plan to swap from left navigation to top navigation next along with other
enhancements.
That means all links under General, Community, Develoment ... are
horizontal links, right?
On the example page "https://template.staged.apache.org/; I can see how
it can look like. However, we have a lot of links more, so how would it
look like for us?
Thanks
Marcus
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 22.06.21 um 19:26 schrieb Matthias Seidel: What about adding .wpl .m3u etc. to the list of secure file extensions? I would like to build a new version soon to let our users test... +1 Marcus Am 15.06.21 um 18:36 schrieb Matthias Seidel: Am 15.06.21 um 18:34 schrieb Marcus: Am 14.06.21 um 17:46 schrieb Matthias Seidel: Am 14.06.21 um 17:39 schrieb Marcus: Am 14.06.21 um 16:58 schrieb Arrigo Marchiori: the original poster of bug 128453 correctly noted that the bug was not solved _for him_: https://bz.apache.org/ooo/show_bug.cgi?id=128453#c9 In his case, AOO is showing a warning when he tries to open a WPL file, that is a Windows Media Player playlist: https://en.wikipedia.org/wiki/Windows_Media_Player_Playlist Shall we just add it to the list of safe extensions, to solve the problem? IMHO we have to be very careful where we draw the line. Who shoud decide what is on the list and what not? That's why Arrigo asked here, I think. When we allow WPL, what about ASX, M3U and other music playlist files? IMHO they should also be allowed. AOO only passes them to the player/CODEC of the OS. would be OK. And do we want to create always a new release to add something new in the internal whitelist? ;-) No, at the moment we want to create a new release based on the feedback of our users... ;-) Yes sure, and with a new issue comes a new request and therefore a new release. ;-) That's the way how a project like ours is maintained... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 14.06.21 um 17:46 schrieb Matthias Seidel: Am 14.06.21 um 17:39 schrieb Marcus: Am 14.06.21 um 16:58 schrieb Arrigo Marchiori: the original poster of bug 128453 correctly noted that the bug was not solved _for him_: https://bz.apache.org/ooo/show_bug.cgi?id=128453#c9 In his case, AOO is showing a warning when he tries to open a WPL file, that is a Windows Media Player playlist: https://en.wikipedia.org/wiki/Windows_Media_Player_Playlist Shall we just add it to the list of safe extensions, to solve the problem? IMHO we have to be very careful where we draw the line. Who shoud decide what is on the list and what not? That's why Arrigo asked here, I think. When we allow WPL, what about ASX, M3U and other music playlist files? IMHO they should also be allowed. AOO only passes them to the player/CODEC of the OS. would be OK. And do we want to create always a new release to add something new in the internal whitelist? ;-) No, at the moment we want to create a new release based on the feedback of our users... ;-) Yes sure, and with a new issue comes a new request and therefore a new release. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 14.06.21 um 16:58 schrieb Arrigo Marchiori: the original poster of bug 128453 correctly noted that the bug was not solved _for him_: https://bz.apache.org/ooo/show_bug.cgi?id=128453#c9 In his case, AOO is showing a warning when he tries to open a WPL file, that is a Windows Media Player playlist: https://en.wikipedia.org/wiki/Windows_Media_Player_Playlist Shall we just add it to the list of safe extensions, to solve the problem? IMHO we have to be very careful where we draw the line. Who shoud decide what is on the list and what not? When we allow WPL, what about ASX, M3U and other music playlist files? And do we want to create always a new release to add something new in the internal whitelist? ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 12.06.21 um 03:47 schrieb Carl Marcum: On 6/11/21 6:19 PM, Matthias Seidel wrote: Am 10.06.21 um 15:53 schrieb Matthias Seidel: Could you provide a test document? Or (if you use Windows) make a test with this build: https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/Full%20Installation/Apache_OpenOffice_4.2.0_Win_x86_install_en-US_56e2535bb8.exe I posted the wrong link for the build, please try this one: https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe This one works great on my test document! No warning on the .uno:Reload button or the odf file or inter-document links. I did discover a bug unrelated to this. When I open the document I created on Linux with the hyperlinks and uno button using the file open dialog it opens correctly using Windows 10. When I open it again using dropdown beside the Open button in the Start Center or File > Recent Documents I get an ASCII Filter Options dialog and then a General Error. General input/output error and the file doesn't open. Also happens with a production 4.1.9 that was on this system I'm testing on. Can anyone on windows confirm with the file [1]? [1] http://home.apache.org/~cmarcum/hyperlink-tests/hyperlink-test-doc.odt thanks for this document. I've tested it with Matthias' AOO 4.1.11 build on Win 10 and can confirm the behavior for showing resp. not showing the warning dialog; especially for the Reload-button (URL: .uno:reload). @Matthias: I've installed the AOO 4.1.11_807d57542e.exe (from 2021-06-13). The file from the above URL above was not available, so I hope this is OK. Marcus Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com: For some years I've had a Reload button in my Calc document to avoid having to use the File menu. Just updated to 4.1.10 and now I get a message when pressing Reload button: This hyperlink is going to open “.uno:Reload”. Do you want to proceed? Is there a way of switching off this message please? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 08.06.21 um 11:16 schrieb Matthias Seidel: Find the Windows build here: https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe here my results: http://www.openoffice.org/ http://www.openoffice.org/test.exe http://www.openoffice.org/test.ods https://www.openoffice.org/ https://www.openoffice.org/test.exe https://www.openoffice.org/test.ods --> Any HTTP or HTTPS links are opened without warning. smb://www.openoffice.org/ smb://www.openoffice.org/test.exe smb://www.openoffice.org/test.ods file://www.openoffice.org/ file://www.openoffice.org/test.exe file://www.openoffice.org/test.ods --> Any SMB or FILE links get the warning dialog before opening. How can I test with UNO links like ".uno:reload"? Thanks Marcus Am 07.06.21 um 18:09 schrieb Marcus: Am 07.06.21 um 02:12 schrieb Carl Marcum: Hi Arrigo, On 6/6/21 3:56 PM, Arrigo Marchiori wrote: Hello Carl, All, On Sun, Jun 06, 2021 at 11:50:12AM -0400, Carl Marcum wrote: Hi Arrigo and All, On 6/5/21 5:53 PM, Arrigo Marchiori wrote: Hello Carl, All, On Sat, Jun 05, 2021 at 03:47:12PM -0400, Carl Marcum wrote: Hi Arrigo, On 6/5/21 9:50 AM, Arrigo Marchiori wrote: Dear Matthias, Czesław, All, On Sat, Jun 05, 2021 at 12:39:16PM +0200, Matthias Seidel wrote: Hi Czesław, Am 05.06.21 um 12:35 schrieb Czesław Wolański: Hi Matthias, all A preliminary check in Calc (Windows 7, 64-bit) (1) in-document links beginning with # test: button with link to other sheet result: OK (no security warning) (2) .uno:XXX links result: security warning (3) Links to local files test: the "Hyperlink" dialog, button "WWW Browser" result: OK (no security warning) That's what I expected, since the patches are for file:// .uno: hasn't been addressed yet @Arrigo: correct me if I am wrong ;-) You should have just become wrong ;-) I found out that there are many checks on the URL protocol. I suggest that the warning was not checked at the right moment, but too soon. Because we had a report of unexpected _execution_ of malicious links, I suggest we leave the safety check on hyperlinks _just before calling the OS to execute them_. The result is that HTTP, HTTPS, but also "uno:" and all other protocols already understood by AOO are not checked, and no warnings will appear. We could argue that their safety must be assured by the code handling them, as we accepted to delegate the browser for Internet links. The latest commit, just pushed to branch bug128453, moves the check for "safe extensions" (or directory) from the beginning of hyperlinks' processing, to just before the execution of the link target by the OS. The protocol is not checked any more, because supported protocols are already filtered out and processed at that point. This should make all links to non-files work again, and still warn users when they are going to open JAR's, EXE's and other unknown types. What do you think about this? I like your thinking on this. I'll build this branch on Linux and test using some of the test documents and ones I've made to make sure I understand the different cases. Then I'll report back. You can find my 64 bit Linux builds here: https://home.apache.org/~ardovm/openoffice/bug128453/ I tried the "beta" option of the build script... I hope it works. Thank you for your cooperation! Best regards, I've built the bug128453 branch [1] on Linux CentOS 7 and ran the test suite that included the hyperlink tests for the dialogs [2]. I put together some test documents here [3]. Very nice, thank you! [...] So far everything looks good and I get the warning everywhere I expect to with one exception. The smb://nonexistant.url.com link does not display the warning and I get this output: --- This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. gio: smb://nonexistant.url.com/: The specified location is not mounted --- Note that I build on CentOS 7 and use --enable-gio and --disable-gnome-vfs in configure. Maybe there is a reason the SMB protocol is treated differently than the others when there is only the host section of the url? I'm not saying this is bad but just different. We can discuss... Sure. The smb:// protocol is treated like file://. A proof of this is that the link to "smb://nonexistant.url.com/evil.jar" shows a warning dialog because the ".jar" extension is not considered safe. For the same reason, f you create a link to "smb://nonexistant.url.com/whatever.ods" it will be opened without warnings. The link you are discussing points to "smb://nonexistant.url.com/". The target ends with a backslash, therefore it is considered a directory, and thus safe. Thanks for pointing this out. I intended it to end without the /. For some reason AOO adds the trailing / for the smb link no matter what I try. But not for the ot
Re: You are not dead.
Hi Tamika, thanks a lot for your kind words. We appreciate this very much. Even when the linked news report is already a bit older, the fact is still the same that you have stated already in the subject. Maybe the fact that we focus on stability and not feature-richness is irritating many people, so that they think that nothing is coming anymore. But: The work on Apache OpenOffice is still going on. :-) Marcus Am 08.06.21 um 02:59 schrieb Tamika Jolly: Some people are saying you are dying. OpenOffice has been a life saver OMG. O_O https://www.zdnet.com/article/openoffice-is-dead-long-live-libreoffice/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: sharing "installed" builds for Linux testing
Am 08.06.21 um 16:08 schrieb Carl Marcum: Would sharing the "installed" type builds work for Linux testing of small changes as long as the architecture was the same? That way Linux testers wouldn't need to integrate with the system similar to Windows users having the option of an administrative install. I've tested sharing a build from CentOS 7 to Ubuntu 18 and CentOS 8 without any noticeable issues. I would prefer this method of installation. It's faster and - the main point - not that system-integrated. As long as we don't need to test any system or installation issues I would like to test this way. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 07.06.21 um 02:12 schrieb Carl Marcum: Hi Arrigo, On 6/6/21 3:56 PM, Arrigo Marchiori wrote: Hello Carl, All, On Sun, Jun 06, 2021 at 11:50:12AM -0400, Carl Marcum wrote: Hi Arrigo and All, On 6/5/21 5:53 PM, Arrigo Marchiori wrote: Hello Carl, All, On Sat, Jun 05, 2021 at 03:47:12PM -0400, Carl Marcum wrote: Hi Arrigo, On 6/5/21 9:50 AM, Arrigo Marchiori wrote: Dear Matthias, Czesław, All, On Sat, Jun 05, 2021 at 12:39:16PM +0200, Matthias Seidel wrote: Hi Czesław, Am 05.06.21 um 12:35 schrieb Czesław Wolański: Hi Matthias, all A preliminary check in Calc (Windows 7, 64-bit) (1) in-document links beginning with # test: button with link to other sheet result: OK (no security warning) (2) .uno:XXX links result: security warning (3) Links to local files test: the "Hyperlink" dialog, button "WWW Browser" result: OK (no security warning) That's what I expected, since the patches are for file:// .uno: hasn't been addressed yet @Arrigo: correct me if I am wrong ;-) You should have just become wrong ;-) I found out that there are many checks on the URL protocol. I suggest that the warning was not checked at the right moment, but too soon. Because we had a report of unexpected _execution_ of malicious links, I suggest we leave the safety check on hyperlinks _just before calling the OS to execute them_. The result is that HTTP, HTTPS, but also "uno:" and all other protocols already understood by AOO are not checked, and no warnings will appear. We could argue that their safety must be assured by the code handling them, as we accepted to delegate the browser for Internet links. The latest commit, just pushed to branch bug128453, moves the check for "safe extensions" (or directory) from the beginning of hyperlinks' processing, to just before the execution of the link target by the OS. The protocol is not checked any more, because supported protocols are already filtered out and processed at that point. This should make all links to non-files work again, and still warn users when they are going to open JAR's, EXE's and other unknown types. What do you think about this? I like your thinking on this. I'll build this branch on Linux and test using some of the test documents and ones I've made to make sure I understand the different cases. Then I'll report back. You can find my 64 bit Linux builds here: https://home.apache.org/~ardovm/openoffice/bug128453/ I tried the "beta" option of the build script... I hope it works. Thank you for your cooperation! Best regards, I've built the bug128453 branch [1] on Linux CentOS 7 and ran the test suite that included the hyperlink tests for the dialogs [2]. I put together some test documents here [3]. Very nice, thank you! [...] So far everything looks good and I get the warning everywhere I expect to with one exception. The smb://nonexistant.url.com link does not display the warning and I get this output: --- This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. gio: smb://nonexistant.url.com/: The specified location is not mounted --- Note that I build on CentOS 7 and use --enable-gio and --disable-gnome-vfs in configure. Maybe there is a reason the SMB protocol is treated differently than the others when there is only the host section of the url? I'm not saying this is bad but just different. We can discuss... Sure. The smb:// protocol is treated like file://. A proof of this is that the link to "smb://nonexistant.url.com/evil.jar" shows a warning dialog because the ".jar" extension is not considered safe. For the same reason, f you create a link to "smb://nonexistant.url.com/whatever.ods" it will be opened without warnings. The link you are discussing points to "smb://nonexistant.url.com/". The target ends with a backslash, therefore it is considered a directory, and thus safe. Thanks for pointing this out. I intended it to end without the /. For some reason AOO adds the trailing / for the smb link no matter what I try. But not for the other types. Even in the automated test since it just robots the UI. I've removed the smb link in the test document and uploaded a new copy. I'll also disable that specific test in the test suite as well due to this behavior. This is the current logic. It may be worth discussing whether we want to consider links to directories safe or not. The warning messages you reported about gio are worth another discussion: we may need to update the way we "talk to" the OS under GNOME. But as long as it works on current distributions, I would refrain from changing it. I hope that the above makes sense. Best regards, So now I'll say everything works as expected. Thanks again for your work on this! Yes, thanks a lot for your efforts. :-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: SF and AOO download statistics
Am 03.06.21 um 13:43 schrieb Bidouille: Weird I don't think that it's weird. It's a normal thing that you can sit in France and download an English version. The download will be counted as done in France, but the AOO version is counted for the English language. Marcus - Mail original - De: "Matthias Seidel" À: dev@openoffice.apache.org Envoyé: Jeudi 3 Juin 2021 11:51:33 Objet: Re: SF and AOO download statistics Hi, Top downloads are from France, not for the French version... ;-) Matthias Am 03.06.21 um 11:48 schrieb Bidouille: Since a couple of versions, top country for downloading is FR (for 4.1.10 = 13%). But if I go on details, I see that en-US downloads are 94K and FR are 46K. https://www.cjoint.com/doc/21_06/KFdjTDAutNV_capture.jpg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 02.06.21 um 00:07 schrieb Peter Kovacs: On 01.06.21 21:57, Arrigo Marchiori wrote: I would not go for file://. Can we go for a pattern derivated from file://path/document.ods#anchor ? I am not sure I understand your question, Peter. I am suggesting not to trust file:// in general, but the anchored URL, yes, the securty report is talking about nin-http(s) links, And "ile" is not http. There we have to treat this as insecure. maybe file://*#anchor if you like. But maybe I got this URL wrong. Hm, I don't see how an anchor makes the document more secure. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo:eo Localization page
Am 12.05.21 um 20:38 schrieb Marcus: I would say, let's going on in the mail thread in @L10n. Otherwise it's just double postings. ;-) in the meantime the webpages have been updated and are available: https://www.openoffice.org/eo/ Please have a look what you want to translate. Then I can help you. :-) Thanks Marcus Am 12.05.21 um 11:33 schrieb Dean.Webber: I have updated the "main" page for the Esperanto (EO) language. The html code is available at https://justpaste.it/8yuud for upload. The pages have mostly been translated using translate.yandex.com with help from en.bab.la/dictionary/english-esperanto/ for the remaining few. This will still point to the english version of the downloads page, as the Esperanto version has been relocated for housekeeping purposes. If someone could upload this, I can make sure that it looks as it should when sitting in the correct location. As a final check I can translate it back to English, to ensure that the meaning has not changed significantly. I was not sure how the language detection in the page operates, but I set the variable for language to "eo" on line 271, is that sufficient? The original was based from the English (en-GB) version found from www.openoffice.org/?redirect=soft<http://www.openoffice.org/?redirect=soft> and clicking on "This site is also available in English (en-GB). Just click this text to get redirected.". The soft redirect message appears when changing from another language back to English. From: Aivaras Stepukonis Sent: Wednesday, 12 May 2021 1:23 AM To: dev@openoffice.apache.org Subject: Re: OOo:eo Localization page Thank for the link, Marcus! Yes, as long as the visitors are informed they can help with localization, keeping the website up to date by removing from sight the bits that are unmaintained is an appropriate QA step. Aivaras 2021-05-11 14:01, Marcus rašė: Am 11.05.21 um 11:35 schrieb Aivaras Stepukonis: On the subject of unmaintained, untranslated local webpages. One should start with a simple set of criteria that allows to determine what is/is not unmaintained. Something like: 1. incomplete page translation; 2. outdated page layout/design. the criteria are summarized here: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openoffice.org%2Fprojects%2Fnative-lang.htmldata=04%7C01%7C2018001901%40student.sit.ac.nz%7C6379c6930f444b8bf8c008d9148007f2%7Cc46ab213d1794a719ff7b9d9fe3f3b48%7C0%7C1%7C637563362414144036%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=DEnEpvYDuzBAw0qhtWplPWqHwMSd8p56Btwk6S0bDXI%3Dreserved=0 Then one would archive the pages that fall under the above criteria. The visitors coming from the locales of the unlocalized pages would instead be directed to the main page with a message "If you can help translating this page into your native language, let us know!" This is already done in a slightly different way: - Pages have English text - A big, red box with text similar to yours but just a bit more. - No redirection to the main page Marcus 2021-05-11 02:07, Marcus rašė: Am 11.05.21 um 00:18 schrieb Dean.Webber: How many localization pages need to be translated? How many pages are 'not maintained'? the default set has ~40 pages. But I haven't counted the total amount of words or sentences. Depending on the extend of the pages, we can adopt a translate service (which will have some cost attached). For example to translate 100 pages of similar character length using the yandex translate api will cost $5.00/month (assuming USD). Hm, costs are always not a good argument. OpenOffice is made by volunteers. The same should apply to the creation and maintenance of webpages or documentation in general. I don't know the quality of translated languages of Yandex or others. But I know Google Translate and its quality is ... improvable. ;-) Otherwise perhaps a list of these pages can be left for those that are new recruits, or looking for something to do. So, if they chose too, they can spend some time working on localizations or translations. They can then use a translate service (for free) to convert from the sources to the localization language. This may result in poor quality translation, but enough for people to get the general idea, and a good starting point for native language speakers to modify pages. As written previously the pages are unmaintained for years. There are no volunteers that would take care of it. So, translating a part of it and then others can do the remaining stuff will not come true. Very seldom we get a mail that someone has seen a message like you can see here in the red box [1]. We give them a few hints and how and where to start with translation and then ... noting more. Thats all. But honestly, I have no idea of the scale of the localization pages. The problem is that th
Re: What to focus on next
Am 27.05.21 um 19:53 schrieb Marcus: Am 27.05.21 um 19:38 schrieb Matthias Seidel: Am 27.05.21 um 19:10 schrieb Marcus: Am 27.05.21 um 16:18 schrieb Matthias Seidel: Am 27.05.21 um 16:07 schrieb Dave Fisher: IMO there are a couple more issues like hyperlink protocols to always allow to look into before 4.1.11 builds. So, if you are looking to build right now then 4.2.0dev. Yes, 4.2.0-Dev3 would simply be an official "snapshot" of what we have in branch AOO42X. 4.1.11 needs a lot more work to be released. Maybe a thread on the release blockers for 4.2.0? +1 please not as mails. IMHO this will end in a total mess and nobody is able to keep the overview. ;-) Good idea! Better to create a Confluence page, start with the list of opened and targeted issues [1]. Then we can discuss which issues we can fix for 4.2.0. I would simply start with the list of Release Blockers: https://bz.apache.org/ooo/buglist.cgi?bug_status=CONFIRMED_status=ACCEPTED_status=REOPENED_status=RESOLVED_status=VERIFIED_status=CLOSED=flagtypes.name_id=248770=substring=changeddate%20DESC%2Cbug_id%20DESC_based_on=4.2.0_blocker_requested%2B_format=advanced=---=FIXED=4.2.0_release_blocker I've started this list: https://cwiki.apache.org/confluence/display/OOOUSERS/Blocker+issues+4.2.0 Will now add the classified blockers also. done. Let's start the discussion now. Marcus On May 27, 2021, at 6:41 AM, Matthias Seidel wrote: Am 27.05.21 um 15:38 schrieb Jim Jagielski: On May 21, 2021, at 5:02 AM, Matthias Seidel wrote: Am 14.05.21 um 18:56 schrieb Jim Jagielski: On May 14, 2021, at 1:27 AM, Arrigo Marchiori wrote: I agree, but how many 4.1.X versions do we want to publish before 4.2.0? Now that we support two digits, please let us not point to 4.1.99 ! ;-) FWIW, I tend to agree. We fixed the bug. Maybe its not the best solution, but I don't see why we should continue to "focus" on 4.1.X at the expense of 4.2.X. We already made some progress on the Release Blockers for 4.2.0. But the remaining ones are untouched for long time. What about a 4.2.0-Dev3? We already planned it when 4.1.10 got urgent... So should the push be 4.1.11 or 4.2.0-Dev3? I don't see a problem to do both? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: What to focus on next
Am 27.05.21 um 19:38 schrieb Matthias Seidel: Am 27.05.21 um 19:10 schrieb Marcus: Am 27.05.21 um 16:18 schrieb Matthias Seidel: Am 27.05.21 um 16:07 schrieb Dave Fisher: IMO there are a couple more issues like hyperlink protocols to always allow to look into before 4.1.11 builds. So, if you are looking to build right now then 4.2.0dev. Yes, 4.2.0-Dev3 would simply be an official "snapshot" of what we have in branch AOO42X. 4.1.11 needs a lot more work to be released. Maybe a thread on the release blockers for 4.2.0? +1 please not as mails. IMHO this will end in a total mess and nobody is able to keep the overview. ;-) Good idea! Better to create a Confluence page, start with the list of opened and targeted issues [1]. Then we can discuss which issues we can fix for 4.2.0. I would simply start with the list of Release Blockers: https://bz.apache.org/ooo/buglist.cgi?bug_status=CONFIRMED_status=ACCEPTED_status=REOPENED_status=RESOLVED_status=VERIFIED_status=CLOSED=flagtypes.name_id=248770=substring=changeddate%20DESC%2Cbug_id%20DESC_based_on=4.2.0_blocker_requested%2B_format=advanced=---=FIXED=4.2.0_release_blocker I've started this list: https://cwiki.apache.org/confluence/display/OOOUSERS/Blocker+issues+4.2.0 Will now add the classified blockers also. Marcus [1] https://bz.apache.org/ooo/buglist.cgi?query_format=advanced=---_milestone=4.2.0 Marcus On May 27, 2021, at 6:41 AM, Matthias Seidel wrote: Am 27.05.21 um 15:38 schrieb Jim Jagielski: On May 21, 2021, at 5:02 AM, Matthias Seidel wrote: Am 14.05.21 um 18:56 schrieb Jim Jagielski: On May 14, 2021, at 1:27 AM, Arrigo Marchiori wrote: I agree, but how many 4.1.X versions do we want to publish before 4.2.0? Now that we support two digits, please let us not point to 4.1.99 ! ;-) FWIW, I tend to agree. We fixed the bug. Maybe its not the best solution, but I don't see why we should continue to "focus" on 4.1.X at the expense of 4.2.X. We already made some progress on the Release Blockers for 4.2.0. But the remaining ones are untouched for long time. What about a 4.2.0-Dev3? We already planned it when 4.1.10 got urgent... So should the push be 4.1.11 or 4.2.0-Dev3? I don't see a problem to do both? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: What to focus on next
Am 27.05.21 um 16:18 schrieb Matthias Seidel: Am 27.05.21 um 16:07 schrieb Dave Fisher: IMO there are a couple more issues like hyperlink protocols to always allow to look into before 4.1.11 builds. So, if you are looking to build right now then 4.2.0dev. Yes, 4.2.0-Dev3 would simply be an official "snapshot" of what we have in branch AOO42X. 4.1.11 needs a lot more work to be released. Maybe a thread on the release blockers for 4.2.0? +1 please not as mails. IMHO this will end in a total mess and nobody is able to keep the overview. ;-) Better to create a Confluence page, start with the list of opened and targeted issues [1]. Then we can discuss which issues we can fix for 4.2.0. [1] https://bz.apache.org/ooo/buglist.cgi?query_format=advanced=---_milestone=4.2.0 Marcus On May 27, 2021, at 6:41 AM, Matthias Seidel wrote: Am 27.05.21 um 15:38 schrieb Jim Jagielski: On May 21, 2021, at 5:02 AM, Matthias Seidel wrote: Am 14.05.21 um 18:56 schrieb Jim Jagielski: On May 14, 2021, at 1:27 AM, Arrigo Marchiori wrote: I agree, but how many 4.1.X versions do we want to publish before 4.2.0? Now that we support two digits, please let us not point to 4.1.99 ! ;-) FWIW, I tend to agree. We fixed the bug. Maybe its not the best solution, but I don't see why we should continue to "focus" on 4.1.X at the expense of 4.2.X. We already made some progress on the Release Blockers for 4.2.0. But the remaining ones are untouched for long time. What about a 4.2.0-Dev3? We already planned it when 4.1.10 got urgent... So should the push be 4.1.11 or 4.2.0-Dev3? I don't see a problem to do both? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: ReactOS and AOO
Am 17.05.21 um 15:59 schrieb Matthias Seidel: ReactOS [1] has made some great improvements lately and I decided to install it in VirtualBox and test AOO. The App Manager only has AOO 4.1.5 listed, so I created a Pull Request to update the database [2]. AOO still has some repaint issues but I really like the combination... [1] https://reactos.org/ [2] https://github.com/reactos/rapps-db/pull/138 that's great news. Thanks for this. Do you think that it is possible to get this improved in the near future? Then we could add this OS to the list of possible operating systems - even when we do not actively support this platform. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draft of new Templatew for Release Notes
Am 15.05.21 um 18:49 schrieb Keith N. McKenna: Here is a link to a PDF of a draft of the Release Notes Template on Confluence. The original intent of the template was to create a consistent and professional look and feel to the documentation we present to the public. A number of changes have been made and I welcome all comments and suggestions on format, wording, and grammar. The PDF can be found at the Following link: https://1drv.ms/f/s!AsMYmStvrJNJgQRZMOphRisXB35X please delete the link to the .../download/other.html webpage as it is no longer existing. It's now only a redirect to the main download page. Furthermore the info text at the top "it's not released yet ..." can be changed to a colored box which is more visible (insert the macro "warning"). I've done the changes already for the AOO 4.1.11 page but not for the template. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draft of new Templatew for Release Notes
Am 16.05.21 um 14:33 schrieb Dick Groskamp: On 2021/05/15 16:49:46, "Keith N. McKenna" wrote: Here is a link to a PDF of a draft of the Release Notes Template on Confluence. The original intent of the template was to create a consistent and professional look and feel to the documentation we present to the public. A number of changes have been made and I welcome all comments and suggestions on format, wording, and grammar. The PDF can be found at the Following link: https://1drv.ms/f/s!AsMYmStvrJNJgQRZMOphRisXB35X came across the following issues: ___ link Apache OpenOffice - should be HTTPS to shorten this: IMHO every link should be HTTPS. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release Notes for AOO 4.1.11
Am 15.05.21 um 18:29 schrieb Keith N. McKenna: On 2021-05-14 10:04, Marcus wrote: Keith, thanks for creating new notes. I've added a missing space to the headline. Also moved it to the previously created release schedule, sorry haven't told about it yet. I remember that you wanted to create a new template structure for the release notes. Is this already done? Or is it coming later? This reflects the new template structure. I will also be sending a link to a PDF file for all to comment on under its own thread. Confluence is a Wiki system where everybody can do changes. And you can add comments - for the whole page or just select some specific text, and click the comment icon on the mouse tip. Do you see a further advantage with a PDF that the above doesn't fulfill yet? Please note that attachments to mailing lists are mostly not possible. Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Quick poll: can we rename the INCLUDE and LIB variables in Makefiles?
Am 14.05.21 um 21:56 schrieb Arrigo Marchiori: I would go for option A- because option B- would lead to _very_ long command lines and I would expect problems. But would I stomp on anyone's feet if I did that? Would it be bad practice? Would it violate any standards? I am open to suggestions and criticism. Please let me hear your opinion! I'm not a core developer, so I don't know the details. However, renaming such essential keywords like "INCLUDE" and "LIB" is indeed a heavy change. IMHO it's the same like switching the build system to gmake, scons or whatever. It has to be done very carefully and would be an enormous obstacle for us. There are f...cking many makefiles that need to be changed. We have tried to change the build system more than one time and both were not done until the end. So, now we have a mix of 3-4 build systems inside the code. With a mix of renamed keywords it won't get easier to maintain the code and even not for new vontuneers to understand this. What is currently used for building on Windows? Any (good) need to chnge thisto VS 2015? Who should do this change and is there a guarantee that the person is doing it until the end? Is it for sure that this is only influencing how we can build on Windows or has it any side effects on the other platforms? If so, renaming is more than a normal obstacle. We need to discuss and decide this very detailed and carefully. Sorry for these strong words and questions. However, my gut feeling says "this is not a good idea". My 2 ct. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Release Notes for AOO 4.1.11
Keith, thanks for creating new notes. I've added a missing space to the headline. Also moved it to the previously created release schedule, sorry haven't told about it yet. I remember that you wanted to create a new template structure for the release notes. Is this already done? Or is it coming later? Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 14.05.21 um 10:19 schrieb Matthias Seidel: Hi Arrigo, Am 14.05.21 um 07:27 schrieb Arrigo Marchiori: Hello Carl, all, On Thu, May 13, 2021 at 07:23:16PM -0400, Carl Marcum wrote: [...] Hopefully we can collect the exceptions in the BZ issue noted in this thread and then agree on the direction. The few I see so far are: 1. in-document links beginning with #. 2. .uno:XXX links 3. Links to local files. I think all 3 are candidates but that's just me. @Arrigo, were you planning on a PR for AOO41X ? If not, I can try at least some of it but again I'm not really a C++ guy yet :) I suggest we make up our minds on the intended solution first, and then start coding it. We have seen some interesting proposals, some of which were quite complex (adding configuration settings, dialogs etc). The three categories listed above would be candidates for whitelisting, and this would be the quickest fix. But someone fluent in UNO should first ensure all of us that no.2 is not going to reopen any other backdoors! Maybe this topic is worth a discussion with vote, the Apache way? So we get our roadmap fixed. There is also the suggestion (Dave's maybe?) that we add the 3 security levels (that are already in the code) for links to the UI settings and let the user lock it down or open it up from where it is now. Yes, I was referring to this and to Peter's ideas. Yes, but that will only work for trunk/AOO42X since we need to update the translations too. I agree, but how many 4.1.X versions do we want to publish before 4.2.0? Now that we support two digits, please let us not point to 4.1.99 ! ;-) As "soon" as all Release Blocker are fixed we can release 4.2.0 ;-) yes, the goal is easy but to reach it that is the challenge. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 14.05.21 um 07:27 schrieb Arrigo Marchiori: On Thu, May 13, 2021 at 07:23:16PM -0400, Carl Marcum wrote: [...] I suggest we make up our minds on the intended solution first, and then start coding it. We have seen some interesting proposals, some of which were quite complex (adding configuration settings, dialogs etc). +1 Otherwise we may need more time with improving the fix again and again. A little Confluence page could be really helpful to collect the possible ways and with a column to express our all favorite way. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice-org] branch main updated: Reworked the entries for 'brand.html' to use the general English text when no translation is available, to lower the effort for updating the website for new r
Am 04.05.21 um 21:57 schrieb Marcus:
Am 04.05.21 um 21:49 schrieb Dave Fisher:
We would likely split the announce off from the brand.
type=brand
home=home
search=buscar
selectedlang=ast
language=Llingua
name=Apache OpenOffice
tagline=La suite de productividá abierta y llibre
logo=AOO_logos/AOO4_website_logo.png
domain=https://www.openoffice.org
divid=bannera
~~
type=annouce
announce=Espublizada Apache OpenOffice 4.1.10
announceurl=https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.10+Release+Notes
announcetip=Espublizada Apache OpenOffice 4.1.10
~~
announce.gsp:
title="${content.announcetip}">${content.announce}
In page.gsp:
Follow
With:
Re: Start working on AOO 4.1.11?
Am 13.05.21 um 07:50 schrieb Arrigo Marchiori: can someone please allow setting '4.1.11' as 'Target Milestone' on BugZilla? I would like to set it on https://bz.apache.org/ooo/show_bug.cgi?id=128453 done marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hyperlink Warning Message
Am 12.05.21 um 22:12 schrieb Arrigo Marchiori: please allow me to top-post as I just need a ``public reminder''. An Italian user reported another problem [1]: they have links that point _to the same document_ and trigger the warning. Even if you do not understand Italian, you can download the attachment and look at what the buttons do. URLs are in the form: "#anchor". Therefore, we should remember to whitelist all links starting with "#", whatever design choice we make. yes, good point. Would not it be nice to file a BugZilla issue to collect all the reports and URLs, as it happened for other ``popular'' bugs? 1: https://forum.openoffice.org/it/forum/viewtopic.php?f=9=11231 I don't think that we need another issue for the problem. Why not using this one [2] and extend it by comments which URL parts we also want to consider: [2] https://bz.apache.org/ooo/show_bug.cgi?id=128453 Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo:eo Localization page
I would say, let's going on in the mail thread in @L10n. Otherwise it's just double postings. ;-) Marcus Am 12.05.21 um 11:33 schrieb Dean.Webber: I have updated the "main" page for the Esperanto (EO) language. The html code is available at https://justpaste.it/8yuud for upload. The pages have mostly been translated using translate.yandex.com with help from en.bab.la/dictionary/english-esperanto/ for the remaining few. This will still point to the english version of the downloads page, as the Esperanto version has been relocated for housekeeping purposes. If someone could upload this, I can make sure that it looks as it should when sitting in the correct location. As a final check I can translate it back to English, to ensure that the meaning has not changed significantly. I was not sure how the language detection in the page operates, but I set the variable for language to "eo" on line 271, is that sufficient? The original was based from the English (en-GB) version found from www.openoffice.org/?redirect=soft<http://www.openoffice.org/?redirect=soft> and clicking on "This site is also available in English (en-GB). Just click this text to get redirected.". The soft redirect message appears when changing from another language back to English. From: Aivaras Stepukonis Sent: Wednesday, 12 May 2021 1:23 AM To: dev@openoffice.apache.org Subject: Re: OOo:eo Localization page Thank for the link, Marcus! Yes, as long as the visitors are informed they can help with localization, keeping the website up to date by removing from sight the bits that are unmaintained is an appropriate QA step. Aivaras 2021-05-11 14:01, Marcus rašė: Am 11.05.21 um 11:35 schrieb Aivaras Stepukonis: On the subject of unmaintained, untranslated local webpages. One should start with a simple set of criteria that allows to determine what is/is not unmaintained. Something like: 1. incomplete page translation; 2. outdated page layout/design. the criteria are summarized here: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openoffice.org%2Fprojects%2Fnative-lang.htmldata=04%7C01%7C2018001901%40student.sit.ac.nz%7C6379c6930f444b8bf8c008d9148007f2%7Cc46ab213d1794a719ff7b9d9fe3f3b48%7C0%7C1%7C637563362414144036%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=DEnEpvYDuzBAw0qhtWplPWqHwMSd8p56Btwk6S0bDXI%3Dreserved=0 Then one would archive the pages that fall under the above criteria. The visitors coming from the locales of the unlocalized pages would instead be directed to the main page with a message "If you can help translating this page into your native language, let us know!" This is already done in a slightly different way: - Pages have English text - A big, red box with text similar to yours but just a bit more. - No redirection to the main page Marcus 2021-05-11 02:07, Marcus rašė: Am 11.05.21 um 00:18 schrieb Dean.Webber: How many localization pages need to be translated? How many pages are 'not maintained'? the default set has ~40 pages. But I haven't counted the total amount of words or sentences. Depending on the extend of the pages, we can adopt a translate service (which will have some cost attached). For example to translate 100 pages of similar character length using the yandex translate api will cost $5.00/month (assuming USD). Hm, costs are always not a good argument. OpenOffice is made by volunteers. The same should apply to the creation and maintenance of webpages or documentation in general. I don't know the quality of translated languages of Yandex or others. But I know Google Translate and its quality is ... improvable. ;-) Otherwise perhaps a list of these pages can be left for those that are new recruits, or looking for something to do. So, if they chose too, they can spend some time working on localizations or translations. They can then use a translate service (for free) to convert from the sources to the localization language. This may result in poor quality translation, but enough for people to get the general idea, and a good starting point for native language speakers to modify pages. As written previously the pages are unmaintained for years. There are no volunteers that would take care of it. So, translating a part of it and then others can do the remaining stuff will not come true. Very seldom we get a mail that someone has seen a message like you can see here in the red box [1]. We give them a few hints and how and where to start with translation and then ... noting more. Thats all. But honestly, I have no idea of the scale of the localization pages. The problem is that there is nobody who can take care of these pages. The effort for a few or even one person is enormous. I mean the project people. Volunteers of course would takeover only one language. I don't want to be seen as carrier o
