From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sven Bretfeld <sven.bretfeld@gmx.ch>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Bug in org-latex (6.34c)?
Date: Sun, 24 Jan 2010 10:55:24 +0100 [thread overview]
Message-ID: <D0E1A17F-037D-494F-AC37-D2A2110DC2FA@gmail.com> (raw)
In-Reply-To: <87iqasjtcr.fsf@rub.de>
On Jan 24, 2010, at 12:26 AM, Sven Bretfeld wrote:
> Hi Carsten
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> This works for me:
>>
>> (setq org-export-latex-inputenc-alist '(("utf8" . "utf8x)))
>
> Yes, that's working. Thank you very much.
>
>> Is this what you have?
>
> I set that function via customize. I think there was only one set og
> parenthesis.
>
>> I can make a variable to turn this automatic fixing of inputenc
>> off, so
>> that the configured value in org-export-latex-classes will always be
>> used....
>
> So, it's not a bug, it'a a feature. At least it should be documented
> in
> a more accessible place. All the predefined export classes contain the
> \usepackage[utf8]{inputenc} header. This suggests that having that
> line
> or changing it would have any effect.
Maybe we should redefine the classes to use
\usepackage[BUFFERCODING]{inputenc}
and the only modify the coding system if it is the special value
BUFFERCODING, but not if the user has specified one explicitly......
- Carsten
>
> Thanks again and greetings,
>
> Sven
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-01-24 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 11:39 Bug in org-latex (6.34c)? Sven Bretfeld
2010-01-23 16:23 ` Carsten Dominik
2010-01-23 18:48 ` Sven Bretfeld
2010-01-23 23:26 ` Sven Bretfeld
2010-01-24 9:55 ` Carsten Dominik [this message]
2010-01-24 10:24 ` Carsten Dominik
2010-01-24 11:32 ` Sven Bretfeld
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=D0E1A17F-037D-494F-AC37-D2A2110DC2FA@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sven.bretfeld@gmx.ch \
/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).