summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-08-27 13:10:31 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-08-27 13:10:31 -0400
commit5e515b493c00c70095aeb8bad1e0b7757ed943db (patch)
treee507e4d5cc4c6d67392cf35c509371d3f198e01f /doc
parente1acb707db3f204708f88648ed80762689a15425 (diff)
followups
Diffstat (limited to 'doc')
-rw-r--r--doc/plugins/po.mdwn14
1 files changed, 14 insertions, 0 deletions
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
---------