Nicolas Goaziou writes:
> In a nutshell:
>
> (defun my-personal-table-continuation-strings (row backend info)
> (when (org-export-derived-backend-p backend 'latex)
> (replace-regexp-in-string
>"multicolumn{[0-9]+}{l}{\\(.*\\)}" "\\ldots\\ continued from previous
> page"
>
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I have this, based on the example above:
>
>
> #+name: tsd-continuation-strings
> #+begin_src emacs-lisp
>
> (defun my-personal-table-continuation-strings (row backend info)
> (when (org-export-derived-backend-p 'latex)
> (replace-regexp
Nicolas Goaziou writes:
>> An example filter?
>
> (defun my-personal-table-continuation-strings (row backend info)
> (when (org-export-derived-backend-p 'latex)
> (replace-regexp-in-string
>"multicolumn{[0-9]+}{l}{\\(.*\\)}" "String 1"
>(replace-regexp-in-string
>
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
Am I missing something?
>>>
>>> An example filter?
>>
>> (defun my-personal-table-continuation-strings (row backend info)
>> (when (org-export-derived-backend-p 'latex)
>> (replace-regexp-in-string
>>
Nicolas Goaziou writes:
>>> Am I missing something?
>>
>> An example filter?
>
> (defun my-personal-table-continuation-strings (row backend info)
> (when (org-export-derived-backend-p 'latex)
> (replace-regexp-in-string
>"multicolumn{[0-9]+}{l}{\\(.*\\)}" "String 1"
>(
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> I agree customization is more powerful here (although it means that all
>> non-English Org users will need to change it), but so it is for every
>> other multilingual string.
>>
>> Since we didn't choose to make multil
Nicolas Goaziou writes:
> I agree customization is more powerful here (although it means that all
> non-English Org users will need to change it), but so it is for every
> other multilingual string.
>
> Since we didn't choose to make multilingual strings customizable, I find
> it strange that th
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I think there are two axes of variation here:
>
> 1) internationalization, and
> 2) style guides, e.g., for a particular journal, Chicago Manual, etc.
>
> IIUC, hardcoding and org-export-dictionary solve 1) but not 2).
>
> In my experience, variatio
Carsten Dominik writes:
> On 27.10.2013, at 09:05, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> The attached patch should be applied on top of the earlier patch. It
>>> makes the continuation strings customizable.
>>
>> Wouldn't it be better if these
On 27.10.2013, at 09:05, Nicolas Goaziou wrote:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The attached patch should be applied on top of the earlier patch. It
>> makes the continuation strings customizable.
>
> Wouldn't it be better if these strings where hardcoded, but with s
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> The attached patch should be applied on top of the earlier patch. It
> makes the continuation strings customizable.
Wouldn't it be better if these strings where hardcoded, but with support
for internationalization in `org-export-dictionary'?
Mean
Aloha all,
The attached patch should be applied on top of the earlier patch. It
makes the continuation strings customizable.
All the best,
Tom
>From 2b3fbcf9a8ea64ef6207237ef48b9c62cded01ff Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Sat, 26 Oct 2013 14:37:30 -1000
Subject: [PATCH] Longtab
12 matches
Mail list logo
