From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: text formating
Date: Fri, 3 Feb 2023 12:08:40 +0300 [thread overview]
Message-ID: <Y9zPGNiFgOJiQw15@protected.localdomain> (raw)
In-Reply-To: <83zg9vurxl.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2023-02-03 10:33]:
> 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:
1. Enriched mode, with some addition of font sizes or similar
2. By converting Enriched Text to Pango markup
3. By using Pango markup in Emacs Lisp program
Pango – 1.0: Text Attributes and Markup:
https://docs.gtk.org/Pango/pango_markup.html
Pango Markup:
https://shinmera.github.io/pango-markup/
4. By using `paps' command, I have made package for it, but it may be
used by various methods:
GNU Emacs package: rcd-paps.el:
https://gnu.support/gnu-emacs/packages/GNU-Emacs-package-rcd-paps-el-76862.html
5. By converting on the fly the Enriched Text to Pango markup
6. By using Pango markup to produce printable documents with `paps'
The above workflow can produce visually pleasant text with all
attributes how Pango markup has it, provided that Enriched mode get
translation to Pango markup.
Could somebody help with making of such package? For me, I do not know
exactly where to start.
Michael how about some power from North?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-03 9:08 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 [this message]
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=Y9zPGNiFgOJiQw15@protected.localdomain \
--to=bugs@gnu.support \
--cc=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.