Bridging the gap between Office and OpenOffice

OpenOffice 2.0 -- the free, open source office suite -- has many features that are very similar to Microsoft Office. The trick is knowing how to use them. In this Q&A, expert Solveig Haugland explains how to use such OpenOffice features as the Draw tool, tabbed headers and footers. She also describes custom creation of colors, file sharing tips and how Microsoft Office documents are completely compatible with OpenOffice.
Microsoft Office has the 'more colors' option. How can I add more colors to the OpenOffice palette?
Solveig Haugland: You can create any color you want, in OpenOffice.org. Choose Tools > Options > OpenOffice.org > Colors. Then click 'Edit' and in the window that appears. Double-click in the left hand square of colors, then refine it in the right side. You can also just type in the RGB or CMYK values you want. Click OK, then click Add and name the color what you want. The color will show up in all color selection lists in OpenOffice.org.
How does OpenOffice flag or eliminate extra spacing?
-
- Login or register to post comments
Printer-friendly version
- 899 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
GitLab Web IDE
| Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
|
Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
| Security: Updates, Trustjacking, Breach Detection
|
Recent comments
5 min 3 sec ago
5 min 35 sec ago
7 min 3 sec ago
3 hours 13 min ago
3 hours 25 min ago
10 hours 17 min ago
1 day 12 hours ago
1 day 13 hours ago
1 day 19 hours ago
2 days 20 hours ago