payed = paid ;-) Am 21.08.23 um 17:08 schrieb Matthias Seidel:
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-ABOUTRegards, 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.3So 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
smime.p7s
Description: S/MIME Cryptographic Signature
