[O] org-ref: renaming/moving an entire pdf library according to a bibtex file
Hi, I just discovered org-ref recently and would like to manage my entire pdf library with it. Basically, my set-up is a folder containing many scientific papers in pdf, and a bibtex file containing most of the entries related to these pdfs. My bibtex file is well linked to org-ref and I have already moved several pdfs into the bibtex-pdfs/ folder so that they can be opened easily using their bibtex entry. However, I found this to be a lot of work for moving/linking only a few pdfs. I'm wondering if there is a way to automate that. When I'm moving one of my pdfs onto the emacs window with the bibliography opened, it tries to download the pdf from the web using the doi (if found). However, is there a way to bypass the download (because I already have the file) and to directly move/rename the pdf to the bibtex-pdfs/ folder while validating my bibtex entry (or creating a new one, does not matter) ? Thanks for helping, Martin
Re: [O] Sharing documents with bibtex bibliography from org to non-org users
Hi Ken, I tried the Pandoc solution first and the result appears quite
satisfying to me. In the docx document, I can see citations,
bibliography, figures and even equations. I will keep note of your first
suggestion if I face issues with pandoc.
Thanks,
Martin
On 08/16/2016 07:41 AM, Ken Mankoff wrote:
Hi Martin,
The workflow I've been using for the past few months is this:
1) Export to ODT and then use LibreOffice to convert ODT to DOC with,
(use-package ox-odt
:ensure nil
:config (progn
(setq org-odt-preferred-output-format "doc")
(setq org-odt-convert-processes
'(("LibreOffice"
"/Applications/LibreOffice.app/Contents/MacOS/soffice --headless --convert-to %f%x
%i")
Note that LibreOffice *cannot* be open/running while exporting, or the
conversion fails.
2) Clean up the DOC file using the following LibreOffice macro (you can give
its own toolbar button for easy access). This removes some LaTeX-specific
formatting (examples: \( and \), \begin{equation}, \ref, etc.) and replaces
some (examples: ^{-2} to -2).
Sub ReplaceTeXStrings
Dim mTeXStringsNO(99) As String
Dim mTeXStringsCNVfrom(99) As String
Dim mTexStringsCNVto(99) As String
Dim n As Long
Dim oDocument As Object
Dim oReplace As Object
mTeXStringsNO() = Array("\(", "\)", "\ref", "\mathrm", _
"\begin{equation}", "\end{equation}", "\left", "\right", _
"\singlespacing", "\doublespacing", "\,")
mTeXStringsCNV() = Array("\sigma","σ", "\rho","ρ", "\sum", "∑", _
"\phi","ɸ", "\partial","∂", "\Theta","Θ", "^{th}","th", "^{{th}}","th", _
"^{-1}","-1", "^{-2}","-2", "^{2}","^2", "^{3}", "^3", "^{-3}", "^-3")
oDocument = ThisComponent
oReplace = oDocument.createReplaceDescriptor
For n = lbound(mTeXStringsNO()) To ubound(mTeXStringsNO())
oReplace.SearchString = mTexStringsNO(n)
oReplace.ReplaceString = ""
oDocument.replaceAll(oReplace)
Next n
For n = lbound(mTeXStringsCNV()) To ubound(mTeXStringsCNV()) Step 2
oReplace.SearchString = mTexStringsCNV(n)
oReplace.ReplaceString = mTexStringsCNV(n+1)
oDocument.replaceAll(oReplace)
Next n
End Sub
At this point, the DOC file is in decent shape, but equations are in raw LaTeX.
The text does say things like see Figure {fig:foo} and Equation {eq:bar}.
Figures are all numbered SEC.N, where SEC is the section number, and N restarts
at 1 each section. References appear correctly as (Someone, 1942), or inline as
Someone (1942), but there is no bibliography. It is easily readable, decently
formatted, and much better than asking a co-author to read the raw LaTeX.
3) Export to PDF and compile the final product
4) Send both PDF and DOC to co-authors. Let them know they can read and mark up
the DOC via Track Changes, but the PDF is the canonical version and should be
used when looking at Equations, Figures, Bibliography, or anything else that
appears suspect in the DOC file.
5) I manually integrate changes back into the Org file.
Alternative workflows I've used in the past include Org -> LaTeX and then using
Pandoc LaTeX -> DOCX. This version includes a bibliography, but overall I found the
DOC more poorly formatted than the above workflow. If you prefer a cut-and-paste method,
I'd consider Org -> HTML and then cut-and-paste that, rather than cut-and-paste PDF
contents.
I hope this helps,
-k.
On 2016-08-16 at 03:36, Martin Leduc <ldcm...@gmail.com> wrote:
Hi orgers,
People using org-mode or LaTeX to write scientific papers inevitably
face problems when time comes to share a manuscript with co-authors for
reviewing. Unless one decides to restrict the choice of his co-authors
based exclusively on their knowledge of LaTeX, collaborators generally
use Microsoft Word to write their documents.
One way to share LaTeX documents with non-LaTeX users is to simply
copy-paste the LaTeX file into a Word document. You can then share this
file with other people along with a pdf-compiled version of the
manuscript allowing them to see all references, bibliography, equations
and figures. This is the most convenient approach for the first author,
who can simply copy-paste back the text into a tex file after the rounds
of review and then compile the LaTeX manuscript again following some
minor debugging.
However, the latter approach may not be suitable in situations where the
document is intended to stay into a word format for whatever reason. It
could be for instance because you want to be kind with some co-au
Re: [O] Sharing documents with bibtex bibliography from org to non-org users
Hi Julian, thank you for the suggestion. I didn't know pandoc, and didn't expect to find something so near from what I was searching ! Converting the tex file to docx using pandoc, I can see the correct citations and bibliography, and even equations (in openoffice, haven't tested it with Microsoft word) and figures. I see minor issues such as the equation numbers that are not compiled (references stay as labels), but overall it is quite satisfying. On the other hand, exporting from org to odt is more or less like copy-pasting latex source code (no references, no bibliography, but... figures !) All the best, Martin On 08/16/2016 11:16 AM, Julian M. Burgos wrote: Hi Martin, The best solution I found so far is to export to latex, and then use pandoc to convert the tex document into word. You can point pandoc to your .bib file, so the bibliography gets into the word document, doing something like this: pandoc --bibliography /home/julian/Documents/org_files/myrefs.bib -o mypaper.docx mypaper.tex This works ok. Figures sometimes do not get inserted into the Word document, and there are other relatively minor issues. I have not bother looking very deeply to figure out if they can be solved, I just pass the word document to my collaborators for editing (so they can use the track changes options and so for), and I also send the pdf file (from latex) so they can see exactly how the document would look, in terms of figures and tables. When you get your reviews back, you need to manually insert them into your org document, which is a pain in the back. An alternative way is to pass the org document to your coworker, so they can edit them in word directly. They should ignore all the markup language, do not use the track changes option, and save the resulting document as a text file. Then you can incorporate the changes directly into your org file using ediff. But as you said, the markup language may turn off people that are not very friendly to some code and strange commands. A third way would be to export to odt. I think you can set the exporter so it uses libre office to convert the resulting file into .doc or .docx. I have not tried this very well, so I am not sure how this works with references, figures and tables. Hopefully somebody on the list may have a better option, All the best, Julian Martin Leduc writes: Hi orgers, People using org-mode or LaTeX to write scientific papers inevitably face problems when time comes to share a manuscript with co-authors for reviewing. Unless one decides to restrict the choice of his co-authors based exclusively on their knowledge of LaTeX, collaborators generally use Microsoft Word to write their documents. One way to share LaTeX documents with non-LaTeX users is to simply copy-paste the LaTeX file into a Word document. You can then share this file with other people along with a pdf-compiled version of the manuscript allowing them to see all references, bibliography, equations and figures. This is the most convenient approach for the first author, who can simply copy-paste back the text into a tex file after the rounds of review and then compile the LaTeX manuscript again following some minor debugging. However, the latter approach may not be suitable in situations where the document is intended to stay into a word format for whatever reason. It could be for instance because you want to be kind with some co-authors that wouldn't pay much interest into a scary document filled with complicated codes. So I would like to know what are the best known strategies to circumvent the latter issue. To simplify, I accept that I will need to rewrite the equations (and eq. numbers) in the Word document. What I really want, however, is all the citations and the list of references being managed automatically at the step of exporting from org to ODT or to Plain Text. The only solution I see now is to export the org document to a plain pdf (e.g. with no page numbers) and then to copy-paste the pdf into a Word document. This strategy is cumbersome because a lot of work is generally needed to format the word document (page wrapping, no line breaks between paragraphs, words hyphenation, etc). Is there any cleaner solutions to this issue ? Or more general ideas on how we could facilitate the sharing of documents containing a bibtex bibliography between org and non-org users ? Thanks Martin
Re: [O] Sharing documents with bibtex bibliography from org to non-org users
On 08/15/2016 11:36 PM, Martin Leduc wrote: Hi orgers, People using org-mode or LaTeX to write scientific papers inevitably face problems when time comes to share a manuscript with co-authors for reviewing. Unless one decides to restrict the choice of his co-authors based exclusively on their knowledge of LaTeX, collaborators generally use Microsoft Word to write their documents. One way to share LaTeX documents with non-LaTeX users is to simply copy-paste the LaTeX file into a Word document. You can then share this file with other people along with a pdf-compiled version of the manuscript allowing them to see all references, bibliography, equations and figures. This is the most convenient approach for the first author, who can simply copy-paste back the text into a tex file after the rounds of review and then compile the LaTeX manuscript again following some minor debugging. However, the latter approach may not be suitable in situations where the document is intended to stay into a word format for whatever reason. It could be for instance because you want to be kind with some co-authors that wouldn't pay much interest into a scary document filled with complicated codes. So I would like to know what are the best known strategies to circumvent the latter issue. To simplify, I accept that I will need to rewrite the equations (and eq. numbers) in the Word document. What I really want, however, is all the citations and the list of references being managed automatically at the step of exporting from org to ODT or to Plain Text. The only solution I see now is to export the org document to a plain pdf (e.g. with no page numbers) and then to copy-paste the pdf into a Word document. This strategy is cumbersome because a lot of work is generally needed to format the word document (page wrapping, no line breaks between paragraphs, words hyphenation, etc). Is there any cleaner solutions to this issue ? Or more general ideas on how we could facilitate the sharing of documents containing a bibtex bibliography between org and non-org users ? Thanks Martin Sorry for double posting... please take this one. M.
[O] Sharing documents with bibtex bibliography from org to non-org users
Hi orgers, People using org-mode or LaTeX to write scientific papers inevitably face problems when the time comes to share a manuscript with co-authors for reviewing. Unless one decides to restrict the choice of his co-authors based exclusively on their knowledge of LaTeX, collaborators generally use Microsoft Word to write their documents. One way to share LaTeX documents with non-LaTeX users is to simply copy-paste the LaTeX file into a Word document. You can then share this file with other people along with the pdf-compiled version to allow them to see all references, bibliography, equations and figures. This is the most convenient approach for the first author, who can simply copy-paste back the text into a tex file after the rounds of review and then compile the LaTeX manuscript again following some minor debugging. However, the latter approach may not be suitable in several situations. For instance, it could be because the document is intended to stay into a word format for whatever reason, or simply because you want to be kind with some co-authors that wouldn't pay much interest into a scary document filled with complicated codes. So I would like to know what are the best known strategies to circumvent the latter issue. To simplify, I accept that I will need to rewrite the equations (and eq. numbers) in the Word document. What I really want, however, is all the citations and the list of references being managed automatically at the step of exporting from org to ODT or to Plain Text. The only solution I see from now is to export the org document to a plain pdf (e.g. with no page numbers) and then to copy paste from the pdf to a Word documents. This strategy is rather cumbersome as a lot of work is needed in terms of formatting the word document (page wrapping, no line breaks between paragraphs, words hyphenation, etc). Is there any cleaner solutions to this issue ? Or more general ideas on how we could facilitate the sharing documents containing a bibtex bibliography between org and non-org users ? Thanks Martin
[O] Sharing documents with bibtex bibliography from org to non-org users
Hi orgers, People using org-mode or LaTeX to write scientific papers inevitably face problems when time comes to share a manuscript with co-authors for reviewing. Unless one decides to restrict the choice of his co-authors based exclusively on their knowledge of LaTeX, collaborators generally use Microsoft Word to write their documents. One way to share LaTeX documents with non-LaTeX users is to simply copy-paste the LaTeX file into a Word document. You can then share this file with other people along with a pdf-compiled version of the manuscript allowing them to see all references, bibliography, equations and figures. This is the most convenient approach for the first author, who can simply copy-paste back the text into a tex file after the rounds of review and then compile the LaTeX manuscript again following some minor debugging. However, the latter approach may not be suitable in situations where the document is intended to stay into a word format for whatever reason. It could be for instance because you want to be kind with some co-authors that wouldn't pay much interest into a scary document filled with complicated codes. So I would like to know what are the best known strategies to circumvent the latter issue. To simplify, I accept that I will need to rewrite the equations (and eq. numbers) in the Word document. What I really want, however, is all the citations and the list of references being managed automatically at the step of exporting from org to ODT or to Plain Text. The only solution I see now is to export the org document to a plain pdf (e.g. with no page numbers) and then to copy-paste the pdf into a Word document. This strategy is cumbersome because a lot of work is generally needed to format the word document (page wrapping, no line breaks between paragraphs, words hyphenation, etc). Is there any cleaner solutions to this issue ? Or more general ideas on how we could facilitate the sharing of documents containing a bibtex bibliography between org and non-org users ? Thanks Martin
[O] MobileOrg: index.org links files to the wrong folder
Hi,
I really enjoy the MobileOrg project. However, since some time, I cannot
access my org files anymore from my iPhone (I see the file names, but
nodes are empty). After some search, I found that the links made in the
index.org point relatively to the org-directory while they are supposed
(if I'm understanding correctly) to point to the org files in the same
directory as the index.org (that is in org-mobile-directory). My emacs
configuration is the following:
(setq org-directory "~/Dropbox/env/org-mode-files")
(setq org-mobile-inbox-for-pull "~/Dropbox/env/org-mode-files/flagged.org")
(setq org-mobile-directory "~/Dropbox/Apps/MobileOrg")
(setq org-mobile-files '("~/org-mode-files/test.org"))
The generated index.org file in MobileOrg/ looks like:
#+READONLY
#+TODO: TODO
#+TODO: NEXT WAITING SOMEDAY |
#+TAGS: @HOME WORK EMAIL CALL READ ERRAND AGENDAS
#+ALLPRIORITIES: A B C
* [[file:agendas.org][Agenda Views]]
* [[file:~/org-mode-files/test.org][test.org]]
The test.org file cannot be read from my iPhone since only the
org-mobile-directory is accessible to it.
I cannot see from the code or my configuration what causes this
behavior, but if I'm going back to this specific commit:
commit 74d3bd484fc0c79fd51302922c0eee8c3042fe14
Author: Nicolas Goaziou
Date: Sun Apr 17 17:00:14 2016 +0200
the org-mobile-push now creates the index.org correctly with the last
line as follows :
* [[file:test.org][test.org]]
So I see three possibilities: (1) I need to use a different emacs
configuration since this commit, (2) there is some bug in the code or
(3) I missed an important detail.
Thank you in advance for helping,
Martin
Re: [O] Tags management strategies
On 05/17/2016 08:23 AM, Karl Voit wrote: David Weinberger Hi Karl, Thank you so much for these interesting resources. I've read your technique for tagging files and folders and must admit that it's quite impressing. I would love to implement such kind of a system one day along with my GTD set-up, but I'm unfortunately lacking time for such a project at the moment. I found your suggestion of using file-specific tags very interesting because it simplifies a lot of things. For example, rather than using grouptags in a global list, I can use file-specific tags. That way each file can represent a specific context, with a group of tags associated with it. Used along with capture templates, this can become powerful, as I can press C-q and then TAB to display an ordered list of all tags related to that context. Using file-specific tags allowed me to simplify my org-tag-alist to 5 tags (HOME,WORK,MAIL,CALL,READ), which can be added to any file-specific list without any problems since, as you said, context-related lists of tags overlap rather vaguely. David Weinberger's book seems interesting. This is in agreement with Samuel Wales suggestion (see the other response to my first post) to make an extensive use of regexp searches (I need to invest some time for this). At first I thought I was asking a simple and naive question about tags. Thanks for opening this interesting Pandora's box. Martin
Re: [O] Tags management strategies
On 16-05-16 03:59 PM, Samuel Wales wrote: i skip tags almost entirely in favor of regular expression search. :) Hi Samuel, thanks for your response. Using regular expression search is certainly a good approach to this problem and I would like to take some time to master this technique better. I suppose we could even do tag searching based on regexp :)
[O] Tags management strategies
Hi ! Tags are a very useful feature to filter information in org-mode. After few years of developing a system to organize my life with org-mode, I realize that tags can become rather difficult to deal with as we tend to define a lot of tags spread out over several org files. One general issue is to track all the tags that you have defined in all your org files. Rather than requesting an org-mode feature that would make a dynamical list of all the defined tags, I personally prefer the approach of making a static list of all preferred tags in one place and to try to keep this list as small as I can. I can achieve this by defining a global list of tags through the variable "org-tag-alist", which allows to access all the tags from any of my org files, and also because it allows to make "grouptags" which are very convenient to organize tags by themes. The latter approach seems however limited to the use of a rather small number of tags since in the fast-tag-selection interface, tags entries beyond the 33th are marked with extended ASCCI characters such as ^?, \200, \201,... So my first question is how can I access these tags, and if it is possible, what is the physical limit in terms of the number of tags I can define and access ? My second question is a bit more general, but I would like to know what peoples are currently doing to manage, track and make an efficient use of their numerous tags. Many thanks, Martin
Re: [O] Simple copy/paste of an agenda TODO list
On 2016-01-08 10:40 AM, Nick Dokos wrote: Martin Leduc <ldcm...@gmail.com> writes: Hello orgers, I'm wondering how to do a simple copy/paste of a todo list from org-mode. For instance, when I'm producing the list of all my TODOs with C-c a t, and then filtering it using a given tag, how can I simply copy and paste the resulting TODO list from the "Org Agenda" buffer into another one (e.g. scratch) ? I tried to simply select and copy, but then yanking into another buffer results in an un-filtered list of many TODOs (which is nearly the same as the first one constructed from C-c a t, but excludes all TODOs that appear before the first entry retained by the filter). I also tried with org-copy-visible, but still no success. Anybody could explain me how to do this simple task ? C-x C-w (bound to org-agenda-write). -- Nick Thanks for your response Nick, with the new org 8.3.3, org-agenda-write does nearly the what I want: it selects the right filtered list of TODOs. However, it exports all TODO's subtrees, while I want to copy only the list of TODOs as it appears in the agenda view. Any other ideas ?
Re: [O] Simple copy/paste of an agenda TODO list
On 2016-01-08 05:09 PM, Nick Dokos wrote: Martin Leduc <ldcm...@gmail.com> writes: On 2016-01-08 10:40 AM, Nick Dokos wrote: Martin Leduc <ldcm...@gmail.com> writes: Hello orgers, I'm wondering how to do a simple copy/paste of a todo list from org-mode. For instance, when I'm producing the list of all my TODOs with C-c a t, and then filtering it using a given tag, how can I simply copy and paste the resulting TODO list from the "Org Agenda" buffer into another one (e.g. scratch) ? I tried to simply select and copy, but then yanking into another buffer results in an un-filtered list of many TODOs (which is nearly the same as the first one constructed from C-c a t, but excludes all TODOs that appear before the first entry retained by the filter). I also tried with org-copy-visible, but still no success. Anybody could explain me how to do this simple task ? C-x C-w (bound to org-agenda-write). -- Nick Thanks for your response Nick, with the new org 8.3.3, org-agenda-write does nearly the what I want: it selects the right filtered list of TODOs. However, it exports all TODO's subtrees, while I want to copy only the list of TODOs as it appears in the agenda view. Any other ideas ? C-h f org-agenda-write RET says: , | If the extension is .org, collect all subtrees | corresponding to the agenda entries and add them in an .org file. ` so IIUC, all you have to do is use a file name that does not have a .org extension. -- Nick As simple as that ;) Thank you.
[O] Simple copy/paste of an agenda TODO list
Hello orgers, I'm wondering how to do a simple copy/paste of a todo list from org-mode. For instance, when I'm producing the list of all my TODOs with C-c a t, and then filtering it using a given tag, how can I simply copy and paste the resulting TODO list from the "Org Agenda" buffer into another one (e.g. scratch) ? I tried to simply select and copy, but then yanking into another buffer results in an un-filtered list of many TODOs (which is nearly the same as the first one constructed from C-c a t, but excludes all TODOs that appear before the first entry retained by the filter). I also tried with org-copy-visible, but still no success. Anybody could explain me how to do this simple task ? Thanks a lot, Martin
Re: [O] fontenc makes pdf non-searchable
Hi Bastien, thanks a lot for your response but I finally solved the issue by
installing the package cm-super.
Cheers,
Martin
From: b...@gnu.org
To: mart...@hotmail.com
CC: emacs-orgmode@gnu.org
Subject: Re: fontenc makes pdf non-searchable
Date: Wed, 5 Aug 2015 02:00:52 +0200
Hi Martin,
Martin Leduc mart...@hotmail.com writes:
However, when opening the experted pdf (with evince or okular) and
searching for a word, the output from the search function is a list
of words with apparently incorrect character encoding.
I get the same result when compiling directly the exported tex file.
However, if I remove the line:
\usepackage[T1]{fontenc}
the compiled pdf becomes correctly interpreted by the search
function. According to the documentation of the org-article latex
class, There is no facility to disable loading fontenc.
What should I do to make the pdf searchable with the org exporter ?
I would try to remove the relevant entry from
`org-latex-default-packages-alist'. Did you try this?
--
Bastien
Re: [O] fontenc makes pdf non-searchable
You're right, I customized org-latex-pdf-process, which now call a script that basically does latex/dvips/ps2pdf. I cannot use pdflatex since my figures are from eps images. Martin dboyd2 at mmm.com (J. David Boyd) writes: And how did you determine that please? I assume you mean how I determined that the PDF has been produced by dvips and Ghostscript. In this case: I've just looked into the document information of the PDF file. For example with Acrobat Reader I just press CMD+D, with Apple Preview its CMD+I (look out in the menus for document information or properties). In this document information there is somewhere a line like PDF creator. If the PDF is created with pdftex or pdflatex, this line should read something like pdfTeX-1.40.15. Each PDF viewer shows a different degree of details about the file. For example with Apple Preview I do not see the used fonts, these are only shown by Acrobat Reader (or command line tools like pdffonts from xpdf). And how would it be switched? The default settings of org-mode uses pdflatex. The compilation process is configurable via the variable org-latex-pdf-process. I don't know why and how Martin used dvips+gs. Maybe he just generated the tex file with org and used another tool for generating PDF. Or maybe he customized org-latex-pdf-process. -- Until the next mail..., Stefan.
Re: [O] fontenc makes pdf non-searchable
Hey finally your response helped me a lot, that is the problem was probably on
my side.
I solved it by installing the package cm-super, as suggested here. I still
can't search in the pdf I gave you (and still wondering why YOU can), but
re-exporting the org file makes a pdf that now works correctly.
Thanks again !
Martin
Date: Sun, 22 Mar 2015 13:56:45 -0400
From: w...@pobox.com
To: mart...@hotmail.com
CC: emacs-orgmode@gnu.org
Subject: Re: [O] fontenc makes pdf non-searchable
On 21 March 2015, Martin Leduc wrote:
You can find a minimal example here [1], with the org file, and the tex and
pdf files generated from it. Firts try to search within the pdf. It does
not work (at least on my side) To solve the problem, remove the line with
\usepackage[T1]{fontenc}
in the tex file, and compile it. It should now search normally.
It works for me is all I can say, which isn't too helpful. Everything
happens
as it should, and I can search the PDF (in evince). Maybe it's something
with
your LaTeX setup? Sorry I can't suggest anything more.
Bill
[1] https://www.dropbox.com/sh/7s6di4en5ljbkcq/AAAzyQeg6VkMHnC1X9dQTg6ua?dl=0
--
William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
Re: [O] fontenc makes pdf non-searchable
Thanks for your response Bill.
You can find a minimal example here, with the org file, and the tex and pdf
files generated from it. Firts try to search within the pdf. It does not work
(at least on my side) To solve the problem, remove the line with
\usepackage[T1]{fontenc}
in the tex file, and compile it. It should now search normally.
Martin
Date: Sat, 21 Mar 2015 12:24:31 -0400
From: w...@pobox.com
To: mart...@hotmail.com
CC: emacs-orgmode@gnu.org
Subject: Re: [O] fontenc makes pdf non-searchable
On 21 March 2015, Martin Leduc wrote:
I'm using org-mode to write a paper and export it to a pdf. It compiles
just fine.
However, when opening the experted pdf (with evince or okular) and
searching for a word, the output from the search function is a list of
words with apparently incorrect character encoding.
I get the same result when compiling directly the exported tex file.
However, if I remove the line:
\usepackage[T1]{fontenc}
the compiled pdf becomes correctly interpreted by the search function.
According to the documentation of the org-article latex class, There is no
facility to disable loading fontenc.
That seems odd to me. Can you provide an ECM, a minimal complete example,
that
causes this problem?
Bill
--
William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
[O] fontenc makes pdf non-searchable
Hi all,
I'm using org-mode to write a paper and export it to a pdf. It compiles just
fine.
However, when opening the experted pdf (with evince or okular) and searching
for a word, the output from the search function is a list of words with
apparently incorrect character encoding.
I get the same result when compiling directly the exported tex file. However,
if I remove the line:
\usepackage[T1]{fontenc}
the compiled pdf becomes correctly interpreted by the search function.
According to the documentation of the org-article latex class, There
is no facility to disable loading fontenc.
What should I do to make the pdf searchable with the org exporter ?
Thanks,
Martin
Re: [O] Text emphasize with fill-paragraph ?
Hi, to be more specific, I can emphasize a maximum of two lines within a filled paragraph of any length. Thanks, now I can reproduce, at least... ;) From: lexi.ba...@gmail.com To: mart...@hotmail.com CC: emacs-orgmode@gnu.org Subject: Re: Text emphasize with fill-paragraph ? Date: Tue, 25 Feb 2014 15:22:32 +0100 I remember a post from some time ago, where someone reported that this kind of formatting only worked for filled paragraphs under 3 lines long. Sadly I cannot find said post now. Is this the same for you? I don't know if this a bug or not. On 2014-02-21 16:31 Martin Leduc wrote: Hi all, I don't know whether it is a bug, an unimplemented feature or simply that I use it wrongly, but I can't emphasize text (with // ** or _ _) within a filled paragraph. Moreover, sometime I get it to work but I'm not sure how to reproduce. Thanks, Martin Regards, -- Alexander Baier
[O] Text emphasize with fill-paragraph ?
Hi all, I don't know whether it is a bug, an unimplemented feature or simply that I use it wrongly, but I can't emphasize text (with // ** or _ _) within a filled paragraph. Moreover, sometime I get it to work but I'm not sure how to reproduce. Thanks, Martin
[O] EXPORT_FILE_NAME when exporting the entire org file ?
Hi everyone, when exporting only a subtree to pdf, we can set the output file such as: * Some headline:PROPERTIES::EXPORT_FILE_NAME: /path/filename:END: Is it possible to set the output path/filename when exporting the entire org file ? (e.g. in the heading #+OPTIONS) Thanks !Martin
Re: [O] Visibility cycling for headlines with a specific tag ?
Exactly what I was searching for. Thank you very much.
[O] Visibility cycling for headlines with a specific tag ?
Hi, I am currently taking a lot of notes in an org file containing figures, equations, code snippets and text. In my project tree, I have several nodes containing supplementary material and code that will not be part of my final report exported as a LaTeX pdf. These nodes are tagged as :noexport to avoid exporting. However, when editing the buffer, I would like to hide all such parts in order to focus on the important ones. Is there a way to whether: 1) folding (or cycling) all headlines of a specific tag in one key action 2) prevent these tagged headlines to unfold (unless I specifically want to by hitting tab when the cursor is on the headline), by some kind of locking process ? For example, by tagging with :locked ? Thanks for suggestions, Martin
Re: [O] LaTeX export: images subplots
Thanks for all suggestions. I will probably stick with the solution of
generating the panels with imagemagick and then including them as figures
[[panel.png]].
Regards,
Martin
Date: Wed, 11 Sep 2013 22:19:57 -0500
Subject: Re: [O] LaTeX export: images subplots
From: jw.he...@gmail.com
To: mart...@hotmail.com
CC: emacs-orgmode@gnu.org
On Wed, Sep 11, 2013 at 10:13 PM, Martin Leduc mart...@hotmail.com wrote:
Hi John,
this solution using tables was indeed inspired from your post, I am so
sorry, I should have refered to it...
Ha! No problem at all -- small mailing list world :)
I suppose that the feature has not been implemented yet. I am now thinking
of generating a panel with imagemagick before including it in the org
buffer, for example with
#+begin_src sh
convert +append image1.png image2.png panel.png
#+end_src
and hence
#+CAPTION:
[[panel.png]]
What in the wide world of sports!? That's amazing and I can't believe
I've never run into that. Sooo flipping handy. I've been looking for
an easy way to do this with dissimilar ggplot2 plots where facetting
is hard or doesn't make sense as well:
- Like this:
http://stackoverflow.com/questions/18046051/setting-individual-axis-limits-with-facet-wrap-and-scales-free-in-ggplot2
That's pretty awesome and I just tried it; works beautifully.
Then again, I think handling images in Org tables would be just
fantastic. Not need for an external program or the compile time.
Perhaps a bit tricky as one would have to infer from some #+attr_latex
property that one wanted to apply some size parameter to every
[option] box of the converted \includegraphics line...
In any case, thanks for this and I'll keep that in mind. Hopefully
others chime in.
John
to have the two images side by side both in the buffer (with C-cxv) and the
latex pdf (within a figure environment).
Is there a cleaner org solution that I would have missed ?
Thanks again,
Martin
Date: Wed, 11 Sep 2013 21:47:08 -0500
Subject: Re: [O] LaTeX export: images subplots
From: jw.he...@gmail.com
To: mart...@hotmail.com
CC: emacs-orgmode@gnu.org
On Wed, Sep 11, 2013 at 8:56 PM, Martin Leduc mart...@hotmail.com wrote:
Hi all,
I am using org-mode to write a report with several figures. I would like
to group some images into a same figure, let say a 2x2 panel. I know
that I
can directly embed latex code in my org file, for example by using the
subfloats (from the latex subfig package).
However, I would prefer to use an org-based solution of inserting the
image
links in order to keep the convenient way of previewing images right
into
the buffer with C-c C-x C-v.
The only solution I found is by using tables such as:
#+CAPTION: Insert caption here.
#+ATTR_LATEX: :align p{0.5\textwidth}p{0.5\textwidth}
| [[pathtoimage]] | [[pathtoimage]] |
| [[pathtoimage]] | [[pathtoimage]] |
where the size of the images is controled by p{} and C-cxv is working.
However, in the exported TeX file, it is a table, not a figure. Is there
a
cleaner way to make image panels that would preserve the figure
environment
in the exported TeX file ?
Just wanted to cite my similar (same?) question from a bit back:
- http://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg01800.html
The only suggest I got was to use the subfig package, which may
actually be something like what you're looking for.
I guess p{width} /could/ work for what I was going for, but I will
often stagger images and my own captions via the org table:
#+ATTR_LATEX: :align p{0.5\textwidth}p{0.5\textwidth}
| [[pathtoimage]] | [[pathtoimage]] |
| /blah blah/ | /blah blah/ |
| | |
| [[pathtoimage]] | [[pathtoimage]] |
| /blah blah/ | /blah blah/ |
| | |
I don't like using p{} because everything is left aligned and I like
to center the images and the caption text below each one.
Unfortunately, there's no centered equivalent to p{}. Thus, I end up
using \includegraphics[widt]{} manually.
Anyway, sorry if that's off-topic. Just wanted to voice that I have a
use for this general sort of thing as well. Heck, I think even
applying the beamer columns principle to LaTeX article classes would
work and be quite neat.
Thanks,
John
Thanks a lot,
Martin
[O] LaTeX export: images subplots
Hi all,
I am using org-mode to write a report with several figures. I would like to
group some images into a same figure, let say a 2x2 panel. I know that I can
directly embed latex code in my org file, for example by using the subfloats
(from the latex subfig package).
However, I would prefer to use an org-based solution of inserting the image
links in order to keep the convenient way of previewing images right into the
buffer with C-c C-x C-v.
The only solution I found is by using tables such as:
#+CAPTION: Insert caption here.
#+ATTR_LATEX: :align p{0.5\textwidth}p{0.5\textwidth}
| [[pathtoimage]] | [[pathtoimage]] |
| [[pathtoimage]] | [[pathtoimage]] |
where the size of the images is controled by p{} and C-cxv is working. However,
in the exported TeX file, it is a table, not a figure. Is there a cleaner way
to make image panels that would preserve the figure environment in the exported
TeX file ?
Thanks a lot,
Martin
Re: [O] LaTeX export: images subplots
Hi John,
this solution using tables was indeed inspired from your post, I am so
sorry, I should have refered to it...
I suppose that the feature has not been implemented yet. I am now thinking of
generating a panel with imagemagick before including it in the org buffer, for
example with
#+begin_src sh
convert +append image1.png image2.png panel.png
#+end_src
and hence
#+CAPTION:
[[panel.png]]
to have the two images side by side both in the buffer (with C-cxv) and the
latex pdf (within a figure environment).
Is there a cleaner org solution that I would have missed ?
Thanks again,
Martin
Date: Wed, 11 Sep 2013 21:47:08 -0500
Subject: Re: [O] LaTeX export: images subplots
From: jw.he...@gmail.com
To: mart...@hotmail.com
CC: emacs-orgmode@gnu.org
On Wed, Sep 11, 2013 at 8:56 PM, Martin Leduc mart...@hotmail.com wrote:
Hi all,
I am using org-mode to write a report with several figures. I would like
to group some images into a same figure, let say a 2x2 panel. I know that I
can directly embed latex code in my org file, for example by using the
subfloats (from the latex subfig package).
However, I would prefer to use an org-based solution of inserting the image
links in order to keep the convenient way of previewing images right into
the buffer with C-c C-x C-v.
The only solution I found is by using tables such as:
#+CAPTION: Insert caption here.
#+ATTR_LATEX: :align p{0.5\textwidth}p{0.5\textwidth}
| [[pathtoimage]] | [[pathtoimage]] |
| [[pathtoimage]] | [[pathtoimage]] |
where the size of the images is controled by p{} and C-cxv is working.
However, in the exported TeX file, it is a table, not a figure. Is there a
cleaner way to make image panels that would preserve the figure environment
in the exported TeX file ?
Just wanted to cite my similar (same?) question from a bit back:
- http://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg01800.html
The only suggest I got was to use the subfig package, which may
actually be something like what you're looking for.
I guess p{width} /could/ work for what I was going for, but I will
often stagger images and my own captions via the org table:
#+ATTR_LATEX: :align p{0.5\textwidth}p{0.5\textwidth}
| [[pathtoimage]] | [[pathtoimage]] |
| /blah blah/ | /blah blah/ |
| | |
| [[pathtoimage]] | [[pathtoimage]] |
| /blah blah/ | /blah blah/ |
| | |
I don't like using p{} because everything is left aligned and I like
to center the images and the caption text below each one.
Unfortunately, there's no centered equivalent to p{}. Thus, I end up
using \includegraphics[widt]{} manually.
Anyway, sorry if that's off-topic. Just wanted to voice that I have a
use for this general sort of thing as well. Heck, I think even
applying the beamer columns principle to LaTeX article classes would
work and be quite neat.
Thanks,
John
Thanks a lot,
Martin
Re: [O] org Publish subtree to pdf
Thanks for your answers. That worked perfectly. Martin From: n.goaz...@gmail.com To: mart...@hotmail.com CC: emacs-orgmode@gnu.org Subject: Re: org Publish subtree to pdf Date: Sat, 17 Aug 2013 10:28:06 +0200 Hello, Martin Leduc mart...@hotmail.com writes: I have a large org file with several projects in it. I can export one of them (a subtree) to pdf by using C-c C-e C-s l o. However, I would like to use the Publish function since it allows to export the pdf to another folder. However, by using C-s (Subtree option) and P (for publish) and x (to choose template from org-publish-project-alist), the Subtree option does not seem to work well. Subtree export is not meant to be used along with publishing. The latter works on complete files only. The entire tree is exported though without the content of higher-level headlines. Is it the normal behavior to be expected from the publish function ? What is the best way to export in pdf to another location ? Use EXPORT_FILE_NAME node property. See penultimate paragraph from section 12.3 in the manual. Regards, -- Nicolas Goaziou
[O] org Publish subtree to pdf
Hi, I have a large org file with several projects in it. I can export one of them (a subtree) to pdf by using C-c C-e C-s l o. However, I would like to use the Publish function since it allows to export the pdf to another folder. However, by using C-s (Subtree option) and P (for publish) and x (to choose template from org-publish-project-alist), the Subtree option does not seem to work well. The entire tree is exported though without the content of higher-level headlines. Is it the normal behavior to be expected from the publish function ? What is the best way to export in pdf to another location ? Thanks, Martin
