Re: Open XML Filter

[Peter kovacs]

During Apache POI is a cool idea. I will have a look at the weekend. I am in 
general interested in improving OOXML but I am still very slow in getting 
towards dev productivity. ( today is my certificate exam in ab initio, when I 
pass openoffice can move up my priority list again. YAY!)

Raphael if you are evaluating headless servers, have you tried to set one up ?
Can you do that, and check if the office process crashes at 100% cpu after 
transformation?
Or write a guide how to setup a server?. I did not manage and I would like to 
get a bug report in that area tested.


Am 20. Oktober 2017 04:59:33 MESZ schrieb Dave Fisher :
>Hi Raphael,
>
>Sent from my iPhone
>
>> On Oct 19, 2017, at 7:50 PM, Raphael Bircher
> wrote:
>> 
>> Hi Dave
>> 
>> Am .10.2017, 04:20 Uhr, schrieb Dave Fisher :
>> 
>>> Hi -
>>> 
>>> If we can use Java then Apache POI has OOXML support.
>> 
>> You mean, use POI as a library in Apache OpenOffice?
>
>Yes.
>
>Regards,
>Dave
>
>> 
>> Regards, Raphael
>> 
>> 
>> -- 
>> My introduction https://youtu.be/Ln4vly5sxYU
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Templates/Extensions site expired

[Dave Fisher]

Sent from my iPhone

> On Oct 19, 2017, at 5:58 PM, Dave Brondsema  wrote:
> 
>> On 10/19/17 6:45 PM, Andrea Pescetti wrote:
>> Marcus wrote:
 Am 19.10.2017 um 23:20 schrieb Matthias Seidel:
 Unfortunately just today the SSL certificate expired for:
 https://extensions.openoffice.org/
 and
 https://templates.openoffice.org/
 People will see an error message when trying to search for updates via
 Extension Manager.
>> 
>> Yes, and fortunately this will only apply to Extension Updates but not to the
>> OpenOffice updates, that are served from another domain.
>> 
>>> is this something the Infra team can fix or is it on SF's side?
>> 
>> Infra has a wildcard certificate (if I recall correctly) for 
>> *.openoffice.org,
>> but, and I agree with it, they don't make it available to third parties. So 
>> the
>> two expired certificates are managed by SF and SF should update them.
>> 
> 
> These have been fixed now.

Thank you!

Regards,
Dave

> 
> 
> -- 
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>  <><
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Open XML Filter

[Raphael Bircher]

Hi Dave

Am .10.2017, 04:20 Uhr, schrieb Dave Fisher :


Hi -

If we can use Java then Apache POI has OOXML support.


You mean, use POI as a library in Apache OpenOffice?

Regards, Raphael


--
My introduction https://youtu.be/Ln4vly5sxYU

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Open XML Filter

[Dave Fisher]

Hi -

If we can use Java then Apache POI has OOXML support.

Regards,
Dave

> On Oct 19, 2017, at 7:15 PM, Raphael Bircher  wrote:
> 
> Hi all
> 
> Who is willing to work on the Open XML Filters? I have to explain you, why 
> I'm asking.
> 
> In the past few month, I worked on a new project witch resulted in a NGO 
> located in Switzerland called Vefko. The goal is, to offer other Association 
> communication and collaboration tools.
> 
> We are now at the software evaluation, and Apache Openoffice is on the list. 
> At the Moment it's mainly interesting in the headless mode. But the poor 
> OOXML Filter it's something negative at AOO. I know, that this topic came op 
> frequently. But I also know, that this is not an easy task.
> 
> So the big question, who is interested in something like this.
> 
> Regards, Raphael
> 
> --
> My introduction https://youtu.be/Ln4vly5sxYU
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Templates/Extensions site expired

[Dave Brondsema]

On 10/19/17 6:45 PM, Andrea Pescetti wrote:
> Marcus wrote:
>> Am 19.10.2017 um 23:20 schrieb Matthias Seidel:
>>> Unfortunately just today the SSL certificate expired for:
>>> https://extensions.openoffice.org/
>>> and
>>> https://templates.openoffice.org/
>>> People will see an error message when trying to search for updates via
>>> Extension Manager.
> 
> Yes, and fortunately this will only apply to Extension Updates but not to the
> OpenOffice updates, that are served from another domain.
> 
>> is this something the Infra team can fix or is it on SF's side?
> 
> Infra has a wildcard certificate (if I recall correctly) for *.openoffice.org,
> but, and I agree with it, they don't make it available to third parties. So 
> the
> two expired certificates are managed by SF and SF should update them.
> 

These have been fixed now.


-- 
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
  <><

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Building Guides

[Gavin McDonald]

> On 20 Oct 2017, at 9:40 am, Andrea Pescetti  wrote:
> 
> 


> There are no build instructions on the CWiki and there shouldn't be a copy 
> there.

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
 


Gav…
> 

Re: Templates/Extensions site expired

[Andrea Pescetti]

Marcus wrote:

Am 19.10.2017 um 23:20 schrieb Matthias Seidel:

Unfortunately just today the SSL certificate expired for:
https://extensions.openoffice.org/
and
https://templates.openoffice.org/
People will see an error message when trying to search for updates via
Extension Manager.


Yes, and fortunately this will only apply to Extension Updates but not 
to the OpenOffice updates, that are served from another domain.



is this something the Infra team can fix or is it on SF's side?


Infra has a wildcard certificate (if I recall correctly) for 
*.openoffice.org, but, and I agree with it, they don't make it available 
to third parties. So the two expired certificates are managed by SF and 
SF should update them.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Building Guides

[Andrea Pescetti]

On 19/10/2017 Keith N. McKenna wrote:

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step

To the best of my knowledge the step by step link that I gave you is the
latest revisions.


This is correct. The Building Giude and its specialized versions are 
actively maintained on the wiki (MWiki). Tools are in the devtools area 
of our SVN repository. There are no build instructions on the CWiki and 
there shouldn't be a copy there.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Templates/Extensions site expired

[Marcus]

Am 19.10.2017 um 23:20 schrieb Matthias Seidel:

Unfortunately just today the SSL certificate expired for:

https://extensions.openoffice.org/

and

https://templates.openoffice.org/

People will see an error message when trying to search for updates via
Extension Manager.


is this something the Infra team can fix or is it on SF's side?

Thanks

Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Templates/Extensions site expired

[Matthias Seidel]

Hello,

Unfortunately just today the SSL certificate expired for:

https://extensions.openoffice.org/

and

https://templates.openoffice.org/

People will see an error message when trying to search for updates via
Extension Manager.

This is NOT a problem with our latest release! ;-)

Kind regards, Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Building Guides

[Jim Jagielski]

Plus, I used the CentOS step-by-step as well...

> On Oct 19, 2017, at 3:04 PM, Jim Jagielski  wrote:
> 
> I am the one who edited the Mac guide. The actual scripts are in the devtools 
> repo.
> 
>> On Oct 19, 2017, at 2:49 PM, Dave Fisher  wrote:
>> 
>> Hi Keith,
>> 
>> I believe that these guides are old and particularly that the Mac Guide is 
>> in the Confluence Wiki. I would like Matthias and Jim to indicate where 
>> their build instructions are located. Once we have that then we can update.
>> 
>> Regards,
>> Dave
>> 
>>> On Oct 19, 2017, at 11:37 AM, Keith N. McKenna  
>>> wrote:
>>> 
>>> On 10/19/2017 2:12 PM, Dave Fisher wrote:
 Hi -
 
 From the download page there is a link to Building Guides:
 
 This goes
 to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
 
 I don’t think that this leads to the most up to date information. Where
 is the most up to date information?
 
 Regards,
 Dave
>>> Dave;
>>> 
>>> At the bottom of that page there is a link to the step by step guides at
>>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>>> 
>>> Regards
>>> Keith
>>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Building Guides

[Keith N. McKenna]

On 10/19/2017 2:49 PM, Dave Fisher wrote:
> Hi Keith,
> 
> I believe that these guides are old and particularly that the Mac Guide is in 
> the Confluence Wiki. I would like Matthias and Jim to indicate where their 
> build instructions are located. Once we have that then we can update.
> 
> Regards,
> Dave
> 
>> On Oct 19, 2017, at 11:37 AM, Keith N. McKenna  
>> wrote:
>>
>> On 10/19/2017 2:12 PM, Dave Fisher wrote:
>>> Hi -
>>>
>>> From the download page there is a link to Building Guides:
>>>
>>> This goes
>>> to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>>>
>>> I don’t think that this leads to the most up to date information. Where
>>> is the most up to date information?
>>>
>>> Regards,
>>> Dave
>> Dave;
>>
>> At the bottom of that page there is a link to the step by step guides at
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>>
>> Regards
>> Keith
>>
> 
Dave;

To the best of my knowledge the step by step link that I gave you is the
latest revisions. Though as I do not build I could easily be wrong. As
memory serves me at least the Windows step by step is the one frequently
given to new Windows contributors.

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: Building Guides

[Jim Jagielski]

I am the one who edited the Mac guide. The actual scripts are in the devtools 
repo.

> On Oct 19, 2017, at 2:49 PM, Dave Fisher  wrote:
> 
> Hi Keith,
> 
> I believe that these guides are old and particularly that the Mac Guide is in 
> the Confluence Wiki. I would like Matthias and Jim to indicate where their 
> build instructions are located. Once we have that then we can update.
> 
> Regards,
> Dave
> 
>> On Oct 19, 2017, at 11:37 AM, Keith N. McKenna  
>> wrote:
>> 
>> On 10/19/2017 2:12 PM, Dave Fisher wrote:
>>> Hi -
>>> 
>>> From the download page there is a link to Building Guides:
>>> 
>>> This goes
>>> to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>>> 
>>> I don’t think that this leads to the most up to date information. Where
>>> is the most up to date information?
>>> 
>>> Regards,
>>> Dave
>> Dave;
>> 
>> At the bottom of that page there is a link to the step by step guides at
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>> 
>> Regards
>> Keith
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Building Guides

[Matthias Seidel]

Am 19.10.2017 um 20:49 schrieb Dave Fisher:
> Hi Keith,
>
> I believe that these guides are old and particularly that the Mac Guide is in 
> the Confluence Wiki. I would like Matthias and Jim to indicate where their 
> build instructions are located. Once we have that then we can update.

I can't speak for Mac/Linux, but I could do my Windows builds following
the Wiki pages.
Only missing is a section for building the Language Packs and the SDK. I
didn't have the time to add it, yet.

Build scripts are here:
http://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.4/

(Although I don't provide a script for Windows, but I documented as much
as I could)

Matthias

>
> Regards,
> Dave
>
>> On Oct 19, 2017, at 11:37 AM, Keith N. McKenna  
>> wrote:
>>
>> On 10/19/2017 2:12 PM, Dave Fisher wrote:
>>> Hi -
>>>
>>> From the download page there is a link to Building Guides:
>>>
>>> This goes
>>> to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>>>
>>> I don’t think that this leads to the most up to date information. Where
>>> is the most up to date information?
>>>
>>> Regards,
>>> Dave
>> Dave;
>>
>> At the bottom of that page there is a link to the step by step guides at
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>>
>> Regards
>> Keith
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Building Guides

[Dave Fisher]

Hi Keith,

I believe that these guides are old and particularly that the Mac Guide is in 
the Confluence Wiki. I would like Matthias and Jim to indicate where their 
build instructions are located. Once we have that then we can update.

Regards,
Dave

> On Oct 19, 2017, at 11:37 AM, Keith N. McKenna  
> wrote:
> 
> On 10/19/2017 2:12 PM, Dave Fisher wrote:
>> Hi -
>> 
>> From the download page there is a link to Building Guides:
>> 
>> This goes
>> to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>> 
>> I don’t think that this leads to the most up to date information. Where
>> is the most up to date information?
>> 
>> Regards,
>> Dave
> Dave;
> 
> At the bottom of that page there is a link to the step by step guides at
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
> 
> Regards
> Keith
> 



signature.asc
Description: Message signed with OpenPGP

Re: Building Guides

[Keith N. McKenna]

On 10/19/2017 2:12 PM, Dave Fisher wrote:
> Hi -
> 
> From the download page there is a link to Building Guides:
> 
> This goes
> to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
> 
> I don’t think that this leads to the most up to date information. Where
> is the most up to date information?
> 
> Regards,
> Dave
Dave;

At the bottom of that page there is a link to the step by step guides at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: Download Pages for 4.1.4?

[Matthias Seidel]

Am 19.10.2017 um 20:16 schrieb FR web forum:
>> The main download page, as well as German and Netherlands are updated...
>> But we still have a bunch of pages to do.
> Take care of the FR pages for me

I will try. ;-)

>
>
> -
> 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: Download Pages for 4.1.4?

[FR web forum]

> The main download page, as well as German and Netherlands are updated...
> But we still have a bunch of pages to do.

Take care of the FR pages for me


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Download Pages for 4.1.4?

[Andrea Pescetti]

Matthias Seidel wrote:

The main download page, as well as German and Netherlands are updated...
But we still have a bunch of pages to do.


I'll take care of the Italian pages and I'll also put online the 
translations I received from our volunteers.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Building Guides

[Dave Fisher]

Hi -

From the download page there is a link to Building Guides:

This goes to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO 


I don’t think that this leads to the most up to date information. Where is the 
most up to date information?

Regards,
Dave


signature.asc
Description: Message signed with OpenPGP

Re: Download Pages for 4.1.4?

[Dave Fisher]

Hi -

OK. We should be able to fix these js filenames so that users don’t have to 
clear cache. by versioning the following files:






> Did we miss a clause here for mac32?
In download.js:
// If version is '4.1.0' (or newer) and platform is 'Mac OS X <= 10.6', 
show the none-availability to the user.
if( ( DL.VERSION_SEL === "4.1.3" || DL.VERSION_SEL === "4.1.2" || 
DL.VERSION_SEL === "4.1.1" || DL.VERSION_SEL === "4.1.0" ) && DL.PLATFORM === 
"mac32" ) {
// Show an error message that the chosen items do not lead to a 
download.

Should we use DL.VERSION_SEL >= “4.1.0”? If so then we won’t need to version 
download.js.

In globalvars.js:

// Stable release: General properties.
DL.VERSION  = "4.1.4";  // Release version in 
full format "x.y.z".
DL.VERSION_SHORT= DL.VERSION;   // Release version in 
short format "x.y".
DL.MILESTONE= "AOO414m5";   // Milestone ID (from 
AOO build system).
DL.BUILD= "9788";   // Build ID (from AOO 
build system).
DL.SVN_REV  = "r1811857";   // SVN revision.
DL.REL_DATE = "2017-Oct-19";// Date of the public 
announced release.
DL.PREV_VERSION = "4.1.3";  // Release of the 
previous version.
DL.OLDVERSION   = "3.4.1";  // Old version (last 
stable release of 3.x series).
DL.LEGACYVERSION= "3.3.0";  // Old legacy version 
(last stable none-Apache release).

In msg_prop_l10n_en.js:

l10n.dl_rel_notes_aoo414_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.4+Release+Notes;;
l10n.dl_rel_notes_aoo413_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes;;
l10n.dl_rel_notes_aoo412_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes;;
l10n.dl_rel_notes_aoo411_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.1+Release+Notes;;
l10n.dl_rel_notes_aoo410_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes;;
l10n.dl_rel_notes_aoo401_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0.1+Release+Notes;;
l10n.dl_rel_notes_aoo400_link = 
"https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Notes;;

In release_matrix.js:
/* Description for AOO 4.1.4.
 *
 * For the matrix position and their meanings see the descriptions on top of 
file.
 */
DL.release_matrix_414 = {
….

Regards,
Dave

> On Oct 19, 2017, at 10:36 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> I’m seeing that the banner on www.openoffice.org  
> has the 4.1.4 release announced on the release, but the download pages are 
> yet to be changed.
> 
> Is the change in progress?
> 
> Regards,
> Dave



signature.asc
Description: Message signed with OpenPGP

Re: Download Pages for 4.1.4?

[Matthias Seidel]

Hi Dave,

Did you clear your cache? ;-)

The main download page, as well as German and Netherlands are updated...
But we still have a bunch of pages to do.

Matthias


Am 19.10.2017 um 19:36 schrieb Dave Fisher:
> Hi -
>
> I’m seeing that the banner on www.openoffice.org
>  has the 4.1.4 release announced on the
> release, but the download pages are yet to be changed.
>
> Is the change in progress?
>
> Regards,
> Dave



smime.p7s
Description: S/MIME Cryptographic Signature

Download Pages for 4.1.4?

[Dave Fisher]

Hi -

I’m seeing that the banner on www.openoffice.org  
has the 4.1.4 release announced on the release, but the download pages are yet 
to be changed.

Is the change in progress?

Regards,
Dave


signature.asc
Description: Message signed with OpenPGP

Re: Where is http://www.openoffice.org/de/dev/pre_submission_de.html ?

[Matthias Seidel]

Am 19.10.2017 um 19:09 schrieb Jörg Schmidt:
>> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] 
>> Sent: Thursday, October 19, 2017 6:32 PM
>> To: dev@openoffice.apache.org
>> Subject: Re: Where is 
>> http://www.openoffice.org/de/dev/pre_submission_de.html ?
>>
>> I can copy it back for you.
>>
>> But this (and other) page(s) are slightly outdated and have 
>> to be reviewed.
> Then please tell me how this has to be done formally. 
>
> The site is currently [1] linked on other pages, and I did so only after I 
> personally checked the page. 
> (In my opinion, the site is not perfect, but important for information and 
> better than nothing, as long as we don't have anything better.)
>
> As soon as I know how the reviewing has to be done, I will gladly do so as 
> far as my time allows.

The page is now online...

I found several problems, but together we can surely update the page to
be functional again.

Matthias

>
>
> [1]
> in this case "currently" means one, not exactly defined, point in time after 
> the end of the Icubator period of the OO project.
>
>
>
> greetings,
> Jörg
>
>
> -
> 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: Where is http://www.openoffice.org/de/dev/pre_submission_de.html ?

[Jörg Schmidt]

> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] 
> Sent: Thursday, October 19, 2017 6:32 PM
> To: dev@openoffice.apache.org
> Subject: Re: Where is 
> http://www.openoffice.org/de/dev/pre_submission_de.html ?
> 
> I can copy it back for you.
> 
> But this (and other) page(s) are slightly outdated and have 
> to be reviewed.

Then please tell me how this has to be done formally. 

The site is currently [1] linked on other pages, and I did so only after I 
personally checked the page. 
(In my opinion, the site is not perfect, but important for information and 
better than nothing, as long as we don't have anything better.)

As soon as I know how the reviewing has to be done, I will gladly do so as far 
as my time allows.


[1]
in this case "currently" means one, not exactly defined, point in time after 
the end of the Icubator period of the OO project.



greetings,
Jörg


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Where is http://www.openoffice.org/de/dev/pre_submission_de.html ?

[Matthias Seidel]

I can copy it back for you.

But this (and other) page(s) are slightly outdated and have to be reviewed.

Give me 10 minutes... ;-)

Matthias


Am 19.10.2017 um 18:27 schrieb Jörg Schmidt:
> Hello,
>
> The website http://www.openoffice.org/de/dev/pre_submission_de.html returns a 
> 404 error.
>
> How do I get the page displayed again or where in the CMS do I have to change 
> something?
>
>
>
> greetings,
> Jörg
>
>
> -
> 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

Where is http://www.openoffice.org/de/dev/pre_submission_de.html ?

[Jörg Schmidt]

Hello,

The website http://www.openoffice.org/de/dev/pre_submission_de.html returns a 
404 error.

How do I get the page displayed again or where in the CMS do I have to change 
something?



greetings,
Jörg


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Bugreport

[Jörg Schmidt]

Hallo, 

> From: Werkphoto Stefan Schick [mailto:sch...@werkphoto.de] 

> ich arbeite auf einem iMac (5k 27“, Ende 2015), MacOS 10.11.6 
> mit OpenOffice 4.1.3
> 
> Diese Information beziehen sich auf OpenOffice  Calc
> 
> 1. Seit der Installation der aktuellen Version funktioniert 
> die Copy/Paste Funktion zwischen Apple Mail und OpenOfiice 
> Calc nicht mehr. Beispiel: ich erhalte viele technische 
> Informationen oder Bühnenbauanweisungen von Künstlern via 
> Email. Deren Angaben und Informationen muss ich in einen 
> Dienst- & Infoplan für unsere Theatermitarbeiter einkopieren 
> und verwende hierfür OpenOfiice Calc. Die einzige Möglichkeit 
> Copy/Paste noch zu verwenden ist über den Umweg, Kopiertes in 
> das Apple Programms „Textedit“ einzufügen (es quasi als 
> Zwischenspeicher zu nutzen), es dort erneut zu kopieren und 
> in die OpenOffice Calc-Tabelle einzufügen. In der früheren 
> Version war das normal möglich.
> 
> 2. regelmäßiger Programmabsturz beim Exportieren (Menüpunkt 
> „Datei, exportieren als PDF“) von Tabellen als PDF, wenn 
> nicht alle Seiten exportiert werden, sollen sondern nur eine Auswahl.

Das liegt mutmaßlich an einem defekten OO-Benutzerverzeichnis.

Ich würde OO beenden, das bestehende OO-Benutzerverzeichnis um benennen und OO 
neustarten, siehe:
http://de.openoffice.info/viewtopic.php?f=27=54231#p206070

> 3. bei einem installiertem DIN A4 Drucker wie z.B. dem HP 
> Laserjet Pro M252dw wird ein Seitenlayout im DIN A3 
> Querformat Format nicht vollständig als PDF gesichert, obwohl 
> der Drucker ja tatsächlich nicht benutzt wird. Das PDF zeigt 
> nur einen Teilausschnitt im DIN A4-Querformat und der Rest 
> wird einfach abgeschnitten.

dazu kann _ich_ leider nichts sagen 

> 4. Drucken bzw. PDF-Export via Mac Funktion „Drucken - als 
> PDF sichern“ von Tabellen im DIN A3-Querformat: s.o. 3). 
> Außerdem müsste dringend die Seitenansicht von Tabellen im 
> Menü „Datei" überarbeitet werden. Dort ist ein Setzen von 
> manuellen Seitenumbrüchen notwendig und nicht im Menü 
> „Ansicht“ „Seitenumbruch-Vorschau“. Man muss ständig bei 
> jeder kleinen Änderung zwischen diesen beiden Menü-Modi hin- 
> und herschalten. Wenn man im Menü „Ansicht“ 
> „Seitenumbruch-Vorschau“einen Seitenumbruch manuell so 
> verändert hat, wie man es gerne haben will, springt die 
> „Seitenansicht" im „Datei"-Menü immer wieder auf einen 
> kleineren Druckbereich zurück, als den, den man vorher mt den 
> Regler „Ränder" so eingestellt hat, dass das volle, gesamte 
> A3-Papierformat auch ausgenutzt wird.

Um das Papierformat auszunutzen steht unter Format-Seite im erscheinenden 
Dialog Register "Tabelle" der Skalierungsmodus zur Verfügung.


Gruß
Jörg




-
To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-de-h...@openoffice.apache.org

Re: [VOTE][RESULT] Release Apache OpenOffice 4.1.4-RC5 as GA

[Peter kovacs]

Ahh cool, thx. :)

Am 19. Oktober 2017 13:03:04 MESZ schrieb Patricia Shanahan :
>In general, we are documenting our release process in 
>https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release.
>
>We have a problem that the ASF itself documents the rules for voting on
>
>releases in two places: 
>http://www.apache.org/legal/release-policy.html#release-approval and 
>https://www.apache.org/foundation/voting.html
>
>Those rules do not quite work for us. In practice, we treat a justified
>
>-1 from any community member as a veto. We put much more emphasis on 
>testing binaries than on building from source. I suppose in theory when
>
>we see a justified -1 all PMC members should change their votes to -1, 
>and change them back to +1 if and when the problem is resolved.
>
>On 10/19/2017 12:06 AM, Peter kovacs wrote:
>> Have we documented our process somewhere. I am unsure. I think we
>have at least discussed this already.
>> All arguments sound so familiar.
>> 
>> Am 19. Oktober 2017 02:35:29 MESZ schrieb Dave Fisher
>:
>>>
 On Oct 18, 2017, at 4:45 PM, Pedro Lino 
>>> wrote:



> Maybe we need to ask for review of
>>> http://www.apache.org/legal/release-policy.html#release-approval at
>the
>>> same time as looking at the voting process documentation. If taken
>>> literally, a PMC member who cannot do builds from source can't cast
>a
>>> +1 vote, because their vote is binding and a binding +1 requires a
>>> build from source.

 Probably the ASF wants to guarantee that at least 3 PMC members are
>>> developers (or development inclined)?
>>>
>>> It’s not probably. It *IS*!
>>>

> What I would like is to change it to require at least three PMC
>>> members to declare they have done a build from source and tested the
>>> result. Other PMC members could vote based on binary testing and
>>> signature checking without building.

 Actually for a multi-platform software such as AOO it should be
>>> required that building from source and testing the result was
>carried
>>> out by at least one voter (PMC member or not) for each of the
>>> platforms/bit depths.
 If all three PMC members have success in building on e.g. Linux x64
>>> it does not provide any guarantee for the other platforms (as proven
>by
>>> 4.1.4 RC4)
>>>
>>> We had two PMC providing the community builds. The official release
>is
>>> the Source release. We need as much testing as possible of the
>>> community releases. AOO is a unique project for Apache because our
>>> users count on the community builds and not the source releases.
>>>
>>> I think we have grown in the last year because in the first years
>here
>>> at Apache most of the knowledge on how to build was in the minds of
>the
>>> former Hamburg team - Star, Sun, Oracle and then IBM employees.
>>>
>>> Special thanks to Matthias and Jim how providing the Community
>Builds.
>>>
>>> Regards,
>>> Dave
>>>


>-
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org

>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [VOTE][RESULT] Release Apache OpenOffice 4.1.4-RC5 as GA

[Peter kovacs]

I would like to go a step further and go for auto builds with no manual 
involvement.
For this we must be able to produce same binaries independent from the build 
machine so we can verify the build by beeing able to create a reference build. 
In order to ensure that what we build is the result from the source code we use.

And there we will have to look that we get 3 reference builders that verify our 
binary.

Am 19. Oktober 2017 13:32:28 MESZ schrieb Patricia Shanahan :
>On 10/18/2017 5:35 PM, Dave Fisher wrote:
>> 
>>> On Oct 18, 2017, at 4:45 PM, Pedro Lino 
>wrote:
>>>
>>>
>>>
 Maybe we need to ask for review of
>http://www.apache.org/legal/release-policy.html#release-approval at the
>same time as looking at the voting process documentation. If taken
>literally, a PMC member who cannot do builds from source can't cast a
>+1 vote, because their vote is binding and a binding +1 requires a
>build from source.
>>>
>>> Probably the ASF wants to guarantee that at least 3 PMC members are
>developers (or development inclined)?
>> 
>> It’s not probably. It *IS*!
>
>If that is the purpose, it is not a very efficient way of achieving it.
>It would take less of my time, for example, to attach an abbreviated CV
>that I could write once and use for each vote, perhaps just a list of
>degrees, patents, and former employers.
>
>> 
>>>
 What I would like is to change it to require at least three PMC
>members to declare they have done a build from source and tested the
>result. Other PMC members could vote based on binary testing and
>signature checking without building.
>>>
>>> Actually for a multi-platform software such as AOO it should be
>required that building from source and testing the result was carried
>out by at least one voter (PMC member or not) for each of the
>platforms/bit depths.
>>> If all three PMC members have success in building on e.g. Linux x64
>it does not provide any guarantee for the other platforms (as proven by
>4.1.4 RC4)
>> 
>> We had two PMC providing the community builds. The official release
>is the Source release. We need as much testing as possible of the
>community releases. AOO is a unique project for Apache because our
>users count on the community builds and not the source releases.
>> 
>> I think we have grown in the last year because in the first years
>here at Apache most of the knowledge on how to build was in the minds
>of the former Hamburg team - Star, Sun, Oracle and then IBM employees.
>> 
>> Special thanks to Matthias and Jim how providing the Community
>Builds.
>
>I really get convinced that the source code is good for building
>purposes by seeing people I trust upload binaries for each
>combination of language and supported platform. I then download a few
>of
>the binaries and test them.
>
>During the vote period I do a ritual build of one combination on my own
>hardware, and test the resulting binary, just to satisfy the ASF rules.
>I would rather spend more time testing binaries that people are going
>to
>use rather than testing a binary I'm going to throw away.
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Bugreport

[Werkphoto Stefan Schick]

Hallo

ich arbeite auf einem iMac (5k 27“, Ende 2015), MacOS 10.11.6 mit OpenOffice 
4.1.3

Diese Information beziehen sich auf OpenOffice  Calc

1. Seit der Installation der aktuellen Version funktioniert die Copy/Paste 
Funktion zwischen Apple Mail und OpenOfiice Calc nicht mehr. Beispiel: ich 
erhalte viele technische Informationen oder Bühnenbauanweisungen von Künstlern 
via Email. Deren Angaben und Informationen muss ich in einen Dienst- & Infoplan 
für unsere Theatermitarbeiter einkopieren und verwende hierfür OpenOfiice Calc. 
Die einzige Möglichkeit Copy/Paste noch zu verwenden ist über den Umweg, 
Kopiertes in das Apple Programms „Textedit“ einzufügen (es quasi als 
Zwischenspeicher zu nutzen), es dort erneut zu kopieren und in die OpenOffice 
Calc-Tabelle einzufügen. In der früheren Version war das normal möglich.

2. regelmäßiger Programmabsturz beim Exportieren (Menüpunkt „Datei, exportieren 
als PDF“) von Tabellen als PDF, wenn nicht alle Seiten exportiert werden, 
sollen sondern nur eine Auswahl.

3. bei einem installiertem DIN A4 Drucker wie z.B. dem HP Laserjet Pro M252dw 
wird ein Seitenlayout im DIN A3 Querformat Format nicht vollständig als PDF 
gesichert, obwohl der Drucker ja tatsächlich nicht benutzt wird. Das PDF zeigt 
nur einen Teilausschnitt im DIN A4-Querformat und der Rest wird einfach 
abgeschnitten. 

4. Drucken bzw. PDF-Export via Mac Funktion „Drucken - als PDF sichern“ von 
Tabellen im DIN A3-Querformat: s.o. 3). Außerdem müsste dringend die 
Seitenansicht von Tabellen im Menü „Datei" überarbeitet werden. Dort ist ein 
Setzen von manuellen Seitenumbrüchen notwendig und nicht im Menü „Ansicht“ 
„Seitenumbruch-Vorschau“. Man muss ständig bei jeder kleinen Änderung zwischen 
diesen beiden Menü-Modi hin- und herschalten. Wenn man im Menü „Ansicht“ 
„Seitenumbruch-Vorschau“einen Seitenumbruch manuell so verändert hat, wie man 
es gerne haben will, springt die „Seitenansicht" im „Datei"-Menü immer wieder 
auf einen kleineren Druckbereich zurück, als den, den man vorher mt den Regler 
„Ränder" so eingestellt hat, dass das volle, gesamte A3-Papierformat auch 
ausgenutzt wird.

Mut freundlichen Grüßen

Stefan Schick
Herrnhof 8
16269 Bliesdorf

Re: [VOTE][RESULT] Release Apache OpenOffice 4.1.4-RC5 as GA

[Patricia Shanahan]

On 10/18/2017 5:35 PM, Dave Fisher wrote:



On Oct 18, 2017, at 4:45 PM, Pedro Lino  wrote:




Maybe we need to ask for review of 
http://www.apache.org/legal/release-policy.html#release-approval at the same 
time as looking at the voting process documentation. If taken literally, a PMC 
member who cannot do builds from source can't cast a +1 vote, because their 
vote is binding and a binding +1 requires a build from source.


Probably the ASF wants to guarantee that at least 3 PMC members are developers 
(or development inclined)?


It’s not probably. It *IS*!


If that is the purpose, it is not a very efficient way of achieving it.
It would take less of my time, for example, to attach an abbreviated CV
that I could write once and use for each vote, perhaps just a list of
degrees, patents, and former employers.






What I would like is to change it to require at least three PMC members to 
declare they have done a build from source and tested the result. Other PMC 
members could vote based on binary testing and signature checking without 
building.


Actually for a multi-platform software such as AOO it should be required that 
building from source and testing the result was carried out by at least one 
voter (PMC member or not) for each of the platforms/bit depths.
If all three PMC members have success in building on e.g. Linux x64 it does not 
provide any guarantee for the other platforms (as proven by 4.1.4 RC4)


We had two PMC providing the community builds. The official release is the 
Source release. We need as much testing as possible of the community releases. 
AOO is a unique project for Apache because our users count on the community 
builds and not the source releases.

I think we have grown in the last year because in the first years here at 
Apache most of the knowledge on how to build was in the minds of the former 
Hamburg team - Star, Sun, Oracle and then IBM employees.

Special thanks to Matthias and Jim how providing the Community Builds.


I really get convinced that the source code is good for building
purposes by seeing people I trust upload binaries for each
combination of language and supported platform. I then download a few of
the binaries and test them.

During the vote period I do a ritual build of one combination on my own
hardware, and test the resulting binary, just to satisfy the ASF rules.
I would rather spend more time testing binaries that people are going to
use rather than testing a binary I'm going to throw away.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [VOTE][RESULT] Release Apache OpenOffice 4.1.4-RC5 as GA

[Patricia Shanahan]

In general, we are documenting our release process in 
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release.


We have a problem that the ASF itself documents the rules for voting on 
releases in two places: 
http://www.apache.org/legal/release-policy.html#release-approval and 
https://www.apache.org/foundation/voting.html


Those rules do not quite work for us. In practice, we treat a justified 
-1 from any community member as a veto. We put much more emphasis on 
testing binaries than on building from source. I suppose in theory when 
we see a justified -1 all PMC members should change their votes to -1, 
and change them back to +1 if and when the problem is resolved.


On 10/19/2017 12:06 AM, Peter kovacs wrote:

Have we documented our process somewhere. I am unsure. I think we have at least 
discussed this already.
All arguments sound so familiar.

Am 19. Oktober 2017 02:35:29 MESZ schrieb Dave Fisher :



On Oct 18, 2017, at 4:45 PM, Pedro Lino 

wrote:





Maybe we need to ask for review of

http://www.apache.org/legal/release-policy.html#release-approval at the
same time as looking at the voting process documentation. If taken
literally, a PMC member who cannot do builds from source can't cast a
+1 vote, because their vote is binding and a binding +1 requires a
build from source.


Probably the ASF wants to guarantee that at least 3 PMC members are

developers (or development inclined)?

It’s not probably. It *IS*!




What I would like is to change it to require at least three PMC

members to declare they have done a build from source and tested the
result. Other PMC members could vote based on binary testing and
signature checking without building.


Actually for a multi-platform software such as AOO it should be

required that building from source and testing the result was carried
out by at least one voter (PMC member or not) for each of the
platforms/bit depths.

If all three PMC members have success in building on e.g. Linux x64

it does not provide any guarantee for the other platforms (as proven by
4.1.4 RC4)

We had two PMC providing the community builds. The official release is
the Source release. We need as much testing as possible of the
community releases. AOO is a unique project for Apache because our
users count on the community builds and not the source releases.

I think we have grown in the last year because in the first years here
at Apache most of the knowledge on how to build was in the minds of the
former Hamburg team - Star, Sun, Oracle and then IBM employees.

Special thanks to Matthias and Jim how providing the Community Builds.

Regards,
Dave



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [VOTE][RESULT] Release Apache OpenOffice 4.1.4-RC5 as GA

[Peter kovacs]

Have we documented our process somewhere. I am unsure. I think we have at least 
discussed this already.
All arguments sound so familiar.

Am 19. Oktober 2017 02:35:29 MESZ schrieb Dave Fisher :
>
>> On Oct 18, 2017, at 4:45 PM, Pedro Lino 
>wrote:
>> 
>> 
>> 
>>> Maybe we need to ask for review of
>http://www.apache.org/legal/release-policy.html#release-approval at the
>same time as looking at the voting process documentation. If taken
>literally, a PMC member who cannot do builds from source can't cast a
>+1 vote, because their vote is binding and a binding +1 requires a
>build from source.
>> 
>> Probably the ASF wants to guarantee that at least 3 PMC members are
>developers (or development inclined)?
>
>It’s not probably. It *IS*!
>
>> 
>>> What I would like is to change it to require at least three PMC
>members to declare they have done a build from source and tested the
>result. Other PMC members could vote based on binary testing and
>signature checking without building.
>> 
>> Actually for a multi-platform software such as AOO it should be
>required that building from source and testing the result was carried
>out by at least one voter (PMC member or not) for each of the
>platforms/bit depths.
>> If all three PMC members have success in building on e.g. Linux x64
>it does not provide any guarantee for the other platforms (as proven by
>4.1.4 RC4)
>
>We had two PMC providing the community builds. The official release is
>the Source release. We need as much testing as possible of the
>community releases. AOO is a unique project for Apache because our
>users count on the community builds and not the source releases.
>
>I think we have grown in the last year because in the first years here
>at Apache most of the knowledge on how to build was in the minds of the
>former Hamburg team - Star, Sun, Oracle and then IBM employees.
>
>Special thanks to Matthias and Jim how providing the Community Builds.
>
>Regards,
>Dave
>
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org