Re: Check for Updates broken?
nope. I am the only one who has currently access. On 07.12.18 23:01, Pedro Lino wrote: >> On December 5, 2018 at 10:01 PM Peter Kovacs wrote: >> >> On 05.12.18 08:08, Andrea Pescetti wrote: >>> If yes, we'll have to look into another environment. If no, we can >>> reuse one of these two VMs as the new updates server. >> We could try the OpenGrok Server. > Has this been tested? > Could someone on Infra give a little love to this task? > > Regards, > Pedro > > - > 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: Check for Updates broken?
> On December 5, 2018 at 10:01 PM Peter Kovacs wrote: > > On 05.12.18 08:08, Andrea Pescetti wrote: > > > > If yes, we'll have to look into another environment. If no, we can > > reuse one of these two VMs as the new updates server. > We could try the OpenGrok Server. Has this been tested? Could someone on Infra give a little love to this task? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Speichern
Warum glaubst du das die anderen Formate nicht gut sind? - Ich möchte das wirklich von dir wissen. Deine Meinung ist mir wichtig. Wenn du nicht Dokumente zum bearbeiten Tauschen musst, dann sind die ODF Formate kleiner und besser strukturiert. Lassen sich also z.B. schneller öffnen. Wenn du Dokumente tauschen möchtest und der Empfänger soll diese nicht mehr verändern können, so wird in der Geschäftswelt das PDF Format gewählt. Damit wir uns Richtig verstehen, ich hätte auch gerne eine bessere Unterstützung für die neuen MS Formate. Aber wenn ich mich entscheiden muss einen Fehler oder ein neues Feature einzubauen, dann entscheiden wir uns lieber für den Fehler. Wir Entwickler sind nicht viele und verbessern das Programm in unserer Freizeit. So gut wir halt können. Und das heißt wir müssen uns ständig entscheiden was wichtiger ist. Wenn du helfen möchtest kannst du das gerne tun. Beste Grüße Peter On 07.12.18 17:48, Dietmar wrote: > aber die neuen vormate sind wichtig > denn alles andere ist nicht gut. > heute wird alles im office paket im neuen vormat abgespeichert, > schade das ihr das nicht unterstützt. > ansonsten ist openoffice gut > > gruß > dietmar > > > > Am 07.12.2018 um 17:16 schrieb Peter Kovacs: >> In der Tat. dev@ ist eine englische Liste. Wenn schon Entwickler auf >> deutsch dann dev-de >> >> calc = excel >> >> write = word >> >> impress = powerpoint. >> >> >> Die neuen Formate werden nicht unterstützt weil es niemand einbaut. Alle >> aktiven Entwickler fokussieren sich auf andere Themen. Wenn sich jemand >> findet der es einbauen möchte wird es kommen. >> >> Libre Office bringt diese Funktionalität, wenn du sie benötigst. >> Empfehlen kann ich das Format aus technischen Gründen aber nicht. Libre >> Office Mitglieder haben da einen schönen Vortrag zu dem Thema gehalten. >> >> Ich glaube sogar auf der letzten OpenRheinRuhr. >> >> >> Beste Grüße >> >> Peter >> >> On 07.12.18 14:19, Dr. Michael Stehmann wrote: >>> Hello, >>> >>> You are on a wrong mailing list here. Better take >>> >>> users...@openoffice.apache.org >>> >>> Regards >>> Michael >>> >>> Hallo, >>> >>> Du bist hier auf der falschen Liste. Deine Fragen sind hier besser >>> aufgehoben: >>> >>> users...@openoffice.apache.org >>> >>> Gruß >>> Michael >>> >>> Am 07.12.2018 um 10:23 schrieb Dietmar: Hallo, heute habe ich mir open office heruntergeladen und installiert. 2 fragen hätte ich, welche icen muss ich nehmen für excel, word und powerpoint? und warum kann ich die dateien nicht im neuen format von Microsoft abspeichern? Gruß Dietmar >
Re: Speichern
Hallo, die Frage ist doch, warum will man die OOXML-Formate schreiben? Will man beispielsweise Texte weitergeben, bietet sich PDF/A als Format an. Dahin kann Apache OpenOffice exportieren. Will man an Dateien gemeinsam arbeiten, bietet sich ODF an, welches von Microsoft mehr oder weniger gut unterstützt wird. In vielen Fällen ist es ausreichend, dass Apache OpenOffice OOXML-Formate lesen kann. Erst wenn der konkrete Anwendungsfall klar ist, kann man konkrete Ratschläge geben. Gruß Michael signature.asc Description: OpenPGP digital signature
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hello Am 07.12.18 um 20:59 schrieb Dave Fisher: > Hi - > > SVN -> git.apache.org -> GitBox -> GitHub. > > When we switch to GitHub development then it will be: > > GitHub -> GitBox -> git.apache.org > Is it possible to use git.apache.org directly? Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Am 07.12.18 um 21:02 schrieb Dave Fisher: > > >> On Dec 7, 2018, at 11:37 AM, Mechtilde wrote: >> >> Hello >> >> Am 07.12.18 um 20:26 schrieb Dave Fisher: >>> One more bit - >>> >>> Our openoffice.git mirror of svn is not on git-wip-us.apache.org. >>> >>> Before we switch from SVN to GitBox/GitHun for our main repository we will >>> need to understand how to do the hooks to Bugzilla issues. I will use the >>> setup of a Git repository for the Forum setup to figure that out. >> >> Do we have the hooks from SVN? > > I’m told by Infra that we will need to do research and perhaps write a Git > replacement for the hooks we have between bugzilla and SVN, > > I would want to figure this out first. (Or we can take a decision to lose > this capability temporarily) we can first figure it out. thats ok for me. Kind regards > > Warm Regards, > Dave > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
> On Dec 7, 2018, at 11:37 AM, Mechtilde wrote: > > Hello > > Am 07.12.18 um 20:26 schrieb Dave Fisher: >> One more bit - >> >> Our openoffice.git mirror of svn is not on git-wip-us.apache.org. >> >> Before we switch from SVN to GitBox/GitHun for our main repository we will >> need to understand how to do the hooks to Bugzilla issues. I will use the >> setup of a Git repository for the Forum setup to figure that out. > > Do we have the hooks from SVN? I’m told by Infra that we will need to do research and perhaps write a Git replacement for the hooks we have between bugzilla and SVN, I would want to figure this out first. (Or we can take a decision to lose this capability temporarily) Warm Regards, Dave >> >> Meanwhile we can get a sense from the Dev teams when they would want to >> switch early next year. >> >> Regards, >> Dave >> > > Kind regards > > -- > Mechtilde Stehmann > ## Apache OpenOffice > ## Freie Office Suite für Linux, MacOSX, Windows > ## Debian Developer > ## Loook, tbsync, libreoffice-canzeley-client > ## PGP encryption welcome > ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hi - > On Dec 7, 2018, at 11:36 AM, Mechtilde wrote: > > Hello Dave > > Am 07.12.18 um 20:01 schrieb Dave Fisher: >> Hi - >> >>> On Dec 7, 2018, at 9:08 AM, Mechtilde wrote: >>> >>> Hello >>> >>> I know there is http://git.apache.org/openoffice.git/ >> >> I “cloned” this to my machine. >> >> This looks like an update git mirror of svn. >> >> I see your latest commits: >> >> $ git log >> commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, >> origin/trunk, origin/HEAD) >> Author: Mechtilde Stehmann >> Date: Fri Dec 7 18:30:38 2018 + >> >>merged actual translation from pootle with actual code base in trunk for >> ru >> >>git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 >> 13f79535-47bb-0310-9956-ffa450edef68 >> >> commit 23744e0c67a04df55971794b54a12afb90354627 >> Author: Mechtilde Stehmann >> Date: Fri Dec 7 18:27:01 2018 + >> >>merged actual translation from pootle with actual code base in trunk for >> ja >> >>git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 >> 13f79535-47bb-0310-9956-ffa450edef68 >> >> commit 6891308ea2b55199eb36583780f62e25d5ac40d4 > > So this is the same as at Github? Yes. That is apache copy. SVN -> git.apache.org -> GitBox -> GitHub. When we switch to GitHub development then it will be: GitHub -> GitBox -> git.apache.org Regards, Dave >> >> Regards, >> Dave >> >>> >>> But I didn't know how it works or it should work. >>> >>> I hope this is the time for our progejt to switch from svn to git as the >>> main repository. >>> We already discussed it several times in the past. >>> >>> Kind Regards >>> > Kind regards > > -- > Mechtilde Stehmann > ## Apache OpenOffice > ## Freie Office Suite für Linux, MacOSX, Windows > ## Debian Developer > ## Loook, tbsync, libreoffice-canzeley-client > ## PGP encryption welcome > ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hello Dave Am 07.12.18 um 20:01 schrieb Dave Fisher: > Hi - > >> On Dec 7, 2018, at 9:08 AM, Mechtilde wrote: >> >> Hello >> >> I know there is http://git.apache.org/openoffice.git/ > > I “cloned” this to my machine. > > This looks like an update git mirror of svn. > > I see your latest commits: > > $ git log > commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, > origin/HEAD) > Author: Mechtilde Stehmann > Date: Fri Dec 7 18:30:38 2018 + > > merged actual translation from pootle with actual code base in trunk for > ru > > git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 > 13f79535-47bb-0310-9956-ffa450edef68 > > commit 23744e0c67a04df55971794b54a12afb90354627 > Author: Mechtilde Stehmann > Date: Fri Dec 7 18:27:01 2018 + > > merged actual translation from pootle with actual code base in trunk for > ja > > git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 > 13f79535-47bb-0310-9956-ffa450edef68 > > commit 6891308ea2b55199eb36583780f62e25d5ac40d4 So this is the same as at Github? > > Regards, > Dave > >> >> But I didn't know how it works or it should work. >> >> I hope this is the time for our progejt to switch from svn to git as the >> main repository. >> We already discussed it several times in the past. >> >> Kind Regards >> Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hello Am 07.12.18 um 20:26 schrieb Dave Fisher: > One more bit - > > Our openoffice.git mirror of svn is not on git-wip-us.apache.org. > > Before we switch from SVN to GitBox/GitHun for our main repository we will > need to understand how to do the hooks to Bugzilla issues. I will use the > setup of a Git repository for the Forum setup to figure that out. Do we have the hooks from SVN? > > Meanwhile we can get a sense from the Dev teams when they would want to > switch early next year. > > Regards, > Dave > Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
One more bit - Our openoffice.git mirror of svn is not on git-wip-us.apache.org. Before we switch from SVN to GitBox/GitHun for our main repository we will need to understand how to do the hooks to Bugzilla issues. I will use the setup of a Git repository for the Forum setup to figure that out. Meanwhile we can get a sense from the Dev teams when they would want to switch early next year. Regards, Dave > On Dec 7, 2018, at 11:01 AM, Dave Fisher wrote: > > Hi - > >> On Dec 7, 2018, at 9:08 AM, Mechtilde wrote: >> >> Hello >> >> I know there is http://git.apache.org/openoffice.git/ > > I “cloned” this to my machine. > > This looks like an update git mirror of svn. > > I see your latest commits: > > $ git log > commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, > origin/HEAD) > Author: Mechtilde Stehmann > Date: Fri Dec 7 18:30:38 2018 + > >merged actual translation from pootle with actual code base in trunk for ru > >git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 > 13f79535-47bb-0310-9956-ffa450edef68 > > commit 23744e0c67a04df55971794b54a12afb90354627 > Author: Mechtilde Stehmann > Date: Fri Dec 7 18:27:01 2018 + > >merged actual translation from pootle with actual code base in trunk for ja > >git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 > 13f79535-47bb-0310-9956-ffa450edef68 > > commit 6891308ea2b55199eb36583780f62e25d5ac40d4 > > Regards, > Dave > >> >> But I didn't know how it works or it should work. >> >> I hope this is the time for our progejt to switch from svn to git as the >> main repository. >> We already discussed it several times in the past. >> >> Kind Regards >> >> Mechtilde >> (Member of the PMC) >> >> Am 07.12.18 um 17:52 schrieb Daniel Gruno: >>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE >>> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] >>> >>> Hello Apache projects, >>> >>> I am writing to you because you may have git repositories on the >>> git-wip-us server, which is slated to be decommissioned in the coming >>> months. All repositories will be moved to the new gitbox service which >>> includes direct write access on github as well as the standard ASF >>> commit access via gitbox.apache.org. >>> >>> ## Why this move? ## >>> The move comes as a result of retiring the git-wip service, as the >>> hardware it runs on is longing for retirement. In lieu of this, we >>> have decided to consolidate the two services (git-wip and gitbox), to >>> ease the management of our repository systems and future-proof the >>> underlying hardware. The move is fully automated, and ideally, nothing >>> will change in your workflow other than added features and access to >>> GitHub. >>> >>> ## Timeframe for relocation ## >>> Initially, we are asking that projects voluntarily request to move >>> their repositories to gitbox, hence this email. The voluntary >>> timeframe is between now and January 9th 2019, during which projects >>> are free to either move over to gitbox or stay put on git-wip. After >>> this phase, we will be requiring the remaining projects to move within >>> one month, after which we will move the remaining projects over. >>> >>> To have your project moved in this initial phase, you will need: >>> >>> - Consensus in the project (documented via the mailing list) >>> - File a JIRA ticket with INFRA to voluntarily move your project repos >>> over to gitbox (as stated, this is highly automated and will take >>> between a minute and an hour, depending on the size and number of >>> your repositories) >>> >>> To sum up the preliminary timeline; >>> >>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >>> relocation >>> - January 9th -> February 6th: Mandated (coordinated) relocation >>> - February 7th: All remaining repositories are mass migrated. >>> >>> This timeline may change to accommodate various scenarios. >>> >>> ## Using GitHub with ASF repositories ## >>> When your project has moved, you are free to use either the ASF >>> repository system (gitbox.apache.org) OR GitHub for your development >>> and code pushes. To be able to use GitHub, please follow the primer >>> at: https://reference.apache.org/committer/github >>> >>> >>> We appreciate your understanding of this issue, and hope that your >>> project can coordinate voluntarily moving your repositories in a >>> timely manner. >>> >>> All settings, such as commit mail targets, issue linking, PR >>> notification schemes etc will automatically be migrated to gitbox as >>> well. >>> >>> With regards, Daniel on behalf of ASF Infra. >>> >>> PS:For inquiries, please reply to us...@infra.apache.org, not your >>> project's dev list :-). >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail:
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hi - > On Dec 7, 2018, at 9:08 AM, Mechtilde wrote: > > Hello > > I know there is http://git.apache.org/openoffice.git/ I “cloned” this to my machine. This looks like an update git mirror of svn. I see your latest commits: $ git log commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, origin/HEAD) Author: Mechtilde Stehmann Date: Fri Dec 7 18:30:38 2018 + merged actual translation from pootle with actual code base in trunk for ru git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 13f79535-47bb-0310-9956-ffa450edef68 commit 23744e0c67a04df55971794b54a12afb90354627 Author: Mechtilde Stehmann Date: Fri Dec 7 18:27:01 2018 + merged actual translation from pootle with actual code base in trunk for ja git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 13f79535-47bb-0310-9956-ffa450edef68 commit 6891308ea2b55199eb36583780f62e25d5ac40d4 Regards, Dave > > But I didn't know how it works or it should work. > > I hope this is the time for our progejt to switch from svn to git as the > main repository. > We already discussed it several times in the past. > > Kind Regards > > Mechtilde > (Member of the PMC) > > Am 07.12.18 um 17:52 schrieb Daniel Gruno: >> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE >> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] >> >> Hello Apache projects, >> >> I am writing to you because you may have git repositories on the >> git-wip-us server, which is slated to be decommissioned in the coming >> months. All repositories will be moved to the new gitbox service which >> includes direct write access on github as well as the standard ASF >> commit access via gitbox.apache.org. >> >> ## Why this move? ## >> The move comes as a result of retiring the git-wip service, as the >> hardware it runs on is longing for retirement. In lieu of this, we >> have decided to consolidate the two services (git-wip and gitbox), to >> ease the management of our repository systems and future-proof the >> underlying hardware. The move is fully automated, and ideally, nothing >> will change in your workflow other than added features and access to >> GitHub. >> >> ## Timeframe for relocation ## >> Initially, we are asking that projects voluntarily request to move >> their repositories to gitbox, hence this email. The voluntary >> timeframe is between now and January 9th 2019, during which projects >> are free to either move over to gitbox or stay put on git-wip. After >> this phase, we will be requiring the remaining projects to move within >> one month, after which we will move the remaining projects over. >> >> To have your project moved in this initial phase, you will need: >> >> - Consensus in the project (documented via the mailing list) >> - File a JIRA ticket with INFRA to voluntarily move your project repos >> over to gitbox (as stated, this is highly automated and will take >> between a minute and an hour, depending on the size and number of >> your repositories) >> >> To sum up the preliminary timeline; >> >> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >> relocation >> - January 9th -> February 6th: Mandated (coordinated) relocation >> - February 7th: All remaining repositories are mass migrated. >> >> This timeline may change to accommodate various scenarios. >> >> ## Using GitHub with ASF repositories ## >> When your project has moved, you are free to use either the ASF >> repository system (gitbox.apache.org) OR GitHub for your development >> and code pushes. To be able to use GitHub, please follow the primer >> at: https://reference.apache.org/committer/github >> >> >> We appreciate your understanding of this issue, and hope that your >> project can coordinate voluntarily moving your repositories in a >> timely manner. >> >> All settings, such as commit mail targets, issue linking, PR >> notification schemes etc will automatically be migrated to gitbox as >> well. >> >> With regards, Daniel on behalf of ASF Infra. >> >> PS:For inquiries, please reply to us...@infra.apache.org, not your >> project's dev list :-). >> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > -- > Mechtilde Stehmann > ## Apache OpenOffice > ## Freie Office Suite für Linux, MacOSX, Windows > ## Debian Developer > ## Loook, tbsync, libreoffice-canzeley-client > ## PGP encryption welcome > ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F >
Re: [Status] New Chance for Translation Teams
Hello, now a big step is done. - we have a current status for the UI translation in pootle. - we will get it for Help translation as soon as possible. - we had recent builds at https://www.openoffice.org/download/devbuilds.html for 4.2-dev - we had some more linux builds at http://home.apache.org/~mechtilde/NewBuild/ and win builds at http://home.apache.org/~mseidel/AOO-builds/AOO-420-L10n/ If anyone miss a language build or an update in SVN please tell us. We will prepare it. Kind regards Mechtilde Am 27.11.18 um 13:27 schrieb Mechtilde: > Hello, > > in the last month I was working on an update for the translation > process. For a few languages it works fine. At this time it is a more > manual process than an automatic one. I will improve it to be more > automatic. > > Every team who want to improve their translation can write it here. Then > I will extract the previous translation from pootle, merge > them with the actual code base and put them back to pootle. > > I put first builds as RPMS for en-US, de and it at > https://home.apache.org/~mechtilde/NewBuild . > > There are als builds for ar, kab, ro and uk. > > Now I will work at adding the new *.sdf file to repo and then back to > pootle. > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: Speichern
Also es lohnt sich, unter die Haube zu schauen, um zu sehen, was docx eigentlich produziert. Ich muss mit OpenOffice ständig Buchtexte (also längere Texte) die mit Word bearbeitet wurden, öffnen. Dabei mache ich immer wieder die Beobachtung, dass Microsoft am laufenden Band und ohne Wissen oder Zutun des Anwenders dutzende, manchmal sogar hunderte Formatvorlagen produziert, die es selbst nicht verwendet! Microsoft hält sich nicht an internationale .xml-Spezifikationen. Ein konkretes Beispiel: Word sieht zwischen jeder Fußnote in der Formatvorlage für Fußnoten einen Abstand von 3mm vor, es erscheinen aber 0mm. Mit anderen Worten Word ignoriert diese 3mm, die es selbst vorgibt. Effekt: OpenOffice beim Öffnen eine Word-Dokuments respektiert diese 3mm, die ja in der Formatvorlage spezifiziert wurden, kann sie aber nicht entfernen, weil kein Menüpunkt hierfür vorgesehen ist. Lösung: ich muss den importierten Text zunächst speichern und schließen, die Dateiendung .odt in .zip ändern, diese Zip-Datei entpacken, den darin enthaltenen "styles.txt" (oftmals 200kb groß statt den 20kb, mit denen sich OpenOffice begnügt) durch einen sauberen Original-styles.txt ersetzen, das Ganze wieder zippen und die Dateiendung von .zip wieder auf .odt ändern. Dann ist alles perfekt. LibreOffice, anstatt hier zu stolpern, bietet hier und da bequeme Möglichkeiten, mit solcherart Problemen umzugehen, während OpenOffice hier sogar zum Absturz gebracht werden kann. Das ist von Word so gewollt. Aber die Lösung von LO ist nicht befriedigend, weil sie die von Word absichtlich eingebauten Stolpersteine nicht beseitigt, sondern sich denen nur anpasst, so dass letztlich auch hier keine Garantie besteht. Eine langjährige Freundin von mir, die sehr viele Bücher formatiert, sagt mir, dass Word es mittlerweile so bunt treibt, dass es über die eigenen Stolpersteine stolpert und unwiederbringlich abstürzt. Viele Grüße Dave On Fri, 7 Dec 2018 at 17:16, Peter Kovacs wrote: > In der Tat. dev@ ist eine englische Liste. Wenn schon Entwickler auf > deutsch dann dev-de > > calc = excel > > write = word > > impress = powerpoint. > > > Die neuen Formate werden nicht unterstützt weil es niemand einbaut. Alle > aktiven Entwickler fokussieren sich auf andere Themen. Wenn sich jemand > findet der es einbauen möchte wird es kommen. > > Libre Office bringt diese Funktionalität, wenn du sie benötigst. > Empfehlen kann ich das Format aus technischen Gründen aber nicht. Libre > Office Mitglieder haben da einen schönen Vortrag zu dem Thema gehalten. > > Ich glaube sogar auf der letzten OpenRheinRuhr. > > > Beste Grüße > > Peter > > On 07.12.18 14:19, Dr. Michael Stehmann wrote: > > Hello, > > > > You are on a wrong mailing list here. Better take > > > > users...@openoffice.apache.org > > > > Regards > > Michael > > > > Hallo, > > > > Du bist hier auf der falschen Liste. Deine Fragen sind hier besser > > aufgehoben: > > > > users...@openoffice.apache.org > > > > Gruß > > Michael > > > > Am 07.12.2018 um 10:23 schrieb Dietmar: > >> Hallo, > >> heute habe ich mir open office heruntergeladen und installiert. > >> 2 fragen hätte ich, > >> welche icen muss ich nehmen für excel, word und powerpoint? > >> und warum kann ich die dateien nicht im neuen format von Microsoft > >> abspeichern? > >> > >> Gruß > >> Dietmar > >> > > > - > To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-de-h...@openoffice.apache.org > >
Re: Forum migration - Wish list
We’ll need to evaluate extensions. Please provide the url from phpBB.com. Sent from my iPhone On Dec 7, 2018, at 8:26 AM, FR web forum wrote: >> it would take a direct icon, without editing the first post) and >> insert the green check as search options. > This is not an inner feature for PhpBB 3.2 > It must install an extension > > - > 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: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Git is open source. https://en.m.wikipedia.org/wiki/Git GitHub was just acquired by Microsoft. GitLab is an alternative to GitHub. GitBox is a service from Apache Infrastructure to coordinate replication of GitHub with internal copies of everything in the Apache space. If GitHub were to go away then nothing is lost and a switch to something like GitLab is possible. Sent from my iPhone > On Dec 7, 2018, at 9:28 AM, JD wrote: > > Except that GIT is now owned by MS > > I seriously DOUBT that MS will support a competitor to it's > office software on their "OWNED" enterprise website. Microsoft is not concerned about OpenOffice. For example 50% of the VMs running on Azure are Linux. > > I think it would be a bad idea!!! GitHub repositories will be very convenient for our support configurations - forum, MediaWiki, and updates service. > > > >> On 12/07/2018 10:08 AM, Mechtilde wrote: >> Hello >> >> I know there is http://git.apache.org/openoffice.git/ >> >> But I didn't know how it works or it should work. I wonder what’s in there. >> >> I hope this is the time for our progejt to switch from svn to git as the >> main repository. >> We already discussed it several times in the past. I’m not sure, that’s up to the active developers. It could make sense for language translations. Regards, Dave >> >> Kind Regards >> >> Mechtilde >> (Member of the PMC) >> >>> Am 07.12.18 um 17:52 schrieb Daniel Gruno: >>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE >>> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] >>> >>> Hello Apache projects, >>> >>> I am writing to you because you may have git repositories on the >>> git-wip-us server, which is slated to be decommissioned in the coming >>> months. All repositories will be moved to the new gitbox service which >>> includes direct write access on github as well as the standard ASF >>> commit access via gitbox.apache.org. >>> >>> ## Why this move? ## >>> The move comes as a result of retiring the git-wip service, as the >>> hardware it runs on is longing for retirement. In lieu of this, we >>> have decided to consolidate the two services (git-wip and gitbox), to >>> ease the management of our repository systems and future-proof the >>> underlying hardware. The move is fully automated, and ideally, nothing >>> will change in your workflow other than added features and access to >>> GitHub. >>> >>> ## Timeframe for relocation ## >>> Initially, we are asking that projects voluntarily request to move >>> their repositories to gitbox, hence this email. The voluntary >>> timeframe is between now and January 9th 2019, during which projects >>> are free to either move over to gitbox or stay put on git-wip. After >>> this phase, we will be requiring the remaining projects to move within >>> one month, after which we will move the remaining projects over. >>> >>> To have your project moved in this initial phase, you will need: >>> >>> - Consensus in the project (documented via the mailing list) >>> - File a JIRA ticket with INFRA to voluntarily move your project repos >>> over to gitbox (as stated, this is highly automated and will take >>> between a minute and an hour, depending on the size and number of >>> your repositories) >>> >>> To sum up the preliminary timeline; >>> >>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >>> relocation >>> - January 9th -> February 6th: Mandated (coordinated) relocation >>> - February 7th: All remaining repositories are mass migrated. >>> >>> This timeline may change to accommodate various scenarios. >>> >>> ## Using GitHub with ASF repositories ## >>> When your project has moved, you are free to use either the ASF >>> repository system (gitbox.apache.org) OR GitHub for your development >>> and code pushes. To be able to use GitHub, please follow the primer >>> at: https://reference.apache.org/committer/github >>> >>> >>> We appreciate your understanding of this issue, and hope that your >>> project can coordinate voluntarily moving your repositories in a >>> timely manner. >>> >>> All settings, such as commit mail targets, issue linking, PR >>> notification schemes etc will automatically be migrated to gitbox as >>> well. >>> >>> With regards, Daniel on behalf of ASF Infra. >>> >>> PS:For inquiries, please reply to us...@infra.apache.org, not your >>> project's dev list :-). >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
I think you confuse Github [1] and git [2]. The first is a company that offers a service. Microsoft bought and can influence business decisions. The other is a technology where participants disclaim their copyrights (please note that on GPL licenses not all copyrights are disclaimed. The exception is to change the license.) I simplify of course to make a point. All the Best Peter [1] github.com [2] https://git-scm.com/ On 07.12.18 18:28, JD wrote: > Except that GIT is now owned by MS > > I seriously DOUBT that MS will support a competitor to it's > office software on their "OWNED" enterprise website. > > I think it would be a bad idea!!! > > > > On 12/07/2018 10:08 AM, Mechtilde wrote: >> Hello >> >> I know there is http://git.apache.org/openoffice.git/ >> >> But I didn't know how it works or it should work. >> >> I hope this is the time for our progejt to switch from svn to git as the >> main repository. >> We already discussed it several times in the past. >> >> Kind Regards >> >> Mechtilde >> (Member of the PMC) >> >> Am 07.12.18 um 17:52 schrieb Daniel Gruno: >>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE >>> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] >>> >>> Hello Apache projects, >>> >>> I am writing to you because you may have git repositories on the >>> git-wip-us server, which is slated to be decommissioned in the coming >>> months. All repositories will be moved to the new gitbox service which >>> includes direct write access on github as well as the standard ASF >>> commit access via gitbox.apache.org. >>> >>> ## Why this move? ## >>> The move comes as a result of retiring the git-wip service, as the >>> hardware it runs on is longing for retirement. In lieu of this, we >>> have decided to consolidate the two services (git-wip and gitbox), to >>> ease the management of our repository systems and future-proof the >>> underlying hardware. The move is fully automated, and ideally, nothing >>> will change in your workflow other than added features and access to >>> GitHub. >>> >>> ## Timeframe for relocation ## >>> Initially, we are asking that projects voluntarily request to move >>> their repositories to gitbox, hence this email. The voluntary >>> timeframe is between now and January 9th 2019, during which projects >>> are free to either move over to gitbox or stay put on git-wip. After >>> this phase, we will be requiring the remaining projects to move within >>> one month, after which we will move the remaining projects over. >>> >>> To have your project moved in this initial phase, you will need: >>> >>> - Consensus in the project (documented via the mailing list) >>> - File a JIRA ticket with INFRA to voluntarily move your project repos >>> over to gitbox (as stated, this is highly automated and will take >>> between a minute and an hour, depending on the size and number of >>> your repositories) >>> >>> To sum up the preliminary timeline; >>> >>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >>> relocation >>> - January 9th -> February 6th: Mandated (coordinated) relocation >>> - February 7th: All remaining repositories are mass migrated. >>> >>> This timeline may change to accommodate various scenarios. >>> >>> ## Using GitHub with ASF repositories ## >>> When your project has moved, you are free to use either the ASF >>> repository system (gitbox.apache.org) OR GitHub for your development >>> and code pushes. To be able to use GitHub, please follow the primer >>> at: https://reference.apache.org/committer/github >>> >>> >>> We appreciate your understanding of this issue, and hope that your >>> project can coordinate voluntarily moving your repositories in a >>> timely manner. >>> >>> All settings, such as commit mail targets, issue linking, PR >>> notification schemes etc will automatically be migrated to gitbox as >>> well. >>> >>> With regards, Daniel on behalf of ASF Infra. >>> >>> PS:For inquiries, please reply to us...@infra.apache.org, not your >>> project's dev list :-). >>> >>> >>> >>> - >>> 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: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Except that GIT is now owned by MS I seriously DOUBT that MS will support a competitor to it's office software on their "OWNED" enterprise website. I think it would be a bad idea!!! On 12/07/2018 10:08 AM, Mechtilde wrote: Hello I know there is http://git.apache.org/openoffice.git/ But I didn't know how it works or it should work. I hope this is the time for our progejt to switch from svn to git as the main repository. We already discussed it several times in the past. Kind Regards Mechtilde (Member of the PMC) Am 07.12.18 um 17:52 schrieb Daniel Gruno: [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] Hello Apache projects, I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org. ## Why this move? ## The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub. ## Timeframe for relocation ## Initially, we are asking that projects voluntarily request to move their repositories to gitbox, hence this email. The voluntary timeframe is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over. To have your project moved in this initial phase, you will need: - Consensus in the project (documented via the mailing list) - File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories) To sum up the preliminary timeline; - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation - January 9th -> February 6th: Mandated (coordinated) relocation - February 7th: All remaining repositories are mass migrated. This timeline may change to accommodate various scenarios. ## Using GitHub with ASF repositories ## When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner. All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well. With regards, Daniel on behalf of ASF Infra. PS:For inquiries, please reply to us...@infra.apache.org, not your project's dev list :-). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hello I know there is http://git.apache.org/openoffice.git/ But I didn't know how it works or it should work. I hope this is the time for our progejt to switch from svn to git as the main repository. We already discussed it several times in the past. Kind Regards Mechtilde (Member of the PMC) Am 07.12.18 um 17:52 schrieb Daniel Gruno: > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE > DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] > > Hello Apache projects, > > I am writing to you because you may have git repositories on the > git-wip-us server, which is slated to be decommissioned in the coming > months. All repositories will be moved to the new gitbox service which > includes direct write access on github as well as the standard ASF > commit access via gitbox.apache.org. > > ## Why this move? ## > The move comes as a result of retiring the git-wip service, as the > hardware it runs on is longing for retirement. In lieu of this, we > have decided to consolidate the two services (git-wip and gitbox), to > ease the management of our repository systems and future-proof the > underlying hardware. The move is fully automated, and ideally, nothing > will change in your workflow other than added features and access to > GitHub. > > ## Timeframe for relocation ## > Initially, we are asking that projects voluntarily request to move > their repositories to gitbox, hence this email. The voluntary > timeframe is between now and January 9th 2019, during which projects > are free to either move over to gitbox or stay put on git-wip. After > this phase, we will be requiring the remaining projects to move within > one month, after which we will move the remaining projects over. > > To have your project moved in this initial phase, you will need: > > - Consensus in the project (documented via the mailing list) > - File a JIRA ticket with INFRA to voluntarily move your project repos > over to gitbox (as stated, this is highly automated and will take > between a minute and an hour, depending on the size and number of > your repositories) > > To sum up the preliminary timeline; > > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) > relocation > - January 9th -> February 6th: Mandated (coordinated) relocation > - February 7th: All remaining repositories are mass migrated. > > This timeline may change to accommodate various scenarios. > > ## Using GitHub with ASF repositories ## > When your project has moved, you are free to use either the ASF > repository system (gitbox.apache.org) OR GitHub for your development > and code pushes. To be able to use GitHub, please follow the primer > at: https://reference.apache.org/committer/github > > > We appreciate your understanding of this issue, and hope that your > project can coordinate voluntarily moving your repositories in a > timely manner. > > All settings, such as commit mail targets, issue linking, PR > notification schemes etc will automatically be migrated to gitbox as > well. > > With regards, Daniel on behalf of ASF Infra. > > PS:For inquiries, please reply to us...@infra.apache.org, not your > project's dev list :-). > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] Hello Apache projects, I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org. ## Why this move? ## The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub. ## Timeframe for relocation ## Initially, we are asking that projects voluntarily request to move their repositories to gitbox, hence this email. The voluntary timeframe is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over. To have your project moved in this initial phase, you will need: - Consensus in the project (documented via the mailing list) - File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories) To sum up the preliminary timeline; - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation - January 9th -> February 6th: Mandated (coordinated) relocation - February 7th: All remaining repositories are mass migrated. This timeline may change to accommodate various scenarios. ## Using GitHub with ASF repositories ## When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner. All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well. With regards, Daniel on behalf of ASF Infra. PS:For inquiries, please reply to us...@infra.apache.org, not your project's dev list :-). - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] Hello Apache projects, I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org. ## Why this move? ## The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub. ## Timeframe for relocation ## Initially, we are asking that projects voluntarily request to move their repositories to gitbox, hence this email. The voluntary timeframe is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over. To have your project moved in this initial phase, you will need: - Consensus in the project (documented via the mailing list) - File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories) To sum up the preliminary timeline; - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation - January 9th -> February 6th: Mandated (coordinated) relocation - February 7th: All remaining repositories are mass migrated. This timeline may change to accommodate various scenarios. ## Using GitHub with ASF repositories ## When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner. All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well. With regards, Daniel on behalf of ASF Infra. PS:For inquiries, please reply to us...@infra.apache.org, not your project's dev list :-). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Forum migration - Wish list
Also the extension is welcome. Il 07/12/18 17:26, FR web forum ha scritto: it would take a direct icon, without editing the first post) and insert the green check as search options. This is not an inner feature for PhpBB 3.2 It must install an extension - 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: Forum migration - Wish list
> it would take a direct icon, without editing the first post) and > insert the green check as search options. This is not an inner feature for PhpBB 3.2 It must install an extension - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Speichern
In der Tat. dev@ ist eine englische Liste. Wenn schon Entwickler auf deutsch dann dev-de calc = excel write = word impress = powerpoint. Die neuen Formate werden nicht unterstützt weil es niemand einbaut. Alle aktiven Entwickler fokussieren sich auf andere Themen. Wenn sich jemand findet der es einbauen möchte wird es kommen. Libre Office bringt diese Funktionalität, wenn du sie benötigst. Empfehlen kann ich das Format aus technischen Gründen aber nicht. Libre Office Mitglieder haben da einen schönen Vortrag zu dem Thema gehalten. Ich glaube sogar auf der letzten OpenRheinRuhr. Beste Grüße Peter On 07.12.18 14:19, Dr. Michael Stehmann wrote: > Hello, > > You are on a wrong mailing list here. Better take > > users...@openoffice.apache.org > > Regards > Michael > > Hallo, > > Du bist hier auf der falschen Liste. Deine Fragen sind hier besser > aufgehoben: > > users...@openoffice.apache.org > > Gruß > Michael > > Am 07.12.2018 um 10:23 schrieb Dietmar: >> Hallo, >> heute habe ich mir open office heruntergeladen und installiert. >> 2 fragen hätte ich, >> welche icen muss ich nehmen für excel, word und powerpoint? >> und warum kann ich die dateien nicht im neuen format von Microsoft >> abspeichern? >> >> Gruß >> Dietmar >> - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
Re: starting 4.1.7 and 4.2.0 Releases
If/When there is a need, I can do it. > On Dec 1, 2018, at 3:24 PM, Matthias Seidel > wrote: > > Hi all, > > Am 13.11.18 um 21:38 schrieb Andrea Pescetti: >> Peter Kovacs wrote: >>> I am just saying a 4.1.7 release has nothing to do with the efforts we >>> have to organize for 4.2.0. >> >> OK, got it! Let's work together on finishing 4.1.6 and then we will >> have plenty of time for discussing about the next releases. > > Due to Family commitments I am no longer able to volunteer as Release > Manager for 4.1.7. Sorry! > > However, I can provide the Windows builds... > > Regards, > >Matthias > >> >> Regards, >> Andrea. >> >> - >> 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
Forum migration - Wish list
I write here my wish for phpBB 3.2.4 when it will be adopted: Replace [Solved] with the green check (you can already do it today but it would take a direct icon, without editing the first post) and insert the green check as search options. Regards charlie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Speichern
Hello, You are on a wrong mailing list here. Better take users...@openoffice.apache.org Regards Michael Hallo, Du bist hier auf der falschen Liste. Deine Fragen sind hier besser aufgehoben: users...@openoffice.apache.org Gruß Michael Am 07.12.2018 um 10:23 schrieb Dietmar: > Hallo, > heute habe ich mir open office heruntergeladen und installiert. > 2 fragen hätte ich, > welche icen muss ich nehmen für excel, word und powerpoint? > und warum kann ich die dateien nicht im neuen format von Microsoft > abspeichern? > > Gruß > Dietmar > signature.asc Description: OpenPGP digital signature
Speichern
Hallo, heute habe ich mir open office heruntergeladen und installiert. 2 fragen hätte ich, welche icen muss ich nehmen für excel, word und powerpoint? und warum kann ich die dateien nicht im neuen format von Microsoft abspeichern? Gruß Dietmar
