Comment 1 by MHameed on 2013-03-01 18:26
another possibility is to add a macro which only applies to the first line.
%title{this is the title text}

and to apply the two macros to global.t2tconf.

Seems to work around the issue here.
Thoughts?

Attachment 3031-1.patch added by MHameed on 2013-03-01 18:28
Description:

Comment 2 by jteh on 2013-03-02 12:33
That was another option I considered, but my concern is that this requires every translation to be changed accordingly, which is irritating. Btw, I think this can be done with just one filter.

Comment 3 by jteh on 2013-03-11 01:54
For now, I've downgraded txt2tags on the build server, as we don't have this problem with 2.5. We should still address this, though I'd like to get it fixed in txt2tags if possible.
Changes:
Milestone changed from 2013.1 to 2013.2

Comment 4 by jteh on 2013-06-26 03:01
Changes:
Milestone changed from 2013.2 to None

It seems we are still at txt2tags 2.6. I assume it is still not possible to upgrade due to this issue?

CC @jcsteh

Correct.

P4 because we're coping just fine with things as is and txt2tags is rarely updated.

what about, yes I know I'm bad, sending the whole thing through python converting the first h2 it to h1 after postproc?

Hi,

Coming back to this...

This is going to be an important showstopper for compiling Python 3 version of NVDA from source, as txt2tags throws all sorts of errors (exception syntax, print statement, etc.). There is an experimental branch for supporting Python 3, but hopefully it is something that should be addressed via a stable release, including the original issue raised here.

Thanks.

May be a very rigorous idea, but couldn't we convert the whole thing to markdown while at it?

I think we should consider closing this in favour of #8734, as the overall consensus seems to be that markdown is the future proof way to go.

hello
Recommended pandoc-action-example automatic conversion action
Hope this tool can be helpful for the next document conversion
thanks

For now still txt2tags will still be sued, it is adapted to python 3. Thus, I would not close this issue for now.

This is fixed as of NVDA alpha-2789Z42dbabcc (2023.2.0.27892). Closing as works for me.

This is not fixed as such - we're just using older version of txt2tags where this bug does not exist. When / if we would decide to upgrade t2t this would still be a problem or at least we would need to look out for it.

Ah thanks for pointing this out, I am reopening this one so we can track the proggress here.