With Apache OpenOffice you get what you don't pay for
Apache OpenOffice is and always will be free to download from our website. The license allows you to use it yourself and share copies with friends and families or even total strangers. You may use it on home machines, in the office, with your small business, school, church, gardening club, etc. And if you know how to program software, you can take the source code for OpenOffice and modify it and share it with others as well. This is what open source means.
So it is sad when we receive emails from users, reporting that they have paid real money, as much as € 30 ($40 US), to websites in return for a link to our website. These websites promise the user immediate access to "open source office software with support for the lowest price", claim that "supplies are limited" and that prices are "50% off, if you order within the next 2 minutes". But after entering your credit card, or authorizing payment via SMS, you are merely redirected to the www.openoffice.org website, where you can download the same Apache OpenOffice software that everyone else downloads for free!
Of course, the fact that you are reading this blog is evidence that you are familiar with OpenOffice and know that it is free. The people who will be tricked into paying are those who do not read our blog, those who are not already familiar with OpenOffice.
But with your help we can reach those in need of a free office suite, and make them aware of Apache OpenOffice and let them know that they can download it for free. The more people who know about OpenOffice, the fewer people who will be fooled. To help, go to our download page and the "Help Spread the Word" section. Use any (or all) of those links to share the word about OpenOffice to your friends and family. Let's try to make as many people as possible aware of OpenOffice!
When will OpenOffice version X be released?
I'm always impressed by the enthusiasm of OpenOffice users to try out the next great release. A frequent question is, "When will it be released?" I see this question on Facebook and Twitter, the Forums and mailing lists. "When will version <insert next version> of OpenOffice be ready?" I'd like to answer the question fully here, so we can refer users to this answer in the future.
It is tempting to give the response, "It will be released when it is ready". But that sounds a bit snarky, although it is accurate. But the truth is software engineering schedule estimation is notoriously difficult and predicting a specific date is a sure way of looking foolish later on.
There is a well-known diagram in the software industry of a triangle, with the sides labeled: "good", "cheap", "fast" and with the title, "Pick any Two". This expresses the ever-present trade-off between quality, cost and schedule.
In commercial software development arbitrary dates can (sometimes) be met, by dropping quality (or features) or by adding resources to tasks (increasing costs). To some extent open source projects can also try to hit arbitrary dates by dropping quality. But unlike commercial endeavors open source projects don't have the same ability to add resources to recover a schedule slip. On the Apache OpenOffice project we are mainly volunteers, dedicating free time to the project, and that time varies according to school and holiday schedules and other personal needs. So we cannot stick to a schedule in the same way that a commercial software publisher can.
OpenOffice is a mature product and users expect it to just work. They are not looking for surprises. Users want to spend time doing their task, their
work, their business. OpenOffice is a tool, a means to an end, and
having a stable, familiar tool that gets the job done is golden. There
is little pleasure in getting a new hammer and screwdriver every month, with
new bugs, except for the small minority of technologists who relish the challenge and risk of frequent updates. The rest of us have real work to do and don't want to worry about whether the feature that worked last week still works today.
So generally, we've been aiming for two high-quality release of Apache OpenOffice per year, with a cycle that looks approximately like this:
- Brainstorm and discuss possible features. Even before version N is released we're discussing what will be included in version N+1. This includes specific new features, enhancements, new languages, bug fixes, etc. Much of this is tracked in our Bugzilla issue tracker (for bugs and enhancements) and on our mailing lists and wikis (for major features). The contents of the release are determined by the volunteers who do the work, based on their interests and motivations. These are discussed, documented on the wiki and become the goal for the next release.
- Development of the new features occurs, the coding often occurring in "branches" which are segregated areas in our Subversion version control system which help the developers to not step on each other's toes when stabilizing their code.
- As features are completed they are "merged into the trunk". We regularly build install sets from the trunk, so project participants can try the new features as soon as they are ready and give feedback.
- Once all the feature work is done for a release, we translate and test.
- We iterate on testing and fixing bugs until we've eliminated all "release blocking" bugs and have something of sufficient quality to call a Release Candidate. We then vote on the Release Candidate, and if approved it becomes the new release.
We welcome help from new volunteers in all parts of the Apache OpenOffice project. If you want to learn more please have a look at our Get Involved page.
The Sidebar: New And Improved
Usually the phrase "new and improved" does not make much sense because something either is new or did already exist and was improved upon. For the sidebar the situation is a little different. The core implementation is new but the content, the panels, did already exist. The concept, but not the name, of a sidebar has existed for many years both in Apache OpenOffice (and OpenOffice.org before that) and in IBM Lotus Symphony. In OpenOffice.org it was named "task pane" and was used primarily in Impress to give access to backgrounds, layouts, and shape and slide animations. Symphony renamed this to "property panel", extended it to all applications and covered even more frequently used tasks.
So, what did you improve?
The sidebar panels come from three different sources and have been improved in the migration process:
- The property panels that let you for example change the size of text or the color of shapes have all been migrated from Symphony. In the process we have cleaned up the code, made some improvements and fixed many bugs. While the property panels work really well, their implementation could profit from more cleanup. Removing duplicated code could reduce their code size and their complexity considerably. The one new property panel for inserting shapes into draw documents has roughly one tenth the number of code lines of the text property panel and still has about the same number of controls.
- The Impress panels come from OpenOffice. They allow you for example to control animations of slides and shapes. The new framework of the sidebar made big cleanups of their implementations possible. They are not view shells anymore; they are now regular controls. If you don't know what a view shell is, good for you.
- The third group consists of non-modal dialogs like the Navigator, the Gallery, or the Styles and Formatting dialog. Only small changes were necessary to plug them into the sidebar.
And what is new?
The core implementation of the sidebar and the framework provided for panel developers is completely new. The sidebar looks similar to the Symphony property panel but shares no code with it. One important new feature is that the sidebar is easily configurable via the, well, configuration. Another one is that extensions can now add new decks and panels that can freely mix with existing decks and panels. More on that later.
What exactly is "the sidebar"?
The sidebar is a window at the right side of the edit view of Writer, Calc, Impress and Draw. It provides access to frequently used tasks when editing documents. The content in the sidebar is organized into decks and panels. Decks are containers of panels, one or more of them. In very few cases there may not yet be a panel available for the current task. You can switch between decks by clicking on buttons in the tab bar at the right side of the sidebar. A menu allows you to hide decks that you don't need.
The deck that is open by default is the "Properties" deck. Its set of panels is context sensitive and varies depending on what you are currently doing. For example, if you are editing text in Writer then the "Text" panel allows you to change the font, text attributes, text and background color. The "Paragraph" panel has controls for changing bullet style, text alignment and various indents. The "Page" panel lets you change page size and orientation. It is collapsed by default. That means that you can only see its title bar. One click on it and you can see the panel. This avoids cluttering the user interface with panels that are only used occasionally while at the same time making them easily accessible for when they are used.
Why do you call it sidebar and not...?
The Symphony name "property
panel" did not work for us because the sidebar contains more than just
information about document properties.
The OpenOffice.org name
"task pane" came from the never realized idea of making OpenOffice.org
more task oriented. For example for the creation of form letters this
could have been an adapted version of the mail merge wizard that would
have displayed the general workflow and given access to templates,
address books and so on. This idea proved to be too difficult to
The name "sidebar" is generic enough to host very different content such as document properties, clip art, navigator or third party extensions. At the same time it is descriptive enough to be remembered easily. Should you ever turn off the sidebar by accident then you will have no problem finding the menu entry for the "bar" at the "side" of the edit view and turn it back on.
Why add the sidebar now, why at all?Up to now, we, the OpenOffice community (developers, UXers, testers), were busy getting the project going at our new home in the Apache community. After that came two releases and then graduation.
Only after that did we finally have the time to tackle the major task of combining the sidebars of OpenOffice and Symphony.
Many users have asked us in the past to add a Symphony-like sidebar to OpenOffice. The feedback in the Apache community regarding the sidebar in the coming release is very positive. Even downstream has started to integrate our implementation. Some of the benefits of the sidebar are:
- As in toolbars you have the most important functions for the current task available on a single click. Unlike the toolbars it does that in a single place while some toolbars are docked above the edit view, some are docked below, and still others are displayed floating in front of it.
- The position on the right side takes advantage of the form factor of most modern screens that have much more space in the horizontal direction than in the vertical.
- The sidebar provides more space to its panels than the tool bar areas provide to tool bars. Therefore panels can display more information better.
- The sidebar has a constant size (unless you decide to change that size). Context changes lead to different panels being displayed but do not change the size of the sidebar or the edit view. Dock a context sensitive tool bar and you will know how annoying such size changes can be.
What about extensions?
A little known feature of OpenOffice is that extensions can provide panels for the task panel (now called sidebar). These extensions are still supported. But now there is a better way to do this.
You can add a panel that is implemented in any language supported by the UNO API and display this panel in a deck of your choice or even in the properties panel. The panel can react to context changes such as different selections. But it does not have to. You want a panel that is only displayed when editing tables in Writer documents? No problem. You want to analyze a Calc document and display the result in real-time and always visible? That is possible. Or you can display the current time or weather.
Here is an example: an extension adds a deck (see the clock icon in the tab bar) and a panel that shows the current time.
We need your inputThe toolbars and dialogs such as gallery and navigator are not yet scheduled to be disabled by default or even to be removed. Not because we don't think that the sidebar works. It does.
The reason for keeping these established user interface elements is to let you become familiar with the sidebar in your own time. We hope that you will use the toolbars and dialogs less and less.
Apache OpenOffice is an open source project. You can help by telling us what you don't like and what you miss. Share your ideas about how to make the sidebar better. Write a comment in the comment section below or subscribe to our development mailing list if you are willing to invest a little more time. And Apache also accepts donations (not project specific).
Apache OpenOffice: One Year, 50 Million Downloads
We are pleased to note that yesterday we reached the 50 million download mark for Apache OpenOffice 3.4. This milestone occurred within a few days of the first anniversary of the release of Apache OpenOffice 3.4., on May 8th, 2012.
Apache OpenOffice (formerly called OpenOffice.org) is the leading free and open source office application suite for Windows, Mac and Linux. Version 1.0 of OpenOffice was released 11 years ago, in May 2002.
Although we're all very busy now with the testing of our next major release, Apache OpenOffice 4.0, it is worth taking a few minutes to explore some of the trends that can be discerned from our download data over the past year. The information we have gathered, relative to desktop OS versions, 64-bit Linux use, screen aspect ratios, etc., may be of special interest to other open source projects to consider in their
First a scatter plot of daily download numbers, with a 7-day moving average overlay. Noticeable on the chart is the peak in June 2012, when we enabled the upgrade notifications for OpenOffice.org 3.3.0 users, and the peak in September when Apache OpenOffice 3.4.1 was released. There is also a noticeable summer lull and big drop around the end-of-year holidays.
The following histogram shows the distribution of download counts. The average daily download count is 134,900, with a peak day of 197,500. On average we see around a million downloads every 7.4 days. Since a typical download size is
130MB, this amounts to an average of around 17 TB per day of downloads,
ably handled by SourceForge and their distribution network.
One final way to look at the daily counts (shown here in unit of 1000 downloads) is to decompose it into the sum of a smooth trend, a periodic weekly trend, and residual random noise:
We are able to break down these trends along several other dimensions. One is by country, looking at where the download request came from. This information is gleaned from the IP address of the machine making the request. Since each IP address is part of an assigned block of addresses, and blocks are assigned geographically, we can create a table of downloads by country, territory, etc. We show the full table our the website, of all 237 countries, territories, etc., but here are the top 10:
Another approach is to look at which localized versions of Apache OpenOffice were downloaded. We can see these trends in the following dot chart:
We can also look at the trend over time of downloads by operating system. OpenOffice is a mainstream open source desktop application, so the OS distribution reflects overall desktop operating system market shares, and with a slight growth in Windows at the expense of Mac:
Since we have Linux versions of OpenOffice packed as RPMs (e.g., for RedHat) as well as DEBs (e.g., for Ubuntu), we can look for trends in the ratio of requests for these two packaging formats over time:
Also, we have 32-bit and 64-bit Linux downloads, and we see a gradual increase in demand over time for the 64-bit version, though the 32-bit version still dominates. (The drop in July-September is not fully explained, but may have been an error in our download page that was not recommending 64-bit downloads appropriately.)
Although we don't have detailed download data for different Windows versions (we have a single download for all Windows users) we do have information from website visitors (nearly 7 million visitors per month) that tells a similar story. Windows 7 remains the most popular Windows version for our users, accounting for over half of Windows visitors. Windows XP is in second place, though declining. At the end of the year Windows 8 overtook Vista for 3rd place, and continues to rise.
Looking at the similar data for web browsers, we see the rise in Chrome users among our website visitors:
Information from website visitors also tells us their screen resolution. There is a huge diversity of screen resolutions, but the general trend is a gradual increase in HD 16:9 resolutions and away from the older 1280x800 and 1024x768 modes. If you average it all out and look at the average aspect ratio, you see a slow, but steady trend toward increased aspect ratios (wider screen monitors):
Results of Apache OpenOffice 4.0 Logo Survey
A quick update on our recent logo survey for Apache OpenOffice 4.0. We called on community members to submit proposals for a new project logo. The response was huge. We received over 40 logo proposals. To narrow down the choices we sought out feedback from users. We created a survey asking users to rate each logo on a 5-point scale, from Strongly Dislike to Strongly Like, as well as give an optional comment on each logo. The survey ran for one week and 5028 responses were received. Full details of the results can be found in the Apache OpenOffice Logo Survey Report. In this blog post we want to highlight some of the highest scoring logos, recognize the designers, and talk about next steps.
Samer Mansour, a software developer and an engaged citizen in his community in Toronto, aimed for "simple and flat" with his designs, "I had an a-ha moment when I saw another volunteer's flat logo. I had learned from design experts at work that thin font is the trend and is appealing to users, so I narrowed it down to put together a wordmark from an Apache licensed font that fit the bill."
Two of the top-scoring logo proposals came from Kevin Grignon, an OpenOffice contributor and a user experience designer with over 15 years experience designing user interfaces and application graphics. In his submissions, Kevin aimed to leverage some aspects of the existing branding, while modifying and enhancing other elements. As he explains, "Given the large number of graphic assets that would require updating in a refresh, my submissions retain familiar and recognizable elements including the orb element and logo type layout, which would allow a scaled rollout of the new logo. Other elements of the logo submissions were enhanced, including the curvature of the document/gulls or the use of a a stylized feather, a colour palette which harmonizes well with proposed individual product icons, the use of a globe element, and logo type colouring which emphasizes the word "open" - which is our differentiator."
Michael Acevedo is a college student studying Aviation technology in Florida, how humans and technology interact while the aircraft is in operation and finding ways to improve that relationship. He explains his design process as, "I aimed in the design of the new AOO 4 logo for something that was simple (hence why I went with a non capitalized design for the OpenOffice name) yet being something refreshing to reflect the rebirth of Apache OpenOffice. The challenge was how to create a logo that could reflect that philosophy yet being respectful and familiar to the outgoing Apache OpenOffice logo. Taking that into account, my proposed designs offer just that, something refreshing and simple, while at the same time staying true to the brand and image that has made OpenOffice their default office suite for the last 13 years or so."
You can see the top scoring design above, by Chris Rottensteiner, a webworker and genetic genealogist from South Tyrol in the Alps. He supports the free digital data flow and open elaboration trough FOSS software. "I'm a clean flat style fan and tried to make something without glossy or other "modish" elements: the brand should speak for itself. For this second and much better proposal from me I got inspired by Kevin Grignon and the Source Sans Pro font. If the consensus is v4 should receive a logo built on the existing version, I would be happy to work on possible improvements. P.S.: the work was done in Inkscape (SVG), a piece of software I love."
This design, and the next one, although they were not top scorers when measured by average score, were the logos that received the most number of "Strongly Like" selections. So they had more enthusiastic support than the other logos. The above design, from Robin Fowler, takes the traditional gulls element of the OpenOffice.org logo and makes them dynamic, while also suggesting the form of an open book. In Robin's words, "My goal for the logo was to take the traditional elements of the OpenOffice logo and give it more of a connection to the software itself. I kept the sphere similar to the original, adding a border to make it look more like an app icon. My initial idea was to take the birds and use them to form a book. The first attempts were fairly crude but I got some valuable feedback from the mailing list and managed to improve it somewhat. The feather was added to resemble the new 'Apache era' of OpenOffice."
Vasilis Xenofontos, a visionary art designer from the small island of Cyprus aimed for a modern and easy to remember logo design. "I did this design trying to show that OpenOffice will be here forever and that’s why the logo has the infinity circles in it forming the letters AOO. The two colors in it symbolize the sea and the sky showing that this software is free and all over the world."
So what are the next steps in this logo exploration? The designers of the above logos have been invited to review user comments from the survey and based on that feedback submit revised logos. We'll then review the revisions, discuss and pick the new logo. As usual at Apache we try to reach consensus by discussion wherever possible, and only vote if necessary. The above logos already show a good deal of sharing of ideas. The constructive feedback among the designers and the Apache OpenOffice community should lead us to a wonderful new logo for a wonderful new release, Apache OpenOffice 4.0.
Congratulations, obviously, to the top logos, but thanks go out to all those who contributed logos for consideration, as well as to the 5000 users who took time to rate and comment on these designs.
With Special Guest Star... Apache OpenOffice
Viewers of the hit ABC sitcom Suburgatory may have noticed something special in the season 2 finale last night, in an episode called "Apocalypse Meow". Lead character Tessa (played by Jane Levy) used the free, open source office productivity software Apache OpenOffice on her Mac, to outline the pros and cons of getting revenge on her nemesis Dalia:
Those with access (and this may have geo-based access restrictions) can see scene starting at the 8:50 mark on ABC's online version of the episode.
This is an example of "stage dressing". The designer in a play, movie or television show has a particular "look" in mind, to bring life to the script. The designer then works with the properties directory to provision the right props. Most of it is physical stuff, like furniture, lamps or other similar items. But contemporary shows, with characters interacting with technology, also use a digital form of stage dressing.
Here's another example, from Roman Polanski's 2011 comedy Carnage:
The Apache OpenOffice project has received several requests to use our
product in this way, in movies and in US and UK television programs. Why use OpenOffice in such situations? One guess is that securing rights to use open source software like Apache OpenOffice is easier than getting rights for commercial products. Another guess is that using open source avoids potential conflicts with advertisers who are selling competing products. And another guess is that they avoid showing commercial products unless they are paid for placement. I don't really know. But in any case we're pleased to see open source software, and especially Apache OpenOffice, featured in the media.
Visualizing the AOO Dev List
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
- 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.
- Then I manually cleaned up the data, coalescing multiple mail accounts used by some members.
- 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.
Welcome to GSoC Students!
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.
- 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.
One Year until the End of Life for Microsoft Office 2003
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.
Posted at 03:36PM Apr 08, 2013 by robweir in General | |
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:
- Path normalization: all paths of recent files that are saved into X-AOO Portable folder structure have been normalized
- "System" folders: the \Documents and \Backups X-ApacheOpenOffice Portable subfolders have been set as "system" folders, also moving the main folder
- 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
- 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!
Posted at 12:12PM Apr 04, 2013 by robweir in General | |
Document Freedom Day
What is Document Freedom Day?
Document Freedom Day, this year on March 27th, 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?
- Use open standards wherever your application supports them.
- If your favorite application doesn't support open standards like ODF, write to your vendor and request that they add support.
- When you publish or share a document, do so in open formats like ODF or PDF.
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.
- 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!
Apache OpenOffice: 40 Million Downloads
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:
Or, in Europe, imagine a trip from Lisbon to Moscow. That is 4,575 km, less than our Apache OpenOffice downloads would stretch:
Or try Istanbul to Islamabad. That is 4,963 km, just a little longer than the CDs would reach:
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.
Posted at 02:08PM Mar 04, 2013 by robweir in General | |
Call for Documentation Volunteers
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.
Posted at 02:25PM Feb 26, 2013 by robweir in General | |
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개의 공식언어를 가지고 있는데 오픈오피스는 이 언어로 모두 번역되었습니다.
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.