response

diff --git a/doc/forum/Render_more_than_one_dest_page_from_same_source_page.mdwn b/doc/forum/Render_more_than_one_dest_page_from_same_source_page.mdwn
index 73375938cf547e57e05aaace7c8cbd1dd97b983a..e88c23b075b6f2ad01342db9e4923515e4121db7 100644 (file)
--- a/doc/forum/Render_more_than_one_dest_page_from_same_source_page.mdwn
+++ b/doc/forum/Render_more_than_one_dest_page_from_same_source_page.mdwn
@@ -1,6 +1,17 @@
 Is it possible to render more than one destination page from the same source page?
 That is, same source, slightly different presentation at the other end, needing a different output file.
 
 Is it possible to render more than one destination page from the same source page?
 That is, same source, slightly different presentation at the other end, needing a different output file.
 

+> It's possible to render more than one output _file_ from a given source
+> page. See, for example, the inline plugin's generation of rss files.
+> This is done by calling `will_render()` and using `writefile()` to
+> generate the additional files. Probably in a format hook if you want
+> to generate html files.
+> 
+> It's not possible for one source file to represent multiple wiki pages.
+> There is a 1:1 mapping between source filenames and page names. The
+> difference between wiki pages and output files is that you can use
+> wikilinks to link to wiki pages, etc. --[[Joey]] 
+

 I have two problems that would be solved by being able to do this.
 
 [[!toc startlevel=2]]
 I have two problems that would be solved by being able to do this.
 
 [[!toc startlevel=2]]


@@ -12,6 +23,12 @@ One also wants a foo-print.html page, which uses "page-print.tmpl" rather than "
 
 I want to do this for every page on the site, automatically, so it isn't feasible to do it by hand.
 
 
 I want to do this for every page on the site, automatically, so it isn't feasible to do it by hand.
 

+> Did you know that ikiwiki's `style.css` arranges for pages to display
+> differently when printed out? Things like the Action bar are hidden in
+> printouts (search for `@media print`). So I don't see a reason to need
+> whole files for printing when you can use these style sheet tricks.
+> --[[Joey]] 
+

 ##"en" and "en-us" versions of a page.
 
 My site is in non-US English.  However, I want US-English people to find my site when they search for it when they use US spelling on certain search terms (such as "optimise" versus "optimize").  This requires a (crude) US-English version of the site where the spellings are changed automatically, and the LANG is "en-us" rather than "en".  (No, don't tell me to use keywords; Google ignores keywords and has for a number of years).
 ##"en" and "en-us" versions of a page.
 
 My site is in non-US English.  However, I want US-English people to find my site when they search for it when they use US spelling on certain search terms (such as "optimise" versus "optimize").  This requires a (crude) US-English version of the site where the spellings are changed automatically, and the LANG is "en-us" rather than "en".  (No, don't tell me to use keywords; Google ignores keywords and has for a number of years).


@@ -23,3 +40,6 @@ I can't do this with the "po" plugin, as it considers "en-us" not to be a valid
 But I'm not sure how to achieve the result I need.
 
 -- [[KathrynAndersen]]
 But I'm not sure how to achieve the result I need.
 
 -- [[KathrynAndersen]]

+
+> Sounds like this could be considered a single page that generates two
+> html files, so could be handled per above. --[[Joey]]