Re: Smart quotes not working correctly with single quotes

t;'. >>> >>> I should get: >>> >>> | It's a \glq{}test\grq{}. "`Please"'. >>> >>> If I export to odt I get: >>> >>> | It’s a ’test’. „Please“. >>> >>> I should get: >>> >>> | It’s a ‚test‘. „Please“. >>> >>> (The odt example outputs use utf8, I hope it gets transmitted.) >>> >>> So in all three cases apostrophes and double quotes are correctly >>> exported, but not single quotes. Similar problem if I use "#+LANGUAGE: >>> en". >>> >>> I have org-mode 9.3 with emacs 27.1. >>> >>> What could I do to get single quotes to be exported correctly? >>> >>> Thanks a lot! >>> >>> Andreas >>> -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

[PATCH] org-entities: rename section with eth and thorn to "Icelandic"

Eth and thorn are letters in the Icelandic alphabet, and the language is in active use. TINYCHANGE --- lisp/org-entities.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org-entities.el b/lisp/org-entities.el index e32ce269b..5529f77ef 100644 --- a/lisp/org-entities.el

Re: wip-cite status question and feedback

Bruce D'Arcus writes: > On Thu, Apr 9, 2020 at 3:38 AM Albert Krewinkel wrote: >> Bruce D'Arcus writes: >> >> > On Wed, Apr 8, 2020 at 5:32 AM Nicolas Goaziou >> > wrote: >> >> "Bruce D'Arcus" writes: >> &g

Re: wip-cite status question and feedback

gt;> OK, but it is enough for Org to feed a CSL processor with, e.g., >> >> key-> "@doe99" >> prefix -> "see " >> suffix -> ", pp. 33-35" >> >> Then CSL processor does its job to extract whatever information it &

Re: Org <-> Gitlab Wiki

ions and then apply that manually to the Org file. Your should be able to take a shortcut here by using pandoc for the conversion back to org. It might even make sense to use pandoc for the opposite direction as well, but org-mode exporters are usually better at that. See https://pandoc.org and http

Re: [O] Question on nested-blocks syntax

Nicolas Goaziou writes: > Albert Krewinkel writes: > >> Is there any chance that indentation-based nesting will become legit >> org-mode syntax? > > I don't think so. It would introduce unnecessary complexity. I guess that makes sense. Too bad, though. Thanks for

[O] Question on nested-blocks syntax

ader. Is there any chance that indentation-based nesting will become legit org-mode syntax? Thanks, Albert -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

Re: [O] Org-sync status

-ware. Realistically, it is unlikely to materialize any time soon. So again, please let me know if you are working on something interesting in that regard. Cheers, Albert Aurélien Aptel writes: > Hello to org-mode mailing list subscribers & people CC'd in this email, > > I'm n

Re: [O] exporting zotxt or orgref links to HTML and ODF

ng one of the authors of pandocs org-mode reader, I'm very interested in learning the issues you experienced when converting directly to odt. Could you give some feedback on that? Thanks in advance, Albert -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

Re: [O] HTML --> Org-mode?

y in emacs is debateable, however. Cheers, Albert Pandoc: http://johnmacfarlane.net/pandoc/ Pandoc-mode: https://joostkremers.github.io/pandoc-mode/ -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

Re: [O] Other editors supporting Org-Mode

g them emacs) seems out of the question, it's qutie likely as good as it gets. Cheers, Albert -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124 -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

Re: [O] How to escape an asterisk on org-mode

the words that are to be printed in bold, i.e. *this is bold*, but * neither this* is, *nor this *. 2. Markup cannot span more than two lines: *this is not bold* HTH Albert -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

Re: [O] bug: in source block, titles are not seen as source

ame > goes for example blocks, and perhaps other things. You can escape leading stars by putting a comma in front of them: #+begin_src sh cat <<'EOF' ,* some text EOF #+end_src This should do what you want. HTH, Albert -- Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124

Re: [O] Pandoc users, how do you use it with org-mode, and why?

sing org's publishing features, but I found Hakyll/Pandoc to be more convenient and easier to use. Other uses include import of Markdown/HTML into Org documents and the use of Pandoc's support for references and citations; I rarely do that, though. Cheers, Albert [1] http://jaspervdj.be

Re: [O] Preserve formatting when copy/pasting from HTML

rse HTML and convert it to org-mode markup. There is also a helpful answer on stackexchange[3] (just replace "markdown" with "org). You might be able to use the above tools to integrate the mentioned techniques into org's capture mechanism. HTH, Albert [1] http://johnm

[O] [PATCH] org.el (org-offer-links-in-entry): Reuse global variable

* org.el (org-offer-links-in-entry): Use global variable `org-any-link-re' instead of defining a string-equal local variable. The `re' variable defined in function `org-offer-links-in-entry' is string-equal to `org-any-link-re' and is hence replaced by the latter. TINYCHANGE --- lisp/org.el |

Re: [O] [PATCH] org.el (org-offer-links-in-entry): Remove code duplication

Hi Bastien, Bastien writes: > Albert Krewinkel writes: > >> * org.el (org-offer-links-in-entry): Use `org-any-link-re' to avoid >> code duplication. > > This is not really code duplication, as the output of `org-any-link-re' > is different from the output

[O] [PATCH] org.el: Use `org-any-link-re' to avoid duplication

The `re' variable defined in function `org-offer-links-in-entry' is string-equal to `org-any-link-re' and is hence replaced by the latter. --- lisp/org.el | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index ad76e67..741529b 100644 --- a/lisp/o

[O] [PATCH] org.el (org-offer-links-in-entry): Remove code duplication

* org.el (org-offer-links-in-entry): Use `org-any-link-re' to avoid code duplication. The `re' variable defined in function `org-offer-links-in-entry' is string-equal to `org-any-link-re' and is hence replaced by the latter. This is a TINYCHANGE. --- lisp/org.el | 7 ++- 1 file changed, 2

Re: [O] [PATCH] Export: Override headline numbering via properties

Mark Edgington writes: >> Anyway, your patch will not work on back-ends that rely on Org to >> compute section numbers (e.g., ascii, html...) because even if you >> ignore numbering for a particular headline, it still adds up >> internally. IOW, you also need to patch >> `org-export--collect-hea

Re: [O] fill paragraph: math and latex environments

Nicolas Goaziou writes: > Hello, > > a...@fastmail.fm (Albert Z. Wang) writes: > >> I've just recently been having an issue I was wondering if anybody >> could help with, namely, that fill-paragraph does not seem to work as >> expected. >> >> For d

[O] fill paragraph: math and latex environments

doing the trick... I just recently did a big update of the emacs system after a few months, so it's possible there've been some relevant changes I'm unaware of, but I wasn't able to find a solution by searching. Thanks for any help! --Albert

[O] bug#11491: 24.0.96 instead of 23.0.96

The version string has an typo in the original report. I guess it is better to send it again with the correct version in the subject. Should/Can I close this bug-report? I will try. Albert.

Re: [O] fill-paragraph: wrong behaviour after latex-environments

Benjamin Motz writes: > Hi, > > invoking fill-paragraph on the following org-code will delete the > newline after \end{equation}: > > The relation > \begin{equation} > E=mc^2 > \end{equation} > won't be further discussed here. > > This behaviour is undesirable because it makes the org-text less >

Re: [O] Orgmode markups inside LaTeX fragments

\begin{} ... \end{} blocks, but if you can adapt your commands to be environments, this will get you what you want. -- Albert Wang