From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Translating the eps files in lispintro
Date: Wed, 24 Jan 2024 20:59:23 +0200 [thread overview]
Message-ID: <86wmryd0c4.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8X+sij13pyY3rpQpFd_g9=nC0Zzf2M5pBk8E-w2-v5pFg@mail.gmail.com> (message from Yuri Khan on Thu, 25 Jan 2024 01:20:43 +0700)
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Thu, 25 Jan 2024 01:20:43 +0700
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
>
> On Wed, 24 Jan 2024 at 19:26, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > > > bouquet
> > > > |
> > > > | ___ ___ ___ ___ ___ ___
> > > > --> |___|___|--> |___|___|--> |___|___|--> nil
> > > > | | |
> > > > | | |
> > > > --> rose --> violet --> buttercup
>
> > We need a tool that will support at leas the following output formats:
> >
> > . PNG, JPEG, or GIF for HTML
>
> For this kind of illustrations, SVG will be preferable for HTML, too.
I was describing what Texinfo actually supports. If you want to
suggest enhancements to Texinfo, that is better done on the Texinfo
mailing list.
prev parent reply other threads:[~2024-01-24 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 11:17 Translating the eps files in lispintro Jean-Christophe Helary
2024-01-21 12:35 ` Po Lu
2024-01-21 13:47 ` Stefan Kangas
2024-01-21 14:40 ` Eli Zaretskii
2024-01-21 15:34 ` Jean-Christophe Helary
2024-01-21 16:05 ` Eli Zaretskii
2024-01-21 16:32 ` Jean-Christophe Helary
2024-01-23 17:15 ` Eli Zaretskii
2024-01-22 8:57 ` Tim Landscheidt
2024-01-22 13:20 ` Jean-Christophe Helary
2024-01-23 16:09 ` Tim Landscheidt
2024-01-23 20:08 ` Stefan Monnier via Emacs development discussions.
2024-01-24 12:25 ` Eli Zaretskii
2024-01-24 13:10 ` Ihor Radchenko
2024-01-24 18:20 ` Yuri Khan
2024-01-24 18:59 ` Eli Zaretskii [this message]
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=86wmryd0c4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yuri.v.khan@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).