Hi Reuben, Thank you for your bug report.
Reuben Thomas <r...@sc3d.org> writes: > Remember to cover the basics, that is, what you expected to happen and > what in fact did happen. You don't know how to make a good report? See > > http://orgmode.org/manual/Feedback.html#Feedback > > Your bug report will be posted to the Org mailing list. > ------------------------------------------------------------------------ > > The page http://orgmode.org/manual/Advanced-configuration.html has the > following example: > > Here is an example filter that replaces non-breaking spaces ~ in the Org > buffer with _ for the LaTeX back-end. > > (defun my-latex-filter-nobreaks (text backend info) > "Ensure \"_\" are properly handled in LaTeX export." > (when (org-export-derived-backend-p backend 'latex) > (replace-regexp-in-string "_" "~" text))) > > (add-to-list 'org-export-filter-plain-text-functions > 'my-latex-filter-nobreaks) > > This is confusing in several ways. First, the replacement is made the > other way around (that is, _ is replaced by ~). Secondly, “_” does not > denote a non-breaking space in org-mode, as far as I can see. Does the > text mean “LaTeX non-breaking spaces”? Finally, underscore has a > particular meaning in Org, namely, subscript. It should be a non-breaking space " " which is displayed like a ruby-colored "_" in (my) Emacs. It was changed to a normal underscore upstream via commit 961cf22823d55. It was then rewritten in 6ce21caac53d376758 to the current form. It is a useful example so we could undo the first part of 6ce21caac53. Alternatively, perhaps discussing a space unicode character becomes a bit too awkward to follow in anything but Emacs so we could also replace something else in the example. Rasmus -- Nothing's wrong with an email that ends in a minor key
