diff options
author | Joey Hess <joey@kodama.kitenet.net> | 2008-07-14 16:08:54 -0400 |
---|---|---|
committer | Joey Hess <joey@kodama.kitenet.net> | 2008-07-14 17:05:52 -0400 |
commit | aecfebc26d000ab228cd406f5ac51df69352fbae (patch) | |
tree | 9dffb0e1b1706791d056824fd92234ab9d9c9d4a /doc/todo | |
parent | 901487df5ed213c7e82bf176d369617fdd1fbda3 (diff) |
response
Diffstat (limited to 'doc/todo')
-rw-r--r-- | doc/todo/color_plugin.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/todo/color_plugin.mdwn b/doc/todo/color_plugin.mdwn index f8fd11091..ac6eb8c51 100644 --- a/doc/todo/color_plugin.mdwn +++ b/doc/todo/color_plugin.mdwn @@ -14,3 +14,15 @@ It's not as easy in usage like color name or definition as plugin argument, but I don't have a better idea right now. What do you think about it? --[[Paweł|ptecza]] + +> Making a plugin preserve style attributes can be done, it just has to add +> them after the sanitize step, which strips them. The general method is +> adding placeholders first, and replacing them with the real html later. +> +> The hard thing to me seems to be finding a syntax that is better than a +> `<span>`. A preprocessor directive is not really any less ugly than html +> tags, though at least it could play nicely with nested markdown: --[[Joey]] +> +> \[[color red,green """ +> Xmas-colored markdown here +> """]] |