unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: text formating
Date: Sat, 4 Feb 2023 18:24:19 +0300	[thread overview]
Message-ID: <Y954o5r3TeFFJJ5T@protected.localdomain> (raw)
In-Reply-To: <87bkmall1j.fsf@dataswamp.org>

* Emanuel Berg <incal@dataswamp.org> [2023-02-04 17:53]:
> Jean Louis wrote:
> 
> >> 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.
> >
> > Here is how Enriched Text may become word processor with
> > pleasant result
> 
> Most people are from the opposite side of the spectrum, i.e.
> text editor, not word processor.

You have sent references to non-free software, so those I can't use. 

There is much better free software in GNU/Linux then those referenced.

Finally there are also those such as What You See Is What You Mean --
like the beautiful LyX. There is TeXmacs too.

LyX | LyX – The Document Processor:
https://www.lyx.org/

Welcome to GNU TeXmacs (FSF GNU project):
https://www.texmacs.org/tmweb/home/welcome.en.html

There is AbiWord and similar others.

But as I have explained, Emacs can be made to print all styles at
least similar, and in colors, how they are on screen, by using
translator program that would translate from Emacs properties to
Pango.

If you know how to provide conclusive reader function, that would
isolate each property, then I guess that would be already something to
start making translation functions to Pango markup.

Printing is already solved with `paps'.

Basically, that is so close, in my opinion.

But one would not be setting up margins, spacing, that all can be done
by using `paps' not Emacs directly.

Font sizes, colors, types, fonts, all that can be translated to Pango.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2023-02-04 15:24 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
2023-02-03  9:08           ` Jean Louis
2023-02-03 17:24             ` Emanuel Berg
2023-02-04 15:24               ` Jean Louis [this message]
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

  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=Y954o5r3TeFFJJ5T@protected.localdomain \
    --to=bugs@gnu.support \
    --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.
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).