diff options
author | Joey Hess <joey@gnu.kitenet.net> | 2009-03-29 15:25:14 -0400 |
---|---|---|
committer | Joey Hess <joey@gnu.kitenet.net> | 2009-03-29 15:25:14 -0400 |
commit | b94b0b564d90b357d2cb1ba5a5d364f8802fed3b (patch) | |
tree | 7c42aa2330702f38cf0f08e661616a362e9bc705 | |
parent | 3d8f0b1a3f749006424fb719ea1841ef366b5090 (diff) |
another issue
-rw-r--r-- | doc/plugins/contrib/po.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/plugins/contrib/po.mdwn b/doc/plugins/contrib/po.mdwn index 618e16598..fba8de282 100644 --- a/doc/plugins/contrib/po.mdwn +++ b/doc/plugins/contrib/po.mdwn @@ -369,6 +369,17 @@ daring a timid "please pull"... or rather, please review again :) > * 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. +> * 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!) > > --[[Joey]] >> |