pagespec_aliases: future websetup enhancements

[git.ikiwiki.info.git] / doc / todo / po:_rethink_pagespecs.mdwn

diff --git a/doc/todo/po:_rethink_pagespecs.mdwn b/doc/todo/po:_rethink_pagespecs.mdwn
index ada372b0e798419a955dd5e5f0ecdafe4fb54f50..98c7ff655465128427c1b5eedcac2cc0c761743c 100644 (file)
--- a/doc/todo/po:_rethink_pagespecs.mdwn
+++ b/doc/todo/po:_rethink_pagespecs.mdwn
@@ -14,22 +14,27 @@ default when locking pages.) --[[Joey]]
 >> with a specified locaction, as happens whenever a PageSpec is
 >> used on a page, then it should match only `currentlang()`. If it 
 >> is used without a location, as in the setup file, then no such limit.
 >> with a specified locaction, as happens whenever a PageSpec is
 >> used on a page, then it should match only `currentlang()`. If it 
 >> is used without a location, as in the setup file, then no such limit.

->> 
+
+>>> Ok. --[[intrigeri]]
+

 >> Note that
 >> `match_currentlang` currently dies if called w/o a location -- if
 >> it instead was always true w/o a location, this would just mean that
 >> all pagespecs should have `and currentlang()` added to them. How to
 >> implement that? All I can think of doing is wrapping
 >> `pagespec_translate`.
 >> Note that
 >> `match_currentlang` currently dies if called w/o a location -- if
 >> it instead was always true w/o a location, this would just mean that
 >> all pagespecs should have `and currentlang()` added to them. How to
 >> implement that? All I can think of doing is wrapping
 >> `pagespec_translate`.

->>
+
+>>> Seems doable. --[[intrigeri]]
+

 >> The only case I've found where it does make sense to match other
 >> language pages is on `l10n.ikiwiki.info` when listing pages that
 >> need translation.
 >> 
 >> Otherwise, it can be documented, but that's not really enough;
 >> a user who makes a site using auto-blog.setup and enables po will
 >> The only case I've found where it does make sense to match other
 >> language pages is on `l10n.ikiwiki.info` when listing pages that
 >> need translation.
 >> 
 >> Otherwise, it can be documented, but that's not really enough;
 >> a user who makes a site using auto-blog.setup and enables po will

->> get a really scred up blog that lists translations as separate posts
+>> get a really screwed up blog that lists translations as separate posts

 >> and needs significant work to fix. I have thought about making
 >> and needs significant work to fix. I have thought about making

->> `match_currentlang` a stub in IkiWiki, so I can use it in all
->> the PageSpecs in the example blog, but I can't say I love the idea.
+>> `match_currentlang` a stub in IkiWiki (done in my currentlang branch),
+>> so I can use it in all the PageSpecs in the example blog etc, but I
+>> can't say I love the idea.

 >> --[[Joey]] 
 >> --[[Joey]]