Re: FOSDEM

[Dr. Michael Stehmann]

Am 29.01.19 um 01:22 schrieb Peter Kovacs:
> Hello,
> 

> Instead I try to come to Chemnitz. I hope my life is quieter by then.
> 
We have a quota for four booth attendees there, now we are only three.
So please annonce your coming early enough to get you on the list.

The catering for participants of CLT is legendary ;-) .

Regards
Michael



signature.asc
Description: OpenPGP digital signature

AOO 4.2 and OpenSymbol font

[FR web forum]

Hello list,
It seems that Open Symbol font is not up to date.
Read: https://bz.apache.org/ooo/show_bug.cgi?id=127110
martin_g provide a patched font in this thread:
https://forum.openoffice.org/en/forum/viewtopic.php?f=12&t=67772&p=360368#p360385
Is it possible to embed this for next build?

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

Re: Time for our first 4.2.0 beta?

[Pedro Lino]

Hi Jim, all


> I think we are at a stage where we should consider doing our
> 1st beta release of 4.2.0... we have successful builds for macOS,
> Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch,
> and enough changes to warrant a beta release for testing and
> feedback (all IMO ;) ).
> 
Is this going to be an English only Beta test? Only English and a couple more
languages (de, nl, ...) have a complete 4.2.0 translation


> Any comments or other thoughts?
> 
Shouldn't AOO be concerned that previous users are not notified of new releases
(or extension updates)? The update notification mechanism has been broken for 
months. This means that  users
currently on any previous build weren't even notified that 4.1.6 was released 2 
months ago...

I realize that the update notification is working on 4.2.0 but how are users 
going to be notified to update to 4.2.0?

Regards,
Pedro

Problem beim Download

[d . burger]

Ich wollte OpenOffice downloaden aber die Seite:
"https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.6/binaries/de/Apache_OpenOffice_4.1.6_Win_x86_install_de.exe/download";
wurde nicht geöffnet.

Die Fehlermeldung ist:
"Die Website ist nicht erreichbar
Die Server-IP-Adresse von sourceforge.net wurde nicht gefunden.
Versuchen Sie, die Windows-Netzwerkdiagnose auszuführen.
DNS_PROBE_FINISHED_NXDOMAIN"

Ich verwende den Browser Opera. mit Win7

(Was funktioniert nicht? Was wird erwartet?)
Browser Variablen   Werte
navigator.appCodeName   Mozilla
navigator.appName   Netscape
navigator.appVersion	5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, 
like Gecko) Chrome/71.0.3578.98 Safari/537.36 OPR/58.0.3135.47

navigator.platform  Win32
navigator.oscpu undefined
navigator.cpuClass  undefined
navigator.product   Gecko
navigator.productSub20030107
navigator.vendorGoogle Inc.
navigator.vendorSub
navigator.language  de-DE
navigator.browserLanguage   undefined
navigator.userLanguage  undefined
navigator.systemLanguageundefined
navigator.userAgent	Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 OPR/58.0.3135.47

Debian / Ubuntu / IceWeasel ?   Nein / Nein / Nein
Stabiles Release
JavaScript Funktionen/Variablen Werte
Language ISO code   de
Language ISO code (from select box) de
Release matrix platform position (full) 11
Release matrix platform position (lp)   12
Release matrix platform array data  y,157
Release matrix language array 
data	de,German,Deutsch,y,de/downloads/index.html

UI platform nameWindows (EXE)
UI platform name (not supported)
Platform (short)win32
URL platform name (full)Win_x86_install
URL platform name (lp)  Win_x86_langpack
URL platform name (from select box) win32
Version (from select box)   4.1.6
File name (full)Apache_OpenOffice_4.1.6_Win_x86_install_de.exe
File name (lp)  Apache_OpenOffice_4.1.6_Win_x86_langpack_de.exe
File extension  .exe
File size (full) (MByte)157
File size (lp) (MByte)  19
Release info	Milestone AOO416m1 | Build ID 9790 | SVN r1844436 | 
Veröffentlicht 2018-11-18
Download file link 
(full)	https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.6/binaries/de/Apache_OpenOffice_4.1.6_Win_x86_install_de.exe/download
Download file link 
(lp)	https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.6/binaries/de/Apache_OpenOffice_4.1.6_Win_x86_langpack_de.exe/download

Checksum file link (full) (here for MD5)
Checksum file link (lp) (here for MD5)
Base URL to 
Sourceforge.net	https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.6/binaries/
Base URL to Apache 
Archive	https://archive.apache.org/dist/openoffice/4.1.6

getLinkSelection() (download URL)   undefined
isLanguageSupported() (true/false) ?true
Show the sub-box (true/false) ? true
General error (true/false) ?false


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

Re: Problem beim Download

[Marcus]

Am 29.01.19 um 15:55 schrieb d.bur...@posteo.de:

Ich wollte OpenOffice downloaden aber die Seite:
"https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.6/binaries/de/Apache_OpenOffice_4.1.6_Win_x86_install_de.exe/download"; 


wurde nicht geöffnet.

Die Fehlermeldung ist:
"Die Website ist nicht erreichbar
Die Server-IP-Adresse von sourceforge.net wurde nicht gefunden.
Versuchen Sie, die Windows-Netzwerkdiagnose auszuführen.
DNS_PROBE_FINISHED_NXDOMAIN"

Ich verwende den Browser Opera. mit Win7

(Was funktioniert nicht? Was wird erwartet?)
Browser Variablen    Werte
[...]


I've downloaded a second ago using the link you have mentioned and 
haven't seen a problem. So, in general it's working.


When you have problems with specific mirror servers then just change 
them. On the SourceForge webpage there is a grey "Problems Downloading?" 
button. Just click on it and choose a different mirror from the popup 
dialog.


HTH

Marcus


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

Re: Time for our first 4.2.0 beta?

[Marcus]

Am 29.01.19 um 13:52 schrieb Matthias Seidel:

Hi Jim,

Am 29.01.19 um 13:28 schrieb Jim Jagielski:



On Jan 28, 2019, at 3:23 PM, Marcus > wrote:


Am 28.01.19 um 21:06 schrieb Matthias Seidel:

Am 28.01.19 um 20:30 schrieb Marcus:

Am 28.01.19 um 19:39 schrieb Jim Jagielski:

Perfect, thx.

Just so I know, what's the procedure for us doing beta releases?
Where do they go?


this will be our first beta release here at Apache. So, nobody can
tell you what to do / where to go and we have to find the way
together. ;-)

It is "our" second: ;-)
https://archive.apache.org/dist/openoffice/4.1.0-beta/


OK, this is a bit embarrassing. ;-)


I would say we should not do things different (at least not too many)
compared to our normal releases.

After thinking a bit I suggest that we:

- exchange the splash screen with a big and clear hint that it's a
beta (no production use, no regular support, etc.)


When we had already a Beta release then this must be somewhere.



At least on the macOS build, 'beta' is splashed quite obviously:


Yes, that is what I am referring to.
I made a beta build for Windows a year ago and remember having the same 
discussion back then...


sorry to ask, do you have also a screenshot for the About box?

Thanks

Marcus


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

Re: Time for our first 4.2.0 beta?

[Marcus]

Am 29.01.19 um 13:05 schrieb Pedro Lino:



 I think we are at a stage where we should consider doing our
 1st beta release of 4.2.0... we have successful builds for macOS,
 Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch,
 and enough changes to warrant a beta release for testing and
 feedback (all IMO ;) ).


Is this going to be an English only Beta test? Only English and a couple more
languages (de, nl, ...) have a complete 4.2.0 translation


for every language we should take the following factors into account:

- translation ratio = 0 - 100 % --> larger is better
- the last activites = days/weeks ago or years --> shorter is better

With this we should create a list with supported languages.


 Any comments or other thoughts?


Shouldn't AOO be concerned that previous users are not notified of new releases
(or extension updates)? The update notification mechanism has been broken for 
months. This means that  users
currently on any previous build weren't even notified that 4.1.6 was released 2 
months ago...

I realize that the update notification is working on 4.2.0 but how are users 
going to be notified to update to 4.2.0?


If you mean the Beta release:
We shouldn't activate the update service - because it's just a Beta 
which not suitable for any production use.


Marcus


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

Re: Time for our first 4.2.0 beta?

[Matthias Seidel]

Am 29.01.19 um 20:14 schrieb Marcus:
> Am 29.01.19 um 13:52 schrieb Matthias Seidel:
>> Hi Jim,
>>
>> Am 29.01.19 um 13:28 schrieb Jim Jagielski:
>>>
>>>
 On Jan 28, 2019, at 3:23 PM, Marcus >>> > wrote:

 Am 28.01.19 um 21:06 schrieb Matthias Seidel:
> Am 28.01.19 um 20:30 schrieb Marcus:
>> Am 28.01.19 um 19:39 schrieb Jim Jagielski:
>>> Perfect, thx.
>>>
>>> Just so I know, what's the procedure for us doing beta releases?
>>> Where do they go?
>>
>> this will be our first beta release here at Apache. So, nobody can
>> tell you what to do / where to go and we have to find the way
>> together. ;-)
> It is "our" second: ;-)
> https://archive.apache.org/dist/openoffice/4.1.0-beta/

 OK, this is a bit embarrassing. ;-)

>> I would say we should not do things different (at least not too
>> many)
>> compared to our normal releases.
>>
>> After thinking a bit I suggest that we:
>>
>> - exchange the splash screen with a big and clear hint that it's a
>> beta (no production use, no regular support, etc.)

 When we had already a Beta release then this must be somewhere.

>>>
>>> At least on the macOS build, 'beta' is splashed quite obviously:
>>
>> Yes, that is what I am referring to.
>> I made a beta build for Windows a year ago and remember having the
>> same discussion back then...
>
> sorry to ask, do you have also a screenshot for the About box?

No problem, but I would have to install a beta first... ;-)
(In fact I am just building a new one)

Maybe Jim can provide a screenshot.

Regards,

   Matthias

>
> Thanks
>
> 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: Time for our first 4.2.0 beta?

[Marcus]

Am 28.01.19 um 21:58 schrieb F C. Costero:

I am a moderator on the en forum but I am speaking only for myself here. I
think gathering feedback on the forum would be a good solution. The en
forum has a User Experience area that gets very little traffic and could
perhaps be used to gather beta build input. Feedback in languages other
than English could be gathered on the appropriate forums, though they may
need to make a dedicated area. It would be nice to widen the range of
participants beyond people comfortable in English.


thanks for your input.


I am not sure what the concern is behind the comment "What I mean is, is
there enough coverage of moderators and power users?". On the en forum we


When we tell the people "Please visit our forums when you have problems 
or feedback for improvements" there should be enough people for coverage 
to collect that feedback. It would be too bad when the users don't get 
feedback or way too late. ;-)



have close to 24 hour coverage of moderators and volunteers and I don't
think an increase in traffic from a beta build would be a problem. The es
forum is the only other one I have experience with and I think there are
plenty of moderators and volunteers there to handle an increase in traffic,
though I obviously have not asked them about this.


OK, that sounds good. In the worst case the en forums in an special Beta 
release area could take some more languages - of course only as exception.



I would be happy to make note on this list of interesting or repeated input
about a beta build appearing on the en or es forums.


At the moment we are just discussing what is possible to decide later 
what to do.



Stating the correct way to give feedback on the Splash screen should be
considered.


The splash screen is not the best place as it's shown too short. ;-) 
That was my mistake.


But the About box, download webpage, release announcement, release 
notes, blog post are way better to tell the people what to expect and 
where to go.


Marcus




On Mon, Jan 28, 2019 at 12:53 PM Marcus  wrote:


Am 28.01.19 um 19:39 schrieb Jim Jagielski:

Perfect, thx.

Just so I know, what's the procedure for us doing beta releases? Where

do they go?

this will be our first beta release here at Apache. So, nobody can tell
you what to do / where to go and we have to find the way together. ;-)

I would say we should not do things different (at least not too many)
compared to our normal releases.

After thinking a bit I suggest that we:

- exchange the splash screen with a big and clear hint that it's a beta
(no production use, no regular support, etc.)
- prepare the install files as a normal release but with special file names
- no participation with the update service
- upload the install files to SourceForge in an own subdir
- offer them on our download webpage

I don't know how we can to collect the feedback. BZ is not the right
channel for this. Can we create a special beta area in the forums? What
I mean is, is there enough coverage of moderators and power users?

Marcus




On Jan 28, 2019, at 12:31 PM, Mechtilde  wrote:

Hello Jim,

the beta version should contain the recent translation, so I will start
to prepare an update of the *.sdf files.

Kind regards

Am 28.01.19 um 14:20 schrieb Jim Jagielski:

I think we are at a stage where we should consider doing our
1st beta release of 4.2.0... we have successful builds for macOS,
Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch,
and enough changes to warrant a beta release for testing and
feedback (all IMO ;) ).

Any comments or other thoughts?



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

Re: AOO 4.1.6 and MacOS Mojave

[FR web forum]

> Which Problems? I am not sure what they refer to.
Read this report:
https://bz.apache.org/ooo/show_bug.cgi?id=127979
Symptom is high CPU usage and slow scrolling.
End users on french forum confirm this issue.
 
> On 30.10.18 15:56, FR web forum wrote:
> > Hello,
> >
> > We have some questions about compatibility with MacOS 10.14
> > https://roaringapps.com/apps displays "some problems"
> > This next build will be OK?
> >


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

Re: Time for our first 4.2.0 beta?

[Pedro Lino]

> On January 29, 2019 at 7:21 PM Marcus  wrote:

> Am 29.01.19 um 13:05 schrieb Pedro Lino:
> > Shouldn't AOO be concerned that previous users are not notified of new 
> > releases
> > (or extension updates)? The update notification mechanism has been broken 
> > for months. This means that  users
> > currently on any previous build weren't even notified that 4.1.6 was 
> > released 2 months ago...
> > 
> > I realize that the update notification is working on 4.2.0 but how are 
> > users going to be notified to update to 4.2.0?
> 
> If you mean the Beta release:
> We shouldn't activate the update service - because it's just a Beta 
> which not suitable for any production use.

No, I mean that anyone who has AOO 4.1.5 (or previous) has NOT been notified 
that 4.1.6 was released.
The update notification mechanism is broken.
Isn't fixing regressions a priority for Apache OpenOffice?

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

Re: Time for our first 4.2.0 beta?

[Matthias Seidel]

Am 29.01.19 um 21:53 schrieb Pedro Lino:
>> On January 29, 2019 at 7:21 PM Marcus  wrote:
>> Am 29.01.19 um 13:05 schrieb Pedro Lino:
>>> Shouldn't AOO be concerned that previous users are not notified of new 
>>> releases
>>> (or extension updates)? The update notification mechanism has been broken 
>>> for months. This means that  users
>>> currently on any previous build weren't even notified that 4.1.6 was 
>>> released 2 months ago...
>>>
>>> I realize that the update notification is working on 4.2.0 but how are 
>>> users going to be notified to update to 4.2.0?
>> If you mean the Beta release:
>> We shouldn't activate the update service - because it's just a Beta 
>> which not suitable for any production use.
> No, I mean that anyone who has AOO 4.1.5 (or previous) has NOT been notified 
> that 4.1.6 was released.
> The update notification mechanism is broken.
> Isn't fixing regressions a priority for Apache OpenOffice?

How is this related to 4.2.0 Beta?!

Please don't hijack threads... Just open up another one or change the topic.

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: Time for our first 4.2.0 beta?

[Pedro Lino]

> On January 29, 2019 at 9:02 PM Matthias Seidel < 
> matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote:
> 
> 
> 

> How is this related to 4.2.0 Beta?!
> 

The subject of this email/topic is "Time for our first 4.2.0 beta?"

My opinion is that it is better to fix pending issues than to move on...

Unfortunately I can't fix the regression myself so I have to keep reminding the 
few people that can.

I think it is easy to understand that I'm not insisting on this subject to 
benefit myself (I can easily update AOO and ignore the problem) but to benefit 
all current AOO users...

Regards,
Pedro

Re: Time for our first 4.2.0 beta?

[Marcus]

Am 29.01.19 um 22:57 schrieb Pedro Lino:



 On January 29, 2019 at 9:02 PM Matthias Seidel < matthias.sei...@hamburg.de 
mailto:matthias.sei...@hamburg.de > wrote:



 How is this related to 4.2.0 Beta?!


The subject of this email/topic is "Time for our first 4.2.0 beta?"

My opinion is that it is better to fix pending issues than to move on...

Unfortunately I can't fix the regression myself so I have to keep reminding the 
few people that can.

I think it is easy to understand that I'm not insisting on this subject to 
benefit myself (I can easily update AOO and ignore the problem) but to benefit 
all current AOO users...


at the moment the root is not yet found (AFAIK, please say so when I'm 
wrong) and a fix is therefore difficult. But sure, for the final 4.2.0 
this probnlem should be fixed.


Marcus


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