From: Tim Landscheidt <tim@tim-landscheidt.de>
To: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: Re: Translating the eps files in lispintro
Date: Tue, 23 Jan 2024 16:09:58 +0000 [thread overview]
Message-ID: <87bk9cav55.fsf@vagabond.tim-landscheidt.de> (raw)
In-Reply-To: <50B9A33C-4A1F-4C57-B9C7-C158FAAFBD6C@traductaire-libre.org> (Jean-Christophe Helary's message of "Mon, 22 Jan 2024 13:20:34 +0000")
Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org> wrote:
>>> […]
>>> It would seem more practical to have a format that's a bit easier to edit (SVG, if only because it supports unicode) and from there use conversion tools to create the required formats:
>>> eps for TeX (DVI output)
>>> pdf/png/jpg (jpeg) for TeX (PDF output)
>>> png, jpg (jpeg), gif for HTML output (although the current output does not use images but just plain text)
>>> eps, gif, jpeg (jpg), pdf, png, svg for DocBook output
>>> https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#Images
>>> Considering the needs of the lisp introduction, we could have svg for an eventual DocBook output, png for the HTML and PDF output, eps for the DVI output and we'd be all set.
>>> Or maybe the actual source for the EPS (and PDF) files found in the intro is somewhere else? Are the files created from the texinfo source?
>> Looking at the images, it seems natural to write them in
>> groff/pic and then generate whatever.
> Do you have experience in generating images with non ascii text with groff?
> I just tried a simple tutorial and it did not come out well.
> The translation thread mentioned French, Chinese and Japanese.
I have never tried anything non-Latin-1.
Tim
next prev parent reply other threads:[~2024-01-23 16:09 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 [this message]
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
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=87bk9cav55.fsf@vagabond.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traductaire-libre.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 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.