> > Hi Petter! > > I begun a transformer some time ago. His name is "PRAnchorOfSection" > that inherit from "PRNodeTransformer". > For now this transformer is not enable because we need to check some > problems. >
Yeah, I started studying this. > For example this works bad if we put a link inside the title. Maybe combination of using ==PRHeader text== (instead of ==PRHeader children first text== which doesn't work when there's formatting involved... like ! ==PRTransformer==) and then id filtering could solve this? It will be messy, but not if we also give user the ability to specify anchors explicitly... see further down. But I see a different problem which I don't think can be solved with generic Transformer... And that is that in HTML it is customary to place anchor ABOVE or before the target, so when you click on a link it it will show also the name of the chapter, so the user knows where he is. While in LaTeX it's usually placed underneath. So this would require having an extra HTML-only specific transformer (or something) that would swap them. Or what do > we do if we have two times the same title? As "Introduction"? > Well ideally user would still be able to specify an explicit anchor, in which case the default one is not generated. So by default it can append a number or something, but user could override it. I think there's a lot to be learned from Sphinx. Peter
