From: Ihor Radchenko <yantar92@posteo.net>
To: Serghei Iakovlev <egrep@protonmail.ch>
Cc: Eli Zaretskii <eliz@gnu.org>, 73161@debbugs.gnu.org
Subject: bug#73161: 29.4; Exporting Org Agenda to PDF with Cyrillic Characters
Date: Thu, 24 Oct 2024 17:41:07 +0000 [thread overview]
Message-ID: <878qudo0uk.fsf@localhost> (raw)
In-Reply-To: <m15xr21jpx.fsf@protonmail.ch>
Serghei Iakovlev via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
>> IMO, Org should document that org-agenda-write uses ps-print and
>> ps2pdf, so that users could know where to look for cause of trouble
>> and which parts to customize to work around these problems.
>
> I agree with you. Things would have been a bit simpler, and perhaps
> even friendlier, if I had stumbled upon this information right away.
> I'd like to take this opportunity to address Ihor and kindly ask him
> to consider reviewing and enhancing the documentation related to this
> matter.
Would you be interested to prepare a patch updating the documentation?
Honestly, I feel confused about all the complications you have been
discussing here, so you might be a better person to explain the problem
at this point.
See https://orgmode.org/worg/org-contribute.html
Ideally, we need to switch to https://github.com/tecosaur/engrave-faces
that can handle pdf exports.
--
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>
prev parent reply other threads:[~2024-10-24 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 22:38 bug#73161: 29.4; Exporting Org Agenda to PDF with Cyrillic Characters Serghei Iakovlev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 6:19 ` Ihor Radchenko
2024-09-10 13:53 ` Eli Zaretskii
2024-09-10 13:51 ` Eli Zaretskii
2024-09-10 14:45 ` Eli Zaretskii
2024-09-11 12:02 ` Serghei Iakovlev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-24 17:41 ` Ihor Radchenko [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=878qudo0uk.fsf@localhost \
--to=yantar92@posteo.net \
--cc=73161@debbugs.gnu.org \
--cc=egrep@protonmail.ch \
--cc=eliz@gnu.org \
/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).