OpenOffice 1.1 RC 1 Released
Heartz writes "OpenOffice has released OpenOffice 1.1 RC 1. Get details here. Neat features include built in PDF and Flash export, better MS Office document filters and more!"
← Back to Stories (view on slashdot.org)
Simplicity, like AbiWord.
Less bloat, like Gnumeric (which yet scores over Excel)
Performance - It's a lot slower than MS Office, specially on Linux.
If you keep throwing chairs, one day you'll break windows....
Since Ximian have released the code to the modifications that they made to OOo, there's no reason why their icons couldn't be integrated back into the main codebase.
I am TheRaven on Soylent News
It does both of the things you mention. Not perfectly, but then neither does Word when importing older doc versions.
What rock have you been hiding uder?
But bug #1820 remains unresolved. In all fairness though, things are a bit moving for this showstopper. Hopefully there will be a solution for it in the near future.
For the few unaware of this bug, in Calc, if your locale uses "," (comma) as a decimal separator, your numeric pad is worthless because the num pad "." (dot) is interepreted as something else than a decimal separator. You imagine how difficult it is to convert people using Excel when you must explain that they cannot use their num pad anymore. And before you suggest remapping keys, please read the bug report. Many non english locales are affected by this bug.
Remember the year 2000? They promised us flying cars. They delivered the PT Cruiser...
New features in OpenOffice.org 1.1rc over OpenOffice.org beta2 release:
# a "talkback" style crash reporter to collect stacktrace and error information
# new command line parameter -start to automatically start a presentation after the document is loaded
# ability to update existing OpenOffice.org 1.0.x single user installations
# support for drawing objects in headers and footers
# an example XSLT filter for Office 2003 XML format
# support for MS Excel 95 and older form controls
# UNO python bridge - python is now a first class language for creating UNO components for OpenOffice.org
# built in spell checking dictionaries for English (UK) and Italian
# built in hyphenation support for Danish, English (UK), German and Russian
# integrated Bitstream Vera fonts
# improved spelling suggestions using n-gram scoring
Something I thought was a very annoying feature in OpenOffice 1.0.3 was that it tries to be "smart" and open a file in a part of the office suite it "thinks" is best fit to do the job, and no apparent way to turn that function off.
.txt file in Calc, it still open it in Writer. What?! I didn't tell it to open it in Writer. Even MS Office is more smart than that and imports it as best as it can by figuring out the delimiter etc, and certainly not tries to open it in the word processor, when I basically issued the command "ooocalc.exe table.txt". If it lacks the intelligence to open it, at least go confused and show me the Import dialog so I can properly import it as a tab-delimited text. But there doesn't even seem to be a setting for this...
.txt file, pick the .txt file format to be something like "Comma-delimited txt file" somewhere deep in its combo box and then it finally understands "aaah, it's delimited!" and stops forcing me to use another program than I'm trying to open it with.
:-(
For example, if I choose to open a tab-delimited
I noticed there's a setting in OO that let you select the default program to use. But I don't want to open any document in a "default" program, I want to open a document in the program I'm opening it with!
So right now, I have to go through the looong path of starting Calc stand-alone, File->Open, select the
I really hope I'm missing something here, or this behavior will be fixed in OO 1.1, because I really despise programs that think, no... assumes, they know more than you do. I was also shocked to once again have to disable the paper clip feature in OO! Only difference was that the current incarnation was now a light bulb and not a paper clip. What progress the world is making.
Beware: In C++, your friends can see your privates!
The support for anything other than United Statesian English is pretty bad.
Actually, I've been using the Greek spellchecking and autocomplete features since the betas and they beat MS Office out of the water as far as my native language goes...
Manos
there's one here: http://oootools.free.fr/memoire_cnam/ in french.
Others (still in french): http://bureautiquelibre.org/
wolruf@gmail.com
OO, or a seperate project also needs a replacement for 'Access'.
There is one it's called mysql, check out the trail of tears article at linuxworld. I find it funny that all his problems are attributable to RedHat's piss-poor package management system (or any Linux distro for that matter). I did it using FreeBSD as the server with no hassles, on a mixed FreeBSD and windows network.
own proprietary format
Surely you mean it's own open format?
Hey, thanks for the tip - I'll bamf over and check it out when everyones calmed down ;)
Secretaries are a *real* conservative bunch and likely to p*ss themselves if you so much as mention csv files. For you and me this is a great thing. For them, if it deviates too far from the current (read MS) way, it's a no-no.
Thanks again for the tip, I'll look into it.
gs supports links and bookmarks. All you have to do is insert pdfmark's in the ps file. Right now this is a big pain in the ass so hopefully oo will make this easy.
That punch-line drum thing is called a "rimshot".
pr0n - keeping monitor glass spotless since 1981.
We didn't really switch to OO, it came down to everyone needing some office software and the options being to spend about 5000$ on ms office for everyone or 0$ on openoffice.
:)
We are not a huge company (20 people in 2 depts) so we're not really an OO posterchild
What we are however is a realistic example of IT companies trying to work in a dwindling economy (Germany) with the IT market being pretty messed up anyway. For someone in our position to spend the equivilant of an extra staff member or two on software which does not help our core business would be suicidal.
Support = zero. The only times I ever had to do anything was one bug in file-saving (random bug, didnt happen again) and fixing the font sizes in redhat which is hardly the fault of OO. We don't have an office full of drones cranking out vbs infected spreadsheets. We do have a printing department but they wouldn't use an office package anyway as they need more accuracy. For "normal" office use OpenOffice is perfect for us.
If you use RH9 or SuSE 8.2 you can already get a snapshot of the work in progress wrt. a Ximianized OO.o 1.1 from the 'ooo-snapshot' channel in Red Carpet. It's pretty functional.
You don't need CVS. Here's a different tutorial that may help:m
http://www.virtualsky.net/daves/2003-08.ht
Please see http://libwpd.sf.net/ - a couple of AbiWord hackers wrote libwpd, and then wrote an OOWriter plugin for it. Complete with screenshots and downloadable binary plugins.
Dom
proprietary
1. Of, relating to, or suggestive of a proprietor or to proprietors as a group: had proprietary rights; behaved with a proprietary air in his friend's house.
2. Exclusively owned; private: a proprietary hospital.
3. Owned by a private individual or corporation under a trademark or patent: a proprietary drug.
proprietary
adj. 1. In marketroid-speak, superior; implies a
product imbued with exclusive magic by the unmatched brilliance of
the company's own hardware or software designers. 2. In the
language of hackers and users, inferior; implies a product not
conforming to open-systems standards, and thus one that puts the
customer at the mercy of a vendor able to gouge freely on service
and upgrade charges after the initial sale has locked the customer
in. Often in the phrase "proprietary crap". 3. Synonym for
closed-source, e.g. software issued in binary without source and
under a restructive license.
Since the coining of the term open source, many hackers have
made a conscious effort to distinguish between `proprietary' and
`commercial' software. It is possible for software to be commercial
(that is, intended to make a profit for the producers) without being
proprietary. The reverse is also possible, for example in
binary-only freeware.
My wife emailed me her resume (in .doc format, which, like it or not, is the standard nowadays) so I could review it.
OpenOffice.org 1.0.3 crashed upon trying to open it. This is a Word doc that was exported from OO.org 1.0.3... how sad is that? I installed 1.1RC1 and it was just fine though. So I'd guess the import is improved.
Installing RC1 on her system was rather more difficult... since the installer kept bombing about a UNICOWS.DLL error. Yes, the solution was easy to find on the website, but why not have a more useful error message than that in the first place? If it's a FAQ, it should be reasonable to integrate the error message into the installer rather than confuse the user. Most people will get an error like that and say screw it and go back to Word/Works/whatever.
KDE's KOffice is developing a *complete* suite of applications to replace MS Office. In your case, please investigate Kexi (www.koffice.org/kexi/), a true Access replacement.
Eron
Summary:
i don't like style guides
So, what kind of developmet does Open Office allow?
Read all about it. api.openoffice.org udk.openoffice.org
Go over to OOoForum.org , go into the Macros and API section and read what people are doing.
Go over to OOoDocs.org , they also have a Macros and devlopment section.
You can write StarBasic code directly into OOo documents. You can write programs in Java to drive a running OOo, even on a different computer. (For example, a Java program on, say, Windows, telling an OOo running on Linux what to do.) You can write components in C++ or Java or Python.
The Python UNO bridge is new. I haven't tried it yet. I believe you can do anything with Python that you could do with Java or C++ in OOo. StarBasic is limited in that you cannot create new components, it lacks sophisticated data structures, and you can only embed it within documents. The other languages cannot be embedded within documents (yet). I'm hoping to someday be able to embed Java classes or Python within an OOo document, just like I can with StarBasic macros.
Be sure to download the SDK. Read the documentation, especially the developer's guide. The first big learning curve is to understand UNO. This is pretty much a prerequisite for everything else. Once you do though, you're on your way.
Oh yeah, on languages that can access OOo. If you're on Windows, you can use Windows Automation. This means you can access it from, say, Visual Basic. I have seen OpenOffice.org programmed from Visual FoxPro.
The price of freedom is eternal litigation.
Windows Downloads:
://ftp.ussg.iu.edu/pub/openoffice/stable/1.1rc/ OOo_1.1rc_LinuxIntel_install.tar.gz .gz /stab le/1.1rc/OOo_1.1rc_LinuxIntel_install.tar.gz
http://www.binarycode.org/openoffice/s table/1.1rc/ OOo_1.1rc_Win32Intel_install.zip
http://www.ibibl io.org/pub/packages/openoffice/sta ble/1.1rc/OOo_1.1rc_Win32Intel_install.zip
ftp:// ftp.ussg.iu.edu/pub/openoffice/stable/1.1rc/ OOo_1.1rc_Win32Intel_install.zip
http://openoffic e.mirrors.pair.com/stable/1.1rc/OO o_1.1rc_Win32Intel_install.zip
ftp://openofficeor g.secsup.org/pub/software/openof fice/stable/1.1rc/OOo_1.1rc_Win32Intel_install.zip
ftp://mirrors.umbc.edu/pub/editors/openoffice/st ab le/1.1rc/OOo_1.1rc_Win32Intel_install.zip
Linux Downloads:
http://www.binarycode.org/openoffice/s table/1.1rc/ OOo_1.1rc_LinuxIntel_install.tar.gz
http://www.ib iblio.org/pub/packages/openoffice/sta ble/1.1rc/OOo_1.1rc_LinuxIntel_install.tar.gz
ftp
http://openof fice.mirrors.pair.com/stable/1.1rc/OO o_1.1rc_LinuxIntel_install.tar.gz
ftp://openoffic eorg.secsup.org/pub/software/openof fice/stable/1.1rc/OOo_1.1rc_LinuxIntel_install.tar
ftp://mirrors.umbc.edu/pub/editors/openoffice
MacOSX Downloads:
http://porting.openoffice.org/mac/ooo- osx_download s.html#download
New features in OpenOffice.org 1.1rc over OpenOffice.org beta2 release
* a "talkback" style crash reporter to collect stacktrace and error information
* new command line parameter -start to automatically start a presentation after the document is loaded
* ability to update existing OpenOffice.org 1.0.x single user installations
* support for drawing objects in headers and footers
* an example XSLT filter for Office 2003 XML format
* support for MS Excel 95 and older form controls
* UNO python bridge - python is now a first class language for creating UNO components for OpenOffice.org
* built in spell checking dictionaries for English (UK) and Italian
* built in hyphenation support for Danish, English (UK), German and Russian
* integrated Bitstream Vera fonts
* improved spelling suggestions using n-gram scoring
OpenOffice.org 1.1 RC Features
2003-07-11
Enhanced file format support
* PDF (Portable Document Format) export
* Support for mailing a document as PDF.
* DocBook/XML import/export.
* XHTML export.
* Support for exporting as a flat XML file.
* Support for Macromedia Flash (SWF) export.
* Support for mobile device formats like AportisDoc (Palm), Pocket Word and Pocket Excel.
* Example xslt based filter for Office 2003 XML documents
Accessibility
* Support for full keyboard navigation and control
* Support for tracking system colour scheme and theme settings
* Support for accessibility in the help system and documents
* Initial support for Assistive Technologies via Java accessibility APIs
Internationalization
CTL, vertical and bidirectional writing
* Support for vertical writing within text documents, text frames and graphic objects
* Support for vertical writing in spreadsheet cells (the direction is individualy selectable)
* Support for input, display and editing of scripts using Complex Text Layout (CTL)
* Support for RTL layout and text in the OpenOffice.org GUI
* Support for BiDi-writing in OpenOffice.org documents
* Support for using either Arabic or Hindi numerals
* The RTL vs. LTR default text direction is automaticly selected based on locale
Other Internationalization enhancements
* Support for various 8-bit Arabic and Hebrew text encodings / code pages.
* Support for the KOI8_U encoding.
* New CTL options tab in language options dialog.
* Rescue mode support for BiDi/CTL with X11 fonts.
* S
Notepad specialist & FAT administrator, group training available
Have you ever tried going to File > Properties ?
(it's something like that, i dont have it infront of me)
You could even insert a wordcount field and hit F9 every now and then.
Malike Bamiyi wanted my assistance.
File/Properties/Statistics. Certainly not the best implimentation but it's there.
It is way way faster than the previous version at startup. THANK YOU VERY MUCH!!!
Want it faster? Well, there's only so much two guys can do. We just finished our first full Gold Master release just two weeks ago and man, we need a vacation!
Its installer will help a Mac X11 neophyte through the process of setting up an X11 environment. It's also got the Start OpenOffice.org project to allow you to launch it like a normal Mac application and do document associations (e.g. double clicking an OOo doc opens it up!).
Two native versions are in the works, NeoOffice (Cocoa) and NeoOffice/J (Java2D...only for UI, it's still 99% C++! It's the shoddy C++ that's slow, not Java!).
Because of political issues of submitting patches and difficulty modifying code owned by the gsl project, it's difficult to do this work within OpenOffice.org. We're also trying to take the project in directions that Sun doesn't want to take StarOffice, and OpenOffice.org really is just the StarOffice development team with its own motivations needed to keep their jobs...and helping a bunch of free software dudes isn't one of them. As sucn, there may unfortunately never be an official OpenOffice.org Aqua port with a true Mac UI.
We're working as hard as we can (c'mon, we're not paid!), and you should keep your pantyhose on. OpenOffice.org 1.1 Developer Preview for MacOS X shall be coming soon (e.g. we've had time to stop committing patches and make a really rough really untested binary). And also coming down the pike is another binary of NeoOffice/J with full Japanese support, both for input as well as localization!
Surely you mean it's own open format?
No, it's own proprietary format, as in "designed by them, and only used by them".
NO CARRIER
To commit code back into OpenOffice.org, three things must happen:
As an example, all y'all linux, *bsd dudes could have had three-modifier (e.g. use Alt, Control, and Meta for keyboard shortcuts) but project politics kept these patches from being accepted into the source base. Silly that such a simple community-contributed feature wasn't accepted, no?
This patch submission difficulty is one of the reasons why Ximian icons and patches are not within OpenOffice.org. It's also one of the reasons the Tru64 patches never made it back into OpenOffice.org. The Tru64 team got 1.0.0 compiling, but the patch submission/approval process was so daunting they just didn't bother.