word use, equivalent is better.

[ikiwiki.git] / doc / todo / Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn

diff --git a/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn b/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn
index 7adcb5c098c853c157f8a069d14a760491778d52..aa96fc4315d9b6cf9e32b07ca41348396576d14a 100644 (file)
--- a/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn
+++ b/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn
@@ -9,10 +9,25 @@ Right now it changes rendering so that undefined pages (previous errors) are res
 
 The page is rST-parsed once in 'scan' and once in 'htmlize' (the first to generate backlinks). Can the parse output be safely reused?
 
+> The page content fed to htmlize may be different than that fed to scan,
+> as directives can change the content. If you cached the input and output
+> at scan time, you could reuse the cached data at htmlize time for inputs
+> that are the same -- but that could be a very big cache! --[[Joey]] 
+
 Desing issues in general:
 
 We resolve rST links without definition, we don't help resolving defined relative links, so we don't support specifying link name and target separately.
 
+> I found out this is possible by using rST subsitutions. So to do [[Version history...|releases]]
+> you would use:
+> 
+> `|releases|_`  
+> `.. |releases| replace:: Version history...`  
+> Which does not seem to have an inline equivalent. Using non-resolved links there is the alternative:
+>
+> ``Version history <releases/>`_`. --ulrik [kaizer.se]
+
+
 Many other issues with rST are of course unresolved, but some might be solved by implementing custom rST directives (which is a supported extension mechanism).
 
 Patch follows: