emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Denis Bitouzé" <dbitouze@wanadoo.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Internal links broken when exporting from org mode to markdown and odt [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
Date: Thu, 10 Sep 2015 22:06:27 +0200	[thread overview]
Message-ID: <87vbbiqbss.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m3k2ry5ie8.fsf@drums.chezmoi.fr> ("Denis \=\?utf-8\?Q\?Bitouz\?\= \=\?utf-8\?Q\?\=C3\=A9\=22's\?\= message of "Thu, 10 Sep 2015 18:49:35 +0200")

Hello,

dbitouze@wanadoo.fr (Denis Bitouzé) writes:

> When exporting from ~org-mode~, the internal links are okay for ~latex~ or
> ~html~ export but are broken for ~markdown~ (and ~odt~ as well but ).
>
> For instance, the following file:
>
> #+NAME: test.org
> #+begin_src org
> * One section
> See the [[another][another]] section.
> * Another section<<another>>
> #+end_src

Thank you for the report.

I fixed it in Markdown back-end yesterday. You may want to upgrade Org.

However, I don't see anything wrong with ODT.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-09-10 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 16:49 Bug: Internal links broken when exporting from org mode to markdown and odt [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)] Denis Bitouzé
2015-09-10 20:06 ` Nicolas Goaziou [this message]
     [not found]   ` <87vbbiqbss.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-11  5:18     ` Denis Bitouzé
2015-09-18 22:06       ` Nicolas Goaziou
2015-09-20  9:58         ` Denis Bitouzé
2015-09-20 11:26           ` Nicolas Goaziou
     [not found]             ` <87pp1d9vrp.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-20 14:54               ` Denis Bitouzé

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=87vbbiqbss.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dbitouze@wanadoo.fr \
    --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).