From: Joey Hess <joey@gnu.kitenet.net>
Date: Thu, 27 Aug 2009 17:10:31 +0000 (-0400)
Subject: followups
X-Git-Tag: 3.1415926~50
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=5e515b493c00c70095aeb8bad1e0b7757ed943db;p=ikiwiki.git

followups
---

diff --git a/doc/plugins/po.mdwn b/doc/plugins/po.mdwn
index 2e32d78fd..65573b877 100644
--- a/doc/plugins/po.mdwn
+++ b/doc/plugins/po.mdwn
@@ -294,6 +294,12 @@ that po might be replacing the only link on a page, in error?
 > be either good (better overall l10n) or bad (break the other
 > plugin's goal). --[[intrigeri]]
 
+>> Right.. well, the cases where links are added is very small.
+>> Grepping for `add_link`, it's just done by link, camelcase, meta, and
+>> tag. All of these are supposed to work just link regular links
+>> so I'd think that is ok. We could probably remove the currently scary
+>> comment about only wanting to change the first link. --[[Joey]] 
+
 Name of toplevel index page
 ---------------------------
 
@@ -305,6 +311,14 @@ like "index.da". --[[Joey]]
 > test with a predicate call such as isindexpage($page). Such a predicate
 > function could then be overriden by the po plugin. --[[intrigeri]]
 
+>> Could do that, but if you have such a function it's natural to want to
+>> use it elsewhere. Not clear to me it would make sense for po to override
+>> such a function if it were used in some of the other places that compare
+>> to index.
+>> 
+>> The other option would be for po to override the template setting.
+>> --[[Joey]] 
+
 Pagespecs
 ---------