Re: Org to ConTeXt exporter?
On 12/28/20 5:38 AM, Juan Manuel Macías wrote: Hi, Just out of curiosity, I am wondering if there are plans to create an Org to ConTeXt exporter in the future, or if there is already some work in progress on this front. I have to say that among TeX formats I tend to prefer LaTeX to ConTeXt; but ConTeXt has very interesting features (grid typesetting, for example) that LaTeX lacks (for now) and has a more monolithic structure, that is, it does not need to be extended through packages as in LaTeX. Regards, Juan Manuel I recently had the same thought and I've started working on one. You can see it here: https://github.com/Jason-S-Ross/ox-context/ It's no substitute for the LaTeX exporter but it implements a lot of the basics. I'm deriving from the LaTeX exporter but I have to override most of the transcoders so it may be better to start from scratch. Disclaimer: I'm learning elisp as I go, so please excuse the rough edges. Jason Ross
Re: Org to ConTeXt exporter?
On 2020-12-28, at 14:38, Juan Manuel Macías wrote: > Hi, > > Just out of curiosity, I am wondering if there are plans to create an > Org to ConTeXt exporter in the future, or if there is already some work > in progress on this front. > > I have to say that among TeX formats I tend to prefer LaTeX to ConTeXt; > but ConTeXt has very interesting features (grid typesetting, for > example) that LaTeX lacks (for now) and has a more monolithic structure, > that is, it does not need to be extended through packages as in LaTeX. I recently had the same thought and I've started working on one. You can see it here: https://github.com/Jason-S-Ross/ox-context/ It's no substitute for the LaTeX exporter but it implements a lot of the basics. I'm deriving from the LaTeX exporter but I have to override most of the transcoders so it may be better to start from scratch. Disclaimer: I'm learning elisp as I go, so please excuse the rough edges. Jason Ross
Re: [PATCH] A proposal to add LaTeX attributes to verse blocks
Hi,
I am attaching a new version of my patch for adding LaTeX attributes to
verse blocks. Following the kind suggestions from Timothy, I have also
documented this new features that I propose. I don't know if I have done
it correctly and in the right place...
A short reminder: `lines', `versewidth', and `center' require loading
the LaTeX package verse.sty (https://www.ctan.org/pkg/verse), which is
an extension of the standard LaTeX `verse' environment, and that adds
many features for typesetting poetry. `lines' deals with the marginal
verse numbering; `versewidth' and `center' are related to the optical
centering of the poem. The fourth attribute is to include arbitrary
LaTeX code within the verse environment, so I have provisionally named
it `latexcode'.
Of course, Feedback is welcome.
Regards,
Juan Manuel
diff --git a/doc/org-manual.org b/doc/org-manual.org
index b015b502c..fe21b5aca 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -13870,6 +13870,54 @@ The LaTeX export back-end converts horizontal rules by the specified
-
#+end_example
+*** Verse blocks in LaTeX export
+:PROPERTIES:
+:DESCRIPTION: Attributes specific to special blocks.
+:END:
+
+#+cindex: verse blocks, in @LaTeX{} export
+#+cindex: @samp{ATTR_LATEX}, keyword
+
+The LaTeX export back-end accepts four attributes for verse blocks:
+=:lines=, =:center=, =:versewidth= and =:latexcode=. The three first
+require the external LaTeX package =verse.sty=, wich is an extension
+of the standard LaTeX environment. The purpose of these attributes is
+explained below.
+
+- =:lines= :: To add marginal verse numbering. Its value is an
+ integer, the sequence in which the verses should be numbered.
+- =:center= :: With value =t= all the verses on the page are optically
+ centered (a typographic convention for poetry), taking as a
+ reference the longest verse, which must be indicated by the
+ attribute =:versewidth=.
+- =:versewidth= :: Its value is a literal text string with the longest
+ verse.
+- =:latexcode= :: It accepts any arbitrary LaTeX code that can be
+ included within a LaTeX =verse= environment.
+
+A complete example with Shakespeare's first sonnet:
+
+#+begin_src org
+,#+ATTR_LaTeX: :center t :latexcode \color{red} :lines 5
+,#+ATTR_LaTeX: :versewidth Feed’st thy light’st flame with self-substantial fuel,
+,#+begin_verse
+From fairest creatures we desire increase,
+That thereby beauty’s rose might never die,
+But as the riper should by time decrease,
+His tender heir mught bear his memeory:
+But thou, contracted to thine own bright eyes,
+Feed’st thy light’st flame with self-substantial fuel,
+Making a famine where abundance lies,
+Thyself thy foe, to thy sweet self too cruel.
+Thou that art now the world’s fresh ornament
+And only herald to the gaudy spring,
+Within thine own bud buriest thy content
+And, tender churl, makest waste in niggarding.
+Pity the world, or else this glutton be,
+To eat the world’s due, by the grave and thee.
+,#+end_verse
+#+end_src
+
** Markdown Export
:PROPERTIES:
:DESCRIPTION: Exporting to Markdown.
diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 5e5f1954d..47e0ec40e 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -149,6 +149,19 @@ Example:
A new =u= mode flag for Calc formulas in Org tables has been added to
enable Calc units simplification mode.
+*** LaTeX attributes for verse blocks
+
+The LaTeX export back-end now accepts four attributes for verse
+blocks:
+
+- =:lines=, for marginal verse numbering;
+- =:center= and =:versewidth=, for optical centering of the verses;
+- =:latexcode=, for any arbitrary LaTeX code that can be included
+ within a LaTeX =verse= environment.
+
+The three first require the external LaTeX package =verse.sty=, wich
+is an extension of the standard LaTeX environment.
+
** Miscellaneous
*** =org-goto-first-child= now works before first heading
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index fb9fc3cd6..0931b7e9c 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -3506,6 +3506,17 @@ channel."
"Transcode a VERSE-BLOCK element from Org to LaTeX.
CONTENTS is verse block contents. INFO is a plist holding
contextual information."
+ (let*
+ ((lin (org-export-read-attribute :attr_latex verse-block :lines))
+ (latcode (org-export-read-attribute :attr_latex verse-block :latexcode))
+ (cent (org-export-read-attribute :attr_latex verse-block :center))
+ (attr (concat
+ (if cent "[\\versewidth]" "")
+ (if lin (format "\n\\poemlines{%s}" lin) "")
+ (if latcode (format "\n%s" latcode) "")))
+ (versewidth (org-export-read-attribute :attr_latex verse-block :versewidth))
+ (vwidth (if versewidth (format "\\settowidth{\\versewidth}{%s}\n" versewidth) ""))
+ (linreset (if lin "\n\\poemlines{0}" "")))
(concat
(org-latex--wrap-label
verse-block
@@ -3513,19 +3524,20 @@ contextual information."
;; character and change each white space at beginning of a line
;; into a
Re: Org-capture template no longer recognised...
Thanks for looking into this Kyle. ‐‐‐ Original Message ‐‐‐ On Wednesday, January 6, 2021 4:43 AM, Kyle Meyer wrote: > > ...it does seem likely that the issue is outside of Org proper. But > unfortunately I don't have any suggestions about where that might be, or > why it's getting triggered in the above scenario. Hopefully others > will. Beyond downgrading each of the packages I listed if anyone has suggestions on how to debug this further please let me know, more than happy to work through this and post back to the list. -- *Natural selection is a mechanism for generating an exceedingly high **degree of improbability.* - R.A. Fisher *Ignorance more frequently begets confidence than does knowledge* - Charles Darwin PGP Public : 0x700172212EF5818B
columnview: match vs exclude tags
Hi While I understand the option match as a tag, to include certain entries, I don't understand the option exclude-tags #+begin_src ,* Exclude (match) :PROPERTIES: :COLUMNS: :ID: :END: ,** Group1:in: :PROPERTIES: :ID: G1 :Grp1: 1 :Gr: Group-1 :Usuario1: Antonio :Usuario2: Isabel :Usuario3: Paula :Usuario4: Filipe :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ,** Group2 :out: :PROPERTIES: :ID: G2 :Grp1: 1 :Gr: Group-1 :Usuario1: Juan :Usuario2: Eva :Usuario3: Paula :Usuario4: Albert :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ,** Group3 :out: :PROPERTIES: :ID: G2 :Grp1: 1 :Gr: Group-1 :Usuario1: Juan :Usuario2: Eva :Usuario3: Paula :Usuario4: Albert :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ,** List of all group members ,#+TBLNAME: mitglieder2 ,#+BEGIN: columnview :hlines 2 :skip-empty-rows t :indent nil :match "in" :format "%5ITEM(Groups) %5Usuario1(Memember) %5Usuario2(Memember) %5Usuario3(Memember) %5Usuario4(Memember)" | Groups | Memember | Memember | Memember | Memember | |+--+--+--+--| | Group1 | Antonio | Isabel | Paula| Filipe | ,#+END ,* Exclude (exclude tags) :PROPERTIES: :COLUMNS: :ID: :END: ,** Group1:in: :PROPERTIES: :ID: G1 :Grp1: 1 :Gr: Group-1 :Usuario1: Antonio :Usuario2: Isabel :Usuario3: Paula :Usuario4: Filipe :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ,** Group2 :out: :PROPERTIES: :ID: G2 :Grp1: 1 :Gr: Group-1 :Usuario1: Juan :Usuario2: Eva :Usuario3: Paula :Usuario4: Albert :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ,** Group3 :out: :PROPERTIES: :ID: G2 :Grp1: 1 :Gr: Group-1 :Usuario1: Juan :Usuario2: Eva :Usuario3: Paula :Usuario4: Albert :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ,** List of all group members ,#+TBLNAME: mitglieder2 ,#+BEGIN: columnview :hlines 2 :skip-empty-rows t :indent nil :exclude-tags "out" :format "%5ITEM(Groups) %5Usuario1(Memember) %5Usuario2(Memember) %5Usuario3(Memember) %5Usuario4(Memember)" ,#+END #+end_src
how to exclude in columnview certain subheaders (subsection)
Hi The following example puzzles me. * Exclude certain ID :PROPERTIES: :COLUMNS: :ID: :END: ** Group2 :PROPERTIES: :ID: G1 :Grp1: 1 :Gr: Group-1 :Usuario1: Antonio :Usuario2: Isabel :Usuario3: Paula :Usuario4: Filipe :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ** Group2 :PROPERTIES: :ID: G2 :Grp1: 1 :Gr: Group-1 :Usuario1: Juan :Usuario2: Eva :Usuario3: Paula :Usuario4: Albert :Start:<2020-07-26 Sun> :End: <2020-11-22 dom> :STATUS: [X] :ST1: [X] :Hoja: H1 :Ej: E1 :END: ** List of all group members #+TBLNAME: mitglieder2 #+BEGIN: columnview :hlines 2 :skip-empty-rows t :indent nil :ID "G1" :format "%5ITEM(Groups) %5Usuario1(Memember) %5Usuario2(Memember) %5Usuario3(Memember) %5Usuario4(Memember)" | Groups | Memember | Memember | Memember | Memember | |+--+--+--+--| | Group2 | Antonio | Isabel | Paula| Filipe | |+--+--+--+--| | Group2 | Juan | Eva | Paula| Albert | #+END I don't understand why Group 2 is included the ID says "G1" and Group2 has ID "G2" What do I miss? Thanks and regards Uwe Brauer
Re: Generated graphic not included in exported TeX/PDF
I haven't tried your example but maybe add an explicit ":exports results" to the src block? -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.4-166-g291993
Re: Generated graphic not included in exported TeX/PDF
"Loris Bennett" writes:
> "Loris Bennett" writes:
>
>> "Loris Bennett" writes:
>>
>>> Hi,
>>>
>>> I have just re-exported an org beamer presentation, which I created two
>>> years ago with a version of Org which was fairly up-to-date then.
>>> Everything still works fine, except for the fact that the images
>>> generated by the org file are not included in the exported PDF and
>>> indeed are missing from the generated TeX file.
>>>
>>> In the org file I have
>>>
>>> #+NAME: backfill-tikz
>>> #+HEADER: :fit yes :file ./generated/backfill_tikz.png :imagemagick yes
>>> :iminoptions -density 600
>>>
>>> #+HEADER: :headers '("\\usepackage{pgfplots}\\usepackage{sansmath}")
>>> #+HEADER: :results raw
>>>
>>> #+BEGIN_SRC latex :cache yes
>>> \usepgfplotslibrary{colorbrewer}
>>> \begin{tikzpicture}
>>> ...
>>> \end{tikzpicture}
>>> #+END_SRC
>>>
>>> #+RESULTS[e2d28096fe9dceffb0b63ad4a441160ff2a0d1a7]: backfill-tikz
>>> [[file:./generated/backfill_tikz.png]]
>>>
>>> As I say, the image itself is created, but not included when exported,
>>> although it is
>>> displayed if I do org-toggle-inline-images in the org buffer.
>>>
>>> My current Org version is
>>>
>>> Org mode version 9.4 (9.4-9-gab0052-elpaplus @
>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20200928/)
>>>
>>> Any ideas what might be happening?
>>
>> I have just noticed that this only affects images generated with tikz.
>> One image created with ditaa is included correctly. All images are PNGs.
>
> Just updated to
>
> Org mode version 9.4.4 (9.4.4-4-g99eafe-elpa @
> /home/loris/.emacs.d/elpa/org-20210104/)
>
> but the problem remains.
As I was having problems with the caching of the images, I replaced
#+BEGIN_SRC latex :cache yes
with
#+BEGIN_SRC latex :cache yes :eval never-export
and now the images are not only not regenerated but are now also
exported properly.
Is this a bug?
Cheers,
Loris
--
This signature is currently under construction.
columnview how to break lines if cell is to width
Hello Please consider the following example: #+begin_src ,* Group 1 :PROPERTIES: :COLUMNS: :Usuario1: Antonio Gonzales :Email1: go...@ucm.es :Usuario2: Isabel Diaz :Email2: isa...@ucm.es :Usuario3: Paula Rodríguez :Email3: pa...@ucm.es :Usuario4: Filipe Rio :Email4: fil...@ucm.es :END: ,#+TBLNAME: members ,#+BEGIN: columnview :hlines 2 :indent nil :format "%50ITEM %5Usuario1(Member) %5Email1(Email) %5Usuario2(Member) %5Email2(Email) %5Usuario3(Member) %5Email3(Email) %5Usuario4(Member) %5Email4(Email)" | ITEM| Member | Email| Member | Email | Member | Email| Member | Email | |-+--+--+-+---+-+--++---| | Group 1 | Antonio Gonzales | go...@ucm.es | Isabel Diaz | isa...@ucm.es | Paula Rodríguez | pa...@ucm.es | Filipe Rio | fil...@ucm.es | ,#+END #+end_src The resulting table has a bit too much width, I could use #+begin_src ,* Group 1 :PROPERTIES: :COLUMNS: :Usuario1: Antonio Gonzales (email go...@ucm.es) :Usuario2: Isabel Diaz (email: isa...@ucm.es) :Usuario3: Paula Rodríguez (email: pa...@ucm.es) :Usuario4: Filipe Rio (email: fil...@ucm.es) :END: ,#+TBLNAME: members ,#+BEGIN: columnview :hlines 2 :indent nil :format "%50ITEM %5Usuario1(Member) %5Usuario2(Member) %5Usuario3(Member) %5Usuario4(Member)" | ITEM| Member| Member | Member | Member | |-+---++-+---| | Group 1 | Antonio Gonzales (email go...@ucm.es) | Isabel Diaz (email: isa...@ucm.es) | Paula Rodríguez (email: pa...@ucm.es) | Filipe Rio (email: fil...@ucm.es) | ,#+END #+end_src But then I would like to have a newline before (email ...) Is this possible. Another possibility would be to obtain a vertical table like this one | ITEM | Group 1 | | Member | Antonio Gonzales | | Email | go...@ucm.es | | Member | Isabel Diaz | | Email | isa...@ucm.es| | Member | Paula Rodríguez | | Email | pa...@ucm.es | | Member | Filipe Rio | | Email | fil...@ucm.es| How can this be achieved? regards Uwe Brauer
Re: Generated graphic not included in exported TeX/PDF
"Loris Bennett" writes:
> "Loris Bennett" writes:
>
>> Hi,
>>
>> I have just re-exported an org beamer presentation, which I created two
>> years ago with a version of Org which was fairly up-to-date then.
>> Everything still works fine, except for the fact that the images
>> generated by the org file are not included in the exported PDF and
>> indeed are missing from the generated TeX file.
>>
>> In the org file I have
>>
>> #+NAME: backfill-tikz
>> #+HEADER: :fit yes :file ./generated/backfill_tikz.png :imagemagick yes
>> :iminoptions -density 600
>>
>> #+HEADER: :headers '("\\usepackage{pgfplots}\\usepackage{sansmath}")
>> #+HEADER: :results raw
>>
>> #+BEGIN_SRC latex :cache yes
>> \usepgfplotslibrary{colorbrewer}
>> \begin{tikzpicture}
>> ...
>> \end{tikzpicture}
>> #+END_SRC
>>
>> #+RESULTS[e2d28096fe9dceffb0b63ad4a441160ff2a0d1a7]: backfill-tikz
>> [[file:./generated/backfill_tikz.png]]
>>
>> As I say, the image itself is created, but not included when exported,
>> although it is
>> displayed if I do org-toggle-inline-images in the org buffer.
>>
>> My current Org version is
>>
>> Org mode version 9.4 (9.4-9-gab0052-elpaplus @
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20200928/)
>>
>> Any ideas what might be happening?
>
> I have just noticed that this only affects images generated with tikz.
> One image created with ditaa is included correctly. All images are PNGs.
Just updated to
Org mode version 9.4.4 (9.4.4-4-g99eafe-elpa @
/home/loris/.emacs.d/elpa/org-20210104/)
but the problem remains.
--
This signature is currently under construction.
Re: Generated graphic not included in exported TeX/PDF
"Loris Bennett" writes:
> Hi,
>
> I have just re-exported an org beamer presentation, which I created two
> years ago with a version of Org which was fairly up-to-date then.
> Everything still works fine, except for the fact that the images
> generated by the org file are not included in the exported PDF and
> indeed are missing from the generated TeX file.
>
> In the org file I have
>
> #+NAME: backfill-tikz
> #+HEADER: :fit yes :file ./generated/backfill_tikz.png :imagemagick yes
> :iminoptions -density 600
>
> #+HEADER: :headers '("\\usepackage{pgfplots}\\usepackage{sansmath}")
> #+HEADER: :results raw
>
> #+BEGIN_SRC latex :cache yes
> \usepgfplotslibrary{colorbrewer}
> \begin{tikzpicture}
> ...
> \end{tikzpicture}
> #+END_SRC
>
> #+RESULTS[e2d28096fe9dceffb0b63ad4a441160ff2a0d1a7]: backfill-tikz
> [[file:./generated/backfill_tikz.png]]
>
> As I say, the image itself is created, but not included when exported,
> although it is
> displayed if I do org-toggle-inline-images in the org buffer.
>
> My current Org version is
>
> Org mode version 9.4 (9.4-9-gab0052-elpaplus @
> /home/loris/.emacs.d/elpa/org-plus-contrib-20200928/)
>
> Any ideas what might be happening?
I have just noticed that this only affects images generated with tikz.
One image created with ditaa is included correctly. All images are PNGs.
--
This signature is currently under construction.
Generated graphic not included in exported TeX/PDF
Hi,
I have just re-exported an org beamer presentation, which I created two
years ago with a version of Org which was fairly up-to-date then.
Everything still works fine, except for the fact that the images
generated by the org file are not included in the exported PDF and
indeed are missing from the generated TeX file.
In the org file I have
#+NAME: backfill-tikz
#+HEADER: :fit yes :file ./generated/backfill_tikz.png :imagemagick yes
:iminoptions -density 600
#+HEADER: :headers '("\\usepackage{pgfplots}\\usepackage{sansmath}")
#+HEADER: :results raw
#+BEGIN_SRC latex :cache yes
\usepgfplotslibrary{colorbrewer}
\begin{tikzpicture}
...
\end{tikzpicture}
#+END_SRC
#+RESULTS[e2d28096fe9dceffb0b63ad4a441160ff2a0d1a7]: backfill-tikz
[[file:./generated/backfill_tikz.png]]
As I say, the image itself is created, but not included when exported, although
it is
displayed if I do org-toggle-inline-images in the org buffer.
My current Org version is
Org mode version 9.4 (9.4-9-gab0052-elpaplus @
/home/loris/.emacs.d/elpa/org-plus-contrib-20200928/)
Any ideas what might be happening?
Cheers,
Loris
--
This signature is currently under construction.
