Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou <n.goaz...@gmail.com> 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 this particular one is.
>>
>> Also, I you can use a filter to modify that string and make it comply to
>> a specific style, if needed. IOW, you also get 1) and 2) with the
>> `org-export-dictionary' way, with 1) being more user-friendly and 2)
>> more difficult than in the current way.
>>
>> 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"
(replace-regexp-in-string
"multicolumn{[0-9]+}{r}{\\(.*\\)}" "String 2"
row nil nil 1)
nil nil 1)))
(add-to-list 'org-export-filter-table-row-functions
'my-personal-table-continuation-strings)
Untested.
Regards,
--
Nicolas Goaziou
