unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Richard Stallman <rms@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Implementing Vertical Text support in Emacs
Date: Wed, 15 Jun 2022 16:39:23 +0530	[thread overview]
Message-ID: <CAOR1sLwhWLVtPJOX_0rvk8=_eYLp20LyxnksXObUp_mycUp4gw@mail.gmail.com> (raw)
In-Reply-To: <87wndi6xau.fsf@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]

>
> > Are there any scripts that are always and only written vertically?
>
> I think Mongolian script is always written that way.


Yes I think scripts like Mongolian and Phags Pa are always written
vertically.

Are there any scripts that people actually write in
> that people do not nowadays write horizontally in word processors?
>

I am sorry I do not understand the question, did you meant to say
"vertically"?
btw word processors like libreoffice support vertical text.

If people have learned to accept writing those scripts horizontally, I
> think that way is good enough for Emacs too.
>

Wouldn't it be better to support vertical text in Emacs, the only reason
people would have "learned to accept" to write these scripts horizontally
is because their preferred way of writing is not supported in many
softwares/websites.
I know that this is a complex process, but at least we can try.

On Wed, Jun 15, 2022 at 3:52 PM Po Lu <luangruo@yahoo.com> wrote:

> Richard Stallman <rms@gnu.org> writes:
>
> > Are there any scripts that are always and only written vertically?
>
> I think Mongolian script is always written that way.
>

[-- Attachment #2: Type: text/html, Size: 2240 bytes --]

  reply	other threads:[~2022-06-15 11:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 15:29 Implementing Vertical Text support in Emacs समीर सिंह Sameer Singh
2022-06-13 16:16 ` [External] : " Drew Adams
2022-06-13 16:30 ` Eli Zaretskii
2022-06-15 10:08   ` Richard Stallman
2022-06-15 10:22     ` Po Lu
2022-06-15 11:09       ` समीर सिंह Sameer Singh [this message]
2022-06-16 22:48         ` Richard Stallman
2022-06-17  1:43           ` समीर सिंह Sameer Singh
2022-06-17  6:12             ` Eli Zaretskii
2022-09-08 18:44               ` समीर सिंह Sameer Singh
2022-09-08 19:05                 ` Eli Zaretskii
2022-09-10 15:53                   ` समीर सिंह Sameer Singh
2022-09-10 16:17                     ` Eli Zaretskii
2022-09-29 19:57                       ` समीर सिंह Sameer Singh
2022-09-30  6:30                         ` Eli Zaretskii
2022-11-20 11:18                           ` समीर सिंह Sameer Singh
2022-11-20 11:43                             ` Eli Zaretskii
2022-11-20 12:08                               ` समीर सिंह Sameer Singh
2022-11-24 11:39                                 ` Eli Zaretskii

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOR1sLwhWLVtPJOX_0rvk8=_eYLp20LyxnksXObUp_mycUp4gw@mail.gmail.com' \
    --to=lumarzeli30@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rms@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.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).