Re: [O] LaTex export: How to use `csquotes' and `\enquote{}'

Nick Dokos writes: > Here are some points to keep in mind while working on a patch: > o csquotes.sty is part of the texlive-latex-extra package on Ubuntu > (and probably something similar on other Linux distros and > possibly MacOS X - hunoz about Windoz?) On MacOS the MacTeX distribution i

Re: [O] LaTex export: How to use `csquotes' and `\enquote{}'

Nick Dokos writes: > I'd worry a bit about adding the newcommand in the preamble during > org processing: what would happen if I tried to use csquotes then? It should be either the newcommand or else use csquotes. Mixing both would be no good idea. -- Until the next mail..., Stefan. pgpoRt8r2

Re: [O] [PATCH] org-latex.el: New defcustom `org-export-latex-quotes' to control quotes.

Bastien writes: > Org to output something like \endquote{some quoted text} instead s/endquote/enquote/ -- Until the next mail..., Stefan. pgpzl49iatYmp.pgp Description: PGP signature

Re: [O] Unicode and Latex export

"Sebastien Vauban" writes: > having "\usepackage[utf8x]{inputenc}" inserted Please beware that utf8x is part of the obsolete and unsupported ucs package. As ucs deeply affects the LaTeX kernel, more and more modern packages are incompatible with utf8x and ucs (csquotes, hyperref,...). For proper

Re: [O] Wishlist: LaTeX export: automatically append backslash to "." unless at end of sentence

Andras Major writes: > Hi, > in TeX and LaTeX, the width of the glue (blank space) after a "." can > be one of two different values, depending on the context. And depending on the use of \nonfrenchspacing and \frenchspacing. > There is always a longer space between sentences than after a "." >

Re: [O] Latex image placement (...again. H vs. h!)

John Hendy writes: > Was just rediscovering how to properly get floats to drop in where I > want them in LaTeX export (right where I say vs. where LaTeX thinks > is convenient). Another way to tackle this problem may be to just not use floats. As the name suggests, these construct is meant to le

Re: [O] How to debug "org-clock-display: Args out of range: [48230 48230 48230 38618 38618 0 0 0 0 0 ...], 61"

Nick Dokos writes: > The code that sets the level seems suspect to me: > (let* ((headline-forced > (get-text-property (point) > :org-clock-force-headline-inclusion)) > (headline-included > (or (null h

Re: [O] Controlling pagination on headings in Latex/PDF export?

Nick Dokos writes: > \def\mykeepwithnextpar{\par\nobreak\@afterheading} > However, I find it exceedingly difficult to manufacture an example > that will produce the bad break that the OP reports: LaTeX seems > very reluctant to break after the headline. Yes. That's because the above snippet is

Re: [O] Controlling pagination on headings in Latex/PDF export?

Jos'h Fuller writes: > but it still doesn't seem to want to cooperate (heading on one page, > table on the next). Reading this again, another hint: If the table is exported to tabular and wrapped in a figure environment, then that might be the problem. I'm not familiar with org-modes latex expor

Re: [O] Controlling pagination on headings in Latex/PDF export?

Jos'h Fuller writes: > Hi! > Thanks for your kind words! ; - ) > I did wrap the "mykeepwithnextpar" definition and I moved the call between > the heading > and the table as suggested, but it still doesn't seem to want to cooperate > (heading on > one page, table on the next). I just tried to

[O] Include another org-document without settings

Hi. I try to build an org document that has two parts. One file contains the first part of the resulting document and should be useable stand-alone. The second file is some kind of extension to the first file. My idea is to simple #+INCLUDE the first file in the second one. But then the global se

Re: [O] Include another org-document without settings

Eric S Fraga writes: > When I used to do this in LaTeX, I usually had a /master/ document > which included the others. That's what I did with pure LaTeX, too. But then there is the nice feature in AucTeX which allows you to compile the whole document while you are in one of the slaves. I'm just

Re: [O] Include another org-document without settings

Nicolas Goaziou writes: > You can skip the first lines of an INCLUDEd file with :line parameter. > You can also only include a section. See manual for details. Thank you for the hint. I used something like #+INCLUDE "a.org" :lines 3- but still got duplicate keywords (the KEYWORDS option is

[O] Sum marked values in table

Hi. Is there any way to somehow mark cells in an org-table and then sum over all marked cells of the whole table. For example in the following table I marked some time values bold: || Col 1 | Col 2 | Col 3 | Col4 | Sum | |+---+++--+--|

[O] Build-System: Why not compile contrib

Hi. I'm using the maint branch of org-mode and lately I discovered that the files beneath contrib are not compiled and there seems to be no easy way (e.g. via local.mk) to enable compilation of contrib. Is this on purpose and if yes: why? -- Stefan.

Re: [O] Build-System: Why not compile contrib

Suvayu Ali writes: > > Hope this helps, A little bit. I already know about ORG_ADD_CONTRIB, but I thought it would only be used by `make install' and I do not install org-mode, I use it directly from my local repository (running `mak

[O] Bug in table formular - last column specifier broken

Hi. With the last update to Org-mode version 8.3.2 (8.3.2-48-g700b8e-elpaplus) the following table formular breaks: --8<---cut here---start->8--- | | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Sum | |-+--+--+--+-+-+-+

Re: [O] using vref in latex export, and normal links in html export

Alan Schmitt writes: > I'm converting a latex document into org-mode to easily export it both > to latex and html. I've just encountered something that I don't know how > to do: export a \vref reference. I would like to have something that > exports to \vref in latex, and to a normal link in html

Re: [O] Clocking work time vs. office time

Marcin Borkowski writes: > No, you're not - this is one possible solution. I'm curious about other > ones. If tracking the time you're at a specific location is your main objective (and if you own a Smartphone), I would say: Geofencing. Let your Smartphone track when you enter/leave the specifi

Re: [O] Citations, continued

Richard Lawrence writes: > Rasmus writes: >> Citation types for extracting parts: >> citeauthor, citetitle, citeyear, citedate, citeurl, > As I've said in other posts, I think maybe we should not think of > these as `citation' commands and thus don't need to represent them > in citation s

Re: [O] Citations, continued

Richard Lawrence writes: > I know these commands are convenient, and that not having them would > introduce this class of errors, but the question is whether they are > so important that it's worth providing an equivalent for them in > non-LaTeX backends. Hmmm... I don't see this as a big proble

Re: [O] Colon in block name?

"Loris Bennett" writes: > The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'. But you attached it as inline, so the same problems could arise. To be sure to transfer the file unmodified, choose "attachment" as disposition. > Reading with Gnus, I don't see any blank lines betwe

Re: [O] Citation syntax: a revised proposal

Richard Lawrence writes: > Rasmus writes: >> Parts I hate: >> The flag is either `@' or `&'. `@' [...] The optional hyphen (`-') >> Too many weird symbols that I won't be able to remember, much less explain >> to somebody else. > I don't love these either, but I am not sure what a bett

Re: [O] Citation syntax: a revised proposal

Nicolas Goaziou writes: > Time for another crazy idea. Last one on my side for today > [cite ...] [(cite) ...] [Cite ...] [(Cite) ...] > It should solve the :capitalize issue. +1 I really like it - even when looking at the org file with something weird like vim, it's very clear and intuitiv

Re: [O] Citation syntax: a revised proposal

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes: > From what I read in this and the previous thread, the new proposal > tries more or less to reimplement BibTeX in org. No, that's wrong, not the database should be replaced. The goal is to make citations a first class citizen in the

Re: [O] Citation syntax: a revised proposal

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes: > I see, so in the examples provided Doe99 is only the key, org would > not have to know that the author name is Doe and its year is 1999, > or any other information about the citation. Yes and no. In the first place org should only

Re: [O] Citation syntax: a revised proposal

Richard Lawrence writes: > 1) Is it worth allowing a name for a user-defined type in the [cite: > ...] part, or is it OK to confine user-defined types to the second > part (like: [cite: ...] %%(:type foo) or [cite: ...]{:type foo})? IMHO it is better to have such an important part of the citatio

Re: [O] Citation syntax: a revised proposal

Aaron Ecay writes: > I count roughly 50 commands in sections 3.7.1 – 3.7.6 of the > biblatex user’s manual (version 2.9a of 24/06/2014). Some of these > are quite esoteric, of course, but they are all provided. There are many commands (and even more private commands are possible) in order to hel

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Richard Lawrence writes: > Like I said, this seems like an edge case, and I don't see that it > is necessarily Org's responsibility to accommodate the keys produced > by Zotero in such edge cases. And there is a significant benefit to > *not* accommodating such keys: namely, you can use in-text c

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

t...@tsdye.com (Thomas S. Dye) writes: > It strikes me that basing core features of the citation syntax on > the software users happen to be using today is a bit like this--at > some point the design of the system will prove unprepared for new > developments. I don't think this is a big problem.

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C writes: > On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote: >> IMHO keys with lots of ??? in them are a sign of a data problem. >> Therefore the author should solve the root cause. > Not in the specific case that I cited. The Bib entry is a pointer to >

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C writes: > By saying "bibtex is not a requirement", I said "exporting to bibtex". You talked about Zotero but showed a bibtex entry. Therefore exporting from Zotero to bibtex may not be a requirement, there may be a direct interface to Zotero, eventually. We are at the start of t

Re: [O] fontenc makes pdf non-searchable

Martin Leduc writes: > 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} Your PDF is not gene

Re: [O] [OT] A short (less than a minute), informal survey about LaTeX

Marcin Borkowski writes: > 1. Did you know about the savetrees package by Scott Pakin Yes. > 2. Would you find it useful when producing PDF files other that > scientific articles (using Org-mode or not)? No. I use org-mode mostly for documentation and even documentation should look nice (the w

Re: [O] fontenc makes pdf non-searchable

dbo...@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 CM

Re: [O] org-mode to latex, again!

Marcin Borkowski writes: > As I wrote - yes, provided you update the filename database > (e.g. launching mktexlsr from the command line). (Because of speed, TeX > does not search the directory tree each time it looks for a package or > something, but uses a database in a familiar, "ls -R" format.

[O] Babel and R: Call code block and output plot

Hi. I'm playing a little bit with R code blocks in babel and calling them in different parts of my document (e.g. showing output in the main part and the code in the appendix). With most code blocks (e.g. setting some variables or outputting a LaTeX table with xtable) this works as expected (than

Re: [O] Babel and R: Call code block and output plot

Andreas Leha writes: > You still have to specify the format of the results of the #+CALL > line, as in #+CALL: myplot[:exports results]() :results file Works like a charm, thank you very much. -- Until the next mail..., Stefan.

Re: [O] Merge branch 'maint'

Oleh Krehel writes: > Would it be so hard for Git to perform a single merge of master into > maint on release, while keeping them separate and cherry-picking > in-between for the sake of a clean linear history? The question is not whether git is capable of doing this (there are ways to accomplis

[O] Clocktable creates superfluous columns

Hi. In version 9.0.5 Org (Emacs 25.1) seems to generate too many columns in some situations. I'm not quite sure since which version this happens, in Org 8.x I have not seen this behaviour. Here is a small example: --8<---cut here---start->8--- #+BEGIN: clockta

Re: Finally figuring out some ob-sqlite stuff -- for worg?

Eric Abrahamsen writes: > Okay, it's up. If anyone wants to explain to me the point of the > "where exists" clause in the SQL, I would be interested to hear. It > works as expected this way, but is that clause necessary? Yes, very necessary. Without it, all ratings would be changed - the two exa

Re: Finally figuring out some ob-sqlite stuff -- for worg?

Eric Abrahamsen writes: > I was confused in part because the "where exists (select *..." looks > like its main purpose is to return rows. Indeed that's the purpose: Restrict the set of rows upon which update acts on. Here I tried to reformat the statement a bit in order to emphasize its structur

Re: very strange LaTeX error

"Joost Kremers" writes: > The solution I usually opt for is to enclose the brackets in an > additional set of braces: `{[...]}`. Whether Org export can and > should automate that, I can't say. In the generated LaTeX adding a '\relax' (so each line ends with '\\\relax') would be a another solutio

Re: very strange LaTeX error

"Fraga, Eric" writes: > However, it seems that simply adding \relax does not work if there > is an \hline immediately following so the solution is not that > straightforward. Hmmm... but it should be solvable. Maybe something along the lines of this (rough sketch, I have next to no experience wi

Re: emacs build command for org-files

John Kitchin writes: > Hi everyone, > This is only semi-on-topic. I am looking for something like M-x compile for > my org-files, but I don't want it to necessarily use Makefiles. I am > looking for suggestions of existing solutions to this, or thoughts on how > to implement this. This may not

Re: Bug or not a bug? dot expansion in ob-shell

Bastien writes: > I agree we should have a discussion on whether :results value is a > good default. What about a third collection option 'none' and make this the default? This would emphasize that there is no sensible default for all babel languages, users and use cases. Users would be forced

Re: [PATCH] Don't fill displayed equations

Nicolas Goaziou writes: > Now, if you want to discuss changing syntax for \[...\] and make it > a block element I wonder, why it is not a block element. As far as I know, the only difference (even in the context of Org) between \(...\) and \[...\] is, that the former denotes inline math and the

Re: [PATCH] Accept more :tangle-mode specification forms

Timothy writes: > Thank you for considering potential security implications BTW: Security-wise I would argue to even forbid the integer case. From my view next to nobody uses and is used to the decimal codes of file modes. So this decimal integer representation is the most error prone, I would s

Re: [PATCH] Don't fill displayed equations

Nicolas Goaziou writes: > Also, I don't think LaTeX treats it as a block element. > E.g., > > text > \[1+1=3\] > text > > is a single paragraph in LaTeX. Yes and no. LaTeX is a bit more complex and does not only see inline or block elements. It has paragraph mode (and inner paragraph

Re: Org syntax: \[ \] as block element instead of inline object

Max Nikulin writes: > I like Timothy's idea that \[ \] markup should behave like > block-level element rather than inline object. On the other hand, we will loose the ability to inline small parts of math, that should be typeset as separate equation, like: ...text \[ 1+2=3 \] more text...

Re: [Question] A single *-language-alist in ox-latex.el?

Juan Manuel Macías writes: > Well, if I'm not mistaken, the situation in the LaTeX ecosystem is > this: Polyglossia appeared as a babel replacement for XelaTeX and > LuaLaTeX, since babel, at that time, had no support for these two > new Unicode based TeX engines. And, as far as I remember, babe

Re: [PATCH] Don't fill displayed equations

Max Nikulin writes: > On 03/10/2021 00:51, Tom Gillespie wrote: >> I guess one thing I'm missing/not understanding is when/why people >> want to use \[ \] instead of full #+begin_export latex block? > For example, because document without equations may become almost > useless in the case of exp

Re: insert automatically a reference to a section header and a link

Uwe Brauer writes: > I wonder why this was not implemented or asked for. Hmmm... for me, the default way to link to headings is just fine, I seldom need more control over the generated labels: #+begin_src org ,* Intro Lorem ipsum dolor sit amet... ,* Another section As seen in [[*Int

Re: insert automatically a reference to a section header and a link

Uwe Brauer writes: > I am not following you. You insert a header as in > * Intro > Now you want to refer to it with a link > As we have seen in section ... > So what precisely are you typing? I type "As we have seen in section [[*Intro]]" (literally, I tend to not use any keybindings or fun

Re: insert automatically a reference to a section header and a link

Juan Manuel Macías writes: > In Org 9.5 there is a new variable `org-latex-reference-command'. Thanks for the reminder! I once read about it, but forgot to use it after upgrading to 9.5. :) -- Until the next mail..., Stefan.

Re: insert automatically a reference to a section header and a link

Uwe Brauer writes: > Yes, but, what do you do, if you have a 10 header and each has 20 > subheaders. I avoid writing such complex documents for the moment. :) [Some custom functions] > Thanks but this did not work! Sorry. The code is meant as an inspiration, not to be used out-of-the box. I n

Re: wip-cite status question and feedback

Nicolas Goaziou writes: > Alphanumeric suffix provides 62 combinations, which should hopefully > be enough for any citation back-end out there (I'm looking at you > biblatex). It's not terribly readable, tho, as you point out. I second that. Some of the many BibLaTeX commands are due to compatib

Re: wip-cite status question and feedback

Joost Kremers writes: > I don't think it's necessary to use a dash (or any other character) > in longer cite commands, though. =citeintext= isn't that much more > difficult to read than =cite-intext=. (Biblatex does just fine > without dashes, and there's always camelCase if you're so inclined.)

Re: issue tracker?

Detlef Steuer writes: > I would go as far as saying *this list* is one of the fastest > reacting amd friendliest communities I have been part of. The job > Nicolas does is just awesome. +1! -- Until the next mail..., Stefan.

Re: org-time-stamp in German or Spanish or....

Uwe Brauer writes: > But is inserts the name of the days in English The format and language of the time-stamps is controlled by the function format-time-string (the docstring of this function shows all the available placeholders, including "%a" for the locale's abbreviated name of the day of wee

Re: org-time-stamp in German or Spanish or....

Uwe Brauer writes: > But it still inserts <2020-09-06 Sun> What's the value of `system-time-locale'? In a shell (like Bash), is there a difference between the following two commands: #+begin_src bash LC_TIME=C date #+end_src #+begin_src bash LC_TIME=de_DE date #+end_src -- Until the next ma

Re: "text mode" org mode

Emanuel Berg via "General discussions about Org-mode." writes: > Can I tell Org mode to don't change editing back and > forth, also don't collapse items in and out, i.e. > virtually text mode I did not test it to every detail, but the following two settings may be a good starting point: #+begin

Re: "text mode" org mode

Emanuel Berg via "General discussions about Org-mode." writes: > Stefan Nobis wrote: >> (setq org-link-descriptive nil) > I don't have org-link-descriptive, it seems... No problem, the old name is =org-descriptive-links= (this name has been deprecated in Org 9.3,

Re: basic org questions

Hi. Details about Org tables are to be found in the manual at different places (maybe not optimal, but that's the current structure). First of all, aspects of tables inside Emacs and Org are discussed here: https://orgmode.org/manual/Tables.html#Tables But everything about exporting (generati

Re: basic org questions

Emanuel Berg via "General discussions about Org-mode." writes: > Tim Cross wrote: >> #+latex_class: korma-article > user-error: Unknown LaTeX class ‘korma-article’ >> #+latex_header: \setlength{\parindent}{0pt} > Yes, that's removed the indentation but didn't insert > a blank line... First

Re: "text mode" org mode

Emanuel Berg via "General discussions about Org-mode." writes: > Thanks, I wonder tho if all this > (setq org-descriptive-links nil) > (setq org-hide-emphasis-markers nil) > (setq org-startup-folded'showeverything) > is implied, with `visual-mode'? Beware: =visible-mode= no

Re: basic org questions

Eric S Fraga writes: > #+latex_header: \setlength{\parindent}{0pt} > #+latex_header: \setlength{\parskip}{\baselineskip} Better use #+latex_header: \usepackage{parskip} as this package has less bad side-effects on other parts of the document than setting these far-reaching lengths directly. B

Re: basic org questions

Samuel Wales writes: > for my part, i appreciate your using the "wrong" style for your > email message A plain text document presented in a monospaced font is quite a different thing than a (longer) PDF with a plethora of layout and micro-typographic options. Do you also appreciate the workarou

Re: basic org questions

Emanuel Berg via "General discussions about Org-mode." writes: > OK, but the values still ned to be specified, right? No, just use the package - it sets the relevant lengths to change the style of marking paragraphs and tries hard to also reset every other length that depends on the original val

Re: basic org questions

Emanuel Berg via "General discussions about Org-mode." writes: >> #+attr_latex: :center nil :booktabs t >> | My | Columns | >> |+-| >> | 1 | 2 | >> | 3 | 4 | > "PDF file produced with errors." Sorry that I try to make more general examples that are not exactly tailored

Re: basic org questions

"Thomas S. Dye" writes: > There are many pieces of software that will allow the user to the > violate best typesetting practices easily. LaTeX is not one of them. Not quite right. I have seen people create really ugly source code *and* ugly output with LaTeX with ease. You can create garbage wit

Re: The Website Revamp: The final stretch

TEC writes: > 2. Picking the best 'Hero banner' on the home page :: I like Variant 1-1 the most - all other variants are a bit too big and yelling for my eyes. Maybe use size and layout of Variant 1-1 with colors of the last variant (page 9, gray background)? -- Until the next mail..., Stefan

Re: New website - back to the old unicorn!

Hi. Thanks for your great work and the wonderful new page! A minor detail: I use the plugin "Decentraleyes" and with this activated there is quite a bit JavaScript garbage at the end of the page (below the "Created by" footer). The part below the footer is this: #+begin_src js { const iframes =

Re: New website - back to the old unicorn!

TEC writes: > This seems very suspicious for one reason. I cannot see "Canvas" > anywhere in the entire codebase of the website, or any loaded > resources. So I have no idea where on earth the JS you're finding > has come from - I'm guessing it's improperly injected by a > extension. FWIW I also

Re: Changed list indentation behavior: how to revert?

"Dr. Arne Babenhauserheide" writes: > Sad story short:... I'm with you - last weekend I upgrade my OS and had quite some trouble to get everything working again and still have some nasty hoops to jump through. But on the other side: What are we talking about? Org had a given default configurat

Re: [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...")

Ihor Radchenko writes: > But can someone check if Free* fonts are available on Windows and > Mac by default? I just checked TeXLive (on MacOS, but should be the same on all systems): The Free* fonts are part of TeXLive as truetype and as opentype versions (and partly in other formats). For Wind

Re: [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...")

Juan Manuel Macías writes: > 1. There could be a defcustom, something like 'org-latex-use-fontspec' > (I would vote for nil by default). I would vote to activate this by default. > (format > \\usepackage{iftex} > \\ifpdftex > \\relax > \\else > \\usepackage{fontspec} > \\usepackage{unicod

Re: fontsets

Juan Manuel Macías writes: > [1] I have to add, by the way, that MatchLowercase is not always a > panacea. Hmmm... maybe add optional extra config/output option to the fontset, like so: ┌ │ ;; Fonts │ ((myfonta . ((pdflatex . "etc.") (lualatex ...) (html ...) ...)) │ (myfontb ...) │ ...)

Re: [POLL] Proposed syntax for timestamps with time zone info

writes: > 2023-03-23 02:30 @Europe/Berlin refers to /two/ points in time, thus > it /is/ ambiguous. As far as I understand the definitions, the point in time "2023-03-23 02:30 @Europe/Berlin" is clearly defined as 2023-03-23 02:30 UTC+0100. A bit more problematic would be "2023-03-26 02:30 @Eur

Re: [POLL] Proposed syntax for timestamps with time zone info

Ihor Radchenko writes: > [2023-03-29 02:30 @Europe/Berlin] is special. I think you mean [2023-10-29 02:30 @Europe/Berlin]. :) -- Until the next mail..., Stefan.

Re: [POLL] Proposed syntax for timestamps with time zone info

writes: > ...which stems from the fact that the very concept of "time zone" is > somewhat ambiguous, too. Yes - I think most of us here see that. Therefore I really appreciate the flexible timestamp format Ihor suggested. > If you really want to have fun with this (and this thread hasn't > sati

Re: [POLL] Proposed syntax for timestamps with time zone info

Ihor Radchenko writes: > Note that an alternative is > [2022-11-12 10:30-11:00] > [2022-11-12 10:30-11] > [2022-11-12 10:30-11:00-11] > which is much less confusing. Hmmm... is it? I read a lot different timestamps these days and currently I'm very careful reading them, especially while co

Re: [POLL] Proposed syntax for timestamps with time zone info

Jean Louis writes: > Specifying time zone is not ambiguous as long as you use the TZ > database for specifications! That's wrong and you know it. For example [2023-10-29 02:30 @Europe/Berlin] is ambiguous. Period. And that some examples got a bit off has been quite obvious and has already

Re: [RFC] Refactoring org-element API

Hi Ihor, thank you for all your great work. I did not dive deep into all the details, but the overview you provided sounds sensible. One minor nitpick: I would prefer a function like ~org-element-property-1~ to be named e.g. ~org-element-property-lazy~ (or something similar), because the "-1" is

Re: exporting to PDF multi-lingual document

Hi. I got curious and it seems if you are willing to use lualatex (which is, I think, currently the most actively developed engine and nowadays a really good choice), the following solution should work: --8<---cut here---start->8--- #+TITLE: Doc multi-lingual

Re: exporting to PDF multi-lingual document

andrés ramírez writes: > I have tried the snippet. But It shows just Japanese and the other > paragraphs are not present on the PDF. That's quite strange. I just re-tested with emacs -Q (Emacs 28.2 with integrated Org 9.5.5). It generates the following tex file: --8<---cut here-

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > The downside of lualatex is that it is slower: > https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/ Yes, for sure. But I have the impression that newer versions of luatex have become a bit faster (maybe it's just a subjective impression that I want to be true, be

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > The downside of lualatex is that it is slower: > https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/ BTW: One of the discussion points in that thread has been the problem of default fonts. With pdflatex the default font is CM (Computer Modern) and if the appropria

Re: exporting to PDF multi-lingual document

"Dr. Arne Babenhauserheide" writes: > Isn’t the speed more relevant for large documents? I always had the impression that luatex has mostly a rather fixed overhead. Maybe that's because many of my larger documents make quite some use of TikZ and most time may be spend there. Therefore I assumed

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > AFAIR, the basic problem is that we cannot guarantee that any given > UTF font is installed. Yes, indeed. Probably the best route is to make tweaking as easy as possible. There are still too few (if any) really comprehensive (and good looking) Unicode fonts available. -

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > Though ideally all the necessary fonts should be provided by > TeXLive. I am not sure why they are not yet there in 2023. First problem: Is there any free/libre font out there that has a really broad and comprehensive coverage of Unicode glyphs? I really don't know, but

Re: New Orgmode LaTex Document Class ?

David Masterson writes: > I want to install a resume document class for LaTex There are the variables org-latex-classes and org-latex-default-class on the Org side, but that's only about some structural metadata (how to map Org headline levels to LaTeX structure macros). To find the new class f

Re: New Orgmode LaTex Document Class ?

Ihor Radchenko writes: > I'd prefer to put some more generic reference. Some info manual or > good stable URL link that has explanations about kpsewhich and other > LaTeX basics. What about http://mirrors.ctan.org/info/latex-doc-ptr/latex-doc-ptr.pdf No direct references to kpsewhich, but I

Re: Experimental public branch for inline special blocks

Hi Juan, first of all: Thank you for your great work. Looks really good. Just out of curiosity: Why a special syntax for alias expansion? >From a syntax and user point of view, I think I would prefer a simpler syntax. So &alias{text} would check if an alias is registered and if yes use it.

Re: `:export' attribute?: Re: Experimental public branch for inline special blocks

Juan Manuel Macías writes: >>> :export "latex+ html+ rest*" >> "rest" might be a valid backend name. > I will try to implement the "rest" option. What about "others" or even ":others" as a placeholder for any not explicitly mentioned export backend? Another quick thought crossing my mind: May

Re: [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?)

Ihor Radchenko writes: > This is not possible because of how `org-auto-repeat-maybe' is > designed. When repeater is triggered, the original date in the > timestamp is replaced with future date. So, we have no access to the > original date in the timestamp. And even if we would have access to th

Re: [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?)

Ihor Radchenko writes: > +1m! is awkward - what if [2024-05-12 +1m!]? You are right. I have not really spent time to think about a nice syntax. But I think it needs to be encoded in the increment part, not in the date part (because after the first increment, the information that we want the last

Re: [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?)

Ihor Radchenko writes: > It does not have to be lost. We can adjust the repeater function to > handle negative dates/months specially, so that > [2024-05--1 +1m] -> [2024-06--1 +1m] Hmmm... I do not like, that here the wrong month is displayed. On a cursory look, it's easy to assume the wrong m

Re: [RFC] latex preview and pdflatex-only packages

Ihor Radchenko writes: > Uwe Brauer writes: >> Well, there are a couple of packages that explicitly state that they >> only work with pdflatex, nicematrix, todonotes and ocgx for example > Are there packages that are an opposite - do not work with pdflatex, > but work with bare latex? Just to

Re: [RFC] latex preview and pdflatex-only packages

Stefan Nobis writes: > More general: Out there are quite some package that support only one > of the current engines xelatex, lualatex, or pdflatex. My gut feeling > is, that the majority works with any engine and more and more packages > tend to support the more modern engines

  1   2   >