it is (meant to be) possible, just not with that syntax

diff --git a/doc/bugs/It__39__s_not_possible_to_add_the_new_Flattr_meta_tag_using_the_meta_directive.mdwn b/doc/bugs/It__39__s_not_possible_to_add_the_new_Flattr_meta_tag_using_the_meta_directive.mdwn
index 7da8bccc28afe76b0ad5060086102962d32c0d5a..c0452e2060e14e4cd9cf75e6836ec4b6313f5efd 100644 (file)
--- a/doc/bugs/It__39__s_not_possible_to_add_the_new_Flattr_meta_tag_using_the_meta_directive.mdwn
+++ b/doc/bugs/It__39__s_not_possible_to_add_the_new_Flattr_meta_tag_using_the_meta_directive.mdwn
@@ -13,3 +13,10 @@ it gets rendered as:
     <meta name="flattr:id=&quot;4j6y0v&quot;" content="" />
 
 I tried [a number of possibilities](https://feeding.cloud.geek.nz/recentchanges/) and they all failed to produce the correct output.
+
+> Directive syntax doesn't allow named arguments containing colons, so we would have to
+> add a different syntax for weird names. However, we already have that:
+>
+>     \[[!meta name="flattr:id" content="4j6y0v"]]
+>
+> Please try that. --[[smcv]]