Discussion:
[t2t] Interpreted marks in title tags and named links
Galen Menzel
2013-04-04 18:39:58 UTC
Permalink
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{(.*?)}" <\1>

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
Aurelio Jargas
2013-04-04 19:58:51 UTC
Permalink
Hi Galen,

I'm sorry this makes you sad, but it's a design decision made to keep the
program simple.

Postproc filters are the way to do it, as you already did. Maybe you could
simplify your customized mark to just {{i}} or even {i}?
Post by Galen Menzel
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{(.*?)}" <\1>
== 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
--
Aurelio | www.aurelio.net | @oreio
Galen Menzel
2013-04-04 20:31:28 UTC
Permalink
Post by Aurelio Jargas
Hi Galen,
I'm sorry this makes you sad, but it's a design decision made to keep the
program simple.
Postproc filters are the way to do it, as you already did. Maybe you could
simplify your customized mark to just {{i}} or even {i}?
Well, my main source of sadness here is that as soon as we start putting in
specific ways to generate a backend tag (<\1> in this case), we lose the
backend-independence that is one of the main selling points of txt2tags.

Though maybe it's just that my expectations are off. What's the feeling of
the t2t community? Are nontrivial t2t documents generally created with a
specific back-end in mind?

galen
Post by Aurelio Jargas
Post by Galen Menzel
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{(.*?)}" <\1>
== 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.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
txt2tags-list mailing list
https://lists.sourceforge.net/lists/listinfo/txt2tags-list
Loading...