aboutsummaryrefslogtreecommitdiff
path: root/doc/todo
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/todo
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/todo')
-rw-r--r--doc/todo/po:_avoid_rebuilding_to_fix_meta_titles.mdwn32
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/todo/po:_avoid_rebuilding_to_fix_meta_titles.mdwn b/doc/todo/po:_avoid_rebuilding_to_fix_meta_titles.mdwn
new file mode 100644
index 000000000..78e8e3ade
--- /dev/null
+++ b/doc/todo/po:_avoid_rebuilding_to_fix_meta_titles.mdwn
@@ -0,0 +1,32 @@
+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]]
+
+>>>> I eventually did, and got rid of the ugly double rebuild of pages
+>>>> at build time. This involved adding a `rescan` hook. Rationale
+>>>> and details are in my po branch commit messages. I believe this
+>>>> new way of handling meta title escaping to be far more robust.
+>>>> Moreover this new implementation is more generic, feels more
+>>>> logical to me, and probably fixes other similar bugs outside the
+>>>> meta plugin scope. Please have a look when you can.
+>>>> --[[intrigeri]]