aboutsummaryrefslogtreecommitdiff
path: root/doc/plugins
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2010-07-30 16:19:50 +0200
committerintrigeri <intrigeri@boum.org>2010-07-30 16:23:02 +0200
commit543bc7af8be315e44ccca575b788e566bc122db2 (patch)
treefabf5e95b64b24278ba1e473ccceadc8c1b1b420 /doc/plugins
parent1fe87a0808ee4d19d97956d48447644c69334f8a (diff)
downloadikiwiki-543bc7af8be315e44ccca575b788e566bc122db2.tar
ikiwiki-543bc7af8be315e44ccca575b788e566bc122db2.tar.gz
eventually got rid of the double rebuild issue. please have a look.
Diffstat (limited to 'doc/plugins')
-rw-r--r--doc/plugins/po/discussion.mdwn22
1 files changed, 0 insertions, 22 deletions
diff --git a/doc/plugins/po/discussion.mdwn b/doc/plugins/po/discussion.mdwn
index 73858c818..50998e822 100644
--- a/doc/plugins/po/discussion.mdwn
+++ b/doc/plugins/po/discussion.mdwn
@@ -644,28 +644,6 @@ daring a timid "please pull"... or rather, please review again :)
>>> need improvements to the deletion UI to de-confuse that. It's fine to
>>> put that off until needed --[[Joey]]
>>
-> * Re the meta title escaping issue worked around by `change`.
-> I suppose this does not only affect meta, but other things
-> at scan time too. Also, handling it only on rebuild feels
-> suspicious -- a refresh could involve changes to multiple
-> pages and trigger the same problem, I think. Also, exposing
-> this rebuild to the user seems really ugly, not confidence inducing.
->
-> So I wonder if there's a better way. Such as making po, at scan time,
-> re-run the scan hooks, passing them modified content (either converted
-> from po to mdwn or with the escaped stuff cheaply de-escaped). (Of
-> course the scan hook would need to avoid calling itself!)
->
-> (This doesn't need to block the merge, but I hope it can be addressed
-> eventually..)
->
-> --[[Joey]]
->>
->> I'll think about it soon.
->>
->> --[[intrigeri]]
->>
->>> Did you get a chance to? --[[Joey]]
* As discussed at [[todo/l10n]] the templates needs to be translatable too. They
should be treated properly by po4a using the markdown option - at least with my