Apache OpenOffice

Wednesday April 17, 2013

Visualizing the AOO Dev List

Dev list graph

 What am I looking at?

The above image illustrates the social network of posts and responses to the Apache OpenOffice project's main development mailing list, from when it started in May 2011 until the end of March 2013 when this data was collected.  (Click on the image to view a larger version) 

Each circle represents a person posting to the mailing list.  The arcs represent responses to posts, i.e., they are drawn from the person posting to the person to whose post they are replying.  The weight of each line is proportionate to the number of times person X responded to person Y.  So darker lines portray more frequent communication pathways.  The size of each circle is proportionate to the poster's eigenvector centrality, a theoretical measure of influence within the graph.  The colors represent modularity classes, based a calculation that determines the most tightly-connected portions of the overall graph.  These can represent real-world structures within the community. 

Overall the graph has 1077 nodes (persons) and 8181 arcs (response emails).  On average each person responded to 7.6 other persons, and made 27.1 total responses.

Now some interpretation.  This is not the the "hub and spokes" or tree pattern of a command/control or hierarchical organization, but a complex organism, with project participants contributing at various levels of engagement.  The larger circles in the center, connected with many and darker lines, are the core project participants (at least on the development list).  The very small circles at the periphery of the graph are those who posted a single question, received a response were never heard of again.  They typically received one or two response posts, but did not really engage further. And in the middle we see additional rich structure of conversation patterns.  The modularity classes, represented by colors here, appear to segment the list participants into what I'll call "programmers", "marketing" and "support", though these labels are imperfect.

It is difficult to ascribe too much meaning to these email response patterns.  Some mailing lists have been the topic of research before.  In Q&A forums, where nearly 100% of the initial posts are questions, and responses are all answers, it is interesting to look at the response patterns as an indication of expertise.  See Adamic, et al., for a good example.  We might apply a similar analysis to the support forums.  But with the Dev list, an initial post might be a question, but it is often a report, or a proposal or just information sharing.  And responses are not always expert answers or answers at all.  Some responses are expressing approval or disapproval, or asking questions of their own.  All these factors make this quite complex.

How I made the graph

  1. I started with the list archives, downloaded the mbox files extracted the response graph to a text file, with a custom python script, using the python "mailbox" package.
  2. Then I manually cleaned up the data, coalescing multiple mail accounts used by some members.
  3. I used the open source graph visualization package "Gephi" to process the data and draw the graph (layout via the Fruchterman-Reingold algorithm) and export it to a PNG file.

Wednesday April 10, 2013

Welcome to GSoC Students!

Coeds with Hoes

Once again the Apache Software Foundation is a "mentoring organization" in Google Summer of Code, and the Apache OpenOffice project looks forward to this year's program. 

We invite students looking to get their hands dirty with real-world code to consider submitting an GSoC application related to OpenOffice. 

Why OpenOffice?

  • We're one of the most famous open source projects around.  Our latest release has had over 45 million downloads.  The work you do with OpenOffice could be seen by millions of users.
  • We're a fun, international and diverse group of volunteers.  Working with OpenOffice this summer will be fun.
  • The core code for OpenOffice is C++, but extensions can be written in Java, Python and Basic as well.  We probably speak your language.
  • OpenOffice software is central to the daily work of its users, with text documents, spreadsheets and presentations.  There are good opportunities to explore applications that connect OpenOffice to cutting-edge disciplines such as text analytics, natural language processing, social network analysis, the semantic web, etc.

We've posted some initial ideas, suggested by our mentors.  But don't feel limited to these ideas.  If you want to work on a variation of one of these ideas, or an entirely different idea, let us know.  If it is a good fit, and a mentor is able to work with you, then let us know.  If you're passionate about something we want to hear about it.

For more information, please take a look at the Apache-wide GSoC page where many of your questions may be already answered.

Finally, we highly encourage prospective applicants to engage early with the OpenOffice community on our development mailing list.

Monday April 08, 2013

One Year until the End of Life for Microsoft Office 2003

Josephine Smith digging a grave at the Drouin Cemetery, Victoria, [2]

The April 2014 deadline

Microsoft has announced that they will end support of Office 2003 and Windows XP on April 8th, 2014. What does this mean? As they describe, "After April 8, 2014, there will be no new security updates, non-security hotfixes, free or paid assisted support options or online technical content updates." This, according to Microsoft, exposes Office 2003 users to greater "Security & Compliance Risks".

Time to explore the alternatives

Some companies and users will write a big check to Microsoft for an upgraded license for Office. But others will see this as an opportunity to explore the alternatives, including open source products like Apache OpenOffice, the leading free productivity suite, with over 44 million downloads.  Now is a good time to start planning for a migration off of Microsoft Office 2003 and Windows XP. Many companies have already started.

Apache OpenOffice is available on Windows, MacOS and Linux.  It is open source software, which means there are no license or subscription fees required to use or redistribute OpenOffice.  

You can learn more about Apache OpenOffice at www.openoffice.org.   Many companies offer migration services for Apache OpenOffice, some of which are listed on our consultants page.

Thursday April 04, 2013

X-ApacheOpenOffice: A Portable Applications Version of Apache OpenOffice from winPenPack

We receive many questions from users looking for a portable version of Apache OpenOffice.  "Portable Applications" are software applications designed or adapted to run from portable storage, like a USB memory stick, without requiring an installation.  Such applications allow you to bring your applications, settings and documents with you.  One popular portable version of OpenOffice is "X-ApacheOpenOffice", from the winPenPack open source project.   We interviewed the founder of winPenPack, Danilo Leggieri, and his team to learn more.

What is winPenPack?  How did the project start?   How many people work on the project?

Well, it is really difficult to describe in a few words what this project is for us, because since from the first moment has begun to be part of our own life...  Briefly we can say that winPenPack is an Italian open source project that deals with portable software, both natively portable and portabilized by means of X-Launcher, our portable program launcher. These apps can be grouped into suites or can be used also as standalone portable programs, adapting with end users preferences.

winPenPack philosophy is well summarized by our (very restrictive) definition of "portable software": a portable program can't simply be a "no-install" program, but must also be able to save its settings into his own folder (or a user-definable folder), does not write settings or leave other data in user folders (i.e. into c:\Users\TheUserName\AppData\Roaming\ or c:\Documents and Settings\TheUserName) or into the registry, must be able to run from a USB pen drive and can perform path normalizations moving around different PCs (where the pen drive could be installed with different drive letters). Obviously, all of these programs can be executed also from hard drives, greatly simplifying recovery operations of all programs (and their preferred configurations) when reinstalling the operating system.

Our project started in November 2005 by a brilliant intuition of Danilo Leggieri (AKA Danix, the founder of the project). Danilo and a couple of "web friends" expanded the project and the community grew very quickly. Since that date, we have issued about 20 new releases and hundreds of Open Source portable applications. Actually, the project is well known in Italy and is growing also abroad. winPenPack is hosted on SourceForge and all the collections are regularly distributed also in bundles with some IT magazines. The community of users has grown over the years and has actively contributed to the growth of the whole project. The site currently hosts various projects created and suggested also by forum members, and is also used for bug reporting and users suggestions.

Currently, the project involves 6 officially active people and a lot of contributors (translators, testers, and so on). All of them are spending their time completely for free, working on the project out of pure passion. Each member of the staff has a different job in "normal life", not necessarily connected to the world of computer and information technology.

How do you make a winPenPack application?  What kinds of things do you need to do to make a desktop application portable?

The core of all our portabilizations is X-Launcher, the winPenPack program launcher. A program portabilized by X-Launcher is called an "X-Program". The folder structure of any X-Program always contains a \Bin folder (the program folder) and a \User folder (the settings folder), plus other optional folders, such as \Documents or \Downloads (depending on the nature of the portabilized program). At the root of this structure there is X-ProgramName.exe (the launcher of "ProgramName" program) and X-ProgramName.ini (the text file that contains all the settings and instructions for X-ProgramName.exe to make portable the portabilized program). Due to its nature, the .ini file can be easily edited with any text editor, simplifying the creation, the testing and the fine-tuning of the portabilization. The various sections of the X-ProgramName.ini file allow us to define the X-Launcher behavior towards the registry or the user folders or to perform other actions. We can easily copy or move registry keys or files or folders back and forth beween the USB pen drive and the PC hard drive,  leaving the host PC in the exactly same state it was before we executed it on our X-Program.  So X-Launcher allows us to recreate the environment in which a program works correctly (registry keys, user folders, etc.), but, after the program execution completes, it leaves the PC "clean", because when closing the program all these keys (or files) are moved back into the \User folder of the portabilized program folders structure, ready to recreate the environment at the next execution.

The process of portabilization of a program passes through various steps. First of all, someone (a team member or a forum user) signals an interesting program. We test its portability through RegShot, which helps us understand if the program uses the registry or the user folders for saving its settings or for other purposes.  If, after our tests, the program turns out to be natively 100% portable, it is added to the "Portable Software" section of our Download area. If the program is not fully portable, we check whether it is possible to make it portable through X-Launcher. This phase reuses all the information gathered during portability tests to determine which features of X-Launcher should be enabled to portabilize the program.  This is the most important step, that requires all the portabilization skills of our developers, and often makes the difference between being able to consider a program portabilizable or not. The last step is the packaging of the X-Program and its distribution through our "X-Software" Download area. Sometimes even 100% portable programs can receive some benefit from X-Launcher (for example, backups of configurations, paths normalization, use in conjunction with external libraries like Java), so we create also X-Programs of that kind.

Did you run into any special challenges when making the portable version of Apache OpenOffice (X-ApacheOpenOffice)?  Are there any changes we could make in the OpenOffice to make portable versions more powerful?

For developing X-ApacheOpenOffice Portable we were able to put into practice our previous knowledge acquired in past years with early versions of OpenOffice. This background helped us a lot for speeding up the development of X-AOO Portable.

The more relevant features added to Apache OpenOffice for building the completely portable X-ApacheOpenOffice Portable are:

  1. Path normalization: all paths of recent files that are saved into X-AOO Portable folder structure have been normalized
  2. "System" folders: the \Documents and \Backups X-ApacheOpenOffice Portable subfolders have been set as "system" folders, also moving the main folder
  3. Disabled quickstart.exe: quickstart.exe has been disabled to prevent the soffice.exe process from remaining active in the traybar after closing the program, or when the user tries to disconnect the USB pen drive from the PC
  4. JavaGet integration: the integration of JavaGet functions into the launcher allows X-AOO to work with or without a Java installation present on the host PC

We haven't had particular challenges to develop our portable version (just some extra-time due to the download of all language versions to be merged into one single X-Program). However, the fact that Apache OpenOffice recognizes automatically the OS language has simplified our work, allowing us to have a single launcher. For the future we would like very much also a monolithic multi-language setup of Apache OpenOffice to be used as a base for our portable X-ApacheOpenOffice Portable.

When I think of portable applications I think mainly of putting apps on USB keys.  But are you seeing any other interesting uses, like people running their apps from the cloud, DropBox, etc.?

Portable programs aren't simply "apps to be run from USB keys". Portable programs allow the users to carry in their pockets all their preferred applications, with all their preferred settings, to be run anywhere they find a Windows PC with a free USB port. That's it. We could even say that the portable programs were the forerunners of the cloud: your programs, everywhere...  At this moment, we see cloud apps more oriented to mobile devices (that are "portable" by definition). Windows programs need an operating system in which to be executed. If we would be able to run Windows portable programs from the cloud, the only thing that we would do without would be exactly our USB pen drive... 

Where can readers go to learn more about winPenPack or to help with the project?

Of course on our site! We have a "Documentation" section that with considerable efforts we have translated almost entirely in English, in order to help as many users as possible. We have also an English forum where we answer all users' questions and discuss any other aspect of programs portabilization. You all are welcome to visit us and donate to the project to allow us to continue to develop even more exciting portabilizations!

Friday March 22, 2013

Document Freedom Day


What is Document Freedom Day?

Document Freedom Day, the last Wednesday in March, is a global celebration of open standards, especially ones that are used in your documents.  At Apache OpenOffice, we're strong supporters of open standards and we're pleased to join in this year's celebration.  But we're much more than passive supporters of open standards.  We're also active implementers of open standards, and several of our project volunteers serve on standards committees as well.

What is an Open Standard? 

There are many definitions of "open standard", some of which are summarized on this Wikipedia page.  But the central idea is that an open standard is a standard that 1) is developed in an open, consensus based standardization process, and 2) does not require royalty payments in order to implement. 

Why are Open Standards important?

  • The use of open standards makes your software less expensive, since the authors of the code do not need to pay royalties. Free software, including open source software, would be nearly impossible to create without open standards.
  • Open standards promote widespread adoption and interoperability.
  • Open standards encourage a market where vendors compete based on features and quality, rather than rely on vendor lock-in.
  • Open standards put you in control of your documents and your data.

Open standards are what the World Wide Web was built upon, and this openness was essential to its success.  Tim Berners-Lee explained why was so in a 2007 interview:

It was the standardization around HTML that allowed the web to take off. It was not only the fact that it is standard, but the fact that it’s open and the fact that it is royalty-free.

So what we saw on top of the web was a huge diversity and different business which are built on top of the web given that it is an open platform.

If HTML had not been free, if it had been proprietary technology, then there would have been the business of actually selling HTML and the competing JTML, LTML, MTML products. Because we wouldn’t have had the open platform, we would have had competition for these various different browser platforms, but we wouldn’t have had the web. We wouldn’t have had everything growing on top of it.

So I think it very important that as we move on to new spaces … we must keep the same openness we that had before. We must keep an open internet platform, keep the standards for the presentation languages common and royalty free. So that means, yes, we need standards, because the money, the excitement is not competing over the technology at that level. The excitement is in the businesses and the applications that you built on top of the web platform.

How is Apache OpenOffice involved in Open Standards?

We're involved in two ways.   First, we're an implementer of several key open standards, including:

  • Open Document Format (ODF), the ISO-approved standard for office documents.  ODF is the default document format in OpenOffice.
  • Scalable Vector Graphics (SVG), the W3C standard for vector graphics.
  • Portable Document Format (PDF), the ISO-approved standard for fixed-layout document representations.
  • Mathematical Markup Language (MathML), the W3C standard for representing mathematical equations.

Secondly, many of our volunteers are actively involved in the creation and maintenance of open standards, especially at OASIS, where the technical committee for ODF is:

  • Oliver Rainer-Wittman is a long-time member of the OASIS ODF Technical Committee (TC), and also participant in ODF Plugfests.
  • Dennis Hamilton is a member of the ODF TC and Secretary of the ODF Interoperability and Conformance (OIC) TC, and is active as well in ISO/IEC JTC1 SC34/WG6 where the ISO version of ODF is maintained.
  • Rob Weir is Chair of the OASIS ODF TC and a frequent participant in ODF Plugfests.
  • Other OpenOffice Committers are members of the OASIS ODF TC, including Regina Henschel, Louis Suárez-Potts, Don Harbison and Michael Stahl.
  • Others at Apache are involved in ODF standardization, included Svante Schubert, Committer in the Apache ODF Toolkit Project, who is Chair of the Advanced Document Collaboration Subcommittee, developing enhanced change tracking support for the next version of ODF.

What can You do to help promote open standards?

  1. Use open standards wherever your application supports them.
  2. If your favorite application doesn't support open standards like ODF, write to your vendor and request that they add support.
  3. When you publish or share a document, do so in open formats like ODF or PDF.

Wednesday March 06, 2013

Call For Designers: Apache OpenOffice 4.0 Brand Refresh Project

Apache OpenOffice is looking for a refreshed logo and branding for its upcoming 4.0 release.


This is a tremendous opportunity for designers to get involved in one of the most popular free and open source projects, and to get their work displayed to dozens of million of users: Apache OpenOffice just celebrated 40 million downloads in less than ten months.

Brand Refresh Project Scope


  • An AOO Logo


  • Can be altered for use in splash screens, about screens, publications, website, elements in application icons, etc.
  • Brand proposals that show more than just a logo, considering placement in the areas of focus such as splash screen and websites.

Primary Requirements

  • Logo submissions must include the source.
  • Logos can be as large as the designer wishes, but must be able to scale down and not loose detail. eg.. for website, splash screen, etc.
  • Although text in the logo is optional, any font used must be a free and open font. eg. SIL Open Source Fonts.  Any font used in the logo must be disclosed upon submission.
  • Incorporation of gulls literally or symbolically, but not necessarily the existing shape used in current branding.

If you are interested, please read the full Brand Refresh Project page (including the "child pages" at the bottom) to get more background, see what other volunteers are proposing and learn how you can contribute!

Monday March 04, 2013

Apache OpenOffice: 40 Million Downloads

We've reached another big milestone — 40 million downloads of Apache OpenOffice 3.4.x since the release of 3.4.0 in May 2012.  You can view a detailed chart on our Stats page.

40 million.  A number like this is hard to imagine.  With news every day of government budgets and deficits in the trillions, what does 40 million mean?

One way is to look at the value, as free open source software, this brings to the public.  We looked at it from this angle in a previous blog post, $21 million per Day.

Another way is to think in physical terms.  What if the 40 million copies of Apache OpenOffice were distributed on CD ROM rather than distributed electronically (with the generous support of Geeknet and their SourceForge distribution network)?

Consider:  A CD ROM has a diameter of 120mm.  So 40 million CDs, if placed side-by-side, would be 4,800 km (2,983 miles).  That is a distance we can think about and visualize better than the abstract "40 million downloads".

Imagine a road trip from Los Angeles to New York City. It is only 2,789 miles, less than 40 million OpenOffice CDs would stretch:

L.A. to NYC

Or, in Europe, imagine a trip from Lisbon to Moscow.  That is 4,575 km, less than our Apache OpenOffice downloads would stretch:

Lisbon to Moscow

Or try Istanbul to Islamabad.  That is 4,963 km, just a little longer than the CDs would reach:

Istanbul to Iislamabad.jpg

Consider the CD ROM once more.  Its thickness is 1.2mm.  So if we stacked the 40 million CDs (very carefully!) they would be 48 km high, longer than a marathon, 100x taller than the Empire State Building, 5x taller than Mt. Everest, and higher even than Felix Baumgartner's record-breaking skydiving jump.

Of course these are all fun statistics, but our users are much more than just numbers.  They are students, teachers, doctors, lawyers, ministers, public servants, and business people from all industries.  Many of them choose to engage further with the project, by following us on Facebook, Twitter, or Google+, by posting questions on our support forums, or by volunteering to help the project in areas such as Documentation, QA, Marketing or Translation.  We're happy to welcome new volunteers at any time and look forward to serving many millions of users more in the coming months and years.

Tuesday February 26, 2013

Call for Documentation Volunteers

Mt. Holyoke, Massachusetts - Paper. American Writing Paper Co. Super-calender - putting on roll, starting operation, 1936

As the Apache OpenOffice project gets closer to our big 4.0 release we're ramping up our documentation team.  The goal is to have new User Guides ready for the OpenOffice 4.0 launch.  If you know something about technical writing, or OpenOffice, or ideally both, we'd love your help. 

Of all the opportunities you have to volunteer your time for worthy causes, why should you consider volunteering with the Apache OpenOffice documentation team?  A few thoughts on that:

  • We're a fun, international group of volunteers, with a range of skills and experience, dedicated to free software and spreading the word about OpenOffice.
  • Helping with documentation is a good way to "give back" to the open source community, something that can be done without requiring special technical skills or large time commitments.
  • Contributions are needed from volunteers with a range of experience levels and interests. From authoring, to editing, technical verification, proof-reading, graphic design and tooling, we need volunteers in many disciplines.
  • This is a good way to learn more about technical writing and gain practical experience.
  • OpenOffice is among the most recognized open source brands, up there with Linux, Android and Firefox. Your contributions to our efforts will potentially be seen by millions of users.

 If you want to learn more, please see our Introduction to Documentation page or introduce yourself on our documentation mailing list.

Wednesday February 20, 2013

International Mother Language Day 2013

(This post is also translated into the mother languages of some of our volunteers, including Tamil by V.Kadal Amutham, Korean by Jeongkyu Kim, Italian by Fabrizio Marchesano, Asturian by Xuacu Saturio, French by Cyril Beaussier, Spanish by Ricardo Gabriel Berlasso and German by Guenter Marxen.

The Apache OpenOffice project is proud to help commemorate International Mother Language Day on February 21.  Read more about why this day is important, how OpenOffice supports linguistic diversity, and how you can help.

Why February 21 was chosen?

February 21st was declared as International Mother Language Day (IMLD) by UNESCO.   IMLD originated as the international recognition of Language Movement Day, which has been commemorated in Bangladesh (formerly East Pakistan) since 1952, when a number of Dhaka university students were killed by the Pakistani police and army in Dhaka during the Bengali Language Movement. This is the only event where people gave their lives to preserve the independence of using their mother language. 

To remember them there is a monument named Language Martyr's Monument (Shahid Minar) in Dhaka University, Bangladesh. Every year more than a million people give flowers there. This is a big event in Bangladesh. Many foreigners visit Bangladesh just to experience the way the Bangladeshi people give respect to those brave hearts. Every town of Bangladesh has a Language Martyr's Monument, where local people give flowers.  A Language Martyr's Monument is also built in Ikebukoro park of Tokyo, Japan. There are also Language Martyr's Monument in USA, UK, Italy and many other countries. Please think about your Mother Language not only on February 21 but also on other days.

OpenOffice and Linguistic Diversity

Today, the risk to Mother Languages is not just from government oppression.   As we increasingly communicate and work electronically, the support of Mother Languages in our software is critical.  If a language is not well-supported in software, that language and its native speakers are at a disadvantage.  This is why at Apache OpenOffice, our Public Service Mission puts a strong emphasis on supporting linguistic diversity:

There are over 6,000 languages in the world, but unless the language is associated with a G20 economic superpower, commercial vendors tend to ignore it. The OpenOffice community has a long standing tradition of supporting a large number of languages, including languages used by smaller populations, minority languages, endangered languages, etc. For example, South Africa has 11 official languages. OpenOffice has been translated to all of them. By supporting languages that would not otherwise be supported we help reduce "digital exclusion" and promote development, local education and administration.

As a volunteer-run,  non-profit organization, Apache OpenOffice depends on volunteers to help us translate OpenOffice.  With your help we can support hundreds of languages.  A list of languages we are currently trying to support is here.  Contact us if you can help.

text by Khan Md. Anwarus Salam and Rob Weir, logo design by Robin Fowler.

Apache OpenOffice 프로젝트는 자랑스러운 마음으로 2월 21일 세계 모국어의 날을 기리고자 합니다. 여기에서는 이 날이 중요한 이유와 함께 OpenOffice가 어떻게 언어적 다양성을 지원하고 있으며 여러분이 도울 수 있는 방법은 무엇인지 말씀드리겠습니다.

2월 21일을 기리는 이유

2월 21일은 UNESCO가 세계 모국어의 날(International Mother Language Day)로 지정한 날입니다. 세계 모국어의 날은 원래 방글라데시 - 예전의 동파키스탄 - 에서 1952년부터 기념하기 시작한 언어 운동의 날(Language Movement Day)에서 유래했는데, 이 날은 벵골 언어 운동 기간 동안에 Dhaka 대학의 학생들이 파키스탄 경찰과 군대에 의해 사망한 날입니다. 이는 모국어 사용의 독립을 지키기 위해 목숨을 바친 유일한 사건입니다.

그들을 기억하기 위해 방글라데시 Dhaka 대학에는 모국어 순교자 기념비(Shahid Minar)가 있습니다. 매년 백만명 이상의 사람들이 여기에 꽃을 바칩니다. 이는 방글라데시에서 큰 행사입니다. 방글라데시를 방문하는 많은 외국인들은 방글라데시 사람들이 그들의 용감한 영혼에 경의를 표하는 것을 경험합니다. 방글라데시의 많은 도시에는 모국어 순교자의 기념비가 있어서 지역 사람들도 꽃을 바칩니다. 모국어 순교자 기념비는 일본 도쿄에 있는 이케부코로 공원에도 건립되었습니다. 미국, 영국, 이태리를 비롯한 많은 나라에도 모국어 순교자 기념비가 있습니다. 2월 21일 뿐만 아니라 늘 여러분의 모국어에 대해 생각해 보시길 바랍니다.

OpenOffice와 언어적 다양성

오늘날, 모국어에 대한 위기는 정부의 탄압에서만 비롯되는 것이 아닙니다. 우리가 전자적으로 일하고 의사소통함에 따라 우리가 사용하는 소프트웨어에서 모국어를 지원하는 것이 매우 중요합니다. 소프트웨어가 어떤 언어를 지원하지 않으면 해당 언어와 이를 말하는 사람이 불리한 처지에 놓입니다. 이것이 Apache OpenOffice 프로젝트의 공적 목표가 언어적 다양성의 지원을 강조하는 이유입니다:

세상에는 6,000개 이상의 언어가 있지만 G20 경제 대국과 무관하면 상업적인 벤더들이 무시하기 쉽습니다. OpenOffice 커뮤니티는 소수가 사용하는 언어나 사라져 가는 언어를 비롯한 다양한 언어를 지원하는 오랜 전통을 가지고 있습니다. 예를 들어, 남아프리카공화국은 11개의 공식언어를 가지고 있는데 오픈오피스는 이 언어로 모두 번역되었습니다.

자발적인 참여로 운영되는 비영리 기구인 Apache OpenOffice는 자원 봉사자의 도움으로 OpenOffice를 번역하고 있습니다. 여러분의 도움을 통해 우리는 수 백개의 언어를 지원할 수도 있습니다. 현재 우리가 지원하고 있는 언어의 목록은 여기에서 볼 수 있습니다. 여러분의 많은 참여를 바랍니다.

Il progetto Apache OpenOffice è orgoglioso di contribuire alla commemorazione della Giornata Internazionale della Lingua Madre del 21 Febbraio. Continuate la lettura per scoprire perchè questo giorno è importante, come OpenOffice supporta la diversità linguistica e come voi stessi potete contribuire.

Perchè è stato scelto il 21 Febbraio?

Il 21 Febbraio è stata dichiarata Giornata Internazionale della Lingua Madre (International Mother Language Day, IMLD) dall'UNESCO. Le origini di questo riconoscimento internazionale risalgono alla Giornata del Movimento per la Lingua (Language Movement Day) commemorato in Bangladesh (in precedenza denominato Pakistan Orientale) sin dal 1952, quando diversi studenti dell'univeristà di Dacca vennero uccisi dalle forze di polizia ed esercito del Pakistan durante gli eventi dedicati al Movimento per la Lingua Bengalese (Bengali Language Movement). Si tratta dell'unico avvenimento storico in cui furono sacrificate delle vite per difendere la libertà di utilizzare la propria lingua madre.

In memoria delle vittime è stato eretto il Monumento ai Martiri della Lingua (Language Martyr's Monument, orig. Shaheed Minar) all'Università di Dacca, Bangladesh. Ogni anno più di un milione di persone vi si recano per deporre fiori. È un evento importante in Bangladesh. Molti visitatori stranieri si recano in Bangladesh per vivere l'esperienza dell'offerta del proprio rispetto per queste persone coraggiose da parte della popolazione locale. In ogni città del Bangladesh esiste un Monumento ai Martiri della Lingua, dove gli abitanti si recano per deporre fiori. Un altro Monumento ai Martiri della Lingua è stato eretto al parco Ikebukoro di Tokyo, Giappone. Altri Monumenti ai Martiri della Lingua si trovano in USA, Regno Unito, Italia e molti altri paesi. Pensate alla vostra Lingua Madre tutti i giorni, non solo il 21 di Febbraio.

OpenOffice e la Diversità Linguistica

Oggigiorno, i rischi per diverse Lingue Madri non derivano solo dall'oppressione di governo. A causa della sempre maggiore diffusione delle comunicazioni e del lavoro per via elettronica, il supporto alle Lingue Madri nel nostro software è essenziale. Se una lingua non è adeguatamente supportata nel software, quella lingua e coloro che la parlano subiranno uno svantaggio. Questa è la ragione per cui la Missione di Servizio Pubblico di Apache OpenOffice attribuisce grande importanza al supporto della diversità linguistica:

Esistono più di 6000 lingue nel mondo, ma una lingua non associata a una superpotenza economica del G20 è tendenzialmente ignorata dai rivenditori di software commerciale. La comunità di OpenOffice ha una lunga tradizione relativa al supporto di un gran numero di lingue, incluse quelle utilizzate da minoranze etniche o lingue in via di estinzione. Ad esempio, il Sud Africa conta 11 lingue ufficiali. OpenOffice è stato tradotto in ognuna di esse. Collaborando al sostegno di lingue che non ricevebbero altrimenti altro supporto, contribuiamo a ridurre "l'esclusione digitale" e a promuovere l'educazione e amministrazione locale.

In quanto organizzazione no-profit, basata sull'operato di volontari, Apache OpenOffice si avvale esclusivamente del contributo di questi ultimi per le traduzioni. Con il vostro aiuto possiamo garantire il supporto a centinaia di lingue. Una lista di lingue che stiamo attualmente cercando di supportare si trova qui. Contattateci se potete offrire il vostro aiuto.

El proyeutu Apache OpenOffice tien el gustu d'ayudar na conmemoración del Día Internacional de la Llingua Materna el 21 de febreru. Llei más tocante a la importancia d'esti día, cómo OpenOffice da sofitu a la diversidá lingüística, y cómo pues ayudar.

Por qué s'escoyó'l 21 de febreru?

La UNESCO declaró'l 21 de febreru Día Internacional de la Llingua Materna (DILM). L'orixe del DILM ye'l reconocimientu internacional del Día del Movimientu pola Llingua, que vien conmemorandose'n Bangladex (Antiguu Paquistán Oriental) dende 1952, cuando la policía y l'exércitu paquistaninos mataron una cantidá d'universitarios en Dhaka demientres el Movimientu pola Llingua Bengalina. Esta ye la única ocasión en qu'un grupu de persones dieron les sos vides pa conservar el drechu d'usar la so llingua materna.

Na so alcordanza hai un monumentu nomáu Monumentu de los Mártires de la Llingua (Shahid Minar) na Universidá de Dhaka, Bangladex. Cada añu más d'un millón de persones ufren flores ellí, no que ye un acontecimientu importante en Bangladex. Munchos estranxeros visiten Bangladex namái pa vivir el mou en que'l pueblu bangladexín fai alcordanza d'aquellos valientes. Toles ciudaes de Bangladex tienen un Monumentu de los Mártires de la Llingua, onde los llocales ufren flores. Tamién hai construyíu un Monumentu de los Mártires de la Llingua nel parque Ikebukoro de Tokiu, Xapón. Asina mesmo, hai Monumentos de los Mártires de la Llingua nos EE.XX., Reinu Xuníu, Italia y otros paises más. Pidimoste que tengas presente la to llingua materna non namái el 21 de febreru sinón los demás díes.

OpenOffice y la diversidá lingüística

Anguaño, el peligru pa les llingües maternes nun vien namái de la opresión gubernamental. Na midida en que crecen les comunicaciones ya'l trabayu de mou electrónicu, el sofitu pa les llingües maternes nel nuesu software ye críticu. Si una llingua nun tien un bon sofitu pal software, esa llingua y los sos falantes nativos tan en desventaxa. Poro, en Apache OpenOffice, la nuesa Misión de Serviciu Públicu pon un gran énfasis nel sofitu de la diversidá llingüística:

Hai más de 6.000 llingües nel mundu, pero nun siendo que la llingua tea asociada con una superpotencia económica del G-20, los vendedores comerciales tienden a inorala. La comunidá d'OpenOffice tien una llarga tradición de dar sofitu a un gran númberu de llingües, incluyendo llingües qu'usen poblaciones más pequeñes, llingües minorizaes, llingües en peligru, etc. Por exemplu, Sudáfrica tien 11 llingües oficiales. OpenOffice ta traducíu a toes elles. Dando sofitu a les llingües que d'otra miente nun lu tendríen ayudamos a amenorgar la "esclusión dixital" y a promover el desendolcu, y la educación y alministración llocal.

Como organización xestionada por voluntarios, ensin ánimu de lucru, Apache OpenOffice depende de voluntarios p'ayudar a traducir OpenOffice. Cola to ayuda podemos dar sofitu a centenares de llingües. Hai una llista de les llingües a les qu'intentamos dar sofitu equí. Comunicate con nós si pues ayudar.

Le projet Apache OpenOffice est fier d'aider à commémorer la Journée internationale de la langue maternelle le 21 février prochain. Lisez la suite pour comprendre pourquoi ce jour est important, comment OpenOffice aide à la diversité linguistique et comment vous pouvez nous aider.

Pourquoi choisir le 21 février ?

Le 21 février a été déclaré Journée internationale de la langue maternelle (JILM) par l'UNESCO. Cette journée consacre la reconnaissance du Mouvement pour la Langue commémoré au Bangladesh par la Journée du Mouvement pour la Langue depuis 1952, quand la police et l'armée de l'État pakistanais, qui occupait alors ce pays, ouvrirent le feu sur la foule des locuteurs de Bengalî qui manifestaient pour leurs droits linguistiques à Dhaka.

En souvenir, le Monument des Martyrs (Shaheed Minar), près du Dhaka Medical College, au Bangladesh, a été érigé à la mémoire de ces morts. Chaque année, plus d'un million de personnes la fleurissent. C'est un grand événement au Bangladesh. Beaucoup d'étrangers visitent le Bangladesh et viennent découvrir la façon dont ses habitants donnent le respect à ces braves cœurs. Chaque ville du Bangladesh a son monument des Martyrs où la population locale donnent des fleurs. Un monument a également été construit au parc Ikebukoro de Tokyo, au Japon. Il en existe également d'autres aux Etats-Unis, au Royaume-Uni, en Italie et dans bien d'autres pays. Aussi, pensez à votre langue maternelle, non seulement ce 21 février mais aussi les autres jours.

OpenOffice et la diversité linguistique

Aujourd'hui, le risque pour les langues maternelles ne vient plus seulement de l'oppression de gouvernements. Comme nous communiquons et travaillons de plus en plus par voie électronique, le support des langues maternelles dans les logiciels est critique. Si une langue n'est pas bien pris en charge par un logiciel, celle-ci et ses locuteurs natifs sont dans une situation désavantageuse. C'est pourquoi, pour Apache OpenOffice, cette mission de service public met l'accent sur ce soutien à la diversité linguistique :

Il y a plus de 6.000 langues dans le monde, mais tant qu'une langue n'est pas associée à une superpuissance économique du G20, les éditeurs ont tendance à l'ignorer. La communauté OpenOffice a une longue tradition de support d'un grand nombre de langues, avec des langues utilisées par de petites populations, des langues minoritaires, des langues en voie de disparition, etc. Par exemple, l'Afrique du Sud compte 11 langues officielles. OpenOffice a été traduit pour chacune d'elles. En supportant ces langues qui autrement ne seraient pas pris en charge, nous aidons à réduire la «fracture numérique» et promouvons le développement, l'éducation et l'administration locales.

Uniquement géré par des bénévoles, organisation à but non lucratif, Apache OpenOffice dépend de ses volontaires pour l'aide à la traduction d'OpenOffice. Avec vous, nous pouvons supporter des centaines de langues. La liste des langues supportées actuellement est ici. Contactez-nous si vous pouvez nous aider.

El proyecto Apache OpenOffice se enorgullece en ayudar a conmemorar el día internacional de la lengua materna el 21 de febrero. A continuación encontrará más información sobre porqué este día es importante, cómo OpenOffice soporta la diversidad lingüística y cómo puede usted ayudar.

¿Por qué fue elegido el 21 de febrero?

El 21 de febrero fue declarado día internacional de la lengua materna (DILM) por la UNESCO. El DILM se origina como un día de reconocimiento internacional al movimiento del lenguaje materno, que ha sido conmemorado en Bangladesh (antiguamente, Pakistán del este) desde 1952 cuando varios estudiantes de la universidad Dhaka fueron muertos por la policía y el ejército pakistaní durante los eventos de conmemoración del movimiento por la lengua bengalí  Este es el único hecho histórico donde personas han dado su vida para defender la independencia de utilizar su lengua materna.

Para recordarlos se ha erigido un monumento llamado el monumento de los mártires de la lengua (Shahid Minar) en la universidad de Dhaka, en Bangladesh. Cada año más de un millón de personas dejan flores allí. Este es un gran evento en Bangladesh. Muchos extranjeros visitan Bangladesh solo para conocer cómo la gente demuestra su respeto por esos corazones valerosos. Cada pueblo de Bangladesh posee su monumento a los mártires de la lengua donde los pobladores locales depositan flores. Un monumento para los mártires de la lengua ha sido construido también en el parque Ikebukoro en Tokio, Japón. Otros monumentos a los mártires de la lengua existen en los Estados Unidos, el Reino Unido, Italia y muchos otros países. Por favor, piense en su lengua materna no solo el 21 de febrero, sino cada día.

OpenOffice y la diversidad lingüística

Hoy en día, los riesgos que se ciernen sobre las lenguas maternas no vienen solamente de gobiernos opresores. Como nos comunicamos y trabajamos cada vez más en forma electrónica, el soporte a las lenguas maternas en nuestro software resulta crítico. Si una lengua no es correctamente soportada en un software, el lenguaje y sus hablantes se encuentran en desventaja. Esta es la razón por la cual en Apache OpenOffice nuestra pública misión pone un fuerte énfasis en el soporte a la diversidad lingüística:

Existen más de 6000 lenguajes en el mundo, pero a menos que un lenguaje esté asociado a una de las superpotencias económicas del G20, productores y distribuidores de software comercial lo ignorarán. La comunidad de OpenOffice tiene una larga tradición de dar soporte a un gran número de lenguajes, incluyendo los utilizados por pequeñas poblaciones, lenguajes minoritarios, lenguajes en peligro, etc. Por ejemplo, Sudáfrica posee once lenguas oficiales. OpenOffice ha sido traducido a todas ellas. Dando soporte a lenguajes que de otra forma no serían soportados ayudamos a reducir la «exclusión digital» y a promover el desarrollo, la educación local y la administración.

Como una organización sin fines de lucro llevada adelante por voluntarios, Apache OpenOffice depende en estos últimos para ayudar a la traducción de OpenOffice. Con su ayuda podemos dar soporte a cientos de lenguas. Una lista de las lenguas soportadas actualmente se encuentra aquí. Contáctenos si puede ayudar.

Warum wurde der 21. Februar gewählt?

Der 21. Februar wurde von der UNESCO zum Internationalen Tag der Muttersprache (International Mother Language Day, IMLD) erklärt. Dieser Tag hat seinen Ursprung in der internationalen Anerkennung des Tages der Bewegung für die Sprache (Language Movement Day), an den seit 1952 in Bangladesh (dem früheren Ost-Pakistan) gedacht wird, als Studierende der Universität Dhaka während Demonstrationen für die Bengalische Sprache in Dhaka von der Polizei und der Armee getötet wurden. Dies war das einzige Mal, dass Menschen ihr Leben gaben, um die Freiheit zur Nutzung ihrer Muttersprache zu bewahren.

Zu ihrer Erinnerung wurde ein Denkmal mit Namen Shahid Minar ("Märtyrer für die Sprache") in der Universität von Dhaka errichtet. Jedes Jahr legen mehr als eine Million Menschen dort Blumen nieder. Dies ist ein großes Ereignis in Bangladesh, das viele Ausländer besuchen, um zu erleben, wie die Bangladeshi diesen tapferen Menschen ihren Respekt erweisen. Jede Stadt in Bangladesh besitzt ein Denkmal "Märtyrer für die Sprache", an dem die Bewohner Blumen niederlegen. Ein solches Denkmal ist auch im Ikebukoro-Park in Tokyo, Japan, errichtet, ebenso in den USA, in Großbritannien, in Italien und vielen anderen Ländern.

Denken Sie bitte über Ihre Muttersprache nicht nur am 21. Februar nach.

OpenOffice und Sprachenvielfalt

Heutzutage besteht die Gefahr für Muttersprachen nicht nur in der Unterdrückung durch Regierungen. Da wir zunehmend elektronisch kommunizieren und arbeiten, ist die Unterstützung von Muttersprachen in unserer Software ein kritischer Punkt. Falls eine Sprache in Programmen nicht gut unterstützt wird, sind diese Sprache und diese Muttersprachler stark benachteiligt. Daher wird bei Apache OpenOffice großer Wert darauf gelegt, sprachliche Vielfalt zu unterstützen:

Es gibt mehr als 6000 Sprachen weltweit, aber wenn eine Sprache nicht zu einem der wirtschaftlich starken G20-Länder gehört, tendieren kommerzielle Software-Hersteller dazu, sie zu ignorieren. Die OpenOffice-Gemeinschaft hat eine lang währende Tradition darin, eine große Anzahl von Sprachen zu unterstützen einschließlich Sprachen kleiner Völker, Minderheitensprachen, gefährdete Sprachen usw. Beispielsweise besitzt Süd-Afrika elf offizielle Sprachen. OpenOffice ist in alle diese Sprachen übersetzt worden. Indem wir Sprachen unterstützen, die ansonsten nicht unterstützt würden, helfen wir, den "digitalen Ausschluss" zu reduzieren und unterstützen Entwicklung, Ausbildung und Verwaltung dieser Länder.

Als eine von Freiwilligen getragene, nicht Gewinn orientierte Organisation hängt Apache OpenOffice von Helfern ab, die OpenOffice übersetzen. Mit Ihrer Hilfe können wir Hunderte von Sprachen unterstützen. Eine Liste der Sprachen, die wir zur Zeit unterstützen (wollen), finden Sie hier. Kontaktieren Sie uns, wenn Sie helfen können.

Tuesday February 19, 2013

OpenOffice downloaded once - used and installed as often you want

One major advantage of OpenOffice is that it is open source and that the license allows you to use and install it as often you want. Once you have downloaded OpenOffice you can share it with as many other people as you like or install it on as many computers as you need. No limits!


The project likes to count downloads because high download numbers are our motivation and if you want they are the indirect payment for all the volunteers. But we are also happy if you share your download with many other people or inside your company. If you do so please share your success stories of bigger deployments with us and we are happy to share your experience via our blog here. Keep in mind that sharing your experience, your success with other users in the community is also one kind of contribution to help the eco-system around OpenOffice growing.

Tuesday February 12, 2013

$21 Million per Day

Apache OpenOffice is a project within the Apache Software Foundation, a non-profit organization.  We don't charge for Apache OpenOffice; we make it available to all for free.   We don't pay developers; we rely on volunteers

People need office productivity software.  Among our users are students, teachers, doctors, lawyers, ministers, public servants, and business people from all industries.  Perhaps 20 years ago it was only businesses that needed this kind of software.  In 1992 the price of a spreadsheet application alone, not even a complete suite, was $595.  Only business could afford it at that price.   But today almost everyone with a computer needs a word processor, a spreadsheet and/or a presentation editor.    Office productivity applications are used in the home, at school and in the office.

Users have downloaded Apache OpenOffice from 236 countries and territories.   The above chart shows the download density of Apache OpenOffice 3.4 per country, normalized by the number of internet users in each country (based using ITU data).  If you click on the chart you can explore it interactively using IBM's Many Eyes service (Java required).

The reach of Apache OpenOffice is global and deep.  Our 3.4. release has been downloaded over 37 million times since May 2012.

Although Apache OpenOffice is free, it still has value, and the value we produce can be estimated.

The main alternative to OpenOffice is Microsoft Office, perhaps the lower-priced "Home and Student" edition.  The latest version (2013) is sold by Microsoft on their website for a variety of prices, varying by country.  In the U.S. it is $139.99.  In Germany it is quoted at 139,00 €, which is $188.04 USD.  In Australia it is $169.00 AUD which is $174.42 USD.  In Russia it is 3499.00 Rubles, which is $116.30 USD. 

Let's take, for ease of calculation, an intermediate value of $150.00 USD for Microsoft Office 2013 Home and Student.  A person who uses the free OpenOffice saves $150 over paying for Microsoft Office.

Apache OpenOffice 3.4.1 has averaged 138,928 downloads per day.  That is an average value to the public of $21 million per day.  Or $7.61 billion (7.61 thousand million) per year.  This is one estimate of the value we bring to the public.

To put that in perspective, here are annual sales figures for some familiar companies:

  • Campbell Soup Company: $7.88 Billion
  • Royal Caribbean Cruises: $7.66 Billion
  • Mastercard Inc.: $7.39 Billion
  • InfoSys: $7.23 Billion
  • Barnes & Noble: $7.16 Billion
  • OfficeMax Inc.: $7.06 Billion

We should be proud of what we've accomplished over the past decade.  This is not only a success for Apache OpenOffice in our Public Service Mission, but a demonstration of the reach and impact of open source software in general.

[Note: There are various ways to estimate value.  The commercial value of alternative goods, which we used above, is only one approach.  But it is the same approach used when estimating revenue lost to software piracy, when they assume that if users did not use software illegally they would pay for commercial licenses at the prevailing rate.   So there is some justification for using the same approach here.]

Monday February 04, 2013

Call for Development Volunteers

A carpenter at the TVA's new Douglas dam on the French Broad River, Tenn. This dam will be 161 feet high and 1,682 feet ong, with a 31,600-acre reservoir area extending 43 miles upstream. With a useful storage capacity of approximately 1,330,000 acre-feet

We're looking for a few good programmers, C++ hackers who aren't afraid to get their hands dirty. 

The Apache OpenOffice project is an international, volunteer-led open source project.  We develop Apache OpenOffice (formerly OpenOffice.org) the award-winning office productivity suite, and the code we write is used by tens of millions of users in over 200 countries.  Not many open source projects have this reach. Not many commercial products have this reach either.

We have coding tasks, large and small, easy and difficult.  Our developers, some with over a decade's experience with OpenOffice, can help you get started.  We'd also love to hear what ideas you might want to bring to OpenOffice. 

If this sounds interesting and you want to learn more, we have some resources to help you do that:

We hope to hear from you soon!

Friday February 01, 2013

Apache OpenOffice at FOSDEM 2013

Many OpenOffice community members will be attending FOSDEM, one of the most important Free Software and Open Source events in Europe, in Brussels next weekend.

Apache OpenOffice has a dedicated track (devroom) on Saturday 2 February, all day. The devroom schedule includes talks from experienced full-time developers and new volunteers, spanning all development-related topics around OpenOffice: deep technical previews and live demos of what is coming in version 4.0, tutorials on scripting and programming Apache OpenOffice, development-related use cases and tips and tricks for developers of extensions and writing aids.

Hackers who want to test their skills on OpenOffice shouldn't miss the Hacking Apache OpenOffice session, where experienced professional and volunteer OpenOffice developers will give advice on the best ways to get started. And the next step will be to tackle one of our easy or simple development tasks...

If you are interested in knowing more on Apache OpenOffice and the plans for version 4.0, just drop by the Apache OpenOffice stand. Volunteers will be there all day on both Saturday 2 February and Sunday 3 February. See you in Brussels!


Wednesday January 30, 2013

Apache OpenOffice now available in Danish, Norwegian, Swedish, Korean, Polish, Basque, Asturian and Scottish Gaelic

Sydney Grammar School's eight-oar-crew, Putney, Sydney, ca. 1932 / photographer Sam Hood

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, 리눅스 용으로 제공됩니다. 배포 노트 에는 이전 버전에서 업그레이드하기 위한 중요한 정보가 포함되어 있습니다.

이 번역본의 작업에 참여한 많은 번역자들 께 감사와 박수를 보냅니다. 여러분의 도움을 통하여 앞으로 나올 Apache OpenOffice 4.0 버전에서 더 많은 언어를 지원할 수 있습니다. 참여에 관심이 있으신 분은 참여 방법에 대한 정보를 담은 블로그 글 을 참고하시기 바랍니다.

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 数々の賞を受賞し 、 ダウンロード数は3,300万を超えました

新たな言語版は 私たちのウェブサイト からダウンロードしていただけます。

Apache OpenOffice 3.4.1 は、Windowsでも、MacOSでも、Linuxでもご利用いただけます。 リリースノート には、以前のバージョンからのアップグレードに必要な情報が書いてあります。

これら言語版のために翻訳作業をしてくれた多くの 翻訳者 に感謝と称賛の念を捧げたいと思います。多くの方々の助けがあれば、次のリリースApache OpenOffice 4.0 では、もっと多くの言語をサポートすることができます。ボランティアでこのような翻訳作業に参加したい方はぜひ ボランティア募集のブログ を読んでください。参加方法が書いてあります。みなさんの参加をお待ちしています。

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.

Monday January 21, 2013

Merging Lotus Symphony: Allegro moderato

April 8, 1926

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:

  1. 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.
  2. 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!



Hot Blogs (today's hits)

Tag Cloud