> 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
---------------------------
> 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
---------
underlay, and the underlays lack translation to a given language.
--[[Joey]]
-recentchanges links to po files
--------------------------------
-
-When a po file is changed, the recentchanges page shows a link such as
-"sandbox.es". But, clicking on it goes to the English (or negotiated
-language) version of the page. It would be better in this one case if
-the link went direct to the translated version of the page. --[[Joey]]
-
-> The (untested) commit 496e8523c670 in my po branch might fix this...
-> or at least, I believe, put someone on the right track.
-> --[[intrigeri]]
-
Double commits of po files
--------------------------