-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I guess this needs a second api call? The rewrite
branch uses it.
Yes - but not only! It does a lot more since it matches the wiki
text (and the headings there) with the 'anchors' (and others) given
from api call. Additionally it determines the byteoffset within the
wiki text, instead of the byteoffset given by 'parse' with is given
relative to the parsed text (which is quite useless in my opinion ;)
But since the wiki text can also contain wrong syntax or some
notorious examples, it is possible for the function not to resolve.
(In fact this is true for a lot of functions within framework, e.g.
if the network connection is down or else...)
btw I found your isRedirect() method. Since this api
call is not
sure and gives false possitives I prefer checking the text itself.
Sometimes the database contains invalid redirect flags.
Thanks for this hint - never had problems with this, but - I have to
consider that!
Greetings
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk5jexcACgkQAXWvBxzBrDCqgQCeNs0H/GT6Y2QFoAR0b+np0IIZ
N4kAoIZZ9m08mhtevw1+v0zA4PiWgcZQ
=zU7E
-----END PGP SIGNATURE-----