<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Optimise OpenOffice.org</title>
	<atom:link href="http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 13:04:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Silverlokk</title>
		<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/comment-page-1/#comment-3776</link>
		<dc:creator>Silverlokk</dc:creator>
		<pubDate>Mon, 22 Mar 2010 04:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxuser.co.uk/?p=1313#comment-3776</guid>
		<description>Update: my style sheet automagically inserts two line feeds between paragraphs, so when I do the last step of the macro-to-be , I only need to replace the ~!~ with a single \n. Of course, I recommend a style sheet if you consistently want two line feeds between paragraphs, and to save it as the default style.</description>
		<content:encoded><![CDATA[<p>Update: my style sheet automagically inserts two line feeds between paragraphs, so when I do the last step of the macro-to-be , I only need to replace the ~!~ with a single \n. Of course, I recommend a style sheet if you consistently want two line feeds between paragraphs, and to save it as the default style.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silverlokk</title>
		<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/comment-page-1/#comment-3765</link>
		<dc:creator>Silverlokk</dc:creator>
		<pubDate>Sun, 21 Mar 2010 06:16:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxuser.co.uk/?p=1313#comment-3765</guid>
		<description>Sorry, forgot an important step. After doing the search-and-replace of \n\n with ~!~, next enter \n in the &quot;Search for&quot; box, and a single space in the &quot;Replace with&quot; box, then Replace All. After this, Search for: ~!~, then Replace with: \n\n, etc...</description>
		<content:encoded><![CDATA[<p>Sorry, forgot an important step. After doing the search-and-replace of \n\n with ~!~, next enter \n in the &#8220;Search for&#8221; box, and a single space in the &#8220;Replace with&#8221; box, then Replace All. After this, Search for: ~!~, then Replace with: \n\n, etc&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silverlokk</title>
		<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/comment-page-1/#comment-3764</link>
		<dc:creator>Silverlokk</dc:creator>
		<pubDate>Sun, 21 Mar 2010 06:12:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxuser.co.uk/?p=1313#comment-3764</guid>
		<description>BTW, in keeping with the spirit of the article: I would take a text file which has new lines between lines, and two new lines between paragraphs, and record a macro that would have new lines only between paragraphs. Take a README file, for instance. Anyway, first thing to *before* recording is check the Edit &gt; Find dialog to see if it does Regular Expressions. Depending on your preferences, you may leave that box unchecked first, and let the macro take care of checking it upon start, then unchecking it when it exits. Or, if you keep it checked, you&#039;ll record the macro from the time you do the Edit &gt; Find.

Enter \n\n in the &quot;Search for: box, and ~!~ in the &quot;Replace with&quot; box, then click on the Replace All button. That replaces all the double line feeds with the string &quot;~!~&quot;. I&#039;m doing this because I&#039;ll replace single occurrences of \n with a space. If my first find-and-replace was for the single occurrences of \n, paragraphs would run into each other.

The Search-and-replace dialog box stays on-screen. Now, Enter ~!~ in the &quot;Search for&quot; box, and \n\n in the &quot;Replace with&quot; box, then click on the Replace All button. That one breaks paragraphs with two line feeds.

If you prefer to keep Regular Expressions disabled, uncheck the relevant check box. Close the Find-Replace dialog box, stop the macro recording.

One thing I haven&#039;t checked is the effect of paragraph styles on the macro. Like, in my default style sheets, I have two line feed between paragraphs. If that&#039;s also the case for your default style sheet, your replacement string for ~!~ will be a single \n.

As to the ~!~ thingy, I chose that on the assumption that text normally wouldn&#039;t contain that character. Might be safer to use a longer string, e.g., ThisStringIsTemporaryParagraphBreak -- since this is a macro, you&#039;ll be doing that only once anyway :)</description>
		<content:encoded><![CDATA[<p>BTW, in keeping with the spirit of the article: I would take a text file which has new lines between lines, and two new lines between paragraphs, and record a macro that would have new lines only between paragraphs. Take a README file, for instance. Anyway, first thing to *before* recording is check the Edit &gt; Find dialog to see if it does Regular Expressions. Depending on your preferences, you may leave that box unchecked first, and let the macro take care of checking it upon start, then unchecking it when it exits. Or, if you keep it checked, you&#8217;ll record the macro from the time you do the Edit &gt; Find.</p>
<p>Enter \n\n in the &#8220;Search for: box, and ~!~ in the &#8220;Replace with&#8221; box, then click on the Replace All button. That replaces all the double line feeds with the string &#8220;~!~&#8221;. I&#8217;m doing this because I&#8217;ll replace single occurrences of \n with a space. If my first find-and-replace was for the single occurrences of \n, paragraphs would run into each other.</p>
<p>The Search-and-replace dialog box stays on-screen. Now, Enter ~!~ in the &#8220;Search for&#8221; box, and \n\n in the &#8220;Replace with&#8221; box, then click on the Replace All button. That one breaks paragraphs with two line feeds.</p>
<p>If you prefer to keep Regular Expressions disabled, uncheck the relevant check box. Close the Find-Replace dialog box, stop the macro recording.</p>
<p>One thing I haven&#8217;t checked is the effect of paragraph styles on the macro. Like, in my default style sheets, I have two line feed between paragraphs. If that&#8217;s also the case for your default style sheet, your replacement string for ~!~ will be a single \n.</p>
<p>As to the ~!~ thingy, I chose that on the assumption that text normally wouldn&#8217;t contain that character. Might be safer to use a longer string, e.g., ThisStringIsTemporaryParagraphBreak &#8212; since this is a macro, you&#8217;ll be doing that only once anyway :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silverlokk</title>
		<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/comment-page-1/#comment-3763</link>
		<dc:creator>Silverlokk</dc:creator>
		<pubDate>Sun, 21 Mar 2010 05:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxuser.co.uk/?p=1313#comment-3763</guid>
		<description>Find, More options, Regular expressions does it, although you do have to know regular expressions. OTOH, how would you search for new lines in MS Word?</description>
		<content:encoded><![CDATA[<p>Find, More options, Regular expressions does it, although you do have to know regular expressions. OTOH, how would you search for new lines in MS Word?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/comment-page-1/#comment-3614</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Thu, 18 Mar 2010 17:18:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxuser.co.uk/?p=1313#comment-3614</guid>
		<description>i have opened 10 tickets with open office so far since it was star office and it cannot do basic new line search and replace.
10 times my ticket was closed in 10 years telling me its not important feature that needs attention
</description>
		<content:encoded><![CDATA[<p>i have opened 10 tickets with open office so far since it was star office and it cannot do basic new line search and replace.<br />
10 times my ticket was closed in 10 years telling me its not important feature that needs attention</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A. Lurker</title>
		<link>http://www.linuxuser.co.uk/tutorials/optimise-openoffice-org/comment-page-1/#comment-3596</link>
		<dc:creator>A. Lurker</dc:creator>
		<pubDate>Thu, 18 Mar 2010 03:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxuser.co.uk/?p=1313#comment-3596</guid>
		<description>You missed the biggest tip of all: How to properly print to an envelope. I have the vanilla-ist of printers; an HP Laserjet 4. I have looked at maybe a dozen web articles telling me how to print envelopes in Openoffice and none of them worked. Printing in Slackware 7.1 to my Deskjet 520 worked better than this. Printing to envelopes; now there&#039;s a story for you.</description>
		<content:encoded><![CDATA[<p>You missed the biggest tip of all: How to properly print to an envelope. I have the vanilla-ist of printers; an HP Laserjet 4. I have looked at maybe a dozen web articles telling me how to print envelopes in Openoffice and none of them worked. Printing in Slackware 7.1 to my Deskjet 520 worked better than this. Printing to envelopes; now there&#8217;s a story for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

