Re: macOS and AOO42X
+1 Am 03.05.20 um 19:58 schrieb Matthias Seidel: > Hi Jim, > > Am 29.04.20 um 20:43 schrieb Jim Jagielski: >> OK, so I have available a handful of Lang builds for Linux 64bit and macOS >> available at >> >>o http://home.apache.org/~jim/AOO-builds/ >> >> These are of HEAD of AOO42X and were built as developer releases... these >> are not the "official" Dev2m2 releases however, although they are in a >> directory that implies otherwise. >> >> Once people give these a quick A-OK, I can go ahead and do the *real* and >> *official* Dev2/4.2.0-m2 builds > > All needed languages (including the 5 new ones) are now updated in trunk > and cherry-picked for AOO42X. > > How do we proceed? Create a tag for Dev2? > I have seen no objections so far, assuming that everyone is OK with it... > > Regards, > > Matthias > >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: macOS and AOO42X
Hi Jim, Am 29.04.20 um 20:43 schrieb Jim Jagielski: > OK, so I have available a handful of Lang builds for Linux 64bit and macOS > available at > >o http://home.apache.org/~jim/AOO-builds/ > > These are of HEAD of AOO42X and were built as developer releases... these are > not the "official" Dev2m2 releases however, although they are in a directory > that implies otherwise. > > Once people give these a quick A-OK, I can go ahead and do the *real* and > *official* Dev2/4.2.0-m2 builds All needed languages (including the 5 new ones) are now updated in trunk and cherry-picked for AOO42X. How do we proceed? Create a tag for Dev2? I have seen no objections so far, assuming that everyone is OK with it... Regards, Matthias > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: macOS and AOO42X
Hi Marcus, Am 03.05.20 um 19:39 schrieb Marcus: > Am 03.05.20 um 12:16 schrieb Matthias Seidel: >> Hi Marcus, >> >> Am 29.04.20 um 01:04 schrieb Marcus: >>> Am 29.04.20 um 00:56 schrieb Matthias Seidel: Am 29.04.20 um 00:48 schrieb Marcus: > Am 28.04.20 um 23:37 schrieb Matthias Seidel: >> Am 28.04.20 um 23:33 schrieb Pedro Lino: >>> Any chance the Dev2 can include certification for Windows OS? >> No, this costs real money and will only be used for releases. > I assume at least the RC will be certified? > Yes, it costs money but it needs to be verified at some point > before the first official release. I doubt it. But you can discuss that with the ASF if you want. >>> Why should I discuss with ASF? Aren't the members of the AOO PMC >>> convinced that you should not make experiments with Release >>> versions? This will be the first AOO version certified. One of the >>> RCs should be certified to make sure the certification >>> process/script/steps is correct and that the certificate is >>> correctly identified at least under Windows 10. >> >> If you want that you must discuss that with the ASF if they are >> willing >> to pay the costs for "one of the RCs". > > he is already discussing with ASF. ;-) But with the wrong person... >>> >>> hm, do you mean the treasurer? Otherwise I don't know who you mean. >> >> Exactly. >> >>> >> The release will be signed. Thank you for your understanding! > > And when it runs into errors, the first question would be: Haven't > you > tested the signing? The answer would be embarrassing. > > So, lets try it. I already tested it, but thank you for volunteering! I will write you a mail with details. (Until now, I was the only one interested in the Windows Code Signing process) >>> >>> I have no interest in Windows at all. ;-) >> That's a real problem. > > you shouldn't look too much on the black side. ;-) > My daily worker is a Linux machine. However, I can look for / test > something also on Windows. That indeed sounds better than "I have no interest at all"! ;-) We have several issues on Windows and it is still our biggest user base (about 80%) > >>> But OK. I can see what I can do on the weekend. >> >> Maybe you could start with updating the download numbers? >> We have passed the 290 million mark almost 2 weeks ago... > > Sure. I'll do a bigger update on Tuesday. Then we have the next > complete weeks. Thanks! I already updated the graphic/metadata on the web site. Regards, Matthias > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: macOS and AOO42X
Am 03.05.20 um 12:16 schrieb Matthias Seidel: Hi Marcus, Am 29.04.20 um 01:04 schrieb Marcus: Am 29.04.20 um 00:56 schrieb Matthias Seidel: Am 29.04.20 um 00:48 schrieb Marcus: Am 28.04.20 um 23:37 schrieb Matthias Seidel: Am 28.04.20 um 23:33 schrieb Pedro Lino: Any chance the Dev2 can include certification for Windows OS? No, this costs real money and will only be used for releases. I assume at least the RC will be certified? Yes, it costs money but it needs to be verified at some point before the first official release. I doubt it. But you can discuss that with the ASF if you want. Why should I discuss with ASF? Aren't the members of the AOO PMC convinced that you should not make experiments with Release versions? This will be the first AOO version certified. One of the RCs should be certified to make sure the certification process/script/steps is correct and that the certificate is correctly identified at least under Windows 10. If you want that you must discuss that with the ASF if they are willing to pay the costs for "one of the RCs". he is already discussing with ASF. ;-) But with the wrong person... hm, do you mean the treasurer? Otherwise I don't know who you mean. Exactly. The release will be signed. Thank you for your understanding! And when it runs into errors, the first question would be: Haven't you tested the signing? The answer would be embarrassing. So, lets try it. I already tested it, but thank you for volunteering! I will write you a mail with details. (Until now, I was the only one interested in the Windows Code Signing process) I have no interest in Windows at all. ;-) That's a real problem. you shouldn't look too much on the black side. ;-) My daily worker is a Linux machine. However, I can look for / test something also on Windows. But OK. I can see what I can do on the weekend. Maybe you could start with updating the download numbers? We have passed the 290 million mark almost 2 weeks ago... Sure. I'll do a bigger update on Tuesday. Then we have the next complete weeks. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] DiGro commented on pull request #76: Removed whitespave from tags 20200229 1835
DiGro commented on pull request #76: URL: https://github.com/apache/openoffice/pull/76#issuecomment-623125835 Carl, most of these changes are not visible in the office suite itself. At least I couldn't find them where I expected them They are part of the index for the Help, but they show correct in the Help from the suite itself. They caused problems however with translating when they are imported into Pootle. Pootle is the program used for translations from en-us to other languages. In Pootle they generate unwanted spaces in the strings. Because of that the strings in Pootle generate in their turn warnings and failed checks. These warnings and failed checks have to be corrected by the translators. By removing these superfluous spaces strings will be correct in Pootle and won't raise warnings and failed checks anymore. The superfluous spaces were, probably accidentally, inserted in the past when people, for reasons of readability, added them to the original files that then were imported into Pootle and caused this problem, probably without the original authors knowing of it. Removing the white spaces will lighten the "burden" for translators to correct the caused problems. Other removed white space were truncated strings (probably also for reasons of readability in the original file in the past) en wrongful placed spaces (for instance at end of sentence but before end-tag). One example of a truncated string in the Help for Calc is: "Example: Cell E5 contains the text "Europe". Below, in cell E6, is the value 100 and in cell E7 the value 200. If the Automatically find column and row labels box is marked, you can write the following formula in cell A1: =SUM(Europe)." which shows correct in the Help, but does not in Pootle. In Pootle: " Example: Cell E5 contains the text "Europe". Below, in cell E6, is the value 100 and in cell E7 the value 200. If the Automatically find column and row labels box is marked, you can write the following formula in cell A1: =SUM(Europe)." Note the excessive spaces before Example I suppose Mechtilde and Mathias have more insight on the technical details, since I'm not really a "techie" __ DiGro Op zondag 3 mei 2020 16:24:34 CEST schreef Carl Marcum : Where would I look in the office to see the effect of this change? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] cbmarcum commented on pull request #76: Removed whitespave from tags 20200229 1835
cbmarcum commented on pull request #76: URL: https://github.com/apache/openoffice/pull/76#issuecomment-623117983 Where would I look in the office to see the effect of this change? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] Pilot-Pirx commented on pull request #86: Translation
Pilot-Pirx commented on pull request #86: URL: https://github.com/apache/openoffice/pull/86#issuecomment-623107939 I did some proofreading and I think this could be merged now... This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] leginee commented on pull request #76: Removed whitespave from tags 20200229 1835
leginee commented on pull request #76: URL: https://github.com/apache/openoffice/pull/76#issuecomment-623105866 I see. Thanks for the update. So far I am not negative to this proposal, but I have not checked the change within OpenOffice. Hope I can give feedback soon. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] DiGro commented on pull request #76: Removed whitespave from tags 20200229 1835
DiGro commented on pull request #76: URL: https://github.com/apache/openoffice/pull/76#issuecomment-623092077 Yes, but it is not that relevant. When I first started to remove the whitespace, I noticed that the whitespace was caused by extra tabs/spaces before the text. Text should be aligned to the left margin to avoid superfluous whitespace. In the beginning I removed the whitespace and put all text behind each other. That solved the problem of the whitespace. Created however long lines, as you noticed ;- ) Later on I noticed I only had to remove the whitespace before the text so that text was aligned at the left margin and all was OK. I used the last method for the remainder of the texts but yes, there are some long lines. Since they are text that is included into an index for the help, it doesn't seem to cause any problems anymore. Whilst I was working on it, I noticed both long lines as well as short separate lines are used in the original files. __ DiGro Op zondag 3 mei 2020 00:35:15 CEST schreef Peter : Is there a reason why multiple lines have now been addid into a single line? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: macOS and AOO42X
Hi Marcus, Am 29.04.20 um 01:04 schrieb Marcus: > Am 29.04.20 um 00:56 schrieb Matthias Seidel: >> Am 29.04.20 um 00:48 schrieb Marcus: >>> Am 28.04.20 um 23:37 schrieb Matthias Seidel: Am 28.04.20 um 23:33 schrieb Pedro Lino: > Any chance the Dev2 can include certification for Windows OS? No, this costs real money and will only be used for releases. >>> I assume at least the RC will be certified? >>> Yes, it costs money but it needs to be verified at some point >>> before the first official release. >> I doubt it. But you can discuss that with the ASF if you want. > Why should I discuss with ASF? Aren't the members of the AOO PMC > convinced that you should not make experiments with Release > versions? This will be the first AOO version certified. One of the > RCs should be certified to make sure the certification > process/script/steps is correct and that the certificate is > correctly identified at least under Windows 10. If you want that you must discuss that with the ASF if they are willing to pay the costs for "one of the RCs". >>> >>> he is already discussing with ASF. ;-) >> But with the wrong person... > > hm, do you mean the treasurer? Otherwise I don't know who you mean. Exactly. > The release will be signed. Thank you for your understanding! >>> >>> And when it runs into errors, the first question would be: Haven't you >>> tested the signing? The answer would be embarrassing. >>> >>> So, lets try it. >> >> I already tested it, but thank you for volunteering! >> >> I will write you a mail with details. (Until now, I was the only one >> interested in the Windows Code Signing process) > > I have no interest in Windows at all. ;-) That's a real problem. > But OK. I can see what I can do on the weekend. Maybe you could start with updating the download numbers? We have passed the 290 million mark almost 2 weeks ago... Matthias > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
