From: Carsten Dominik <carsten.dominik@gmail.com>
To: Francesco Pizzolante <fpz@missioncriticalit.com>
Cc: mailing-list-org-mode <emacs-orgmode@gnu.org>
Subject: Re: Exporting non utf8 org documents
Date: Fri, 8 Jan 2010 13:39:08 +0100 [thread overview]
Message-ID: <E33721E1-E928-4FA1-B20C-676C341573A4@gmail.com> (raw)
In-Reply-To: <87zl4o3ha1.fsf@missioncriticalit.com>
On Jan 8, 2010, at 1:36 PM, Francesco Pizzolante wrote:
> Hi Carsten,
>
>> here is a possible solution:
>>
>> Please get the latest git version of org-mode. Then put the
>> following code
>> into
>> .emacs:
>>
>> (defun my-org-export-latex-fix-inputenc ()
>> "Set the codingsystem in inputenc to what the buffer is."
>> (let* ((cs buffer-file-coding-system)
>> (opt (latexenc-coding-system-to-inputenc cs)))
>> (when opt
>> (goto-char (point-min))
>> (while (re-search-forward "\\\\usepackage\\[\\(.*?\\)\\]
>> {inputenc}"
>> nil t)
>> (goto-char (match-beginning 1))
>> (delete-region (match-beginning 1) (match-end 1))
>> (insert opt))
>> (save-buffer))))
>>
>> (eval-after-load "org-latex"
>> '(add-hook 'org-export-latex-after-save-hook
>> 'my-org-export-latex-fix-inputenc))
>>
>> Let me know how it goes.....
>
> Thanks for your solution.
>
> I've tested with both latin1 and utf8 Org buffers and I get the
> correct
> encoding passed to LaTeX in both cases.
>
> Regarding the utf8 encoding, I had a remark in my first message,
> which was:
>
>>> In addition, Org should use the `utf8x' option (instead of `utf8')
>>> which
>>> enables to handle unbreakable spaces (useful in french).
>
> Could you change that too?
no, because utf8x is not in all TeX distributions, so that is too
risky. I was considering to make it configurable, though.
- Carsten
>
> Thanks a lot,
> Francesco
- Carsten
next prev parent reply other threads:[~2010-01-08 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 16:22 Exporting non utf8 org documents Francesco Pizzolante
2010-01-04 14:16 ` Carsten Dominik
2010-01-06 8:26 ` Carsten Dominik
[not found] ` <6B5F0F7A-F055-435F-ADE2-846E99649B1D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-08 12:36 ` Francesco Pizzolante
2010-01-08 12:39 ` Carsten Dominik [this message]
2010-01-08 12:43 ` Carsten Dominik
2010-01-10 9:20 ` Carsten Dominik
[not found] ` <0929970B-35B4-495A-A972-985AF9FF1B91-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-03-22 14:20 ` Francesco Pizzolante
2010-03-23 8:06 ` Carsten Dominik
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=E33721E1-E928-4FA1-B20C-676C341573A4@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fpz@missioncriticalit.com \
/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).