aboutsummaryrefslogtreecommitdiff
path: root/doc/plugins/po.mdwn
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2010-07-04 16:08:54 -0400
committerJoey Hess <joey@kitenet.net>2010-07-04 16:08:54 -0400
commit472d3fba7db7184fee3c4122d8f628cd6436c6bc (patch)
treeece5f1ba10048171842468c19809525ee0448060 /doc/plugins/po.mdwn
parent35fd6f81f110a187135fd2bafe1341666ff5d5ac (diff)
downloadikiwiki-472d3fba7db7184fee3c4122d8f628cd6436c6bc.tar
ikiwiki-472d3fba7db7184fee3c4122d8f628cd6436c6bc.tar.gz
comment
Diffstat (limited to 'doc/plugins/po.mdwn')
-rw-r--r--doc/plugins/po.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/plugins/po.mdwn b/doc/plugins/po.mdwn
index fab6053b3..fe4d75748 100644
--- a/doc/plugins/po.mdwn
+++ b/doc/plugins/po.mdwn
@@ -266,6 +266,14 @@ to an array to support this. (If twere done, twere best done quickly.)
> Done in my po branch, preserving backward compatibility. Please
> review :) --[[intrigeri]]
+>> Right, well my immediate concern is that using an array to hold
+>> hash-like pairs is not very clear to the user. It will be displayed
+>> in a confusing way by websetup; dumping a setup file will probably
+>> also cause it to be formatted in a confusing way. And the code
+>> seems to assume that the array length is even, and probably blows
+>> up if it is not.. and the value is marked safe so websetup can be
+>> used to modify it and break that way too. --[[Joey]]
+
Pagespecs
---------