<?xml version='1.0'?>
<rss xmlns:admin='http://webns.net/mvcb/'
     version='2.0'
     xmlns:sy='http://purl.org/rss/1.0/modules/syndication/'
     xmlns:dc='http://purl.org/dc/elements/1.1/'
     xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
  <channel>
    <title>Paul's Web Pages</title>
    <link>http://paul.luon.net</link>
    <description>Trying to figure it all out</description>
    <dc:language>en-us</dc:language>
    <dc:creator>Jekyll</dc:creator>
    <dc:date>2013-01-05T21:21:00+01:00</dc:date>
    <dc:license>http://creativecommons.org/licenses/by-sa/3.0/nl/</dc:license>
    <admin:generatorAgent rdf:resource='http://jekyllrb.com'/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
  
    
    <item>
      <title>Jabber and YTex</title>
      <link>http://paul.luon.net/journal/2004/10/05/jabber-and-ytex</link>
      
      <guid isPermaLink='false'>hacking/JabberAndYTex@http://paul.luon.net/journal</guid>
      
      <dc:subject>hacking</dc:subject><dc:subject>jabber</dc:subject><dc:subject>latex</dc:subject>
      <dc:creator>Paul van Tilburg</dc:creator>
      <dc:date>2004-10-05T00:00:00+02:00</dc:date>
      <description>&lt;h3&gt;Jabber RFCs 3920 &amp;#8212; 3922&lt;/h3&gt;
&lt;p&gt;Today, the &lt;acronym title=&quot;Internet Engineering Task Force&quot;&gt;&lt;span class=&quot;caps&quot;&gt;IETF&lt;/span&gt;&lt;/acronym&gt; published the Jabber (actually &lt;acronym title=&quot;Extensible Messaging and Presence Protocol&quot;&gt;&lt;span class=&quot;caps&quot;&gt;XMPP&lt;/span&gt;&lt;/acronym&gt;) protocols as RFCs with the &lt;em&gt;Proposed Standard&lt;/em&gt; status. See also the press release on &lt;a href=&quot;http://www.jabber.org/press/2004-10-04.php&quot;&gt;jabber.org&lt;/a&gt; .
I am happy to see this!  Using Jabber for almost 4 years now, I&amp;#8217;ve noticed it has grown through the years and Jabber contacts dominate my roster since the past months.
In my opinion, Jabber suffers a bit from decentralisation. On the lists I see a lot of stuff happening but nobody that controls it at all.  The &lt;span class=&quot;caps&quot;&gt;XMPP&lt;/span&gt; system is capable of so much neat stuff, I hope this brings back the drive in &lt;acronym title=&quot;Free and Open Source Software&quot;&gt;&lt;span class=&quot;caps&quot;&gt;FOSS&lt;/span&gt;&lt;/acronym&gt; developers to work on Jabber, and the industry as well.&lt;/p&gt;
&lt;h3&gt;YTex&lt;/h3&gt;
&lt;p&gt;Working with Hobix and &lt;a href=&quot;http://hobix.com/textile&quot;&gt;Textile&lt;/a&gt; a lot, I got kindof a vibe/idea yesterday. Looking at the source of the  &lt;a href=&quot;http://poignantguide.net/&quot;&gt;Poignant Guide&lt;/a&gt; I saw it was totally done in &lt;span class=&quot;caps&quot;&gt;YAML&lt;/span&gt; to, so&amp;#8230; What if the power of Textile is combined with &lt;span class=&quot;caps&quot;&gt;YAML&lt;/span&gt; for structuring text as pre-language for generating LaTeX files. It&amp;#8217;s not that I dislike writing LaTeX and want to discard it or something, but for rapid documenting, this could be really nice. An example:
&lt;pre&gt; 
 title: An YTex document 
 author: Paul van Tilburg&lt;/p&gt;
sections:
- First section: &amp;gt;
Bla bla, this is the first section.
- Second section:
- &amp;gt;
Hmm, if there are more sections, heading stuff goes
here.  I can do &lt;strong&gt;bold&lt;/strong&gt; text and &lt;em&gt;emphasized&lt;/em&gt; text.
- First subsection: &amp;gt;
A subjection with a &lt;img src=&quot;figure.jpg&quot; title=&quot;nice caption&quot; alt=&quot;nice caption&quot; /&gt; and a
table:
| head1 | head2 |
| key1  | 3.0   |
| key2  | 15.0  |
&lt;p&gt;&lt;/pre&gt;
I&amp;#8217;ve started hacking a bit and so far the structure stuff is working out. Getting Textile to work for LaTeX instead of &lt;span class=&quot;caps&quot;&gt;HTML&lt;/span&gt; is a different story. You will hear more of this&amp;#8230; if it doesn&amp;#8217;t work out, you won&amp;#8217;t. :)&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
