From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Boxquote for code in UTF-8 export
Date: Fri, 12 Sep 2014 21:10:22 +0200 [thread overview]
Message-ID: <87ppf0psdd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <86y4tori3n.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 12 Sep 2014 17:09:16 +0200")
Hello,
Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> I'd advice to use UTF-8 characters more wildly available in the
> different fonts for drawing the Boxquote around code, in function:
>
> ╭────
> │ (defun org-ascii--box-string (s info)
> │ "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`----")
> │ (replace-regexp-in-string
> │ "^" (if utf8p "│ " "| ")
> │ ;; Remove last newline character.
> │ (replace-regexp-in-string "\n[ \t]*\\'" "" s)))))
> ╰────
[...]
> 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. What
should be the third?
Anyhow, do you want to provide a patch?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-09-12 19:10 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 [this message]
2014-09-26 10:12 ` Sebastien Vauban
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppf0psdd.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).