<?xml version="1.0"?>
<rss version="2.0.">
  <channel>
    <title>Advogato blog for caolan</title>
    <link>http://www.advogato.org/person/caolan/</link>
    <description>Advogato blog for caolan</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Sat, 17 May 2008 19:31:46 GMT</pubDate>
    <item>
      <pubDate>Wed, 7 May 2008 07:09:02 GMT</pubDate>
      <title>dead code list</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=104</link>
      <guid>http://blogs.linux.ie/caolan/2008/05/07/dead-code-list/</guid>
      <description>&lt;p&gt;Up to date lists of the currently unreferenced symbols in OOo are available &lt;a href="http://people.redhat.com/caolanm/callcatcher/" &gt;here&lt;/a&gt;. Currently 2823 methods, though a lot of these should go away when the submitted patches filter through.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Thu, 1 May 2008 11:16:53 GMT</pubDate>
      <title>OOo gio integration</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=103</link>
      <guid>http://blogs.linux.ie/caolan/2008/05/01/ooo-gio-integration/</guid>
      <description>&lt;p&gt;So I finished off Jan&amp;#8217;s initial gio OpenOffice.org integration work (i.e. &lt;a href="http://www.openoffice.org/issues/show_bug.cgi?id=88090" &gt;issue 88090&lt;/a&gt; as workspace ucpgio1)&lt;/p&gt;
&lt;p&gt;The gio api is a &lt;b&gt;far&lt;/b&gt; better fit to the OOo worldview than gnome-vfs is and was pretty straightforward to implement modulo my own bafflement as to why I had an error claiming that mounting share named &amp;#8220;X&amp;#8221; failed as not existing which incredibly had the root cause that the share named &amp;#8220;X&amp;#8221; was really called &amp;#8220;Y&amp;#8221;.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Mon, 14 Apr 2008 10:11:50 GMT</pubDate>
      <title>GoOOoCon08</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=102</link>
      <guid>http://blogs.linux.ie/caolan/2008/04/14/goooocon08/</guid>
      <description>&lt;p&gt;The GoOOoCon08 &lt;a href="http://people.redhat.com/caolanm/GoOOoCon08.odp" &gt;Presentation&lt;/a&gt; that I gave.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Tue, 19 Feb 2008 15:05:52 GMT</pubDate>
      <title>ms binary docs</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=101</link>
      <guid>http://blogs.linux.ie/caolan/2008/02/19/ms-binary-docs/</guid>
      <description>&lt;p&gt;Since the ms binary docs documentation release I&amp;#8217;m gotten a veritable blizzard of mails about it.&lt;/p&gt;
&lt;p&gt;The move is welcome of course, efforts to improve interoperability are always appreciated. So thanks.&lt;/p&gt;
&lt;p&gt;But the original &amp;#8216;97 formats were released on MSDN around 97/98 and were available on the MSDN website for some months around then, so this isn&amp;#8217;t as totally new as people seem to think. MS has done this once before. (I wrote &lt;a href="http://www.skynet.ie/~caolan/Packages/ivt2html.html" &gt;ivt2html&lt;/a&gt; a stack of years ago just to read the .ivt format of that era). Though clearly the documentation for 2007 will include the changes since 97, but the changes to the format are compatible ones and over the years OOo has already figured out pretty much all of the relevant additions. So the release of the formats is likely to help &lt;strong&gt;other&lt;/strong&gt; projects that want to start from scratch much more than it helps a project like OOo that has pretty much already figured out the majority of what I assume (I don&amp;#8217;t do much .doc import/export anymore) is in the documentation.&lt;/p&gt;
&lt;p&gt;The remaining major issues for compatibility IMO for .doc/.odt at least break down into 3 categories&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Misunderstanding of the format, that&amp;#8217;s the smallest issue by far, maybe some table in table glitches fall into this category&lt;/li&gt;
&lt;li&gt;Disjoint feature sets, e.g. there are some constructs in writer that don&amp;#8217;t exist in word which are problematic to export to .doc, i.e. all of the writer page styles possibilities are not expressible in the word section system, and vice-versa there are word features that don&amp;#8217;t have mapping in writer, i.e. highlighting as a separate setting than text foreground color, though that&amp;#8217;s obviously easier to fix&lt;/li&gt;
&lt;li&gt;weirdness, i.e. the layout algorithm rules to determine what to do when faced with layout constraints that cannot be met, e.g. roughly a circular dependency where e.g. a graphic anchored to a paragraph affects its own layout in some nasty feedback way, especially in multi-column documents. As as example of an oddity that&amp;#8217;s taken care of by the .doc import/export filters the top left corner of a graphic in writer is position x,y of its properties and the border (if any) is drawn inside that extent while in word the border is drawn outside it, i.e. the top left corner of a bordered graphic&amp;#8217;s exent in word is x-borderwidth,y-borderheight, unless it is one of a small class of banded borders where only the first stripe or two is positioned outside the unbordered graphics extent, and the other stripes are inside it. i.e. when importing or exporting it you have to know what type of border is being applied and fudge the figures to get the same size and position of the total entity to get the same positioning as in the other application.&lt;/li&gt;
&lt;/ol&gt;
</description>
    </item>
    <item>
      <pubDate>Sun, 17 Feb 2008 12:11:32 GMT</pubDate>
      <title>OOo ia64 port</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=100</link>
      <guid>http://blogs.linux.ie/caolan/2008/02/17/ooo-ia64-port/</guid>
      <description>&lt;p&gt;I&amp;#8217;ve completed a ia64 linux uno bridge. Patch &lt;a href="http://qa.openoffice.org/issues/show_bug.cgi?id=84999" &gt;here&lt;/a&gt; and corresponding demo OOo &lt;a href="http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/ia64port01/" &gt;debs&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Thu, 24 Jan 2008 10:07:21 GMT</pubDate>
      <title>24 Jan 2008</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=99</link>
      <guid>http://blogs.linux.ie/caolan/2008/01/24/144/</guid>
      <description>&lt;p&gt;Here&amp;#8217;s a zoomed in view of the gedit &lt;i&gt;File&lt;/i&gt; label which is rendered with cairo. &lt;img src="http://people.redhat.com/caolanm/png/gedit-example.png" alt="gedit" /&gt;. And here&amp;#8217;s one of the same label as rendered by OOo currently. &lt;img src="http://people.redhat.com/caolanm/png/OOo-orig-example.png" alt="orig" /&gt;&lt;/p&gt;
&lt;p&gt;After adding my experimental &lt;a href="http://qa.openoffice.org/issues/show_bug.cgi?id=85470" &gt;cairo text render&lt;/a&gt; patch, here&amp;#8217;s the OOo one again. &lt;img src="http://people.redhat.com/caolanm/png/OOo-cairo-example.png" alt="new" /&gt;. Pretty neat.&lt;/p&gt;
&lt;p&gt;Cairo makes it utterly trivial to support text rotation, scaling and artificial oblique. All pretty neat. On the other hand currently artificial emboldening is painful as you can only get it through the &lt;tt&gt;cairo_ft_font_face_create_for_pattern&lt;/tt&gt; api and not my preferred &lt;tt&gt;cairo_ft_font_face_create_for_ft_face&lt;/tt&gt;, so the code to do that is disabled and we fall back to the current rendering mechanism for emboldened fons. You can turn it on in today&amp;#8217;s rawhide OOo with &lt;tt&gt;export SAL_ENABLE_CAIROTEXT=1&lt;/tt&gt;. I haven&amp;#8217;t done any extensive testing to see if all is ok with CJK text, but I don&amp;#8217;t really expect any problems.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Mon, 21 Jan 2008 15:05:47 GMT</pubDate>
      <title>pixmap leaking</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=98</link>
      <guid>http://blogs.linux.ie/caolan/2008/01/21/pixmap-leaking/</guid>
      <description>&lt;p&gt;So I &lt;a href="http://www.openoffice.org/issues/show_bug.cgi?id=85321" &gt;fixed a little Pixmap leak&lt;/a&gt; in OOo and afterwards wanted to see what the the remaining pixmaps might be. Stripping down &lt;a href="https://www.redhat.com/archives/olpc-software/2006-March/msg00032.html" &gt;this code&lt;/a&gt; to gave me a quick and dirty Pixmap browser that takes pixmap ids from stdin and then I stuffed a LD_PRELOAD lib in there to intercept OOo&amp;#8217;s XCreatePixmap and XFreePixmap and fed the list of unfreed pixmaps to the browser and ta-da intsta-handy debugging tool. &lt;a href="http://people.redhat.com/caolanm/pixmaps/pixmap.c" &gt;pixmaptracker&lt;/a&gt; and &lt;a href="http://people.redhat.com/caolanm/pixmaps/dumper.c" &gt;browser&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Wed, 9 Jan 2008 11:13:13 GMT</pubDate>
      <title>english locales</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=97</link>
      <guid>http://blogs.linux.ie/caolan/2008/01/09/english-locales/</guid>
      <description>&lt;p&gt;For some reason (crap translations ?, just prefer using English ?), it&amp;#8217;s common for some non-english speakers to run their desktop with an en_US locale but then to have difficulties that stuff like openoffice.org, etc. defaults to letter size paper and inches for display units. So my modest suggestion is that if you want to use an English locale then a non en_US locale like e.g. en_GB will default to the way more common A4 paper format and also default to cm for units. Even better for most europeans, using en_IE will also give you A4, cm and additionally the default currency as Euro.&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Mon, 3 Dec 2007 16:04:10 GMT</pubDate>
      <title>hp ski simulator</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=96</link>
      <guid>http://blogs.linux.ie/caolan/2007/12/03/hp-ski-simulator/</guid>
      <description>	&lt;p&gt;Tried to get the hp &lt;a href="http://ski.sourceforge.net/" &gt;&lt;i&gt;ski&lt;/i&gt;&lt;/a&gt; ia64 simulator running recently, and fell into some newbie problems trying to get a 2.6 kernel running at the right speed with a useful amount of memory on it, mostly because I was looking at the wrong bit to try and find what limited the memory and controlled the clock timing, i.e.
&lt;ol&gt;
&lt;li&gt;The bootloader is what restricts the available memory, not the simulator itself. &lt;a href="http://people.redhat.com/caolanm/ski/linux-hpsim.increasemem.patch" &gt;Patch&lt;/a&gt; to increase from 130Megs to 1Gigs
&lt;/li&gt;
	&lt;li&gt;The clock runs way too fast, again the simulator doesn&amp;#8217;t control that, the bootloader does. &lt;a href="http://people.redhat.com/caolanm/ski/linux-hpsim.slowclock.patch" &gt;Patch&lt;/a&gt; to reduce speed dramatically so &lt;i&gt;make&lt;/i&gt; doesn&amp;#8217;t get woefully confused
&lt;/li&gt;
	&lt;li&gt;A &lt;a href="http://people.redhat.com/caolanm/ski/vmlinux" &gt;prebuilt&lt;/a&gt; 2.6.18 kernel, and &lt;a href="http://people.redhat.com/caolanm/ski/bootloader" &gt;bootloader&lt;/a&gt; from &lt;a href="http://people.redhat.com/caolanm/ski/skiconfig" &gt;this config&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
</description>
    </item>
    <item>
      <pubDate>Thu, 29 Nov 2007 21:04:37 GMT</pubDate>
      <title>Seagate Free Agent Pro</title>
      <link>http://www.advogato.org/person/caolan/diary.html?start=95</link>
      <guid>http://blogs.linux.ie/caolan/2007/11/29/seagate-free-agent-pro/</guid>
      <description>	&lt;p&gt;Amazingly, &lt;a href="http://thebs413.blogspot.com/2007/06/seagate-free-agent-pro-forgets-esata.html&gt;the rumour&lt;/a&gt; is true, I had to strip back a chunk of plastic from a eSata cable to get it to sit correctly into the connector of my Seagate Free Agent Pro, truly bizarre.
&lt;/p&gt;
" </description>
    </item>
  </channel>
</rss>
