From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yantar92@posteo.net, acorallo@gnu.org, emacs-devel@gnu.org,
stefankangas@gmail.com
Subject: Re: RTF import/export emacs (was: New Emacs features via Google Summer of Code (or other similar stipend schemes))
Date: Sun, 18 Aug 2024 11:38:49 -0700 [thread overview]
Message-ID: <0982af39-b866-e16b-4af5-868d79cd74cf@gmail.com> (raw)
In-Reply-To: <86y14ty9wa.fsf@gnu.org>
On 8/18/2024 11:16 AM, Eli Zaretskii wrote:
>> Date: Sun, 18 Aug 2024 10:37:51 -0700
>> Cc: acorallo@gnu.org, emacs-devel@gnu.org, stefankangas@gmail.com
>> From: Jim Porter <jporterbugs@gmail.com>
>>
>> EWW/shr.el don't actually use slicing for flowing text, as far as I
>> know. I suppose that could work, but I'd be worried about
>> miscalculations causing the slices to be misaligned (for example if we
>> tried to support the CSS 'float: right' property).
>
> Using :align-to should allow us to align the slices horizontally (if
> that is what you had in mind).
My worry was that if you had this,
This is some text [image slice]
that goes on [image slice]
multiple lines. [image slice]
we'd have to be very careful. Text-scaling is probably the biggest risk.
If you enlarge the text, the line-height changes, which would probably
break things (though I guess we could scale the image too).
In any case, we can cross this bridge when we get to it.
> I say let's start from the text parts: the fonts, the faces, the
> indentation, the numbered and unnumbered lists, etc. If we can pull
> that out, we will already have a terrifically useful feature.
I agree. SHR has already implemented these[1], so it would probably be a
good source of ideas for how to render these parts. Maybe we could even
pull some of the code out into a common file.
[1] There's no CSS support though, so in practice, most web pages these
days end up using the default font with SHR.
next prev parent reply other threads:[~2024-08-18 18:38 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 ` RTF import/export emacs (was: New Emacs features via Google Summer of Code (or other similar stipend schemes)) Ihor Radchenko
2024-08-18 14:14 ` 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 [this message]
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=0982af39-b866-e16b-4af5-868d79cd74cf@gmail.com \
--to=jporterbugs@gmail.com \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@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).