emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Yasushi SHOJI <yasushi.shoji@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: exporting a big project in multiple files to both pdf and html
Date: Thu, 1 Feb 2018 20:09:52 +0900	[thread overview]
Message-ID: <CAELBRWLEoO0mc6gUXzSfnP4wfHOc2nQFR94CQ9vs9N2bG7xZoQ@mail.gmail.com> (raw)
In-Reply-To: <m28tcdayjr.fsf@charm-ecran.irisa.fr>

Hi,

On Thu, Feb 1, 2018 at 5:45 PM, Alan Schmitt
<alan.schmitt@polytechnique.org> wrote:
> On 2018-02-01 11:17, Yasushi SHOJI <yasushi.shoji@gmail.com> writes:
>> On Fri, Jan 26, 2018 at 2:37 AM, Alan Schmitt
>> <alan.schmitt@polytechnique.org> wrote:
>>> My question is about pdf export. Is it possible to take a document made
>>> of multiple org files and generate a single book from it? I'm worried
>>> that if I use a master org file that includes the other ones, the links
>>> between chapters would break.
>>
>> You can just use '#+INCLUDE' construct and Org will take care.
>
> My problem is links. To give a concrete example, here is the file I want
> to split in two:
>
> * A headline
>   :PROPERTIES:
>   :CUSTOM_ID: head1
>   :END:
>
> This is the first file.
>
> * Second headline
>
> The first headline is number [[#head1]]
>
>
> How do I change the link in the second headline so that I can split the
> second headline into its own file and export it by itself?

Using [[*A headline]] ?

I might be still missing something but I got following:

$ cat a.org
* A headline

This is the first file.

#+INCLUDE: b.org :minlevel 1

$ cat b.org
* Second headline

The first headline is number [[*A headline]]

$ org-export.sh a.org
$ cat a.tex
% Created 2018-02-01 Thu 20:08
% Intended LaTeX compiler: pdflatex
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{grffile}
\usepackage{longtable}
\usepackage{wrapfig}
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{textcomp}
\usepackage{amssymb}
\usepackage{capt-of}
\usepackage{hyperref}
\author{Yasushi SHOJI}
\date{\today}
\title{}
\hypersetup{
 pdfauthor={Yasushi SHOJI},
 pdftitle={},
 pdfkeywords={},
 pdfsubject={},
 pdfcreator={Emacs 26.0.91 (Org mode 9.1.6)},
 pdflang={English}}
\begin{document}

\tableofcontents

\section{A headline}
\label{sec:org0ac96d1}

This is the first file.

\section{Second headline}
\label{sec:org2092415}

The first headline is number \ref{sec:org0ac96d1}
\end{document}


hmm... latex export will generate \ref{sec:\#head}
if you have CUSTOM_ID set.  html exporter works, though.

Is it a bug?
-- 
          yashi

  reply	other threads:[~2018-02-01 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 17:37 exporting a big project in multiple files to both pdf and html Alan Schmitt
2018-02-01  2:17 ` Yasushi SHOJI
2018-02-01  8:45   ` Alan Schmitt
2018-02-01 11:09     ` Yasushi SHOJI [this message]
2018-02-01 12:29       ` Alan Schmitt
2018-02-01 12:56         ` Nicolas Goaziou
2018-02-01 13:47           ` Alan Schmitt
2018-02-02  0:38         ` Yasushi SHOJI
2018-02-02  7:41           ` Alan Schmitt
2018-02-02  9:41             ` Yasushi SHOJI
2018-02-02 13:13               ` Alan Schmitt

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=CAELBRWLEoO0mc6gUXzSfnP4wfHOc2nQFR94CQ9vs9N2bG7xZoQ@mail.gmail.com \
    --to=yasushi.shoji@gmail.com \
    --cc=alan.schmitt@polytechnique.org \
    --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).