From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: double-width characters in tables
Date: Tue, 12 Feb 2013 19:43:50 +0100 [thread overview]
Message-ID: <877gmdcqzd.fsf@Rainer.invalid> (raw)
In-Reply-To: 87vc9x4jwq.fsf@ericabrahamsen.net
Eric Abrahamsen writes:
> Yes, org-string-width eventually calls string-width, so that behaves
> "correctly" as far as it goes, but unfortunately that's not where the
> value in the text properties comes from...
>
> 《蛙》
> 123456
>
> Doesn't that line up for you? Those bracket characters come with their
> own "whitespace", maybe this is clearer:
>
> 正能量
> 123456
>
> One Chinese character should definitely take up two screen columns.
That's a function of the font that is ultimately used and their
run-length. Since you are unlikely to use a font that has _all_ those
glyphs, eventually the ones that are missing in your specified font will
be replaced with the glyph corresponding to the same codepoint in a
different font if it exists or possibly a composition of multiple glyphs
(if not you'll get a placeholder).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2013-02-12 18:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 10:56 double-width characters in tables Eric Abrahamsen
2013-02-12 11:02 ` Jambunathan K
2013-02-12 11:22 ` Bastien
2013-02-12 11:16 ` Bastien
2013-02-12 15:43 ` Eric Abrahamsen
2013-02-12 15:50 ` Nick Dokos
2013-02-12 15:55 ` Bastien
2013-02-12 17:55 ` Takaaki ISHIKAWA
2013-02-12 18:43 ` Achim Gratz [this message]
2013-02-13 1:46 ` Eric Abrahamsen
2013-02-13 2:23 ` [PATCH] " Eric Abrahamsen
2013-02-13 11:42 ` Bastien
2013-02-13 13:18 ` Eric Abrahamsen
2013-02-13 8:50 ` Eric Abrahamsen
2013-02-13 11:31 ` Bastien
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=877gmdcqzd.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.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).