From: Eli Zaretskii <eliz@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: yantar92@posteo.net, 71909@debbugs.gnu.org, visuweshm@gmail.com
Subject: bug#71909: 30.0.60;
Date: Sun, 20 Oct 2024 20:58:00 +0300 [thread overview]
Message-ID: <867ca2irmf.fsf@gnu.org> (raw)
In-Reply-To: <e7178b2b-fed9-4192-ada8-84d0d347f14e@imayhem.com> (message from Cecilio Pardo on Sun, 20 Oct 2024 19:16:03 +0200)
> Date: Sun, 20 Oct 2024 19:16:03 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, 71909@debbugs.gnu.org
> From: Cecilio Pardo <cpardo@imayhem.com>
>
> I had planned to try to use UnRTF for this.
>
> https://www.gnu.org/software/unrtf/
>
> It's a GNU package, and despite being old and (I think) unmaintained, it
> is used by many wrappers for different languages, so it probably works
> well, though I haven't tested it myself yet.
>
> Has it been already tried for emacs?
I don't think so.
> If not, which approach (tree-sitter, unrtf) would be more promising?
It depends on which one covers the RTF spec better, I think. All the
rest being equal, I think tree-sitter is more promising, because it
will definitely be faster. OTOH, an Emacs-specific downside of using
tree-sitter is that we don't have any experience using TS
structure-related information (sectioning, tables, numbered lists,
etc.) in Emacs, we only use TS for faces and indentation. UnRTF
converts to HTML, and we already know how to use this stuff when
expressed in HTML.
next prev parent reply other threads:[~2024-10-20 17:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <865xtnhyn6.fsf@foxmail.com>
2024-10-05 12:28 ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-05 12:33 ` Eli Zaretskii
2024-10-05 12:42 ` Eli Zaretskii
2024-10-05 17:14 ` Cecilio Pardo
2024-10-05 19:31 ` Eli Zaretskii
2024-10-05 21:24 ` Cecilio Pardo
2024-10-06 5:59 ` Eli Zaretskii
[not found] ` <87ldz1h5s4.fsf@gmail.com>
2024-10-06 11:50 ` Eli Zaretskii
2024-10-06 12:15 ` Visuwesh
2024-10-20 13:09 ` Ihor Radchenko
2024-10-20 13:51 ` Eli Zaretskii
2024-10-20 13:59 ` Ihor Radchenko
2024-10-20 14:22 ` Eli Zaretskii
2024-10-20 15:02 ` Ihor Radchenko
2024-10-20 15:34 ` Eli Zaretskii
2024-10-20 15:57 ` Ihor Radchenko
2024-10-20 17:50 ` Visuwesh
2024-10-20 17:59 ` Eli Zaretskii
2024-10-20 17:16 ` Cecilio Pardo
2024-10-20 17:58 ` Eli Zaretskii [this message]
2024-10-07 10:24 ` Cecilio Pardo
2024-10-07 11:58 ` Eli Zaretskii
2024-10-09 12:52 ` Cecilio Pardo
2024-10-09 13:40 ` Eli Zaretskii
2024-10-10 10:04 ` Cecilio Pardo
2024-10-10 10:49 ` 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=867ca2irmf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71909@debbugs.gnu.org \
--cc=cpardo@imayhem.com \
--cc=visuweshm@gmail.com \
--cc=yantar92@posteo.net \
/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).