From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: text formating
Date: Fri, 03 Feb 2023 09:30:30 +0200 [thread overview]
Message-ID: <83zg9vurxl.fsf@gnu.org> (raw)
In-Reply-To: <Y9wZLVGKHG22LpXr@protected.localdomain> (message from Jean Louis on Thu, 2 Feb 2023 23:12:29 +0300)
> Date: Thu, 2 Feb 2023 23:12:29 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: help-gnu-emacs@gnu.org
>
> * Eli Zaretskii <<eliz@gnu.org> [2023-02-02 17:31]:
> > > Date: Thu, 2 Feb 2023 13:52:22 +0000
> > > From: Gottfried <<gottfried@posteo.de>
> > >
> > > I don't understand why until now nobody made in Emacs a
> > > WYSIWYG Mode.
> >
> > They did: it's called Enriched mode.
>
> By reference from:
> https://en.wikipedia.org/wiki/WYSIWYG
>
> In computing, WYSIWYG (/ˈwɪziwɪɡ/ WIZ-ee-wig), an acronym for What You
> See Is What You Get,[1] is a system in which editing software allows
> content to be edited in a form that resembles its appearance when
> printed or displayed as a finished product,[2] such as a printed
> document, web page, or slide presentation. WYSIWYG implies a user
> interface that allows the user to view something very similar to the
> end result while the document is being created.[3] In general, WYSIWYG
> implies the ability to directly manipulate the layout of a document
> without having to type or remember names of layout commands.
Thank you for the lecture. I surely needed it.
> Enriched mode is far from there.
>
> At least user should be able to get same printed representation even
> if font sizes are not changed.
If you are talking specifically about WYSIWYG printing, then yes, we
still aren't where we should be, especially with non-ASCII text;
patches welcome. But the OP didn't mention that, so this is not
necessarily what was the issue.
next prev parent reply other threads:[~2023-02-03 7:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 12:06 text formating Gottfried
2023-01-30 20:28 ` H. Dieter Wilhelm
2023-01-31 7:34 ` Jean Louis
2023-01-31 11:23 ` Ulrich Deiters
2023-01-31 12:43 ` Jean Louis
2023-02-02 13:52 ` Gottfried
2023-02-02 14:30 ` Eli Zaretskii
2023-02-02 15:40 ` [External] : " Drew Adams
2023-02-02 20:12 ` Jean Louis
2023-02-03 7:30 ` Eli Zaretskii [this message]
2023-02-03 9:08 ` Jean Louis
2023-02-03 17:24 ` Emanuel Berg
2023-02-04 15:24 ` Jean Louis
2023-02-04 21:44 ` Emanuel Berg
2023-02-07 17:25 ` Gottfried
2023-02-07 22:28 ` Jean Louis
2023-02-08 16:49 ` Gottfried
2023-02-08 19:37 ` Jean Louis
2023-02-08 20:18 ` [External] : " Drew Adams
2023-02-09 14:59 ` Gottfried
2023-02-09 15:27 ` [External] : " Drew Adams
2023-02-09 16:59 ` Gottfried
2023-02-09 17:13 ` Drew Adams
2023-02-09 18:10 ` Gottfried
2023-02-09 18:26 ` Jean Louis
2023-02-09 19:12 ` Drew Adams
2023-02-10 4:18 ` Jean Louis
2023-02-09 19:11 ` Drew Adams
2023-02-11 15:25 ` Gottfried
2023-02-11 16:10 ` tomas
2023-02-11 19:17 ` Jean Louis
2023-02-11 16:56 ` Drew Adams
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=83zg9vurxl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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 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.