$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> WORKSPACE » Linux Magazine
 

Implementing the bracket notation system in OpenOffice.org

WORKSPACE

Author(s):

We’ll show you a universal system for marking changes in text documents; and along the way, you’ll get some practical experience with writing OpenOffice marcos.

The Changes feature in Open-Office.org is an essential tool for collaborative editing. Although it is easy to understand, this feature has a couple of serious drawbacks. First, Changes works best only when you are dealing with OpenOffice.org’s native formats. If your peers are using Microsoft Office, there is no guarantee that changes will survive back-and-forth conversion. And if your colleagues are using any other word processor, such as AbiWord, TextMaker, or KWord, you are completely out of luck. Secondly, the Changes feature is not the most elegant solution out there, and it can sometimes be quite cumbersome.

Fortunately, you don’t have to put up with these limitations. Instead, you can implement an alternative solution for marking changes in a document. This alternative is known as bracket notation. Although bracket notation is not a new idea, it is best explained and implemented by the people behind the Get Humanized blog [1].

Read full article as PDF »

Workspace_Bracket_Notation.pdf (189.53 kB)
comments powered by Disqus

Visit Our Shop

Trial Subscription

Digital Subscription

Subscribe

Direct Download

Read full article as PDF »

Workspace_Bracket_Notation.pdf (189.53 kB)

Tag Cloud

Bruce Byfield Gnome KDE Kernel Linux Linux Pro Magazine Open Source Projects Red Hat Ubuntu events foss free software google

News