From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acorallo@gnu.org, emacs-devel@gnu.org, stefankangas@gmail.com
Subject: RTF import/export emacs (was: New Emacs features via Google Summer of Code (or other similar stipend schemes))
Date: Sun, 18 Aug 2024 13:56:46 +0000 [thread overview]
Message-ID: <87a5hax7c1.fsf@localhost> (raw)
In-Reply-To: <86frr2ymos.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> > That paragraph includes 20 separate tasks. They could be performed
>> > one by one, not necessarily all of them together. At least some of
>> > them are definitely suitable for GSoC type jobs. For example, "import
>> > / export RTF files".
>>
>> Doesn't it require completing a couple of display-engine related
>> features like flowing text around images? Or does import/export imply
>> something else, not _displaying_ and editing RTF document?
>
> Determining what it means and where it ends is IMO part of the job.
> The ability to import RTF files will be a very useful feature even if
> it doesn't support images at first.
Then, it is indeed doable.
If we limit features to current display engine capabilities, simply
something like libpandoc will be good enough for basic import/export
(not just RTF, but a plethora of other formats as well).
> ... (And what exactly is a problem
> with supporting images, given that Emacs is already capable of
> displaying them?)
Some text flowing around the images
.... ... with multiple lines of text
.... .... . going beside the
. . . image.
. .... . .
. .. .. .
.. ..... .
......... ... .
.. ..
Or text and image displayed on top of each other.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-08-18 13:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 22:48 as for Calc and the math library Emanuel Berg
2024-08-11 4:58 ` Eli Zaretskii
2024-08-11 16:45 ` Ihor Radchenko
2024-08-11 16:55 ` Christopher Dimech
2024-08-11 17:05 ` Emanuel Berg
2024-08-11 17:59 ` Eli Zaretskii
2024-08-11 18:17 ` Christopher Dimech
2024-08-11 18:32 ` Eli Zaretskii
2024-08-11 19:53 ` Christopher Dimech
2024-08-11 18:27 ` Ihor Radchenko
2024-08-11 18:38 ` Emanuel Berg
2024-08-12 6:28 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library) Ihor Radchenko
2024-08-12 11:09 ` Eli Zaretskii
2024-08-12 12:10 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) Joel Reicher
2024-08-12 18:59 ` Ihor Radchenko
2024-08-12 22:28 ` Pedro
2024-08-14 10:07 ` Ihor Radchenko
2024-08-15 11:44 ` Ihor Radchenko
2024-08-12 19:17 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library) Ihor Radchenko
2024-08-13 8:12 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) Andrea Corallo
2024-08-18 11:48 ` Ihor Radchenko
2024-08-18 12:35 ` Eli Zaretskii
2024-08-18 12:52 ` Ihor Radchenko
2024-08-18 13:39 ` Eli Zaretskii
2024-08-18 13:56 ` Ihor Radchenko [this message]
2024-08-18 14:14 ` RTF import/export emacs (was: New Emacs features via Google Summer of Code (or other similar stipend schemes)) Eli Zaretskii
2024-08-18 14:35 ` Ihor Radchenko
2024-08-18 14:38 ` Eli Zaretskii
2024-08-18 17:37 ` Jim Porter
2024-08-18 18:16 ` Eli Zaretskii
2024-08-18 18:38 ` Jim Porter
2024-08-18 19:05 ` tomas
2024-08-13 11:02 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library) Eli Zaretskii
2024-08-18 11:09 ` Ihor Radchenko
2024-08-18 11:25 ` Eli Zaretskii
2024-08-18 11:33 ` Stefan Kangas
2024-08-18 12:47 ` Ihor Radchenko
2024-08-11 18:52 ` as for Calc and the math library Eli Zaretskii
2024-08-11 19:13 ` Ihor Radchenko
2024-08-12 2:24 ` Eli Zaretskii
2024-08-11 21:50 ` Christopher Dimech
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=87a5hax7c1.fsf@localhost \
--to=yantar92@posteo.net \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/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).