doc/po: follow-up

[ikiwiki.git] / doc / plugins / po.mdwn

diff --git a/doc/plugins/po.mdwn b/doc/plugins/po.mdwn
index 2e32d78fd60843e1ad3ec1fbf06da81e0f2c4b77..1d343e0f81b642783af498fbadcdecf73025a5a2 100644 (file)
--- a/doc/plugins/po.mdwn
+++ b/doc/plugins/po.mdwn
@@ -294,6 +294,14 @@ 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]] 
+
+>>> Commit 3c2bffe21b91684 in my po branch does this. --[[intrigeri]]
+
 Name of toplevel index page
 ---------------------------
 
@@ -305,6 +313,16 @@ 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]] 
+
+>>> Great idea. Commit 6c0f9c691c3df3a in my po branch does it. --[[intrigeri]]
+
 Pagespecs
 ---------