Carsten Dominik <carsten.domi...@gmail.com> writes: > On 27.10.2013, at 09:05, Nicolas Goaziou <n.goaz...@gmail.com> 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 support >> for internationalization in `org-export-dictionary'? > > I agree that this would be better. > > - Carsten >
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, variation in 2) is idiosyncratic, though I haven't looked specifically at table continuation lines. The user can solve both 1) and 2) with customizable continuation strings, so it might be best to stay on this path instead of hardcoding and internationalization in org-export-dictionary. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
