Difference between revisions of "User:Zero0w"
From Apache OpenOffice Wiki
(Adding Autopackage distribution information) |
m (cleanup) |
||
| Line 20: | Line 20: | ||
* [[Firefox ODFReader extension]] -- It will go a long way to help the spread of ODF if everybody can read it without downloading the 70-100MB+ OpenOffice.org main program (at least on Windows or Mac), when a 20-200kb+ Firefox extension can do the job. | * [[Firefox ODFReader extension]] -- It will go a long way to help the spread of ODF if everybody can read it without downloading the 70-100MB+ OpenOffice.org main program (at least on Windows or Mac), when a 20-200kb+ Firefox extension can do the job. | ||
| − | * [[Autopackage distribution]] -- | + | * [[Autopackage distribution]] -- While autopackage format may still need further polish, in the long run, I believe the official Linux binary of OpenOffice.org should be delivered in '''autopackage format''' (*.package) to address the following needs: |
| − | *# | + | *# Installation among multiple Linux distributions without end users converting RPM to other package format |
| − | *# | + | *# An incremental update system (such as the one in Firefox 1.5) that can work independently outside distribution package database: Users want to use the latest and greatest -- and possibly security fixes, not wait for Linux suppliers to release a new version in a 6-9 month upgrade cycle. |
Revision as of 09:20, 27 March 2006
My name is Wily Yuen. I participate in a number of Linux and open source advocacy groups such as HKLPG and OAKA in Hong Kong. In addition, I am now a member of the Ubuntu CJK testers team, helping developers to test and fix CJK problems under Linux and OpenOffice.org.
In addition, I am also currently studying the XML round-trip possibility between the file formats of DocBook -> OpenOffice.org -> Scribus.
It will be very cool if these FOSS apps can join forces to provide a smooth and interoperable workflow in many publishing and business organizations. It certainly will boost the appeal for each of these applications.
Wiki page to work on
- Press coverage on OpenOffice.org
It's shaping up nicely. I sincerely invite you to join and continue to improve it further.
- Font-FAQ
Help on improving and documenting the CJK support in OpenOffice.org 2.x
- OOoHelpOutline - OpenOffice.org User resources
- Probably need further re-organizing
- Expand to cover links & resources for international OpenOffice.org community.
- I know that one of the Chinese OpenOffice.org user groups is trying to build up a strong community resource portals, with add-on module and projects of their own. Hence we can expand to cover OOo resources for users with different languages.
- What is interesting is that, right now, Wikipedia:OpenOffice.org is the best gathering source for international OpenOffice.org information: the "in other languages" column on the left side of the page will lead you to loads of information of OpenOffice.org in other languages around the world.
- Given strong community interest, we can build up wiki page similar to OOoHelpOutline for users of other languages in this official Wiki.
- Wikipedia did a very great job of gathering information and resources on OpenDocument (most of the writing was undertaken by David Wheeler I believe). I'm not sure, but it may be a good idea if we can have them mirrored in this Wiki (assuming the content licenses are compatible).
- Firefox ODFReader extension -- It will go a long way to help the spread of ODF if everybody can read it without downloading the 70-100MB+ OpenOffice.org main program (at least on Windows or Mac), when a 20-200kb+ Firefox extension can do the job.
- Autopackage distribution -- While autopackage format may still need further polish, in the long run, I believe the official Linux binary of OpenOffice.org should be delivered in autopackage format (*.package) to address the following needs:
- Installation among multiple Linux distributions without end users converting RPM to other package format
- An incremental update system (such as the one in Firefox 1.5) that can work independently outside distribution package database: Users want to use the latest and greatest -- and possibly security fixes, not wait for Linux suppliers to release a new version in a 6-9 month upgrade cycle.
