-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Org to mediawiki: File links with colons #2713
Comments
I currently maintain the org reader, sorry for not getting back to you earlier. This is an instance of the general impedance mismatch between markup languages. Mediawiki allows a nice way to write and distinguish between external and wiki links. This isn't the case in markup languages designed for more general (i.e. non-wiki) use. Gitit/Pandoc use the convention of empty links |
I'm unsure how the org reader should behave here. I see two solutions: 1. allow However, there is another issue here: using the MediaWiki reader and writer, |
MediaWiki wikis frequently have pages with names like `User:John` which were interpreted as URIs, thus turning internal links into global links. This is prevented by also checking whether the scheme of a URI is frequently used (i.e. is IANA registered or an otherwise well-known scheme). Fixes: jgm#2713
API change: the function `isURI`, testing if a string is a valid URI with a known scheme, is exported from the Shared module, as is the set of known `schemes`. The new function replaces the function of the same name from *Network.URI*, as the latter did not check whether a scheme is well-known. E.g. MediaWiki wikis frequently feature pages with names like `User:John`. These links were interpreted as URIs, thus turning internal links into global links. This is prevented by also checking whether the scheme of a URI is frequently used (i.e. is IANA registered or an otherwise well-known scheme). Fixes: jgm#2713
API change: the function `isURI`, testing if a string is a valid URI with a known scheme, is exported from the Shared module, as is the set of known `schemes`. The new function replaces the function of the same name from *Network.URI*, as the latter did not check whether a scheme is well-known. E.g. MediaWiki wikis frequently feature pages with names like `User:John`. These links were interpreted as URIs, thus turning internal links into global links. This is prevented by also checking whether the scheme of a URI is frequently used (i.e. is IANA registered or an otherwise well-known scheme). Fixes: jgm#2713
API change: the function `isURI`, testing if a string is a valid URI with a known scheme, is exported from the Shared module, as is the set of known `schemes`. The new function replaces the function of the same name from *Network.URI*, as the latter did not check whether a scheme is well-known. E.g. MediaWiki wikis frequently feature pages with names like `User:John`. These links were interpreted as URIs, thus turning internal links into global links. This is prevented by also checking whether the scheme of a URI is frequently used (i.e. is IANA registered or an otherwise well-known scheme). Fixes: jgm#2713
In Org, if I have this:
Then it becomes this after being converted to mediawiki:
[User:Me/about About]
It should have become:
The "User:Me" example is used because that is the common practice for user pages in mediawiki.
The text was updated successfully, but these errors were encountered: