From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Boxquote for code in UTF-8 export
Date: Fri, 26 Sep 2014 12:12:07 +0200 [thread overview]
Message-ID: <86mw9mn11k.fsf@somewhere.org> (raw)
In-Reply-To: 87ppf0psdd.fsf@nicolasgoaziou.fr
Hello,
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> I'd advice to use UTF-8 characters more wildly available in the
>> different fonts for drawing the Boxquote around code, in function
>> `org-ascii--box-string'.
>>
>> The results is that only \u250C and \u2514 are "universal" (except in
>> Lucida Sans Typewriter which implements almost nothing -- unlike
>> DejaVu Sans Mono which implements almost everything).
>
> There are three characters required. You are only suggesting two.
Yes.
> What should be the third?
The third is present in (almost?) all fonts. No problem with it.
> Anyhow, do you want to provide a patch?
Here it is.
Best regards,
Seb
* ox-ascii.el (org-ascii--box-string): Choose more universal Unicode
characters for boxquote corners.
---
lisp/ox-ascii.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el
index 6f2b43a..6316e59 100644
--- a/lisp/ox-ascii.el
+++ b/lisp/ox-ascii.el
@@ -542,7 +542,7 @@ Empty lines are not indented."
"Return string S with a partial box to its left.
INFO is a plist used as a communication channel."
(let ((utf8p (eq (plist-get info :ascii-charset) 'utf-8)))
- (format (if utf8p "╭────\n%s\n╰────" ",----\n%s\n`----")
+ (format (if utf8p "┌────\n%s\n└────" ",----\n%s\n`----")
(replace-regexp-in-string
"^" (if utf8p "│ " "| ")
;; Remove last newline character.
--
2.1.1
next prev parent reply other threads:[~2014-09-26 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 15:09 Boxquote for code in UTF-8 export Sebastien Vauban
2014-09-12 19:10 ` Nicolas Goaziou
2014-09-26 10:12 ` Sebastien Vauban [this message]
2014-09-27 12:59 ` Nicolas Goaziou
2014-09-12 20:36 ` Samuel Wales
2014-09-13 8:29 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mw9mn11k.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.