[PLUGIN] Texy

Texy is a competition to Textile. But it’s much much much much better. The only disadvantage is a fact, that it is poorly documented in English (heavily in Czech).

The only english page: http://www.texy.info/en/
Czech page: http://www.texy.info/cz/

CHECK THIS: http://www.texy.info/cz/syntax - it’s in czech, but you’ll get what’s going on.

Installation is the same as textile plugin. Put the plugin.texy.tpl to the Manager, asociate the plugin with OnWebPagePrerender and use <texy> </texy> elements.

Next thing is, that Texy can be ***HEAVILY*** configured. Support of tables, UTF8 and so on.... There are at least 10 plug-ins to Texy. In this version, no extra settings are done, the translation method is called "as is". You might want to have a look at: http://www.texy.info/cz/implementation to see just the methods names.

There is also an experimental XML-RPC implementation: http://www.texy.info/cz/xmlrpc (in ENGLISH)

I would like to get rid of those elements. Can someone please tell me how do I get Texy to the list of editors, next to FCKEd? THX.

I’ll check it out...

As a long time Textpattern user I have been a long student of Textile and familiar with Markdown.
You claim Texy is much better : in what way ?

As for getting Texy in the list of editor, that’s not the way it works (though it could be cool the way you describe it) : If Texy is similar to Textile or Markdown, it’s a syntax not an editor... the way the MODx Textile plugin allows for Textile use is wrap your content with <textile> .... </textile> tags. I’ll let Jeff get into the detail about Textile and Markdown plugins for MODx, WYSIWYG editor and so on...

Texy looks very cool... thanks!

At texy.info website, there are several examples of why Texy is better than Textile or Markdown. The basic principle is a fact, that Texy does not use a bunch of regural expressions to get the work done. It there is an algorithm/expression, that produce good results, but fails in some rare cases, it will be not used in Texy. The author describes some examples:

Textile: *well _formed* text_
Markdown: _well **formed_ text**

In both cases, the interprets won’t create a well-formed output (author claims).

This will fail in Textile, according to it’s rules: _(this *will* fail in)Textile_ Reason - asterixes in a modifier

Many cool mini-features.

- For example, in Czech language, there is a rule about when two words can be separated in line-break. For example if a word "nice" is on the end of the line and "bedroom" on the begining of the next one, it will remain "nice bedroom" in the output. But if we have words like for, in, to and so on before subject, we should not break them. So "for Tom" will become "for&nbsp;Tom".

- If you use character "-" in text (minus), it will be converted to typogrphically appropriate one (a dash afaik, a little bit longer line)

- (C), (R) will become C and R in a circle

- automatically repairs typograpical misuse of quotes (moves them down by the beginning of the word and up by the end in stead of "this")

These are my favourites =).

Ok thanks tillda, I’ll have a harder look at it, it seems I have not done my homework... I’ll try out your plugin and try to get familiar with Texty

davidm: No problem here, I created the plugin only for the reason that I’m familiar with it, while not with Textile/Markdown =).

tillda
thanks for your plugin
I was about to write my own for Texy, when I found that someone has already done it, thanks!