turn that into a hyperlink. However, if a translated page contains a
WikiLink to itself, a hyperlink is inserted, at least with the default
`po_link_to` the link points to the English version of the page. Is there a
-good reason for that to be done? --[[Joey]]
+good reason for that to be done? --[[Joey]]
+
+> The commit 0113c69d4fb in my po branch might fix this. --[[intrigeri]]
+
+>> It may fix it in passing, but shouldn't it also be fixed for the other
+>> `po_link_to` styles?
+
+>>> Other `po_link_to` styles already work ok: say there is
+>>> a \[[dest]] link on a page called `dest`. When rendering
+>>> `dest.LL`, `mybestlink` returns `dest.LL`, and `htmllink` is then
+>>> able to detect, and manage correctly, that it is a self-link.
+>>> --[[intrigeri]]
+
+>> (Also, if `mybestlink` is going to always just return `bestlink` in
+>> this case, there seems no reason to inject it.) --[[Joey]]
+
+>>> Right. Commit cdc3576c8d1efb2 in my po branch prevents
+>>> `mybestlink` to be injected when `po_link_to` is
+>>> `default`. --[[intrigeri]]
Language display order
----------------------
that po might be replacing the only link on a page, in error?
--[[Joey]]
+> It would replace it. The only problematic case is when another
+> plugin has its own reasons, in its `scan` hook, to add a page
+> that is already there to `$links{$page}`. This other plugin's
+> effect might then be changed by po's `scan` hook... which could
+> 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
---------------------------
Normally at the top index page of a wiki, you see the wiki name at
the top. However, at the top *translated* index page, you see something
-like "index.da". --[[Joey]]
+like "index.da". --[[Joey]]
+
+> I suggest changing `Render.pm`, line 115, to replace the `$page eq 'index'`
+> 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
---------
brings up an edit form to create a new, english page.
This is with po_link_to=current or negotiated. With default, it doesn't
-happen.. --[[Joey]]
+happen..
+
+Also, this may only happen if the page being linked to is coming from an
+underlay, and the underlays lack translation to a given language.
+--[[Joey]]
Double commits of po files
--------------------------
Same thing happens when a change to an existing page triggers a po file
update. --[[Joey]]
+Ugly messages with empty files
+------------------------------
+
+If there are empty .mdwn files, the po plugin displays some ugly messages.
+
+Translation of directives
+-------------------------
+
+If a translated page contains a directive, it may expand to some english
+text, or text in whatever single language ikiwiki is configured to "speak".
+
+Maybe there could be a way to switch ikiwiki to speaking another language
+when building a non-english page? Then the directives would get translated.
+
Documentation
-------------