Hi Dick,
Thanks! However, the tooltip was correct... ;-)
Matthias
Am 26.08.21 um 15:44 schrieb Dick Groskamp:
>
> On 2021/08/26 13:30:53, Dick Groskamp wrote:
>>
>> On 2021/08/26 13:22:08, Dick Groskamp wrote:
>>> Just noticed a typo in the navigation b
On 2021/08/26 13:30:53, Dick Groskamp wrote:
>
>
> On 2021/08/26 13:22:08, Dick Groskamp wrote:
> > Just noticed a typo in the navigation bar on the website pages for
> > www.openoffice.org
> >
> > In the bar it says: "Extentions & Templates&quo
On 2021/08/26 13:22:08, Dick Groskamp wrote:
> Just noticed a typo in the navigation bar on the website pages for
> www.openoffice.org
>
> In the bar it says: "Extentions & Templates" which should be "Extensions &
> Templates"
> (It is the
Just noticed a typo in the navigation bar on the website pages for
www.openoffice.org
In the bar it says: "Extentions & Templates" which should be "Extensions &
Templates"
(It is the bar below the announcement: "Released: Apache OpenOffice 4.1.10")
I
not touching the code as I have no idea how to fix it.
>
> On 2021/03/05 09:51:58, Matthias Seidel wrote:
>> Hi all,
>>
>> It really seems to be a typo and OpenGrok can only find two instances of it:
>>
>> http://opengrok.openoffice.org/search?project=trunk&f
Rigo / Matthias,
thanks for the info. Now I know that I saw it right then.
I'm not touching the code as I have no idea how to fix it.
On 2021/03/05 09:51:58, Matthias Seidel wrote:
> Hi all,
>
> It really seems to be a typo and OpenGrok can only find two instances of
Hi all,
It really seems to be a typo and OpenGrok can only find two instances of it:
http://opengrok.openoffice.org/search?project=trunk&full=%22_earArray%22&defs=&refs=&path=&hist=&type=&si=full
So I think it would be without risk to correct this.
Regards,
Ma
t; on line 140 it says however: Calendar_gregorian::init(Era *_eraArray)
>
> It seems to me that _eraArray is right because it is used further on in the
> code.
>
> QUESTION:
> Are the *_earArray on line 136 and _earArray on line 138 intentional or are
> they typo&
I'm definitely no developer but when I added the new Japanse era Reiwa to the
file
openoffice-trunk/main/i18npool/source/calendar/calendar_gregorian.cxx,
I noticed this code:
132 Calendar_gregorian::Calendar_gregorian()
133 {
134 init(NULL);
135
DiGro commented on pull request #1:
URL: https://github.com/apache/openoffice-project/pull/1#issuecomment-762174709
@Pilot-Pirx,
Matthias, I'm still struggling with Git.
Didn't get the change merged.
Dave has however made the change for me, so all is well
---
Pilot-Pirx commented on pull request #1:
URL: https://github.com/apache/openoffice-project/pull/1#issuecomment-761868165
Has this ever been merged?
This is an automated message from the Apache Git Service.
To respond to the m
DiGro closed pull request #2:
URL: https://github.com/apache/openoffice-project/pull/2
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
DiGro opened a new pull request #2:
URL: https://github.com/apache/openoffice-project/pull/2
Line 223 : "contributers" should be "contributors". Changed.
This is an automated message from the Apache Git Service.
To respond
DiGro closed pull request #1:
URL: https://github.com/apache/openoffice-project/pull/1
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
DiGro opened a new pull request #1:
URL: https://github.com/apache/openoffice-project/pull/1
Line 223 ; "contributers" should be spelled with an "o" : Changed to
"contributors"
This is an automated message from the Apache Gi
Hi Pedro,
Am 10.12.20 um 12:09 schrieb Pedro Lino:
> Hi Matthias
>
>> On 12/10/2020 10:52 AM Matthias Seidel wrote:
>> Since you are committer, you can do it yourself, see:
>>
>> https://github.com/apache/openoffice-org/blob/main/README.md
> Thanks!
> In this case it is not needed because the lin
Hi Matthias
> On 12/10/2020 10:52 AM Matthias Seidel wrote:
> Since you are committer, you can do it yourself, see:
>
> https://github.com/apache/openoffice-org/blob/main/README.md
Thanks!
In this case it is not needed because the link in OpenOffice.org is pointing
directly to
https://openoff
Hi Pedro,
Am 10.12.20 um 11:42 schrieb Pedro Lino:
> Hi Matthias
>
>> On 12/10/2020 9:40 AM Matthias Seidel wrote:
>> Thanks! Since you have write access you can skip the Pull Request... ;-)
> Excellent :)
>
>> BTW: The project page is self publishing, openoffice.org needs a manual
>> step for pu
Hi Matthias
> On 12/10/2020 9:40 AM Matthias Seidel wrote:
> Thanks! Since you have write access you can skip the Pull Request... ;-)
Excellent :)
>
> BTW: The project page is self publishing, openoffice.org needs a manual
> step for publishing.
Can I do that myself as well or is it preferab
Hi Matthias,
> Because you request someone to pull your changes?
>
> But better ask Linus... ;-)
Indeed XOR More or less. ;-)
Regards,
Czesław
Am Do., 10. Dez. 2020 um 11:28 Uhr schrieb Matthias Seidel <
matthias.sei...@hamburg.de>:
> Hi,
>
> Am 10.12.20 um 11:24 schrieb Czesław Wolański:
> >
Hi,
Am 10.12.20 um 11:24 schrieb Czesław Wolański:
> Hi Pedro and Matthias,
>
> Thanks for fixing and advice.
>
>> I still haven't figured out the Pull Request part :)
>>
>>> Thanks! Since you have write access you can skip the Pull Request... ;-)
> And I still haven't figured out the "Request" pa
Hi Pedro and Matthias,
Thanks for fixing and advice.
> I still haven't figured out the Pull Request part :)
>
>>
>> Thanks! Since you have write access you can skip the Pull Request... ;-)
And I still haven't figured out the "Request" part. ;‑)
Regards,
Czesław
Am Do., 10. Dez. 2020 um 10:41 U
Hi Pedro,
Am 10.12.20 um 10:28 schrieb Pedro Lino:
> Hi Matthias and Czeslaw
>
>> On 12/10/2020 9:05 AM Matthias Seidel wrote:
>>> I could have sworn I reported that ages ago. ;‑)
>> Meanwhile the page is on GitHub and you can easily create a Pull
>> Request! ;-)
>>
>> https://github.com/apache/o
Hi Matthias and Czeslaw
> On 12/10/2020 9:05 AM Matthias Seidel wrote:
> > I could have sworn I reported that ages ago. ;‑)
>
> Meanwhile the page is on GitHub and you can easily create a Pull
> Request! ;-)
>
> https://github.com/apache/openoffice-project
Fixed. Thank you for teaching others
. Fixed now!
>>
>> Regards,
>>
>>Matthias
>>
>> Am 09.12.20 um 18:00 schrieb LJ Pilipenko:
>>> You have a typo on webpage:
>>>
>>>
>>> https://openoffice.apache.org/get-involved.html
>>>
>>>
>&
Fixed now!
>
> Regards,
>
>Matthias
>
> Am 09.12.20 um 18:00 schrieb LJ Pilipenko:
> > You have a typo on webpage:
> >
> >
> > https://openoffice.apache.org/get-involved.html
> >
> >
> > In the following sentence &
Hi,
Thanks for finding that. Fixed now!
Regards,
Matthias
Am 09.12.20 um 18:00 schrieb LJ Pilipenko:
> You have a typo on webpage:
>
>
> https://openoffice.apache.org/get-involved.html
>
>
> In the following sentence 'you' should be 'your'.
>
&g
You have a typo on webpage:
https://openoffice.apache.org/get-involved.html
In the following sentence 'you' should be 'your'.
To help bring the benefits ofOpenOffice to you country or region
---Your welcome,Mrs P.
Peter has granted Matthias Seidel 's
request for 4.1.6_release_blocker:
Issue 126736: fix typo in systemactions.pm
https://bz.apache.org/ooo/show_bug.cgi?id=126736
--- Comment #5 from Peter ---
Accepted for 4.1.6
---
Matthias Seidel has asked for 4.1.6_release_blocker:
Issue 126736: fix typo in systemactions.pm
https://bz.apache.org/ooo/show_bug.cgi?id=126736
--- Comment #4 from Matthias Seidel ---
Although not a real "blocker" this patch removes some warnings in the build
process.
It is in
ithub?
>
>I will correct the typo in trunk. And a second one I found in the same
>comment... ;-)
>
>Regards, Matthias
>
>
>Am 28.11.2017 um 20:53 schrieb Matthias Seidel:
>>
>> We have a new pull request on Github...
>>
>> Just out of interest: If we
Anyway, this is a pull request for AOO415!
Should we make the branches "read-only" on Github?
I will correct the typo in trunk. And a second one I found in the same
comment... ;-)
Regards, Matthias
Am 28.11.2017 um 20:53 schrieb Matthias Seidel:
>
> We have a new pull r
We have a new pull request on Github...
Just out of interest: If we would review and approve this (small) patch,
would it become visible in subversion?
Regards, Matthias
Weitergeleitete Nachricht
Betreff:[apache/openoffice] Fix typo (#4)
Datum: Tue, 28 Nov 2017 12
Am 03/10/2014 07:02 PM, schrieb Marco A.G.Pinto:
Hello!
I was reading the "release notes" and the first thing I spotted was:
Updated Dictionaries
English (en)
*Note: The extension contains multiple varients. Only the en-GB
dictionary has ben updated.
*
I believe there is
dictionary has ben updated.
I believe there is a typo in "varients" and "ben".
Kind regards,
>Marco A.G.Pinto
--
Original Message
From: Elly Mo
To: Dave Barton
Date: Sun, 19 Jan 2014 06:54:03 -0500
> Hi there,
> Just to let you know there is a typo on this page >
> http://openoffice.apache.org/orientation/index.html
> As highlighted below;
> "Once you have co
Hi there,
Just to let you know there is a typo on this page >
http://openoffice.apache.org/orientation/index.html
As highlighted below;
"Once you have completed these first two Levels, you will have been exposed to
the basic skills that enable you to volunteer as a general contributo
Am 07/23/2013 10:14 PM, schrieb S. C. Gardner:
Hi,
I'm a web administrator... so I *KNOW* you want to know this:
at:
http://www.openoffice.org/why/why_new_computers.html
find:
You are not required to spent $100, $200 more for a copy
I believe it should be "*spend*"... not "Spent" I think
Hi,
I'm a web administrator... so I *KNOW* you want to know this:
at:
http://www.openoffice.org/why/why_new_computers.html
find:
You are not required to spent $100, $200 more for a copy
I believe it should be "*spend*"... not "Spent" I think you may want
to add the word "or" too. So:
*You
j...@apache.org has granted 4.0.0_release_blocker:
Bug 122564: Typo in English string ("is always save")
https://issues.apache.org/ooo/show_bug.cgi?id=122564
--- Additional Comments from j...@apache.org
set showstopper flag
40 matches
Mail list logo
