Bastien wrote:
Hi Wanrong,
Wanrong Lin <[EMAIL PROTECTED]> writes:
Finally, I decided to learn some elisp debugging techniques and as a
practice, it seems I found the bug and fixed it with this patch (against
org.el in 5.16b)
@@ -24437,7 +24437,7 @@
(when (re-search-backward
"\\(<p>\\)\\([ \t\r\n]*\\)\\=" (- (point) 100) t)
(setq par (match-string 1))
- (replace-match "\\2\n"))
+ (replace-match ""))
(insert line "\n")
(while (and lines
(get-text-property 0 'org-protected (car lines)))
I am not completely sure whether this is the right fix, but so far the
output looks OK to me.
Thanks for this. I think the patch is safe (I'm testing it for two or
three days now) but I cannot predict it will be in any cases. I guess
Carsten will have a better call on this.
(BTW, the issue your raising here concerns the way the HTML code *looks*
and IMO they are less important than issues regarding the correctness of
the HTML code... Just a thought.)
Thanks for testing. Surely the No.1 priority is to have correct HTML
syntax. But I think how the page looks comes very close as a second
priority. After all, we use HTML because we want certain look (and
better navigation).
Wanrong
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
