Re: [Discussion] ODF 1.3 filter implementation strategy
I think it is a good idea. As I mentioned before, I'm available to contribute and implementing ODF 1.3 is a good goal. However, there is already an Open Collective for OpenOffice, although I'm not sure if it refers to this Office suite... https://opencollective.com/openoffice Best, Pedro > On 08/21/2023 4:08 PM WEST Matthias Seidel wrote: > > > Hi Rony, All, > > Am 20.08.23 um 12:47 schrieb Matthias Seidel: > > Hi Rony, > > > > Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache): > >> Has there been any work on this since? It seems that not supporting > >> 1.3 causes troubles for AOO users who receive 1.3 documents. > > > > Acknowledged. > > > > But to my knowledge we have no volunteer working on that topic... > > Personally, I think we need a payed developer for such a task. > > We would need to collect money outside the ASF, maybe the way Groovy > does it [1] could be a solution. > > Opinions? > > Regards, > > Matthias > > [1] https://opencollective.com/friends-of-groovy#category-ABOUT > > > > > Regards, > > > > Matthias > > > >> > >> ---rony > >> > >> > >> On 12.10.2021 00:00, Kay Schenk wrote: > >>> Hello all -- > >>> > >>> If you'd like an opinion from someone who hasn't contributed to the > >>> project in about 3 years... > >>> > >>> I think using the filter API is the way to go. I remember getting > >>> very curious about the filter API quite some time ago for something > >>> I wanted to work on -- maybe generic XML docs, and realized this API > >>> seemed very useful but I wasn't sure how it had been used. So, one > >>> opinion for you in any case. > >>> > >>> On 10/10/21 4:35 AM, Peter Kovacs wrote: > Hi all, > > ODF 1.3 becomes more relevant soon. MS Office 2021 will support > only ODF 1.3 > > So I try to look into this, however our implementation on ODF > currently uses not the filter API but office Document model directly. > > Should we stay with this architecture or should we use this > opportunity to migrate on a API driven filter? > > What is your opinion on this? > > >> > >> - > >> 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: [Discussion] ODF 1.3 filter implementation strategy
Hi Pedro, Good find! "OpenOffice" (exactly written like that) is a registered trademark of the ASF. I think we need to add that to our list of trademark violations? Regards, Matthias Am 22.08.23 um 17:13 schrieb Pedro Lino: I think it is a good idea. As I mentioned before, I'm available to contribute and implementing ODF 1.3 is a good goal. However, there is already an Open Collective for OpenOffice, although I'm not sure if it refers to this Office suite... https://opencollective.com/openoffice Best, Pedro On 08/21/2023 4:08 PM WEST Matthias Seidel wrote: Hi Rony, All, Am 20.08.23 um 12:47 schrieb Matthias Seidel: Hi Rony, Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache): Has there been any work on this since? It seems that not supporting 1.3 causes troubles for AOO users who receive 1.3 documents. Acknowledged. But to my knowledge we have no volunteer working on that topic... Personally, I think we need a payed developer for such a task. We would need to collect money outside the ASF, maybe the way Groovy does it [1] could be a solution. Opinions? Regards, Matthias [1] https://opencollective.com/friends-of-groovy#category-ABOUT Regards, Matthias ---rony On 12.10.2021 00:00, Kay Schenk wrote: Hello all -- If you'd like an opinion from someone who hasn't contributed to the project in about 3 years... I think using the filter API is the way to go. I remember getting very curious about the filter API quite some time ago for something I wanted to work on -- maybe generic XML docs, and realized this API seemed very useful but I wasn't sure how it had been used. So, one opinion for you in any case. On 10/10/21 4:35 AM, Peter Kovacs wrote: Hi all, ODF 1.3 becomes more relevant soon. MS Office 2021 will support only ODF 1.3 So I try to look into this, however our implementation on ODF currently uses not the filter API but office Document model directly. Should we stay with this architecture or should we use this opportunity to migrate on a API driven filter? What is your opinion on this? - 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 smime.p7s Description: S/MIME Cryptographic Signature
Re: [Discussion] ODF 1.3 filter implementation strategy
Dear All, On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote: > Hi Pedro, > > Good find! > > "OpenOffice" (exactly written like that) is a registered trademark of the > ASF. > > I think we need to add that to our list of trademark violations? +1 If we wanted to follow this way, we should probably establish a "Friends of OpenOffice" collective as Groovy did. [...] > > > [1] https://opencollective.com/friends-of-groovy#category-ABOUT -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: facebook
Hello All, I am sorry for chiming in very late. On Tue, Jul 04, 2023 at 02:36:21PM +0200, Matthias Seidel wrote: > Hi Peter, All, > > Am 02.07.23 um 17:35 schrieb Peter Kovacs: > > > > Am 02.07.23 um 16:03 schrieb Matthias Seidel: > >> Hi Peter, > >> > >> Am 19.06.23 um 22:57 schrieb Peter Kovacs: > >>> Hello all, > >>> > >>> > >>> I have not logged into Facebook for quite some time. Can someone take > >>> over? Can it be shared? I am no Facebook expert, but I was pulled into a sort of ``business'' account and now I can choose whether to impersonate myself or that business. This sort of sharing allows many people to cooperate in managing a Facebook account. Is it already so? Could we just share this burden instead of moving it from a single person to another? > >> If we have no volunteer for Facebook, we should shut that profile down > >> sooner or later... > > +1 > > That said, we should not remove the account, but simply state that it is > not maintained actively. > > Plus we should redirect users that look for help to our other resources... +1 Sending ``canned'' replies to Facebook queries such as ``Write to the dev@ mailing lists or to the forums'' could be a group effort. What do you think? Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: facebook
Am 22.08.23 um 21:50 schrieb Arrigo Marchiori: Hello All, I am sorry for chiming in very late. On Tue, Jul 04, 2023 at 02:36:21PM +0200, Matthias Seidel wrote: Hi Peter, All, Am 02.07.23 um 17:35 schrieb Peter Kovacs: Am 02.07.23 um 16:03 schrieb Matthias Seidel: Hi Peter, Am 19.06.23 um 22:57 schrieb Peter Kovacs: Hello all, I have not logged into Facebook for quite some time. Can someone take over? Can it be shared? I am no Facebook expert, but I was pulled into a sort of ``business'' account and now I can choose whether to impersonate myself or that business. This sort of sharing allows many people to cooperate in managing a Facebook account. Is it already so? Could we just share this burden instead of moving it from a single person to another? yes, i need your account and can add you. If we have no volunteer for Facebook, we should shut that profile down sooner or later... +1 That said, we should not remove the account, but simply state that it is not maintained actively. Plus we should redirect users that look for help to our other resources... +1 Sending ``canned'' replies to Facebook queries such as ``Write to the dev@ mailing lists or to the forums'' could be a group effort. What do you think? Best regards, - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
