Re: [FIXED] Re: Typo in navigation bar website www.openoffice.org
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 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've been looking some time to find the responsible element, but can't find >>> it anywhere in Github. >>> >>> It is probably the element called: topbara >>> >>> I have no idea where to look for it anymore. >>> Would someone be so kind to fix it for us, or point me to the right place ? >>> >> Should probably be the element : >> Sorry >> >> - > Found it in openoffice-org/content/topnav.md (need better glasses I presume) > Fixed > > - > 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
[FIXED] Re: Typo in navigation bar website www.openoffice.org
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" which should be "Extensions & > > Templates" > > (It is the bar below the announcement: "Released: Apache OpenOffice 4.1.10") > > > > I've been looking some time to find the responsible element, but can't find > > it anywhere in Github. > > > > It is probably the element called: topbara > > > > I have no idea where to look for it anymore. > > Would someone be so kind to fix it for us, or point me to the right place ? > > > Should probably be the element : > Sorry > > - Found it in openoffice-org/content/topnav.md (need better glasses I presume) Fixed - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Typo in navigation bar website www.openoffice.org
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 bar below the announcement: "Released: Apache OpenOffice 4.1.10") > > I've been looking some time to find the responsible element, but can't find > it anywhere in Github. > > It is probably the element called: topbara > > I have no idea where to look for it anymore. > Would someone be so kind to fix it for us, or point me to the right place ? > Should probably be the element : Sorry - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Typo in navigation bar website www.openoffice.org
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've been looking some time to find the responsible element, but can't find it anywhere in Github. It is probably the element called: topbara I have no idea where to look for it anymore. Would someone be so kind to fix it for us, or point me to the right place ? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: code> Is this a typo or is it intentional?
Hi Dick,
I just created a Pull Request for it and asked Arrigo for review:
https://github.com/apache/openoffice/pull/123
Regards,
Matthias
Am 05.03.21 um 12:33 schrieb Dick Groskamp:
> 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 it:
>>
>> http://opengrok.openoffice.org/search?project=trunk=%22_earArray%22==full
>>
>> So I think it would be without risk to correct this.
>>
>> Regards,
>>
>> Matthias
>>
>> Am 05.03.21 um 08:31 schrieb Arrigo Marchiori:
>>> Hello Dick,
>>>
>>> On Thu, Mar 04, 2021 at 06:25:10PM -, Dick Groskamp wrote:
>>>
>>>> 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 }
>>>> 136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
>>>> 137 {
>>>> 138 init(_earArray);
>>>> 139 }
>>>> _
>>>> 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's ?
>>> I think that "ear" instead of "era" is a typo.
>>>
>>> If you look at the corresponding include file
>>> main/i18npool/inc/calendar_gregorian.hxx at line 51:
>>>
>>> 45 class Calendar_gregorian : public CalendarImpl
>>> 46 {
>>> 47 public:
>>> 48
>>> 49// Constructors
>>> 50Calendar_gregorian();
>>> 51Calendar_gregorian(Era *_eraArray);
>>> 52void SAL_CALL init(Era *_eraArray);
>>>
>>> The parameter is spelled correctly there.
>>>
>>> However the code compiles and works fine, because the typo is ``used
>>> consistently'' inside Calendar_gregorian::Calendar_gregorian(Era *)
>>>
>>> If you don't like to have that typo in the code, I believe you can fix
>>> it straight away as it is a ``trivial edit'' (i.e. no need to review
>>> before committing), as I think you did for the new Japanese era.
>>>
>>> I hope this helps.
>>>
>>> Best regards,
>>
> -
> 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: code> Is this a typo or is it intentional?
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 it:
>
> http://opengrok.openoffice.org/search?project=trunk=%22_earArray%22==full
>
> So I think it would be without risk to correct this.
>
> Regards,
>
> Matthias
>
> Am 05.03.21 um 08:31 schrieb Arrigo Marchiori:
> > Hello Dick,
> >
> > On Thu, Mar 04, 2021 at 06:25:10PM -, Dick Groskamp wrote:
> >
> >> 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 }
> >> 136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
> >> 137 {
> >> 138 init(_earArray);
> >> 139 }
> >> _
> >> 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's ?
> > I think that "ear" instead of "era" is a typo.
> >
> > If you look at the corresponding include file
> > main/i18npool/inc/calendar_gregorian.hxx at line 51:
> >
> > 45 class Calendar_gregorian : public CalendarImpl
> > 46 {
> > 47 public:
> > 48
> > 49// Constructors
> > 50Calendar_gregorian();
> > 51Calendar_gregorian(Era *_eraArray);
> > 52void SAL_CALL init(Era *_eraArray);
> >
> > The parameter is spelled correctly there.
> >
> > However the code compiles and works fine, because the typo is ``used
> > consistently'' inside Calendar_gregorian::Calendar_gregorian(Era *)
> >
> > If you don't like to have that typo in the code, I believe you can fix
> > it straight away as it is a ``trivial edit'' (i.e. no need to review
> > before committing), as I think you did for the new Japanese era.
> >
> > I hope this helps.
> >
> > Best regards,
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Is this a typo or is it intentional?
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=%22_earArray%22==full
So I think it would be without risk to correct this.
Regards,
Matthias
Am 05.03.21 um 08:31 schrieb Arrigo Marchiori:
> Hello Dick,
>
> On Thu, Mar 04, 2021 at 06:25:10PM -, Dick Groskamp wrote:
>
>> 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 }
>> 136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
>> 137 {
>> 138 init(_earArray);
>> 139 }
>> _
>> 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's ?
> I think that "ear" instead of "era" is a typo.
>
> If you look at the corresponding include file
> main/i18npool/inc/calendar_gregorian.hxx at line 51:
>
> 45 class Calendar_gregorian : public CalendarImpl
> 46 {
> 47 public:
> 48
> 49// Constructors
> 50Calendar_gregorian();
> 51Calendar_gregorian(Era *_eraArray);
> 52void SAL_CALL init(Era *_eraArray);
>
> The parameter is spelled correctly there.
>
> However the code compiles and works fine, because the typo is ``used
> consistently'' inside Calendar_gregorian::Calendar_gregorian(Era *)
>
> If you don't like to have that typo in the code, I believe you can fix
> it straight away as it is a ``trivial edit'' (i.e. no need to review
> before committing), as I think you did for the new Japanese era.
>
> I hope this helps.
>
> Best regards,
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Is this a typo or is it intentional?
Hello Dick,
On Thu, Mar 04, 2021 at 06:25:10PM -, Dick Groskamp wrote:
> 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 }
> 136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
> 137 {
> 138 init(_earArray);
> 139 }
> _
> 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's ?
I think that "ear" instead of "era" is a typo.
If you look at the corresponding include file
main/i18npool/inc/calendar_gregorian.hxx at line 51:
45 class Calendar_gregorian : public CalendarImpl
46 {
47 public:
48
49// Constructors
50Calendar_gregorian();
51Calendar_gregorian(Era *_eraArray);
52void SAL_CALL init(Era *_eraArray);
The parameter is spelled correctly there.
However the code compiles and works fine, because the typo is ``used
consistently'' inside Calendar_gregorian::Calendar_gregorian(Era *)
If you don't like to have that typo in the code, I believe you can fix
it straight away as it is a ``trivial edit'' (i.e. no need to review
before committing), as I think you did for the new Japanese era.
I hope this helps.
Best regards,
--
Arrigo
http://rigo.altervista.org
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Is this a typo or is it intentional?
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 }
136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
137 {
138 init(_earArray);
139 }
_
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's ?
Could someone with more knowledge enlighten me or at least check if it is
correct as it is ?
Couldn't file an issue on GitHub so mentioned it here
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-project] DiGro commented on pull request #1: Typo corrected
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 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-project] Pilot-Pirx commented on pull request #1: Typo corrected
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 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-project] DiGro closed pull request #2: Typo corrected ("contributors")
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 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-project] DiGro opened a new pull request #2: Typo corrected ("contributors")
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 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-project] DiGro closed pull request #1: Typo corrected
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 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-project] DiGro opened a new pull request #1: Typo corrected
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 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: typo
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 link in OpenOffice.org is pointing > directly to > https://openoffice.apache.org/get-involved.html > >> But it is a question of timing, so you should be subscribed to >> comm...@openoffice.apache.org >> to see the status messages. > What is this for? > Can't I simply press Build Now in > https://ci-builds.apache.org/job/OpenOffice/job/OpenOffice-org-Publish-Site/? No, the page first must be built. See the readme. > > For instance: wouldn't it make sense to remove the banner for the now passed > ApacheCon in the footer? No, this is an external link, The graphic is controlled be ASF. It will change when the next event is planned. Regards, Matthias > > Regards > Pedro > > - > 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: typo
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://openoffice.apache.org/get-involved.html > But it is a question of timing, so you should be subscribed to > comm...@openoffice.apache.org > to see the status messages. What is this for? Can't I simply press Build Now in https://ci-builds.apache.org/job/OpenOffice/job/OpenOffice-org-Publish-Site/? For instance: wouldn't it make sense to remove the banner for the now passed ApacheCon in the footer? Regards Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: typo
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 publishing. > Can I do that myself as well or is it preferable that a second person does > that? > Is there a How-to somewhere? Since you are committer, you can do it yourself, see: https://github.com/apache/openoffice-org/blob/main/README.md But it is a question of timing, so you should be subscribed to comm...@openoffice.apache.org to see the status messages. Regards, Matthias > > Regards, > Pedro > > - > 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: typo
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 preferable that a second person does that? Is there a How-to somewhere? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: typo
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 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. ;‑) > > Because you request someone to pull your changes? > > But better ask Linus... ;-) > > Matthias > > > > > Regards, > > Czesław > > > > Am Do., 10. Dez. 2020 um 10:41 Uhr schrieb Matthias Seidel < > > matthias.sei...@hamburg.de>: > > > >> 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/openoffice-project > >>> Fixed. Thank you for teaching others how to fish ;) > >>> > >>> I did a quick edit which is already reflected on the website > >>> > >>> I still haven't figured out the Pull Request part :) > >> Thanks! Since you have write access you can skip the Pull Request... ;-) > >> > >> BTW: The project page is self publishing, openoffice.org needs a manual > >> step for publishing. > >> > >> Regards, > >> > >>Matthias > >> > >>> Regards, > >>> Pedro > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > >> > >
Re: typo
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" part. ;‑) Because you request someone to pull your changes? But better ask Linus... ;-) Matthias > > Regards, > Czesław > > Am Do., 10. Dez. 2020 um 10:41 Uhr schrieb Matthias Seidel < > matthias.sei...@hamburg.de>: > >> 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/openoffice-project >>> Fixed. Thank you for teaching others how to fish ;) >>> >>> I did a quick edit which is already reflected on the website >>> >>> I still haven't figured out the Pull Request part :) >> Thanks! Since you have write access you can skip the Pull Request... ;-) >> >> BTW: The project page is self publishing, openoffice.org needs a manual >> step for publishing. >> >> Regards, >> >>Matthias >> >>> Regards, >>> Pedro >>> >>> - >>> 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: typo
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 Uhr schrieb Matthias Seidel < matthias.sei...@hamburg.de>: > 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/openoffice-project > > Fixed. Thank you for teaching others how to fish ;) > > > > I did a quick edit which is already reflected on the website > > > > I still haven't figured out the Pull Request part :) > > Thanks! Since you have write access you can skip the Pull Request... ;-) > > BTW: The project page is self publishing, openoffice.org needs a manual > step for publishing. > > Regards, > >Matthias > > > > > Regards, > > Pedro > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > >
Re: typo
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/openoffice-project > Fixed. Thank you for teaching others how to fish ;) > > I did a quick edit which is already reflected on the website > > I still haven't figured out the Pull Request part :) Thanks! Since you have write access you can skip the Pull Request... ;-) BTW: The project page is self publishing, openoffice.org needs a manual step for publishing. Regards, Matthias > > Regards, > Pedro > > - > 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: typo
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 how to fish ;) I did a quick edit which is already reflected on the website I still haven't figured out the Pull Request part :) Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: typo
Hi Czesław, Am 10.12.20 um 06:09 schrieb Czesław Wolański: > Hi Matthias, > > The same section - "Why get involved with the OpenOffice project?" > > https://openoffice.apache.org/get-involved.html#why-get-involved-with-the-openoffice-project > > 1st paragraph: "There are many motivations for why volunteers (...)" > is superfluous because it is already where it should be i.e. in the 2nd > paragraph (the 2nd & 3rd sentence). > > 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 Regards, Matthias > > Regards, > Czesław Wolański > > Am Mi., 9. Dez. 2020 um 23:57 Uhr schrieb Matthias Seidel < > matthias.sei...@hamburg.de>: > >> 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'. >>> >>> >>> To help bring the benefits ofOpenOffice to you country or region >>> >>> >>> >>> ---Your welcome,Mrs P. >>> >>> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: typo
Hi Matthias, The same section - "Why get involved with the OpenOffice project?" https://openoffice.apache.org/get-involved.html#why-get-involved-with-the-openoffice-project 1st paragraph: "There are many motivations for why volunteers (...)" is superfluous because it is already where it should be i.e. in the 2nd paragraph (the 2nd & 3rd sentence). I could have sworn I reported that ages ago. ;‑) Regards, Czesław Wolański Am Mi., 9. Dez. 2020 um 23:57 Uhr schrieb Matthias Seidel < matthias.sei...@hamburg.de>: > 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'. > > > > > > To help bring the benefits ofOpenOffice to you country or region > > > > > > > > ---Your welcome,Mrs P. > > > > > >
Re: typo
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'. > > > To help bring the benefits ofOpenOffice to you country or region > > > > ---Your welcome,Mrs P. > > smime.p7s Description: S/MIME Cryptographic Signature
typo
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.
4.1.6_release_blocker granted: [Issue 126736] fix typo in systemactions.pm
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 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.6_release_blocker requested: [Issue 126736] fix typo in systemactions.pm
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 trunk for more than 2 years now, so the risk is zero. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: [apache/openoffice] Fix typo (#4)
I think they are only read-only. I do not have any way in manipulating requests on GitHub. So the only way is to do what you did. Am 28. November 2017 23:44:28 MEZ schrieb Matthias Seidel <matthias.sei...@hamburg.de>: >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 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:33:57 + (UTC) >> Von: Luan Kevin Ferreira <notificati...@github.com> >> Antwort an: apache/openoffice >> ><reply+00624cb620976296c7a6022692a0c910ddd0667e2c3e049392cf0001163519b592a169ce10884...@reply.github.com> >> >> An: apache/openoffice <openoff...@noreply.github.com> >> Kopie (CC): Subscribed <subscri...@noreply.github.com> >> >> >> >> >---- >> >> >> You can view, comment on, or merge this pull request online >at: >> >> https://github.com/apache/openoffice/pull/4 >> >> >> Commit Summary >> >> * Fix typo >> >> >> File Changes >> >> * *M* main/extensions/source/config/ldap/ldapuserprofilebe.hxx >> <https://github.com/apache/openoffice/pull/4/files#diff-0> (2) >> >> >> Patch Links: >> >> * https://github.com/apache/openoffice/pull/4.patch >> * https://github.com/apache/openoffice/pull/4.diff >> >> — >> You are receiving this because you are subscribed to this thread. >> Reply to this email directly, view it on GitHub >> <https://github.com/apache/openoffice/pull/4>, or mute the thread >> ><https://github.com/notifications/unsubscribe-auth/AGJMtl_NxGXGSz7p5WWuUGAGkIh38c7Lks5s6_21gaJpZM4QtKm2>. >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: [apache/openoffice] Fix typo (#4)
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 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:33:57 + (UTC) > Von: Luan Kevin Ferreira <notificati...@github.com> > Antwort an: apache/openoffice > <reply+00624cb620976296c7a6022692a0c910ddd0667e2c3e049392cf0001163519b592a169ce10884...@reply.github.com> > > An: apache/openoffice <openoff...@noreply.github.com> > Kopie (CC): Subscribed <subscri...@noreply.github.com> > > > > > > > You can view, comment on, or merge this pull request online at: > > https://github.com/apache/openoffice/pull/4 > > > Commit Summary > > * Fix typo > > > File Changes > > * *M* main/extensions/source/config/ldap/ldapuserprofilebe.hxx > <https://github.com/apache/openoffice/pull/4/files#diff-0> (2) > > > Patch Links: > > * https://github.com/apache/openoffice/pull/4.patch > * https://github.com/apache/openoffice/pull/4.diff > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/openoffice/pull/4>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGJMtl_NxGXGSz7p5WWuUGAGkIh38c7Lks5s6_21gaJpZM4QtKm2>. > smime.p7s Description: S/MIME Cryptographic Signature
Fwd: [apache/openoffice] Fix typo (#4)
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:33:57 + (UTC) Von:Luan Kevin Ferreira <notificati...@github.com> Antwort an: apache/openoffice <reply+00624cb620976296c7a6022692a0c910ddd0667e2c3e049392cf0001163519b592a169ce10884...@reply.github.com> An: apache/openoffice <openoff...@noreply.github.com> Kopie (CC): Subscribed <subscri...@noreply.github.com> You can view, comment on, or merge this pull request online at: https://github.com/apache/openoffice/pull/4 Commit Summary * Fix typo File Changes * *M* main/extensions/source/config/ldap/ldapuserprofilebe.hxx <https://github.com/apache/openoffice/pull/4/files#diff-0> (2) Patch Links: * https://github.com/apache/openoffice/pull/4.patch * https://github.com/apache/openoffice/pull/4.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/apache/openoffice/pull/4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGJMtl_NxGXGSz7p5WWuUGAGkIh38c7Lks5s6_21gaJpZM4QtKm2>. smime.p7s Description: S/MIME Cryptographic Signature
AOO 4.1 beta - typo in release notes
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 a typo in "varients" and "ben". Kind regards, Marco A.G.Pinto --
Re: AOO 4.1 beta - typo in release notes
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 a typo in varients and ben. Thanks for the hint. I've fixed the typos. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Typo on New Volunteer Orientation page
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 contributor, or to dive deeper into a specialized are of the project, like Quality Assurance, Marketing, Translation or Development.' *area That is all. Love your work and value OpenOffice immensely. Kindest Regards, Ellen :) ~ Please consider the environment before printing this e-mail ~
Re: Typo on New Volunteer Orientation page
Original Message From: Elly Mo ellym...@mail.com To: Dave Barton d...@tasit.net 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 completed these first two Levels, you will have been exposed to the basic skills that enable you to volunteer as a general contributor, or to dive deeper into a specialized are of the project, like Quality Assurance, Marketing, Translation or Development.' *area That is all. Love your work and value OpenOffice immensely. Kindest Regards, Ellen :) Hi Ellen, Thank you for your keen eyed observation. The typo are has now been corrected to area. Kindest Regards Dave - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Website] - Typo?
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 are not required to spend $100, $200, or more for a copy of Microsoft Office*. Thanks for all the wonderful work being accomplished by the amazing Open Office team. Respectfully, Conrad s.c.g. :-) = + = + = + = + = + = + = + =
Re: [Website] - Typo?
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 you may want to add the word or too. So: *You are not required to spend $100, $200, or more for a copy of Microsoft Office*. Thanks for your hint. I've fixed it in our staging area. With the next push it will go Live. Thanks for all the wonderful work being accomplished by the amazing Open Office team. Thank you very much. :-) Please don't miss our today's brand-new release of Apache OpenOffice 4.0: http://www.openoffice.org/download/ https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Notes Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
