Re: [O] problem with code blocks
Aloha Thomas,
Thanks for the suggestion, but the problem persists!
Only replacing the "0" with an "a" helps.
--
#+LaTeX_CLASS: beamer
#+startup: beamer
* Lanx
** title
#+BEGIN_Example perl
grep { $_ ->[a] } # <- 0 fails
X{1,2,3} X{1,2,3} X{1,2,3};
#+END_Example
--
type C-c C-e d (or C-c C-e L)
Re: [O] Unicode and Latex export
Hi Seb,
On Mon, Aug 8, 2011 at 8:13 AM, Sebastien Vauban
wrote:
> For the sake of completeness, please know you can use PDFLaTeX and UTF-8 -- I
> do it for all my documents -- by having "\usepackage[utf8x]{inputenc}"
> inserted at the right place(TM).
>
> Normally, if your Org files are UTF-8, this should even be automatic, thanks
> to the line:
>
> \\usepackage[AUTO]{inputenc}
>
> in `org-export-latex-classes'.
>
I believe you mean `org-export-latex-default-packages-alist'?
Everything seems fine with my settings "(("AUTO" "inputenc" t)..)",
but the exported latex code has this:
\usepackage[utf8]{inputenc}
I edited the tex file to utf8x and everything works wonderfully. Any
ideas how I could get this working?
> Best regards,
> Seb
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Unicode and Latex export
Hi Suvayu,
suvayu ali wrote:
> Since I am a science student, I end up using lots of unicode
> characters for Greek and mathematical symbols. I usually read my notes
> in Emacs itself, unicode makes this a much nicer experience. However
> sometimes there is a need to export to html or pdf. Exporting to html
> works great with this, but I run into problems with missing characters
> when I export to latex.
>
> So my question is, is there a convenient way to translate the unicode
> characters into their corresponding latex commands for latex export
> and keep the unicode characters as is in the org file or for html
> export?
For the sake of completeness, please know you can use PDFLaTeX and UTF-8 -- I
do it for all my documents -- by having "\usepackage[utf8x]{inputenc}"
inserted at the right place(TM).
Normally, if your Org files are UTF-8, this should even be automatic, thanks
to the line:
\\usepackage[AUTO]{inputenc}
in `org-export-latex-classes'.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Help confirming odt->doc bug (Was Re: [odt] User-visible improvements)
Jambunathan K writes: >> I pushed few user-visible improvements to org-lparse/org-odt a few >> minutes ago. With these changes an exported document could be >> post-processed to another format (using an external converter) with just >> a single command (i.e., you no longer have to launch OpenOffice and do >> "Save As" etc) > > This addition seems to be bearing fruit immediately. I just reported a > problematic behaviour with org->odt->doc conversion in LibreOffice > mailing list. See > > http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/14739 > > I am using OpenOffice.org-3.2.1 (OOO20m18/Build:9502). I have pushed an alternative implementation + workaround that doesn't trigger this bug. Please update your local copies. > Does anyone else see the reported behaviour with recent LibreOffice > builds? I am surprised that no one has complained about this problematic > behaviour yet. Is it that people in this list (and their friends) have > actually shifted to OpenDocument formats and don't rely on Word > anymore. Or Is it that users simply "hand fix" the generated document. > > Jambunathan K. > > --
Re: [O] Help confirming odt->doc bug (Was Re: [odt] User-visible improvements)
Achim Gratz writes: > Jambunathan K writes: >> Does anyone else see the reported behaviour with recent LibreOffice >> builds? > > The behaviour seems to be the same in LibreOffice3.3.3. Thanks for confirming this. > Regards, > Achim. --
Re: [O] Bug: Column view in the agenda does not clean up ITEM [7.7]
Hi Christian, Christian Schmidt wrote: > I have got an issue with the column view in the agenda. In version > 7.5 I could clean up the column "ITEM" by setting the variable > org-agenda-columns-remove-prefix-from-item. > > As far as I understood, this variable is depricated since version 7.6 > and the functionality is somehow replaced by the function > org-columns-cleanup-item in the file org-colview.el. > > Unfortunately this does not work in the agenda view. > > > I would like to give a minimal example: > > * NEXTACTION [#B] Test :Tag: > SCHEDULED: <2011-08-07 So> > > Directly using column view in this buffer via "CTRL-c CTRL-x CTRL-c" > yields to: > > NEXTACTION | B | * Test :Tag: | :Tag: | | | 2011-08-07 So | > > > Like expexted the word "NEXTACTION" and the priority "B" are cleaned > up from the column ITEM. This is the desired behaviour. > > > When using the agenda view with "CTRL-c CTRL-a L" on this buffer we > get in a seperate buffer: > > Sunday 7 August 2011 > Scheduled: NEXTACTION [#B] Test :Tag: > > > Now I use column view on this agenda via "CTRL-c CTRL-x CTRL-c" and > end up with in the seperate buffer: > > NEXTACTION | B | NEXTACTION [#B] Test :Tag: | :Tag: | | | 2011-08-07 So | > > Thus we still have the unwanted "NEXTACTION [#B]" in the ITEM-column. I (would have) thought that, when having a column dedicated for tags, the tag would as well be removed from the "headline" column (3^rd one, in your example). Is there a good reason it's not working like that for the tag as well? Best regards, Seb -- Sebastien Vauban
Re: [O] Refiling list items
Would someone throw me a bone? I couldn't find anything on gmane, but I my gmane-fu isn't the strongest. :D On Sat, Aug 6, 2011 at 14:54, Jeff Horn wrote: > Should org-refile be able to refile list items? I suspect it would be > non-trivial to add this functionality if it isn't already there, but I > feel a bit overwhelmed keeping notes as headlines, particularly > because I like to leave soft wrapping off and have a hard wrap at 80 > columns. > > ,[ Sample Outline ] > | * Headline 1 > | - List level 1 > | - List level 2 > | * Headline 2 > | Some text. > ` > > If I attempt to refile the item "- List level 1" to the second headline, I get > > ,[ Mangled Outline ] > | * Headline 2 > | Some text. > | ** Headline 1 > | - List level 1 > | - List level 2 > ` > > when the following is expected > > ,[ Expected Outline ] > | * Headline 1 > | * Headline 2 > | - List level 1 > | - List level 2 > | Some text. > ` > > Where the list items appear before or after "Some text." depending on > refile variables. > > -- > Jeffrey Horn > http://www.failuretorefrain.com/jeff/ > -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
Re: [O] ebib configuration for org-bibtex
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all,
>>
>> I'm trying, partially successfully, to configure org-bibtex so it mimics
>> some useful features of ebib. In particular, I'm wanting to add several
>> optional fields that ebib uses.
>>
>>
>> I have this in .emacs:
>>
>> #+begin_src emacs-lisp :tangle yes
>> (dolist (type org-bibtex-types)
>> (push :url (cdr (assoc :optional (cdr type
>> (push :annote (cdr (assoc :optional (cdr type
>> (push :abstract (cdr (assoc :optional (cdr type
>> (push :keywords (cdr (assoc :optional (cdr type
>> (push :file (cdr (assoc :optional (cdr type
>> )
>>
>> (push (cons :url "A URL for the reference") org-bibtex-fields)
>> (push (cons :annote "Annotation is typically not exported")
>> org-bibtex-fields)
>> (push (cons :abstract "Abstract for annotated bibliography")
>> org-bibtex-fields)
>> (push (cons :keywords "Keywords for sorting with ebib") org-bibtex-fields)
>> (push (cons :file "A local file path used by ebib to open the
>> reference in an appropriate application") org-bibtex-fields)
>> #+end_src
>>
>> Most of it works fine, but the optional :file field doesn't respect its
>> argument. So, the following entry in the Org-mode file:
>>
>
> Hi Tom,
>
> The :file property is treated in a special manner when Org-mode resolves
> properties (notice it is an element of the `org-special-properties'
> variable). I've just pushed up a change which temporarily removes :file
> from this list while resolving bibtex entries. This change should fix
> your reported problem -- please let me know if it doesn't. If any other
> elements of `org-special-properties' seem likely to cause problems we
> can temporarily remove them as well.
>
> Best -- Eric
Hi Eric,
I think this fix is causing some mischief. In the Org-mode file where
a :FILE: property is set to preza-thesis.pdf R source code blocks
misbehave, as follows:
#+source: land-sale-plot
#+begin_src R :var y=sales
str(y)
#+end_src
#+results: land-sale-plot
[[file:preza-thesis.pdf]]
All the best,
Tom
>
>>
>> ** Active Documents with Org-mode
>>:PROPERTIES:
>>:TITLE:Active Documents with Org-mode
>>:TYPE: article
>>:AUTHOR: Eric Schulte and Dan Davison
>>:JOURNAL: Computing in Science and Engineering
>>:YEAR: 2011
>>:VOLUME: 13
>>:NUMBER: 3
>>:PAGES:2--9
>>:MONTH:May/June
>>:URL: http://www.cs.unm.edu/~eschulte/data/CISE-13-3-SciProg.pdf
>>:FILE: Schulte-Davison-Babel.pdf
>>:CUSTOM_ID: schulte11:_activ_docum_org
>>:END:
>>
>> is exported with org-bibtex like this:
>>
>> @article{schulte11:_activ_docum_org,
>> author = {Eric Schulte and Dan Davison},
>> title ={Active Documents with Org-mode},
>> journal = {Computing in Science and Engineering},
>> year = 2011,
>> file = {/Users/dk/Public/projects/916-rr/rr.org},
>> url =
>> {http://www.cs.unm.edu/~eschulte/data/CISE-13-3-SciProg.pdf},
>> volume = 13,
>> number = 3,
>> pages ={2--9},
>> month ={May/June}
>> }
>>
>> Pressing f in ebib now just takes me back to the Org-mode file, rather
>> than launching a pdf reader on my local copy of the article.
>>
>> Any ideas how I can achieve my goal?
>>
>> All the best,
>> Tom
--
Thomas S. Dye
http://www.tsdye.com
[O] What's the license for worg.css?
Hi, What's the license for worg.css? I would like to use it at the company I work for if that's allowed. Thanks, Jeff
Re: [O] problem with code blocks
LanX writes:
> Hi
>
> hier a ECM which fails
>
> ---
> #+LaTeX_CLASS: beamer
> #+startup: beamer
>
> * title
>
> #+BEGIN_Example: perl
> grep { $_ ->[0] }
> X{1,2,3} X{1,2,3} X{1,2,3};
> #+END_Example:
> ---
>
> originally I tried Begin_src but I wanted to be sure that it has not to do
> with highlighting.
>
> I get the message "if: Wrong type argument: stringp, nil"
>
> But deleting the [0] solves the problem
>
> -
> #+BEGIN_Example: perl
> grep { $_ -> }
> X{1,2,3} X{1,2,3} X{1,2,3};
> #+END_Example:
> ---
>
> Does org try to find footnotes in code blocks?
>
> Any help appreciated!!!
>
> Cheers
> Rolf
Aloha Rolf,
Try removing the colons after Example. The following exports fine here:
* Lanx
#+LaTeX_CLASS: beamer
#+startup: beamer
** title
#+BEGIN_Example perl
grep { $_ ->[0] }
X{1,2,3} X{1,2,3} X{1,2,3};
#+END_Example
hth,
Tom
> Hihier a ECM which fails---#+LaTeX_CLASS:
> beamer#+startup: beamer* title#+BEGIN_Example: perl grep { $_ ->[0] }
> X{1,2,3} X{1,2,3} X{1,2,3};#+END_Example:
> ---originally I tried Begin_src but I wanted to be
> sure that it has not to do with highlighting.I get the message "if: Wrong
> type argument: stringp, nil"But deleting the [0] solves the problem
> -#+BEGIN_Example: perl
> grep { $_ -> }
> X{1,2,3} X{1,2,3} X{1,2,3};
> #+END_Example:
> ---
> Does org try to find footnotes in code blocks?Any help
> appreciated!!!Cheers Rolf
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] problem with code blocks
Sorry forgot to mention that I tried to export it to pdf or latex!
2011/8/8 LanX
> Hi
>
> hier a ECM which fails
>
> ---
> #+LaTeX_CLASS: beamer
> #+startup: beamer
>
> * title
>
> #+BEGIN_Example: perl
> grep { $_ ->[0] }
> X{1,2,3} X{1,2,3} X{1,2,3};
> #+END_Example:
> ---
>
> originally I tried Begin_src but I wanted to be sure that it has not to do
> with highlighting.
>
> I get the message "if: Wrong type argument: stringp, nil"
>
> But deleting the [0] solves the problem
>
> -
> #+BEGIN_Example: perl
> grep { $_ -> }
> X{1,2,3} X{1,2,3} X{1,2,3};
> #+END_Example:
> ---
>
> Does org try to find footnotes in code blocks?
>
> Any help appreciated!!!
>
> Cheers
> Rolf
>
Re: [O] Beamer latex export of included partial files
Thanks I will try it out.
2011/8/7 Rasmus
> LanX writes:
>
> > Is there a recommended way to do this?
>
> From the beamer manual:
>
> ┏━━━┫ 4.3.3 Ways of Improving Compilation Speed ┃
> ┃ While working on your presentation, it may sometimes be useful to TeX
> ┃ your .tex file quickly and have the presentation contain only the most
> ┃ important information. This is especially true if you have a slow
> ┃ machine. In this case, you can do several things to speed up the
> ┃ compilation. First, you can use the draft class option.
> ┃
> ┃ #+begin_src latex
> ┃ \documentclass[draft]{beamer}
> ┃ #+end_src
> ┃
> ┃ Causes the headlines, footlines, and sidebars to be replaced by gray
> ┃ rectangles (their sizes are still computed, though). Many other
> ┃ packages, including pgf and hyperref, also “speed up” when this option
> ┃ is given.
> ┃
> ┃ Second, you can use the following command:
> ┃ #+begin_src latex
> ┃ \includeonlyframes{⟨frame label list⟩}
> ┃ #+end_src
> ┃
> ┃ This command behaves a little bit like the \includeonly command: Only
> ┃ the frames mentioned in the list are included. All other frames are
> ┃ suppressed. Nevertheless, the section and subsection commands are still
> ┃ executed, so that you still have the correct navigation bars. By
> ┃ labeling the current frame as, say, current and then saying
> ┃ \includeonlyframes{current}, you can work on a single frame quickly.
> ┃
> ┃ The ⟨frame label list⟩ is a comma-separated list (without spaces) of the
> ┃ names of frames that have been labeled. To label a frame, you must pass
> ┃ the option label=⟨name⟩ to the \frame command or frame environment.
> ┃
> ┃ Example:
> ┃ #+begin_src latex
> ┃ \includeonlyframes{example1,example3}
> ┃ \frame[label=example1]
> ┃ {This frame will be included. }
> ┃ \frame[label=example2]
> ┃ {This frame will not be included. }
> ┃ \frame{This frame will not be included.}
> ┃ \againframe{example1} % Will be included
> ┃ #+end_latex
> ┗━━━
>
> --
> Sent from my Emacs
>
>
>
[O] problem with code blocks
Hi
hier a ECM which fails
---
#+LaTeX_CLASS: beamer
#+startup: beamer
* title
#+BEGIN_Example: perl
grep { $_ ->[0] }
X{1,2,3} X{1,2,3} X{1,2,3};
#+END_Example:
---
originally I tried Begin_src but I wanted to be sure that it has not to do
with highlighting.
I get the message "if: Wrong type argument: stringp, nil"
But deleting the [0] solves the problem
-
#+BEGIN_Example: perl
grep { $_ -> }
X{1,2,3} X{1,2,3} X{1,2,3};
#+END_Example:
---
Does org try to find footnotes in code blocks?
Any help appreciated!!!
Cheers
Rolf
Re: [O] Schedule event
Carsten Dominik writes: > Why do you want this special interface for setting an event date. > How is that better than `C-c .'? Is it that you don't need to > position the cursor? Yes, that was my original reason. But your suggestion of adding a special keyword for events is another good reason. Also, as recently discussed, consistent formatting conventions and clarifying the frequently-misunderstood issue of SCHEDULED vs. no-keyword active timestamps are good reasons. Regards, Jason
Re: [O] Merge org-7.7 into emacs
Memnon Anon googlemail.com> writes: > > Hi, > > Just a heads up: > >http://permalink.gmane.org/gmane.emacs.devel/142944 > > I don't know anything about this, but maybe something can be said/done > about it while Bastien enjoys his vacation? > I'm afraid I'm mentioned twice. The first has to do with copyright assignment; I've begun the process described in org-contribute.org to assign copyright to the FSF. The second has to do with an incomplete ChangeLog entry for one of my patches (commit 49e6bc899758114d6d29e69a8f9e40798d26782b). I don't know the best to clean this up, since the ChangeLog is derived from the git log. But here's a ChangeLog entry that I think would have been valid: commit 49e6bc899758114d6d29e69a8f9e40798d26782b Author: Ethan Ligon Date: Sat Apr 9 18:39:35 2011 +0200 Fix for html & docbook export of description list items * lisp/org-html.el (org-html-export-list-line): Fix regexp for detecting description lists to allow "::" marker to be last visible element at end of line. * lisp/org-docbook.el (org-docbook-export-list-line): Fix regexp for detecting description lists to allow "::" marker to be last visible element at end of line. The problem is illustrated by the following example: * Illustration of bug in html export - This has a space after the colons :: so will work in latex and html - This doesn't have a space after the colons ::so is an invalid description item according to the org manual. Won't work in html or docbook. Will nevertheless work in latex, provided /first/ description item is valid. - Has a terminating space :: - So it works in both html and latex export! - Even though it's difficult to distinguish from the next example. - Lacks a terminating space :: - At present, *doesn't* work in html or docbook export, does in latex. This is the case that the following patch fixes. -Ethan
[O] Bug: Column view in the agenda does not clean up ITEM [7.7]
Hi,
I have got an issue with the column view in the agenda. In version
7.5 I could clean up the column "ITEM" by setting the variable
org-agenda-columns-remove-prefix-from-item.
As far as I understood, this variable is depricated since version 7.6
and the functionality is somehow replaced by the function
org-columns-cleanup-item in the file org-colview.el.
Unfortunately this does not work in the agenda view.
I would like to give a minimal example:
* NEXTACTION [#B] Test:Tag:
SCHEDULED: <2011-08-07 So>
Directly using column view in this buffer via "CTRL-c CTRL-x CTRL-c"
yields to:
NEXTACTION | B | * Test :Tag: | :Tag: | | | 2011-08-07 So |
Like expexted the word "NEXTACTION" and the priority "B" are cleaned
up from the column ITEM. This is the desired behaviour.
When using the agenda view with "CTRL-c CTRL-a L" on this buffer we
get in a seperate buffer:
Sunday 7 August 2011
Scheduled: NEXTACTION [#B] Test :Tag:
Now I use column view on this agenda via "CTRL-c CTRL-x CTRL-c" and
end up with in the seperate buffer:
NEXTACTION | B | NEXTACTION [#B] Test :Tag: | :Tag: | | | 2011-08-07 So |
Thus we still have the unwanted "NEXTACTION [#B]" in the ITEM-column.
I would really appreciate your help, because this behaviour inhibits
me from using versions 7.6 and later.
Thanks in advance!
Please find below my org-mode configuration.
Best,
Christian
Emacs : GNU Emacs 23.3.1 (i386-mingw-nt6.1.7600)
of 2011-03-10 on 3249CTO
Package: Org-mode version 7.7
current state:
==
(setq
org-export-latex-after-initial-vars-hook
'(org-beamer-after-initial-vars)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
org-export-latex-format-toc-function
'org-export-latex-format-toc-default
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-todo-keywords '("NEXTACTION" "WAITING" "MAYBE" "DONE")
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-hide-drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-mode-hook '((lambda nil (org-add-hook (quote
change-major-mode-hook) (quote org-show-block-all) (quote append)
(quote local)))
(lambda nil (org-add-hook (quote change-major-mode-hook)
(quote org-babel-show-result-all) (quote append) (quote
local)))
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-export-interblocks '((lob org-babel-exp-lob-one-liners) (src
org-babel-exp-inline-src-blocks))
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-occur-hook '(org-first-headline-recenter)
org-from-is-user-regexp nil
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-columns-default-format "%TODO %PRIORITY %50ITEM %ALLTAGS
%6Effort{:} %DEADLINE %SCHEDULED"
org-export-latex-final-hook '(org-beamer-amend-header
org-beamer-fix-toc org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-export-blocks '((src org-babel-exp-src-block nil) (comment
org-export-blocks-format-comment t) (ditaa
org-export-blocks-format-ditaa nil)
(dot org-export-blocks-format-dot
nil))
)
[O] Org: HTML export breaks when you have %20 in the URL:
Org export to html when exporting image links fails --- if you have %20 (url-encoded space) in the URL. The anchor around the img link gets broken. Here is an example: #+ATTR_HTML:alt="Waiting to leave for White Plains" align="center" height="384" [[http://lh5.ggpht.com/-LC4N-cVAb8o/TjrW8pgkcXI/Cws/F0fdPijBcRE/TVJA%2520015.jpg]] If you translate the above to html through org export you get this broken markup: [[http://lh5.ggpht.com/-LC4N-cVAb8o/TjrW8pgkcXI/Cws/F0fdPijBchttp://lh5.ggpht.com/-LC4N-cVAb8o/TjrW8pgkcXI/Cws/F0fdPijBcRE/TVJA 015.jpg" alt="Waiting to leave for White Plains" align="center" height="384" />TVJA%2520015.jpg][http://lh5.ggpht.com/-LC4N-cVAb8o/TjrW8pgkcXI/Cws/F0fdPijBcRE/TVJA%2520015.jpg]] Note that we didn't get a well-formed .. wrapping the image url. -- Best Regards, --raman
Re: [O] Unicode and Latex export
Hi Florian,
On Sun, Aug 7, 2011 at 8:41 PM, Florian Beck wrote:
>>
>> CP channel: Bs⁰ -> Ds⁻ K⁺ / Ds⁺ K⁻ (interference b/w decay modes of
>> Bs⁰ or anti-Bs⁰)
>
> In this case, XeLaTeX with
>
> \setmainfont{DejaVu Serif}
>
> in the preamble seems to give reasonable results.
>
Indeed! The output is exactly what I was hoping to achieve.
>>
>> I think I'll try to find an alternate solution. Maybe I'll end up
>> writing that unicode to latex translation function in elisp.
>
> I did something like that for muse-mode. IIRC the main problem was that
> the translation has to be context sensitive (ie math mode vs. text
> mode). Let me know if you are interested, maybe I can dig something out.
Since the above resolves my issue very well, that will not be necessary.
Probably I'll take it up when I have more free time. Thanks a lot to
both you and Chris for your help, appreciate it a lot. :)
>
> --
> Florian Beck
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Unicode and Latex export
suvayu ali writes:
> On Sun, Aug 7, 2011 at 8:07 PM, Florian Beck wrote:
>> But if you mostly have single characters it might be too much of a hassle.
>
> It does indeed sound like too much hassle for my use case. I only use it
> for scientific note taking. For example I would write something like
> this:
>
>
> CP channel: Bs⁰ -> Ds⁻ K⁺ / Ds⁺ K⁻ (interference b/w decay modes of
> Bs⁰ or anti-Bs⁰)
In this case, XeLaTeX with
\setmainfont{DejaVu Serif}
in the preamble seems to give reasonable results.
>
> I think I'll try to find an alternate solution. Maybe I'll end up
> writing that unicode to latex translation function in elisp.
I did something like that for muse-mode. IIRC the main problem was that
the translation has to be context sensitive (ie math mode vs. text
mode). Let me know if you are interested, maybe I can dig something out.
>
> Thanks a lot for the pointers though.
--
Florian Beck
Re: [O] Merge org-7.7 into emacs
Hi, On Sun, Aug 7, 2011 at 7:54 PM, Memnon Anon wrote: > Hi, > > Just a heads up: > > http://permalink.gmane.org/gmane.emacs.devel/142944 > > I don't know anything about this, but maybe something can be said/done > about it while Bastien enjoys his vacation? > I see my name in there. I only submitted a small (touching less than 20 lines) documentation patch[1]. Would I still need to sign the copyright assignment? If so, how do I initiate the process? > Memnon > Footnotes: [1] commit 71d871f96e3e916a9542daeb6d3b102a77d9b068 Author: Suvayu Ali Date: Mon Jul 4 15:03:06 2011 +0200 Improve "Images in LaTeX export" documentation * Mention use of keywords like multicolumn and float * Remove previous mention of hack with placement option as per comments on the mailing list. The hack is better suited for Worg. doc/org.texi | 34 -- 1 files changed, 16 insertions(+), 18 deletions(-) -- Suvayu Open source is the future. It sets us free.
Re: [O] Unicode and Latex export
On Sun, Aug 7, 2011 at 8:07 PM, Florian Beck wrote: > But if you mostly have single characters it might be too much of a hassle. It does indeed sound like too much hassle for my use case. I only use it for scientific note taking. For example I would write something like this: CP channel: Bs⁰ -> Ds⁻ K⁺ / Ds⁺ K⁻ (interference b/w decay modes of Bs⁰ or anti-Bs⁰) I think I'll try to find an alternate solution. Maybe I'll end up writing that unicode to latex translation function in elisp. Thanks a lot for the pointers though. -- Suvayu Open source is the future. It sets us free.
Re: [O] Unicode and Latex export
suvayu ali writes:
> On Sun, Aug 7, 2011 at 6:50 PM, suvayu ali
> wrote:
>>> BTW, this only works if you use a font that provides all the characters
>>> you need (and looks nice enough for your taste).
>>
>> I don't usually customise my fonts and go with the default latex
>> fonts. Do you have any suggestions what fonts that would be
>> appropriate here? I tried using XITS, but that didn't help.
>
> I should clarify, when I say didn't work I mean xelatex couldn't find
> the fonts although I have them installed.
Not sure. XeTeX uses the fonts you have installed on your system, not
those for TeX. Everything in M-: (font-family-list) should work.
Maybe one of the DejaVu fonts? Generally, though, universal fonts aren't the
best choice.
Here is what I do. Create a custom link style for export with XeLaTeX:
(org-add-link-type "uc" 'ignore 'org-unicode-export)
(defun org-unicode-export (path desc format)
"Export unicode characters."
(cond
((eql format 'html) (format "%s" desc))
((eql format 'latex)
(format "{\\fontspec[Scale=MatchLowercase]{%s}%s}"
path desc))
(t desc)))
And write [[uc:Code2000][⫳]] to use Code2000 as a font.
I use it mostly for greek words, e.g.
[[uc:Alexander][φύσις κρύπτεσθαι φιλεῖ]]
But if you mostly have single characters it might be too much of a hassle.
--
Florian Beck
[O] Merge org-7.7 into emacs
Hi, Just a heads up: http://permalink.gmane.org/gmane.emacs.devel/142944 I don't know anything about this, but maybe something can be said/done about it while Bastien enjoys his vacation? Memnon
Re: [O] Unicode and Latex export
On Sun, Aug 7, 2011 at 6:50 PM, suvayu ali wrote: >> BTW, this only works if you use a font that provides all the characters >> you need (and looks nice enough for your taste). > > I don't usually customise my fonts and go with the default latex > fonts. Do you have any suggestions what fonts that would be > appropriate here? I tried using XITS, but that didn't help. I should clarify, when I say didn't work I mean xelatex couldn't find the fonts although I have them installed. -- Suvayu Open source is the future. It sets us free.
Re: [O] Unicode and Latex export
Hi Florian,
On Sun, Aug 7, 2011 at 6:33 PM, Florian Beck wrote:
>> My lisp is not very good, but what is the need for such an extensive
>> setup? Isn't setting org-latex-to-pdf-process to xelatex enough to
>> switch packends?
>
> It is, more or less. XeLaTeX needs a different header, that is what the
> instructions set up. However, I would recommend keeping it simple and
> put your packages etc in your own style file.
>
> In `org-export-latex-classes', replace
>
> "\\documentclass[11pt]{article}"
>
> with
>
> "[NO-DEFAULT-PACKAGES]
> \\documentclass[11pt]{article}\n\\usepackage{myxe}"
>
> and put everything you need in myxe.sty.
>
That is a good solution. I think I will consider this.
> BTW, this only works if you use a font that provides all the characters
> you need (and looks nice enough for your taste).
I don't usually customise my fonts and go with the default latex
fonts. Do you have any suggestions what fonts that would be
appropriate here? I tried using XITS, but that didn't help.
> Alternatively, you could
> use `org-export-latex-final-hook' and write a function that translates
> unicode characters to latex code.
>
I have considered this, but as I mentioned I am not well versed in
lisp. Going this route might be more fun, but not good for work. ;)
Thanks,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Unicode and Latex export
Hello Chris, On Sun, Aug 7, 2011 at 6:36 PM, Christopher Witte wrote: > Did you remember to set the variable > > #+LATEX_CMD: xelatex > > at the top of the org file? > I forgot to do that. However correcting my error doesn't help either. I get a message like this in the output buffer: Latexmk: Run number 1 of rule 'pdflatex' Latexmk: Running 'xelatex -interaction=batchmode "/home/jallad/tmp/analysis.tex"' This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) restricted \write18 enabled. entering extended mode Latexmk: References changed. Latexmk: References changed. Collected error summary (may duplicate other messages): pdflatex: Command for 'pdflatex' gave return code 256 Latexmk: Use the -f option to force complete processing. However this time a PDF is produced but with the unicode fonts missing (as was happening with pdflatex). > > Chris. -- Suvayu Open source is the future. It sets us free.
Re: [O] Beamer latex export of included partial files
LanX writes:
> Is there a recommended way to do this?
>From the beamer manual:
┏━━━┫ 4.3.3 Ways of Improving Compilation Speed ┃
┃ While working on your presentation, it may sometimes be useful to TeX
┃ your .tex file quickly and have the presentation contain only the most
┃ important information. This is especially true if you have a slow
┃ machine. In this case, you can do several things to speed up the
┃ compilation. First, you can use the draft class option.
┃
┃ #+begin_src latex
┃ \documentclass[draft]{beamer}
┃ #+end_src
┃
┃ Causes the headlines, footlines, and sidebars to be replaced by gray
┃ rectangles (their sizes are still computed, though). Many other
┃ packages, including pgf and hyperref, also “speed up” when this option
┃ is given.
┃
┃ Second, you can use the following command:
┃ #+begin_src latex
┃ \includeonlyframes{⟨frame label list⟩}
┃ #+end_src
┃
┃ This command behaves a little bit like the \includeonly command: Only
┃ the frames mentioned in the list are included. All other frames are
┃ suppressed. Nevertheless, the section and subsection commands are still
┃ executed, so that you still have the correct navigation bars. By
┃ labeling the current frame as, say, current and then saying
┃ \includeonlyframes{current}, you can work on a single frame quickly.
┃
┃ The ⟨frame label list⟩ is a comma-separated list (without spaces) of the
┃ names of frames that have been labeled. To label a frame, you must pass
┃ the option label=⟨name⟩ to the \frame command or frame environment.
┃
┃ Example:
┃ #+begin_src latex
┃ \includeonlyframes{example1,example3}
┃ \frame[label=example1]
┃ {This frame will be included. }
┃ \frame[label=example2]
┃ {This frame will not be included. }
┃ \frame{This frame will not be included.}
┃ \againframe{example1} % Will be included
┃ #+end_latex
┗━━━
--
Sent from my Emacs
Re: [O] Unicode and Latex export
On 08/07/2011 02:15 PM, suvayu ali wrote: Hello Christopher, On Sun, Aug 7, 2011 at 12:01 PM, Christopher Witte wrote: You could try using XeLaTeX, which supports unicode. Instructions for setting it up with org-mode are here http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export My lisp is not very good, but what is the need for such an extensive setup? Isn't setting org-latex-to-pdf-process to xelatex enough to switch packends? In any case, I tried evaluating the provided code in a scratch buffer and processing to pdf (C-c C-e p). But it keeps failing. From the error it seems org is still trying latex instead of xelatex and no pdf is produced. Do you have any ideas about what could I doing wrong? Error: Latexmk: Run number 1 of rule 'latex' Latexmk: Running 'latex -interaction=batchmode "/home/jallad/org/analysis.tex"' This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) restricted \write18 enabled. entering extended mode Latexmk: References changed. Latexmk: References changed. Latexmk: References changed. Collected error summary (may duplicate other messages): latex: Command for 'latex' gave return code 256 Latexmk: Use the -f option to force complete processing. Chris. Thanks a lot for your response. Did you remember to set the variable #+LATEX_CMD: xelatex at the top of the org file? Chris.
Re: [O] Unicode and Latex export
suvayu ali writes:
> Hello Christopher,
>
> On Sun, Aug 7, 2011 at 12:01 PM, Christopher Witte wrote:
>> You could try using XeLaTeX, which supports unicode. Instructions for
>> setting it up with org-mode are here
>> http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export
>>
>
> My lisp is not very good, but what is the need for such an extensive
> setup? Isn't setting org-latex-to-pdf-process to xelatex enough to
> switch packends?
It is, more or less. XeLaTeX needs a different header, that is what the
instructions set up. However, I would recommend keeping it simple and
put your packages etc in your own style file.
In `org-export-latex-classes', replace
"\\documentclass[11pt]{article}"
with
"[NO-DEFAULT-PACKAGES]
\\documentclass[11pt]{article}\n\\usepackage{myxe}"
and put everything you need in myxe.sty.
BTW, this only works if you use a font that provides all the characters
you need (and looks nice enough for your taste). Alternatively, you could
use `org-export-latex-final-hook' and write a function that translates
unicode characters to latex code.
--
Florian Beck
[O] Beamer latex export of included partial files
Hi I'm working on a fairly large beamer presentation and the turn-around times from edit till pdf-view are fairly long. Are there any recommended ways to shorten that? I tried to split my org-file at the top level into a master and several others which are inserted at export-time via "#+include" The idea is that I can work on single chapters and speed up processing time. Unfortunately all beamer settings of the master get lost when I export one of the lower level files. Including the settings for each chapter from an individual file doesn't work. Is there a recommended way to do this? Cheers Rolf
Re: [O] Unicode and Latex export
Hello Christopher, On Sun, Aug 7, 2011 at 12:01 PM, Christopher Witte wrote: > You could try using XeLaTeX, which supports unicode. Instructions for > setting it up with org-mode are here > http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export > My lisp is not very good, but what is the need for such an extensive setup? Isn't setting org-latex-to-pdf-process to xelatex enough to switch packends? In any case, I tried evaluating the provided code in a scratch buffer and processing to pdf (C-c C-e p). But it keeps failing. From the error it seems org is still trying latex instead of xelatex and no pdf is produced. Do you have any ideas about what could I doing wrong? Error: Latexmk: Run number 1 of rule 'latex' Latexmk: Running 'latex -interaction=batchmode "/home/jallad/org/analysis.tex"' This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) restricted \write18 enabled. entering extended mode Latexmk: References changed. Latexmk: References changed. Latexmk: References changed. Collected error summary (may duplicate other messages): latex: Command for 'latex' gave return code 256 Latexmk: Use the -f option to force complete processing. > Chris. Thanks a lot for your response. -- Suvayu Open source is the future. It sets us free.
[O] Exporting images in included Org file (bug)
A while ago I reported images not being included exports from Org files that have #+INCLUDEd Org files. I think the images are being searched from relative path of the top Org file, and not respecting the different path of the included Org files. Described by me here: http://lists.gnu.org/archive/html/emacs-orgmode/2011-04/msg00265.html and reproduced by Robert Goldman here: http://lists.gnu.org/archive/html/emacs-orgmode/2011-05/msg00025.html I've checked the 7.7 bug fixes but it hasn't been mentioned. Can I please report it again in case it's slipped off the radar? Thanks John
Re: [O] Unicode and Latex export
On Sun 07 Aug 2011 01:25:32 AM CEST, suvayu ali wrote: So my question is, is there a convenient way to translate the unicode characters into their corresponding latex commands for latex export and keep the unicode characters as is in the org file or for html export? You could try using XeLaTeX, which supports unicode. Instructions for setting it up with org-mode are here http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export Chris. -- Dr Christopher Witte Postdoctoral Research Fellow Molecular Imaging Group Leibniz-Institut für Molekulare Pharmakologie (FMP) Campus Berlin-Buch Robert-Roessle-Str. 10 13125 Berlin, Germany Phone: 00493094793-279
