summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/plugins/contrib/po.mdwn14
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/plugins/contrib/po.mdwn b/doc/plugins/contrib/po.mdwn
index 5f0de3b5e..618e16598 100644
--- a/doc/plugins/contrib/po.mdwn
+++ b/doc/plugins/contrib/po.mdwn
@@ -332,7 +332,8 @@ daring a timid "please pull"... or rather, please review again :)
> Ok, I've reviewed and merged into my own po branch. It's looking very
> mergeable. I would still like to go over the `po.pm` code in detail and
> review it, but it's very complex, and I'm happy with all the changes
-> outside `po.pm`.
+> outside `po.pm`. (Reviewed the first 520 lines, up to injected
+> functions.)
>
> * Is it worth trying to fix compatability with `indexpages`?
>>
@@ -358,6 +359,17 @@ daring a timid "please pull"... or rather, please review again :)
>> disabled, I fear the ones who could do this would maybe think
>> it's blandly impossible and give up.
>>
+
+> * What's the reasoning behind checking that the link plugin
+> is enabled? AFAICS, the same code in the scan hook should
+> also work when other link plugins like camelcase are used.
+> * In `pagetemplate` there is a comment that claims the code
+> relies on `genpage`, but I don't see how it does; it seems
+> to always add a discussion link?
+> * Is there any real reason not to allow removing a translation?
+> I'm imagining a spammy translation, which an admin might not
+> be able to fix, but could remove.
+>
> --[[Joey]]
>>
>> --[[intrigeri]]