> # B/I/S/U versus STRONG/EM/DEL/, there is a strong reason to change?

well, if you consider the users of screen readers, i think there is. b/i/s/u are strictly presentational elements, while the others are structure elements.

Markdown ? what means? .t2t is very good, so for fun and power ,i suggest: thought2tags things2tags thin2tags t2t=just make easy for publish idea with tags doc Sayeahoo?

i think that the new latex-beamer target is a nice thing.

to improve it, i suggest to include multiple styles. something like: %!style: blue, wolverine, dark-green

it's quite useful to work with the themes provided by latex-beamer, since it has a color theme, a font theme and inner/outer theme. :)

btw, txt2tags is an amazing name!

I wouldn't change the name either. Love it, as it is. Btw, still I prounounce it "text to tags"

Hi! I welcome the footnote feature! I would also like to see some sort of bibliography support! User could declare a .bib file, and when she wants to cite a reference, she'd say something like:

All your base are belong to us [someone2001].

Here, someone2001 should be a valid key in the provided .bib file.

I would also like an easy way to escape txt2tags parsing, to allow for inline inclusion of specific markup code. Let's suppose for now that the (()) characters do this, right? One might say:

And then some scientist came up with a very complicated formula: ((-tex-specific-complicated-formula-markup)).

This of course would be specific to one target, but the user will already be aware of that.

Thank you for txt2tags, Aurelio! I use it every day!

I would love seeing admonitions in Txt2tags. Juste like AsciiDoc? and restructured text.

I would also like to see new tag like :

align center : ">>> my text <<<<" align right : ">>> my text >>>"

Image legend would be cool as well.

I think that a "wiki" style output could be nice.

And also some tools to convert from output formats to txt2tags, but this is a lot of work :)

Thanks for txt2tags.

Python 3?

Zoom.Quiet: 'markdown' is the opposite of 'markup', and (as a native English speaker) I agree it's a killer name. One of the UNIX inventors was asked many years later if there was anything he would do differently if he could go back in time to write UNIX again. He said would have added an 'e' at the end of the system function 'creat'.

'text2tags'

Thanks to Aurelio!

@elias: b/i/s/u are in fact presentational elements in txt2tags, not semantical, so we're fine.

@vecchi.b: Inline inclusion of specific markup code is already added to the development code, with the ''tagged'' mark. Example: First line.''<br>''Second line.

@otrocorreoinutil: Sorry, I didn't understood what you meat with "wiki style output". You weren't talking about the current wiki targets (Google Code, Wikipedia, MoinMoin?, DokuWiki?)?

@william.dowling: Python version 3 is incompabile with older versions. At some point in time we'll have to move to it. For years I think about adding the missing 'e' to the program name. This creat quote is a strong incentive, thanks! :)

about the $HOME/txt2tags, I think it's the greatest idea ever!

but I would make it a hidden directory, cause I don't feel comfortable with config files showing up on my $HOME. also, there are people who use their Desktop folder as $HOME, so I think it's not just me who would prefer that way. it could be configurable, at least, what do you think?

> Mark table columns to make it easy to style them <td class="col1"> or use colgroup

I would prefer the class approach instead of the colgroup, since it also makes it easier to get the elements with JS.

oh, I would love a plugin interface!! :) some way to add my own marks, allowing to easily code the processing of it... it would be just fantastically marvelous to have txt2tags extensible that way!

the latex-beamer, for example, could be implemented as a plugin, and could be mantained by someone else, taking the burden out of the main mantainer.

this would be simply perfect!

It might be nice to provide a syntax specifically for wiki-style links, since that's a common application. It can be translated directly into wiki targets, and labelled with a comment or null command in non-wiki targets (eg LaTeX, html) to allow easy manipulation with postproc. Obvious suggestion is double square-brackets:

[[pagename]]
[[page name with spaces]]

Might also be good to fix and document the API, so txt2tags can be an easy choice to call/embed in python applications needing markup.

Footnotes would be excellent, since they're common in some of the writing styles txt2tags is well suited to (technical documentation, reports, essays, and so on).

I think I'd prefer not to have built-in %!exec ability. There are plenty of safe and convenient ways to do machine-generated content already: better to have external programs generate the input files and/or call txt2tags than vice versa.

Idea from Leonardo Rosa:

Use a default target (such as TXT or HTML) if none is specified by the user (instead of showing an error message)

clean the code. I love the project but it's pretty hackish and quite difficult to reuse in other applications.

I think the ideal for me would be to replicate as many standard latex environments as possible. I'm forced to drop into latex every time I want to cite, footnote, or use a glossary. Even cooler would be equation support, which switches to mathml, or latex automtically. Support for a verse environment, which I believe will be part of html5, would be nice, as would support for more semantic HTML tags like acronym.

+1 on plugin support, which would allow me to scratch my own itch. Something like a baseclass for a given syntax which can be modified to add new markup syntax, taking advantage of the special case of double characters on either side, bit having a more fundamental version which is as flexible as any python regex.

@griff.rees: I completely agree that the code needs a clean up. I'll try to make it better for v3.

@aureliojargas less is more!

• for name short is best them long;
• for function realy strong support better then too more function but not stable;

- don't support more target(like Lout/PageMaker is usage less?!)
- make realy div covered HTML export,,, so CSS can realy made t2t export realy good,,because export HTML is thoe most in common use t2t!
- make more support for pop wiki engine (moinMoin/DokuWiki/Wikipedia) so t2t can usage middle doc for multi wiki !!!

As previously suggested, image labeling would be great. Maybe something like:

[image1.jpg]
^^Figure: some figure of me^^

I don't know if that markup collapses with some other planned feature; i thought it would be intuitive for a table/image label since it seems to point up at the object being referred to.

I would like :

• docbook support (because a docbook document could be converted to odf, rtf... and many others not directly supported by text2tags)
• table and image labeling ("|=" or "|+"
• make anchor works every where (actually, just for titles)
• make colspan works for latex (\multicolumn{\a}{text})
• with preproc or postproc, \n is not matching, but it would be nice...

Example ("|+" is a numbered title table, "|=" is a non numbered title table) :

|| A | B | C 
| C | D | E 
|+ numbered title (and end of the table)

I would like to have a direct way to override specific target tags and/or rules - the current way, by either using "%!postproc" or editing txt2tags source, is unnecessarily tortuous. Tags and rules are nothing but named entries in one hash or another - implementing "%!override" which assigns a new value to a name would cost a dozen lines at most, and make customizing the output many times easier.

I would like to convert things from some markup back to text2tags format. That would really be a nice feature, though I guess it requires a lot of work.

However this is a very useful program. Thanks for it!

hello,

here are some suggestions and comments:

- About: $HOME/txt2tags

if possible, it should follow the freedesktop specifications which recommend to use the $(XDG_CONFIG_HOME) variable to store the configuration files (often into $HOME/.config/): http://freedesktop.org/wiki/Software/xdg-user-dirs

- About a new name, I like txt2tags but it's not really easy to pronunce or write (so many "t"s). Markdown is a "better" name, but if we can't find a better name for txt2tags it's probably better to stick with it.

- I'd like to see also a wiki or a forum where users could brainstorm and present theirs txt2tags configurations and tricks. For example I've made those lines for being able to add links to wikipedia:

%!preproc: '\[\[:([^ ].*?):([^ ].*?)\|([^ ].*?)\]\]' '\3[* http://\1.wikipedia.org/wiki/\2]'
%!preproc: '\[\[:([^ ].*?):([^ ].*?)\]\]' '\2[* http://\1.wikipedia.org/wiki/\2]'
%!preproc: '\[\[([^ ].*?)\]\]' '\1[* http://fr.wikipedia.org/wiki/\1]'

So [Borodine?] will link to the default French wikipedia page about Borodine, [[:fr:Edmond_Dulac?|Edmond Dulac]] will link to the French wikipedia page about Dulac (I have to explicitly specify :fr: here, otherwise the syntax will mix up, while [[:en:Lukas_Kandl?|Lukáš Kándl]] will lead to the English page about Lukáš Kándl. I had to :en:Lukas_Kandl? because txt2tags couldn't handle unicode names in links.

- Even if python is great, a php module which could handle the basic syntax of txt2tags (not the pre/processors macros of course but just the markup) could help the widespead of txt2tags. There are such modules for using the Markdown syntax into CMS or wiki: http://code.suckless.org/hg/genosite/ http://www.ohloh.net/tags/markdown/wiki

I'd like to be able to write directly txt2tags syntax into an online wiki or blog, and publish it into html. Most web hosters don't provide python but only php.

And I generally don't like to use the other wiki syntaxes at all (mediawiki, markdown), especially when I find the txt2tags syntax so clear and efficient.

- In addition, a markdown filter would be useful.

If the txt2tags code were more modular, we could propose such new syntax as an external module first, and then it could be included into the txt2tags core later.

- For example the txt2tags source code could be split into several modules:

- core syntax for html (the markup), this part could be converted into php for inclusion into other project - the basic html exports (meta tags, css, and code such as encoding="utf-8" etc) - the exportable part for latex, lout, mediawiki etc - the preproc / postproc and macro features - some use defined modules and plugins

- I fully agree with wjaguar.wj, Jan 17, 2009 ("a direct way to override specific target tags and/or rules")

- Add more control for using txt2tags with dynamic websites. For example using php include and such. We still can make our own rules, but it's less portable among users, for example I'm using:

%!postproc:  '@@include"([^ ].*?)"'  '<?\n   include("\1")\n ?>'

so the inclusion is made with @@include"myphppage.php" but other people may use something else.

- Correction of the \n in pre/postproc as proposed by dhajage, Jan 16, 2009

- Use strict html syntax. Use lower case html markup, I'd like that too. And most of the other proposals make sense too.

- I'd like to make or have a syntax highlight for the Geany software. A really cool feature is it can use a browser for listing CSS or C classes and such, and for txt2tags it could list the headers in the left panel, helping to create very long documents. ( example http://www.geany.org/images/geany_main.png? )

It seems it supports ctags / scintilla parser but I don't know anything about this. I've tried to adapt an already existing parser (restructured text and css), but it's difficult and doesn't work well.

(or another graphical editor supporting such a feature could be so great to edit long txt2tags texts, but geany is multiplateform, there is even a mac version on http://geany.darwinports.com/)

Good luck with programming all this!

ps: I don't like google wiki syntax as well!! Everything is mixed up. And why can't we just edit our comments instead of deleting and copying it again with the modifications?

Hi! First of all, thanks for the great app! For me personally there are just a few things needed in order for txt2tags to become the best lightweight markup language that can easily replace AbiWord?:

-better support for paragraph styling. Center/right/left alighnment, first-line indent (for example, by adding a line in the settings section that would start every paragraph with a tab). -footnotes support. Really need to do references in my academic papers -rtf/doc/odt support for export. Would be really great to have at least RTF.

BTW, are there any plans for the 3.0 release date? At least estimated, of course I understand that I am likely to get a "when it's ready" answer here, but anyways.

The answer I wanted to the release date is "it should already be done and released", but unfortunately, what I got now is "I have no idea, since there's still so much to do :("

I think it would be a good idea to drop some common txt2tags pitfalls such as requiring two blank lines after a list, but then again I don't know how many changes in the code that would require.

I would suggest some other or additional marking for verbatim areas. '`' is not so easy to distinguish by the human eye in some fonts and also using the same tag for opening and closing a block might not be so easy to convert to other markup tags. Something like '' and '' in MoinWiki? is allowing unambiguous marking of inside and outside of a verbatim block.

oops, didn't think about this wiki to have markup ;-) I meant, instead of

```

for opening and closing verbatim blocks, one should use the {{{ and }}} markups.

+1 on the "add your own markup" options.

+1 on the two blank lines after a list.