<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.text.txt2tags">
    <title>gmane.text.txt2tags</title>
    <link>http://blog.gmane.org/gmane.text.txt2tags</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/395"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/389"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/386"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/380"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/376"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/375"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/366"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/365"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/365"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/363"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/355"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/351"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/348"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/347"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/345"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/344"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/343"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/334"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/329"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.txt2tags/325"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/395">
    <title>hyphens, dashes and friends</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/395</link>
    <description>&lt;pre&gt;Many years ago, when I was in school, I used LaTeX for writing all my
papers.  From that, I developed the following habits for hyphen/dash usage:

    - A single hyphen for combined words: "blue-green"
    - A double hyphen for numerical ranges: "50--100"
    - A triple hyphen---in other words, a dash---as a grammatical
construct, as in this bullet point

Of course, LaTeX transformed those strings of hyphens into lines of
increasing length for the printable output.  But I personally adopted the
convention even for plain text (such as emails), and now it's virtually
impossible for me to not do that.

And for what it's worth, I've noticed that the auto-correct features in
Microsoft Outlook seems to follow somewhat similar rules... I haven't taken
the time to figure out exactly what does what, but there is definitely a
distinction between hyphens and dashes.

I can't seem to find if there is any similar convention in txt2tags.  In
fact, the double hyphen gets interpreted as strikethrough.  So I was just
wonderi&lt;/pre&gt;</description>
    <dc:creator>Matt Garman</dc:creator>
    <dc:date>2013-04-11T21:26:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/389">
    <title>txt2tags in a python script</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/389</link>
    <description>&lt;pre&gt;Hi,

I would like to create a python script that uses a variable as input for
txt2tags without the creation of a t2t file. Is it possible?

Thanks
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis &amp;amp; visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter&lt;/pre&gt;</description>
    <dc:creator>gui b</dc:creator>
    <dc:date>2013-04-09T11:19:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/386">
    <title>Interpreted marks in title tags and named links</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/386</link>
    <description>&lt;pre&gt;Hi all.

I'm trying to find a way to get interpreted marks inside a title tag or a
named link.  For example, say I want a section of my document to have the
title

Why *Wuthering Heights* should not be taught in school

Doing this the naive way

  == Why //Wuthering Heights// should not be taught in school ==

doesn't work, because marks are not interpreted inside of title tags.  The
only thing I've been able to figure out is to use a postproc filter like

%!postproc(html): "TAG{(.*?)}" &amp;lt;\1&amp;gt;

and then use this inside the title tags:

  == Why TAG{i}Wuthering HeightsTAG{/i} should not be taught in school ==

Of course, this makes me sad for many reasons.  A similar problem happens
in named links, and I'm sure in many other places where marks aren't
interpreted.  I've looked and looked and can't find a nice way to do this.
 Does anyone have any advice for me?

Thanks!

galen
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.&lt;/pre&gt;</description>
    <dc:creator>Galen Menzel</dc:creator>
    <dc:date>2013-04-04T18:39:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/380">
    <title>mark2tags, the new lightweight markup langage.</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/380</link>
    <description>&lt;pre&gt;John Gruber and Aurelio Jargas, the respective founders of markdown and txt2tags, have just announced the imminent release of mark2tags, the future of wiki markup.

It will be the next industry standard, with an innovative syntax everyone will agree on.


"mark2tags, the last wiki syntax you'll ever need to learn. Period."



= Heading level 1 =
===================

&lt;/pre&gt;</description>
    <dc:creator>Forgeot Eric</dc:creator>
    <dc:date>2013-04-01T17:42:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/376">
    <title>txt2tags generating wrong asciidoc ?</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/376</link>
    <description>&lt;pre&gt;Hi,

I am using txt2tags version "txt2tags version 2.6 &amp;lt;http://txt2tags.org&amp;gt;"
and I am using it to generate asciidoc. It seems its generating wrong
asciidoc, is it a bug or something?

====test.t2t====

%!target   : adoc
%!encoding : UTF-8

- Item
  - Sub Item
====text.t2t====

generates

====test.adoc====


- Item
  - Sub Item
====test.adoc====

Notice the list markup in generated adoc.

&lt;/pre&gt;</description>
    <dc:creator>Pradeep Jindal</dc:creator>
    <dc:date>2013-02-11T18:29:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/375">
    <title>dokuwiki and txt2tags</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/375</link>
    <description>&lt;pre&gt;Now you can create dokuwiki pages and edit them using the txt2tags syntax!

https://www.dokuwiki.org/plugin:txt2tags

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
&lt;/pre&gt;</description>
    <dc:creator>Forgeot Eric</dc:creator>
    <dc:date>2012-12-11T00:49:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/366">
    <title>How do you convert HTML to txt2tags _automatically_???</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/366</link>
    <description>&lt;pre&gt;Greetings,
the title says it all.

I DO know about this VI/VIM macro (if that's the correct name):

http://txt2tags.org/tips.html#html-to-t2t

but I am looking for a way to do everything in a shell script, not
interactively inside VI or VIM

I have found this suggestion on how to run vi inside a shell script:

http://www.computing.net/answers/linux/use-vi-within-script/29184.html

but I can't find a way to adapt that trick to load a local copy of
this file

http://txt2tags.googlecode.com/svn/trunk/extras/unhtml.vim

and execute it. Is it possible?

If not, could that unhtml.vim file be loaded/executed via awk, sed, whatever...
with as little editing as possible?

If that isn't possible either, are there other already tested ways to
automatically convert an HTML file to t2t markup from inside a shell script?

TIA,
MArco

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and p&lt;/pre&gt;</description>
    <dc:creator>M. Fioretti</dc:creator>
    <dc:date>2012-12-06T19:19:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/365">
    <title>Latex equations</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/365</link>
    <description>&lt;pre&gt;Hello !

I'm new to txt2tags.
I would like to create a latex document and a html document from the 
same source.
My problem is with math equations in latex : what should I type in 
txt2tags in order to obtain, for example, $\frac{1}{2}$ in the latex 
output, instead of \$\backslash frac\{1 ... ?
Thanks
&lt;/pre&gt;</description>
    <dc:creator>Fabrice Lallemand</dc:creator>
    <dc:date>2012-11-20T10:39:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/365">
    <title>Latex equations</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/365</link>
    <description>&lt;pre&gt;Hello !

I'm new to txt2tags.
I would like to create a latex document and a html document from the 
same source.
My problem is with math equations in latex : what should I type in 
txt2tags in order to obtain, for example, $\frac{1}{2}$ in the latex 
output, instead of \$\backslash frac\{1 ... ?
Thanks
&lt;/pre&gt;</description>
    <dc:creator>Fabrice Lallemand</dc:creator>
    <dc:date>2012-11-20T10:39:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/363">
    <title>some scammers made a fake txt2tags book</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/363</link>
    <description>&lt;pre&gt;I've just discovered this "book":

http://www.barnesandnoble.com/w/txt2tags-lambert-m-surhone/1026253107

It's very expensive ($45) for a meaningless collection of articles retrieved from wikipedia. I don't understand why Barnes and Noble (and others such as Amazon) allow this compagny to sell such things on their store. It's not a good advertisement for their business.

More about this:
https://en.wikipedia.org/wiki/VDM_Publishing
https://en.wikipedia.org/wiki/User:PrimeHunter/Alphascript_Publishing_sells_free_articles_as_expensive_books
http://www.chrisrand.com/blog/index.php/2010/02/27/odd-tale-alphascript-publishing-betascript-publishing/------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_n&lt;/pre&gt;</description>
    <dc:creator>Forgeot Eric</dc:creator>
    <dc:date>2012-11-13T20:54:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/355">
    <title>First post, possibly an odd request..</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/355</link>
    <description>&lt;pre&gt;Hello everyone, first post, and apologies if my question seems a bit
odd. It might need to go to the devs list

I have an old E61 Nokia phone, I can run python 1.4.5 on it. I've
tried in the past to get an older version of txt2tags to run on it. I
never got it to run, from memory I tried to import as many modules as
I could see mentioned.

I almost got it to run in the past but I think the problem is there is
no command line interface. Python script shell 1.4.5 and python for
d60 is installed.

So sorry for the odd request has anyone got an idea how to get the
thing to work? Any guesses?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Nicholas</dc:creator>
    <dc:date>2012-07-30T07:28:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/351">
    <title>convert from html to txt2tags</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/351</link>
    <description>&lt;pre&gt;I often need to convert from HTML to t2t.

There is already https://txt2tags.googlecode.com/svn/trunk/extras/unhtml.vim but the result is not always clean and it's not scriptable.


Pandoc (http://johnmacfarlane.net/pandoc/) can also convert from html to several other formats, but I didn't manage to adapt it to txt2tags (it seems complicated to compile so I didn't go furthen than a simple installation)


But I've just discovered this handy piece of software:

http://search.cpan.org/dist/HTML-WikiConverter/

It converts from html to some wiki formats, such as dokuwiki or mediawiki. The good new is it's very easy to adapt to new syntax. For example part of the definition file is like this:

b =&amp;gt; { start =&amp;gt; '**', end =&amp;gt; '**' },
    strong =&amp;gt; { alias =&amp;gt; 'b' },
    i =&amp;gt; { start =&amp;gt; '//', end =&amp;gt; '//' },
    em =&amp;gt; { alias =&amp;gt; 'i' },
    u =&amp;gt; { start =&amp;gt; '__', end =&amp;gt; '__' },


I've create a txt2tags export: https://textallion.googlecode.com/hg/contrib/HTML-WikiConverter-Txt2tags/lib/HTML/WikiConverter/Txt2t&lt;/pre&gt;</description>
    <dc:creator>Forgeot Eric</dc:creator>
    <dc:date>2012-07-25T12:24:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/348">
    <title>Image scaling - LaTeX target</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/348</link>
    <description>&lt;pre&gt;I am attempting to scale an image by prefixing the file name with the 
appropriate scalefactor.

My images are stored in a directory called 'Images' and so the following 
%!postproc works for a LaTeX target, with a only a single image, but 
fails for multiple images on the same input line:

%!postproc(tex): '\{(.*)Images' '[width=\1\\textwidth]{Images'

No doubt my regular expression syntax/understanding is wrong.

(1) How can I make this work?
(2) Is there a more general regex?    In my case all I need to match is  
{#    of the LaTeX \includegraphics{#filename} where #=scalefactor 
number, and substitute      [width=#\textwidth]{

Thanks,

Steve.

e.g.

txt2tags input file -----------------------------------------------

Title
author
%%date(%c)
%!postproc(tex): '\{(.*)Images' '[width=\1\\textwidth]{Images'

=This works=
The following image scales by 0.5\textwidth in the LaTeX target
[0.5Images/txt2tagslogo.png]


=This fails=
[0.5Images/txt2tagslogo.png] two images [0.5Images/txt2tagslogo.png]


txt2tags t&lt;/pre&gt;</description>
    <dc:creator>Stephen Gibson</dc:creator>
    <dc:date>2012-06-29T05:00:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/347">
    <title>vim highlighting</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/347</link>
    <description>&lt;pre&gt;Thanks, for supplying the vim syntax highlight file. IMO the 
highlighting would be better if it looked more like the LaTeX theme:

(1) Highlight includes the tags
(2) Font colour coded rather than background colour

I don't know how to fix (1).
(2) can be changed with (I use vim in a console):

hi default t2tItalic      term=italic      ctermfg=blue cterm=none      
gui=italic

hi default link t2tTitle         String

However, I have insufficient knowledge to proceed further.
Has anyone hacked a better txt2tags.vim file?

Sorry, this is not really a txt2tags question.

Steve.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Stephen Gibson</dc:creator>
    <dc:date>2012-06-27T02:12:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/345">
    <title>postvoodoo example</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/345</link>
    <description>&lt;pre&gt;Hi,
       Are there any examples of the use of postvoodoo? All my efforts 
to use this command have been futile.

e.g. the following voodoo to increase the LaTeX item indent does nothing.

Steve.
txt2tags version 2.6.967

Title
author
%%date(%c)
%!postvoodoo: 'sed 
s/\\begin{compactitem}/\\begin{compactitem}\\setlength{\\itemindent}{50pt}/'


=This is a test=
  - An item
  - another
  - final


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Stephen Gibson</dc:creator>
    <dc:date>2012-06-22T05:44:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/344">
    <title>article and discussion on txt2tags at Tech Republic</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/344</link>
    <description>&lt;pre&gt;As per subject, enjoy, and please contribute to the discussion there:

http://www.techrepublic.com/blog/opensource/txt2tags-a-great-lightweight-markup-language-for-many-tasks/3674?tag=mantle_skin;content

Marco F.
http://stop.zona-m.net (written with txt2tags!)

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>M. Fioretti</dc:creator>
    <dc:date>2012-06-18T17:28:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/343">
    <title>Some preproc Help Needed</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/343</link>
    <description>&lt;pre&gt;Hey guys, it's me again.

I was creating a "config" file to be used in all the documents in a
project and one thing I wanted to do was "auto-anchor" titles.

I have titles like so:
= An Awesome Heading =

and I have the following preproc so far:
%%!preproc: '^=+(.*?)=+$' '\g&amp;lt;0&amp;gt;[\1]'

This gets me this far:
= An Awesome Heading =[ An Awesome Heading ]

I can easily modify the regex to remove the outside spaces:
= An Awesome Heading =[An Awesome Heading]

but that doesn't quite cover it.  Is there a way to strip spaces (and
other bad characters) from a section of a line.  I have considered
brute-forcing it but that isn't pretty and can only handle a set amount
of words.
%!preproc: '^=+\s*(\S*?)\s*(\S*?)\s*(\S*?)\s*(\S*?)\s*=+$' '\g&amp;lt;0&amp;gt;[\1\2\3\4]'

This last one works but is super ugly.  Does anyone have and suggestions?

Thanks, Kevin

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and &lt;/pre&gt;</description>
    <dc:creator>Kevin</dc:creator>
    <dc:date>2012-05-28T22:36:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/334">
    <title>Custom Sections</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/334</link>
    <description>&lt;pre&gt;Hello,

I was thinking about switching some documents to t2t after finding some
limitations in other plain-text mark-up languages.

The biggest thing that I would like to see is some sort of named
sections.  For example if I want to put a warning or sidenote it would
be nice to have it delimited by a colored box or other thing.  I noticed
that a lot of output formats support some time of section or division
that can be styled.

If I want to limit my docs to html I can simply use: ''&amp;lt;div
class="warning"&amp;gt;'' and ''&amp;lt;/div&amp;gt;'' but then I can only get html output
(and AFAIK there are no conditional macros).

I think that this is a common feature and it would be nice to have some
syntax for it.  My first thoughts are "{{class text}}" for inline and
"{{{class line" for one line and "{{{class" closed with "}}}" for
multi-line.  I chose braces because they have different opening and
closing allowing nesting and I tried to match your syntax for quoted and
non-parsed areas.  Also the name-space combination matches links.
&lt;/pre&gt;</description>
    <dc:creator>Kevin</dc:creator>
    <dc:date>2012-05-25T23:40:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/329">
    <title>2.7 release (was: I NEED YOUR OPINION: Website and docs)</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/329</link>
    <description>&lt;pre&gt;
Thanks for the reminder Florent.

Txt2tags deserves a hard work week(s?) to prepare the multitude of
changes for a release. There's so many news that it's even hard to
choose where to start. This time, I can't do it alone.

I need help.

1) The test suite is broken —  (cd test ; ./run.py). It needs to be
fixed and all tests should pass OK. It the problem is the test, such
as it's OK-template is not updated, just fix the template. If the
problem is the wrong txt2tags behavior, fix txt2tags.

2) Changelog — We need to track changes since r382. Here's a good link
to start: http://code.google.com/p/txt2tags/source/list?num=25&amp;amp;start=406
Any effort to summarize the changes or at least highlight the
important ones will be appreciated. Things such as new targets, new
marks, new options, new rules are the most important.

3) Code isolation — Ideally all the new features added to txt2tags
since v2.6 should be, were possible, isolated in it's own class or
function. It will make it easy to modularize the code in &lt;/pre&gt;</description>
    <dc:creator>Aurelio Jargas</dc:creator>
    <dc:date>2012-05-17T14:32:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/325">
    <title>etherpad-lite / nested: some external tools with sometxt2tags in it.</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/325</link>
    <description>&lt;pre&gt;1/ Etherpad-lite
Maybe you already are aware of Etherpad. Now there is Etherpad-lite, which only needs a simpler php/apache installation. 

https://github.com/Pita/etherpad-lite

Etherpad-lite is __almost txt2tags ready__, there is a dokuwiki export which is close to txt2tags syntax. If you intend to export to txt2tags, just use those modifications on  etherpad-lite/node/utils/ExportDokuWiki.js :

68c68
&amp;lt;   var tags = ['======', '=====', '**', '//', '__', 'del&amp;gt;'];
---
255c255
&amp;lt;       pieces.push(new Array(line.listLevel + 1).join('  ') + '* ');
---


You can also change etherpad-lite/static/pad.html and call to &amp;lt;a id="exportdokuwikia" target="_blank" class="exportlink"&amp;gt;&amp;lt;div class="exporttype" id="exportdokuwiki"&amp;gt;Txt2tags text&amp;lt;/div&amp;gt;&amp;lt;/a&amp;gt;

The only drawback is that the exported file will be named with the .dokuwiki extension.  



2/Nested:
I've just discovered this text editor dedicated to txt2tags documents: http://nestededitor.sourceforge.net/-------------------------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Forgeot Eric</dc:creator>
    <dc:date>2012-04-16T22:25:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.txt2tags/323">
    <title>I NEED YOUR OPINION: Website and docs</title>
    <link>http://comments.gmane.org/gmane.text.txt2tags/323</link>
    <description>&lt;pre&gt;Hi folks,

I want to rethink the txt2tags website and docs. I want them to be
open to contributions, always updated, easy to find and read.

It's 2012 and we're still using the same static documents for the
website, manual page, user guide, quick reference, etc etc etc.

Maybe there's a better way?

Help us find! http://code.google.com/p/txt2tags/issues/detail?id=133


&lt;/pre&gt;</description>
    <dc:creator>Aurelio Jargas</dc:creator>
    <dc:date>2011-12-21T23:55:56</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.txt2tags">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.txt2tags</link>
  </textinput>
</rdf:RDF>
