Apache OpenOffice now available in Danish, Norwegian, Swedish, Korean, Polish, Basque, Asturian and Scottish Gaelic
The Apache OpenOffice project is pleased to announce the immediate availability of Apache OpenOffice 3.4.1 in 8 new translations: Danish, Norwegian, Swedish, Korean, Polish, Basque, Asturian and Scottish Gaelic.
The award winning Apache OpenOffice 3.4 software, downloaded over 33 million times, already supports US English, German, Japanese, Czech, French, Brazilian Portuguese, Russian, Simplified and Traditional Chinese, Galician, Arabic, Dutch, Spanish, Italian, Hungarian, Khmer, Finnish, British English, Slovenian and Slovak.
Users can download the new translations from our website.
Apache OpenOffice 3.4.1 is available on Windows, MacOS and Linux. The Release Notes contain important information for those upgrading from earlier versions.
Warm thanks and applause go to the many translators who worked on these translations. With your help we can support even more languages in our next release, Apache OpenOffice 4.0. Anyone interested in volunteering is encouraged to read this earlier blog post for information on how to get involved.
Apache OpenOffice-projektet gläds av att kunna tillkännage att Apache OpenOffice 3.4.1, med omedelbar verkan, är tillgängligt i 8 nya översättningar: danska, norska, svenska, koreanska, polska, baskiska, asturiska och skotsk gäliska.
Det prisbelönta Apache OpenOffice 3.4, som laddats ner över 33 miljoner gånger, stödjer redan amerikansk engelska, tyska, japanska, tjeckiska, franska, brasiliansk portugisiska, ryska, förenklad och traditionell kinesiska, galiciska, arabiska, holländska, spanska, italienska, ungerska, khmer, finska, brittisk engelska, slovenska och slovakiska.
De nya översättningarna kan laddas ner från vår hemsida.
Apache OpenOffice 3.4.1 är tillgängligt för Windows, MacOS och Linux. Den nya versionens dokumentation innehåller viktig information för de som uppdaterar från äldre versioner.
Ett varmt tack och applåder går till de många översättare som arbetat med dessa översättningar. Med er hjälp kan vi stödja ännu fler språk i vår nästa version, Apache OpenOffice 4.0. Är man intresserad att hjälpa till, uppmanas man att läsa detta blogginlägg för information om hur man kan bidra.
이제 Apache OpenOffice가 덴마크어, 노르웨이어, 한국어, 폴란드어, 바스크어, 아스투리아스어, 스코틀랜드 게일어를 지원합니다.
Apache OpenOffice 프로젝트는 Apache OpenOffice 3.4.1 버전의 새로운 8개 번역본을 발표하게 된 것을 기쁘게 생각합니다.
다양한 수상 경력에 빛나며 3천만회 이상의 다운로드를 기록한 Apache OpenOffice 3.4 버전은 이미 미국 영어, 독일어, 일본어, 체코어, 프랑스어, 브라질 포르투칼어, 러시아어, 중국어, 갈라시아어, 아랍어, 네덜란드어, 스페인어, 이탈리아어, 헝가리어, 크메르어, 필란드어, 영국 영어, 슬로베니아어, 슬로바키아어를 지원하고 있습니다.
사용자들은 우리 웹사이트 에서 새로운 번역본을 다운로드할 수 있습니다.
Apache OpenOffice 3.4.1은 윈도우, 맥 OS, 리눅스 용으로 제공됩니다. 배포 노트 에는 이전 버전에서 업그레이드하기 위한 중요한 정보가 포함되어 있습니다.
Al proyeutu Apache OpenOffice presta-y dar anuncia de la disponibilidá inmediata d'Apache OpenOffice 3.4.1 en 8 nueves traducciones: danés, noruegu, suecu, coreanu, polacu, vascu, asturianu y gaélicu escocés.
El premiáu software Apache OpenOffice 3.4, descargáu más de 33 millones de vegaes, yá tien sofitu pal inglés de los EE.XX., alemán, xaponés, checu, francés, portugués del Brasil, Rusu, chinu simplificáu y tradicional, gallegu, árabe, neerlandés, castellanu, italianu, húngaru, khmer, finlandés, inglés británicu, eslovenu y eslovacu.
Los usuarios puen descargar les nueves traducciones del nuesu sitiu web
Apache OpenOffice 3.4.1 ta disponible pa Windows, MacOS y Linux. Les Notes de llanzamientu contienen información importante pa los qu'anueven dende versiones anteriores.
Candiales gracies y un aplausu pa los munchos traductores que trabayaron n'estes traducciones. Cola to ayuda podremos sofitar inda más llingües nel siguiente llanzamientu, Apache OpenOffice 4.0. A toles persones interesaes en ser voluntaries encamentamos-yos lleer esta entrada anterior del blog pa más información tocante a cómo collaborar.
Apache OpenOfficeプロジェクトは、OpenOffice 3.4.1で新たに8つの言語版が ただちにご利用いただけるようになったこと をお知らせいたします。デンマーク語版、ノルウェー語版、スウェーデン語版、韓国語版、ポーランド語版、バスク語版、アストゥリアス語版およびスコットランド・ゲール語版の8つです。
新たな言語版は 私たちのウェブサイト からダウンロードしていただけます。
Apache OpenOffice 3.4.1 は、Windowsでも、MacOSでも、Linuxでもご利用いただけます。 リリースノート には、以前のバージョンからのアップグレードに必要な情報が書いてあります。
O projeto Apache OpenOffice tem o prazer de anunciar de
imediato a atualização do Apache OpenOffice 3.4.1, em 8
novas traduções: Dinamarquês, Norueguês, Sueco, Coreano, Polônes,
Basco, Australiano e Gálego Escocês.
O premiado Apache OpenOffice 3.4, teve mais de 33 milhões de downloads, e já suporta várias linguas: Inglês (EUA), Alemão, Japonês, Tcheco, Francês, Português do Brasil, Russo, Chinês simplificado e tradicional, Galego, Árabe, Holandês, Espanhol, Italiano, Húngaro, Khmer , Finlandês, Inglês Britânico, Esloveno e Eslovaco.
Podem baixar as novas versões em nosso site
Apache OpenOffice está disponível para Windows, Mac OS e Linux. Na nota do lançamento (inglês) tem anotações importantes para atualizações e as versões antigas.
Sinceros agradecimentos e aplausos para todos tradutores que trabalharam nas traduções. Com sua ajuda nós podemos suporta ainda mais idiomas nas próximas versões, Apache OpenOffice 4.0. Quem tiver interesse em ser voluntário é incentivado a ler esse post no blog (inglês) que possui informações de como participar do projeto.
Apache OpenOffice-prosjektet kan med glede offentliggjøre at Apache OpenOffice 3.4.1, med umiddelbar virkning, er tilgjengelig i 8 nye oversettelser: dansk, norsk, svensk, koreansk, polsk, baskisk, asturisk og skotsk gælisk.
Det prisbelønte Apache OpenOffice 3.4-programmet, som har blitt lastet ned mer enn 33 millioner ganger, støtter allerede amerikansk engelsk, tysk, japansk, tsjekkisk, brasiliansk portugisisk, russisk, forenklet og tradisjonell kinesisk, galisisk, arabisk, nederlandsk, spansk, italiensk, ungarsk, khmer, finsk, britisk engelsk, slovensk og slovakisk.
De nye oversettelsene kan lastes ned fra vår hjemmeside.
Apache OpenOffice 3.4.1 er tilgjengelig på Windows, MacOS og Linux. Den nye versjonens dokumentasjon inneholder viktig information for de som oppdaterer fra eldre versjoner.
Vi ønsker å takke og applaudere de mange oversetterne som har arbeidet med disse oversettelsene. Med deres hjelp kan vi støtte enda flere språk i vår neste utgave, Apache OpenOffice 4.0. De som ønsker å bidra kan lese dette blogginnlegget for informasjon.
Merging Lotus Symphony: Allegro moderato
The house lights flash; Please take your seats. The symphony is about to begin.
Apache OpenOffice will soon have some new features and other
improvements, courtesy of IBM and their Lotus Symphony effort. Interoperability, performance, accessibility improvements, as well as exciting new user interface elements are in the works. Read on to
learn how the Apache OpenOffice volunteer community is doing this, and how this will benefit users of OpenOffice as well as developers who build upon OpenOffice.
Movement I: The Contribution.
IBM Lotus Symphony is an IBM licensed derivative of OpenOffice, offered at no charge, which IBM enhanced for their customer and corporate use. Symphony was developed with OpenOffice.org technology, essentially a fork of OpenOffice. Last May IBM decided to end that fork and combine their development effort with the Apache OpenOffice project. IBM contributed the source code for Symphony to Apache, via a Software Grant Agreement (SGA). (An SGA is an agreement by which a code base developed outside of Apache is contributed to Apache under specified licensing terms.) Since the areas that IBM improved Symphony are also areas of interest for OpenOffice users, and for 3rd party products based on OpenOffice, the Apache OpenOffice project was glad to receive this contribution.
Once the Symphony contribution was received and checked into the Apache OpenOffice version control, the discussion to determine the best way to use this new code. The two primary options discussed on our mailing list were:
- Make the Symphony code the new base for Apache OpenOffice. Then merge back into Symphony the code improvements that had been made in Apache OpenOffice 3.4.
- Continue with the existing Apache OpenOffice 3.4 as the base and merge features from Symphony into that code.
There were good arguments for either approach, and we had a spirited discussion. The main points were:
- Using Symphony as the new base would have required careful review of that code base, and months of additional work to bring it up to Apache IP requirements. Essentially we would need to redo much of the work we had already done with the OpenOffice code that Oracle had contributed via their SGA. This would have been more disruptive to other, non-IBM, OpenOffice developers, but would have brought the distinguishing Symphony features to a release faster.
- Merging Symphony features into OpenOffice would be less disruptive, but would be a slower path to integrating Symphony features, and would require more attention from IBM, since they know the Symphony code best.
In the end the consensus was to go with the 2nd option, merging Symphony code into OpenOffice. This brings the Symphony code, feature by feature, bug fix by bug fix, into OpenOffice, where it is integrated, tested, reviewed, etc., in smaller chunks, as it works its way toward release. Doing it this way is less flashy. There is no 'big bang integration" where everything happens at once. But that was the point, to avoid the disruptions of a radical change in the code base.
Work on the "slow merge" has been ongoing since last summer, in parallel with work on Apache OpenOffice 3.4.1. Our use of Apache Subversion facilitated this kind of parallel development, where one group focused on the 3.4.1 release in a "branch", another group of developers started to bring Symphony enhancements into the "trunk".
Movement II: Many Bug Fixes
Expect to see a lot of bug fixes in Apache OpenOffice 4.0, especially in the area of Microsoft interoperability. The Symphony team reviewed their IBM bug reports from Symphony and pulled out the most important ones that were already fixed in Symphony. They then tested Apache OpenOffice, to see which of these bugs still existed in OpenOffice. For the ones that still were in OpenOffice, they merged in the fix from Symphony. This was a very efficient approach to a targeted merge and led to many fixes, include the following so far (and we're still months away from release):
- To open a sample file contains chart with large data source can lead to AOO crash
- Application crashed if undo paste text from shape
- Impress crashed when play screen show with sample file
- Crash if undo redo creating data pilot from imported data
- Application crash if insert sample file to section
- Application crashed if undo/redo covert nest table to text
- Undo redo insert file cause application crashed
- User-definded format code is lost with a cell which value is TRUE or FALSE when importing xls file
- Loading performance for xls file with row banded style is bad
- Macro doesn't work if click "Undo" button
- Chart data lost if the source data refers to a range name which is defined as a reference formula
- Sample file's table border is missing
- Page number in footer display incorrectly
- Text is overlapped by the drawing object when open the .doc file
- "Fit shape to text" property not work after openning ppt by AOO
- It costs too much memory to open a large spreadsheet file containing pivot tables
- Numbering will lose when saving or opening a ppt file
- Color of underline display wrongly
- Grid size for snake wipe transition too fine
- Bookmark value changed when opening the doc file
- Repeat count of animations ignored.
- Fill color animations run too fast
- Table changes to multiple shapes after saved in AOO
- after save the sample file with page border and shadow to doc, the shadow depth and color changed
- The graphic's spacing is not correct when open the .doc file
- The graphic's border size and spacing is not correct when open the .doc file
- Animation color is not exported correctly to PPT.
- Number range variable filed shows in AOO
- import of Microsoft Word document: indent of certain paragraphs in list is wrong
- the text properties from table style are lost for table in the docx file
- the background color from table style are lost for table in the docx file
- Page number in footer alignment changed after saved
- Shape Gradient MS2003 import/export Enhancement
- Connector line does not shown correctly in grouped object
- characters at the beginning of each lines in shape are lost when loading the sample ppt in AOO
- disable antialiased lines for background hatches
- Cell text direction changed after saved as doc file
- Time format is different than MS Office
- the text in textbox display paritially when opening .ppt file
- After doc file saved by AOO, one more section is created
- Doc file saved by AOO, section size changed
- the text in the table turn to black from white when opening the pptx file
- the background of the file create from template 'blue_floral.otp' changed after save as the ppt or pot file
- Filter is not shown in merged cell
- Need press "ESC" key twice to exist chart edit mode
- Cannot modify the second document even if close range picker in first document
- Pie chart height becomes greater when open Excel file
- Ellipse shape display too large in MS office after save odp file to ppt format file
- Formula GETPIVOTDATA returns #REF! value
- The Emphasis or Exit or Motion Path effect can not play if there is an Entrance effect after it.
- Picture missing when saving ODP file
- Number displays different from MS with the same format code
- TOC should not be updated if load doc in Writer
- Placeholder in ppt file created by MS 2007 is lost if load in Impress
- Text outside quotation cannot be paste in cell
- Cannot open sample file
- Application crashed if undo add caption to drawing object
- Underline "_" can not work with ";" in format code, the semicolon will always be regarded as separator
- Last agrument of formula should not be removed
- Removing chart in odt file, it causes a crash.
- Graphic in header and footer can not be displayed correctly
- Crash when redo split the pasted table
- Number formating are changed after save and reopen it again.
- Import .pptx file into OO3.4, the vertical text direction of the table will be lost.
- Shape border and fill color lost if open the ppt doc via AOO
- Shape shadow position changed incorrect if open the ppt doc via AOO
- Fontwork alignment changes after saving to another ppt with AOO
- The graphic background in left table display incorrectly when using AOO open the sample .ppt file
- Vertical text direction in table cell change to horizontal after saving to another .ppt by AOO
- The vertical text alignment of the placeholder is wrong while opening the ppt file in AOO
- all drawing objects lost aftering saving to another ppt by AOO
- Line transparency value is lost after saving as another ppt by AOO
- Graphic bullet is incorrect in the .ppt doc which saved via AOO
- The bullet in outline area lost after openning by AOO
- Some shapes in master page lose after save to another ppt by AOO
- The position of conncector change after save to another ppt by AOO
- Froze when saving the doc file to another one.
- TOC jumping function lost if save document by AOO
- star and symbol shape in ppt changed after openning by AOO
- Transparency setting of Fill color lost in cell comments.
- animation flash once doesn't work after save the ppt by aoo
- exit animation changed after save as ppt file to another ppt
- Page number lost if save template to doc format
- Some numbering format not support
- Additional dot appear after the numbering.
- Apply Envelope page style cause application crash
- Crash after delete column(s) from chart's source table, and then adjusted table size
- [Crash]When press "Ctrl+Shift+Backspace" in table cell "A1" ,Undo,crash
- Font size increased if saved by AOO
- Hyperlink font size increased if saved to .doc file
- Function "Case sensitive" in "Special Filter" dialog can not work.
- Shape shadow lost if load .doc file in AOO
- Macro button lost if save template to .doc file
- Teardrop shape can not show correct in pptx sample file
- Bullet color is lost when open pptx sample file
- Arrow shape changed is save doc file by AOO
- Outline level in sample file lost
- the .doc page number is incorrect when opened in aoo 3.4
- [BiDi]The order of Hebraic string are changed after save as new .doc
- Alphabetical and roman numberals became ditial numbering
- Text font spacing in comments doesn't expand/condense by the expected value
- The left-style columns display with the same width when opening with AOO
- MS Word that has Table that with Text wrap around the table can not be shown correctly
- MS's Macro button symbol can't correct display in aoo 3.4
- ][BIDI]The position and direction of Right bracket is incorrect in Arabic locale
- Paragraph indent and spacing between bullets and text are inconsistent with MS word
- the content display mess when open the sample in AOO3.4
- WMF graphic size changed too small to see if saved by AOO
- The text box style display incorrectly when open the sample in AOO3.4
- Vertical letters in "VerticalText" fontwork get horizontal when opening .ppt file
- Table rows get heighter when opening a .docx file with AOO 3.4
- Column header can not be displayed correclty in AOO3.4 after open the xls file.
- font size of Fontwork changes from 96 to 36 after save as new .doc file
- Text anchor in subtitle text box is changed from Top to Center when open a pot template in AOO3.4
- Can't pop up protect password dialog when attempt to unprotect sheet with password for xls file in AOO.
- Can't open by MS Office correctly when save sample file contain line with text to ppt format file
- Position of drawing obj incorrect when opening .doc in aoo 3.4 if the text direction of the whole document is vertical
- paragraph>pagination> Window/Orphan control setting lost after save the .doc file by aoo 3.4
- The title text is Align left in sample file, while in MS Office ,it is align right.
- he table border got lost when open the .ppt file in AOO
- The title text is not Italic in Studio design template like that in MS Office.
- sequence number is not displayed when open docx
- Failed to open sample file but no any feedback to user
- <Shape><Extrusion>The Extrusion direction of shape can't be saved correctly
- arrow change size and position in MS after save odp to ppt format
- Trendline of two Data Series can't be displayed but after edit it the trendline will be showed correctly
- the bullet color display incorrectly in AOO3.4
- the subtitle area of ppt file display incorrectly in AOO3.4
- Can not open the sample ppt file which contain vb controls in the slide master.
- The line indent change after save once by AOO
- the right brace shape cannot display after save the sample .odt file to .doc file then reopen in aoo
- One shape's border cannot be displayed completely
- Text and fill color in a table are lost while opening a ppt file
- Text in a text box can not be displayed correctly
- a pic in the .doc file cannot display in Aoo 3.4
- The numbering in table cell changes to bullets when saved in AOO
- Item lists are incorrectly imported by Symphony.
- Picture is lost when opening sample PPT file
- Import file created by MS Excel, if there is blank item selected in Page filed of Pivot Table, the selection will be lost.
- one column is lost if opened in AOO
- [Crash]When save the file as ppt, AOO crashes
- PPT Import:Word Art becomes larger
- Arrow style of line changes after save the sample file to a new .ppt file.
- AOO crash if a connector which connected to PPT table
- The .xlsx sample file is opened with modified state
- Under Handout view mode, Header&Footer displays inconsistent with the one presented in MS PowerPoint
- Images lose macro association when open Excel file in AOO.
- TOC lost if saved by AOO
- PPT Import:Cell background color in table gets lost while opening a ppt file with AOO
- PPT Export: Diagram bullet can not be displayed correctly after saved as *.ppt in AOO
- page number in header lost when we save the .doc file as another in web layout
- Picture shadow lost after saved by AOO
- Form controls cannot be saved into .ppt file in AOO3.4
- text alignment changed from left to center when importing the docx
- The position of Shape (connectors) in slide is incorrect after save once by AOO3.4.
- The image OLE's icon doesn't display correctly in Aoo3.4
- Formula field lost
- the shape 3D property effect in MS PPT can't be load correctly.
- Some field is not shown
- White block( on Mac and Black block on Windows) appears if click somewhere else in presentation
- Presentation crashed if exit screen show
- Writer crash after modify properties of new Frame
- Calc crashes when Redo refreshing data
- Create summary slide in .odp file which has expanded blank slides in,there is a crash.
- Calc crashed if paste unsupport formula from MS Excel
- Worksheet.Change event works not correctly
- Application.Run could not work correctly
On our wiki you can see a visual "before & after" look and some of these fixes.
Movement III: New Features
Of course, a long list of bug fixes is impressive, but what about new features? Symphony brings those as well. A large one is a user interface addition of a "Task Pane". Since a Task Pane is continuously available, it can greatly improve productivity with some repetitive operations. Symphony had one version of this feature, but we're not just doing a literal copy of that UI, since grafting a UI of one application onto another is rarely successful. So we're reviewing several variations on a Task Pane design, which you can see on our wiki. Coding for this feature is ongoing in a branch.
Symphony had a nice collection of clipart and themes, and we're bringing those into OpenOffice.
IAccesible2 is an interface used by "assistive technologies" (screen readers, etc.) to help persons with disabilities use desktop applications. We're bringing the IAccesible2 support from Symphony into OpenOffice. Coding for this feature is also ongoing in a branch.
Movement IV: più allegro, anyone?That's a summary of what Symphony is bringing to Apache OpenOffice 4.0 and beyond. Users of OpenOffice will benefit from these enhancements, of course. But so will other products, based on Apache OpenOffice, as they build their solutions on top of Apache OpenOffice, or selectively copy functionality from our releases.
When exactly will Apache OpenOffice 4.0 be released? We don't have a date set yet, but we think it will be before mid-year. As a volunteer-led open source project we rely on our volunteers to set the direction and pace of the work. We welcome help in any of these areas, from developers of course, but also from associated project functions, like QA, design, documentation, translation, marketing, etc. If you are interested in volunteering with the Apache OpenOffice project, please read our "Getting Involved" page. With your help we can go even faster!
Books about OpenOffice
As the leading open source office productivity suite for over a decade, it is not surprising that Apache OpenOffice (formerly OpenOffice.org) has attracted attention from authors of technical instruction books. A search of the catalog of online book retailers shows many titles, including a new one on OpenOffice Basic from as recently as a few weeks ago.
We encourage books to be written about Apache OpenOffice. This is good for the ecosystem. We keep a list of known books about OpenOffice on our website. If you know of a book that we are missing, be sure to let us know via our marketing mailing list.
Also, authors and publishers of books related to OpenOffice are encouraged to contact us (via the above marketing mailing list). We can help in several ways. For example, we can answer any technical questions you might have about OpenOffice. We can also answer any of your questions regarding the use of Apache OpenOffice trademarks in your book. We're also interested in doing interviews with authors for this blog. Again, contact the marketing mailing list for more information.
Posted at 02:02AM Jan 11, 2013 by robweir in General | |
Your top questions answered
A little over a month ago we asked our users to submit questions to us, on any OpenOffice-related topic. Users also had the opportunity to vote questions up or down, so we could identify the questions that were of the greatest interest. We received 274 questions, and 1,743 votes were cast by 365 users. Thanks to all who participated! Let is know, via your comments, whether such Q&A is useful.
But without further delay, the top questions, as voted by you, along with our answers, are:
1a. "From an end user's point of view what is the advantage of OpenOffice over LibreOffice?"
1b. "What is the difference between LibreOffice and Apache OpenOffice ? "
(Combining two related questions)
The question asked for an end-user point of view, so we went and asked our users what they thought. Using our Facebook page we asked the following question: "You have a choice of several open source office suites. Why do you use OpenOffice rather than alternatives like LibreOffice or KOffice?"
The results were:
- Features (47%)
- Quality (22%)
- Compatibility/Interoperability (22%)
- Reputation/Familiarity (9%)
Of course, your needs and preferences may or may not be the same as these users.
2. "Why are some bugs never handled? I've reported at least one -- a
showstopper for some MS Office users -- that has never been fixed nor,
so far as I can tell, even viewed seriously. Even just more feedback
would be appreciated."
Giving a specific answer is impossible, since we don't know what bug the user is referring to. But in general terms we treat all bug reports seriously. Our testers attempt to verify them and then classify them according to severity and priority. We don't release a new version of Apache OpenOffice if there are outstanding showstopper issues. In any case, we encourage the user to communicate the details of their concern directly to the project by commenting on the specific defect report in Bugzilla.
3."Do you share code with Libre? sub question A: If so, will you soon both be even more similar -- in effect unforked? Sub question B: If you are not using each other's code, why not?"
We cooperate and coordinate and share with LibreOffice, as well as other open source and even proprietary application vendors, in several ways:
- We coordinate on the response and responsible disclosure of security vulnerabilities that may affect both products due to their common code base. Although this is not visible to the public, due to the sensitive nature of the topic, there is a shared mailing list subscribed to by security experts from both projects, where we address such issues for the mutual benefit of our users.
- Experts from both projects, along with representatives from other open source and proprietary products, work together at OASIS, on the Open Document Format standard, which is the native format for both projects. For example, experts from several open source projects are active in defining enhanced change tracking for ODF 1.3.
- Similarly, at ODF Plugfests we work with other editor vendors, open source and proprietary, on testing and other activities to improve interoperability.
- The code that we create in Apache OpenOffice is under the Apache License 2.0, which is compatible with most other open source licenses, including those used by LibreOffice. So all of our code is made available for others to use. This is not just a theoretical statement. We see ongoing integration of Apache OpenOffice features into LibreOffice. This is a good thing, and we encourage it.
- It is easy for developers to contribute their work to both Apache OpenOffice and other open source projects as well. We have a few volunteers who are happy to contribute to both projects, and we've seen programmers contribute their patches to both LibreOffice as well as Apache.
So there is a good amount of sharing already occurring, though not as much as we'd like to see. We'll continue to seek ways to engage more directly with LibreOffice developers, including at the upcoming FOSDEM conference in February.
4. "Now that Apache OpenOffice is part of the Apache Software Foundation, can we then expect a cloud solution ? (NOT only interface, but also collaboration tracking)."
It is often thought that Apache is only about server software, or only about cloud computing. Certainly the ASF hosts some key applications in this space, from the Apache HTTP Server to Apache Hadoop. But Apache has all sorts of software projects, from developer-oriented tools like Apache Ant and Apache Maven, to domain specific libraries like Apache OpenNLP. What is common across the Apache projects is not technological. The commonalities are:
- A common permissive open source software license, the Apache License 2.0
- A common way of working within a project, a set of social/cultural norms called The Apache Way.
- The common benefits of working within an established non-profit foundation.
- Shared responsibilities for common infrastructure, common events (ApacheCon, for example).
But aside from these commonalities, each project charts its own path for how its product evolves. So moving to Apache does not mean that we will necessarily develop a cloud solution, though this is certainly a topic of discussion and is of interest to some of our volunteers.
5. "I am curious if there is a free product like Adobe Reader/Writer in OpenOffice? Thanks for your help."
OpenOffice is not intended to be a replacement for a dedicated PDF reader/editor. But we do have some strong PDF export support. You can access this feature under the File/Export menu item. There are additional PDF export options in the dialog that give you additional control over the output.
6. "Is the project looking at the needs of multi-user installations such as government and business organisations?"
Yes. We're investigating improvements in the following areas:
- Support for incremental updates, so a maintenance update can be applied without requiring a full re-install.
- Support for admin/script directed "silent" installs, with ability to control default settings, which extensions are installed, etc.
- Reducing the storage requirement of the per-user profile information.
7. "Open Office doesn't handle tables in Word well - for example re-sizing of columns, keeping table rows together, inserting page breaks within tables. Could OpenOffice development include a goal of fully matching MS Office functionality for tables?"
Improved interoperability with Microsoft Office is a key requirement for many users. We're in the process of merging in a significant number of improvements in this area (over 100) from the IBM Lotus Symphony contribution. These improvements (you can see some examples of them) will start showing up in Apache OpenOffice 4.0.
8. "When is OpenOffice going to get a visual refresh and be built with each OSes native widgets?"
A visual refresh is part of our continuous effort to improve the user experience (UX). It is challenging to innovate with a modern UI vs. gradual transformation of the huge amount of existing users, leverage OSes native widgets vs. keep consistent look & feel across multiple platforms. Look at the mixed feedback Microsoft gets when it makes major changes to its UI for an example of some of the issues we are dealing with.
Our UX designers and developers are working together on a visual refresh. You will notice some improvements in Apache OpenOffice 4.0. You can see some of the design sketches on our wiki. The more feedback we get from you, the better design we can make.
9a. "Is there a version of OpenOffice for iPad3?"
9b. "Can I load OpenOffice onto my Google Android tablet?"
(Combining two related questions)
Apache OpenOffice is available from the project for Windows, MacOS and Linux. Community members additionally have ported OpenOffice to BSD, Solaris and OS/2, and make these ports available on their own websites. There is also a new 3rd party port to Android. There is also a 3rd party service called rollApp, that allows remote access to an OpenOffice session from an iOS device.
10. "Why is the "User Profile" causing so much trouble in migration from older versions to 3.4.1?"
Apache OpenOffice 3.4.0 and 3.4.1 manage the user profile differently than previous versions. The user profile contains the user's customizations and installed extensions, and the new handling helps make the OpenOffice startup faster and reduces the amount of disk space it uses. The old user profile is not deleted when OpenOffice is upgraded. It is automatically converted so that users can keep their extensions and settings. In a minority of cases, especially with highly customized profiles (many extensions or customizations) the conversion doesn't succeed. Typical symptoms are: frequent application crashes, problems with dictionaries or thesaurus, OpenOffice starting and crashing after a few seconds. To solve this, just reset/rename your user profile as explained in the OpenOffice community forum. http://user.services.openoffice.org/en/forum/viewtopic.php?t=12426
These problems should go away with Apache OpenOffice 4.0, since with major version updates we start with a clean profile.
11. "Does Apache OpenOffice run on Windows 8?"
Yes. Although Microsoft Windows 8 was only in preview when we released Apache OpenOffice 3.4.1, subsequent testing and user feedback has been positive, and no
incompatibilities have emerged so far. Note: OpenOffice runs as a desktop application on the x86 or x64 platforms. We don't support Windows RT or the Metro UI.
12. Is a portable version of OpenOffice available?
Yes. It's called "X-ApacheOpenOffice", see http://www.openoffice.org/porting/