From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Section about latex export is broken in the html manual?
Date: Tue, 28 Apr 2020 21:31:31 -0400 [thread overview]
Message-ID: <87ees7nklo.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 46e83b9d-3440-4a91-667a-46a7a231eaec@cs.umu.se
Niclas Borlin <niclas.borlin@cs.umu.se> writes:
> Hi,
>
> As far as I can tell, several links of section 10.13 LaTeX Export
> (https://orgmode.org/manual/LaTeX-Export.html) are broken (last
> checked 2020-04-28 19:15 UTC).
>
> The first four links on the page point to useful pages, i.e., clicking
> on "Quoting LaTeX code:" will get you to
> https://orgmode.org/manual/Quoting-LaTeX-code.html#Quoting-LaTeX-code,
> that contains section 13.10.4 Quoting LaTeX code.
>
> However, from the link "Tables in LaTeX export" downwards, you are
> linked back to the same page. For instance, clicking on "Tables in
> LaTeX export" will get you to
> https://orgmode.org/manual/LaTeX-Export.html#Tables-in-LaTeX-export. (I
> suspect the content of the page should be an updated version of
> https://www.gnu.org/software/emacs/manual/html_node/org/Tables-in-LaTeX-export.html.)
>
> I suspect this is a link naming issue in the .org version of the
> manual. Can anyone fix this?
>
I can confirm your findings, but I don't see anything wrong in the
.org version of the manual: I exported it to .html locally and that
works fine. But I'm not sure what happens on the way from one's local
system to the site.
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2020-04-29 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 19:19 Section about latex export is broken in the html manual? Niclas Borlin
2020-04-29 1:31 ` Nick Dokos [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ees7nklo.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).