DocBook: implement CALS tables

[Richard Kimberly Heck]

On 7/13/20 2:51 AM, Richard Kimberly Heck wrote:
> On 7/13/20 2:49 AM, Richard Kimberly Heck wrote:
>> On 7/13/20 2:29 AM, Jürgen Spitzmüller wrote:
>>> Am Montag, den 13.07.2020, 03:41 +0200 schrieb Thibaut Cuvelier:
>>>> Dear list, 
>>>>
>>>> Here is a patch to improve DocBook support by allowing the user to
>>>> choose the way they want tables to be output (i.e. either HTML or
>>>> CALS, right now). This amounts to including a switch in the GUI (did
>>>> I do this right? the diff for the .ui file is quite large for what it
>>>> does) and, depending on the value, output in HTML or CALS. 
>>> I only had a quick look, but as you introduce a new buffer param, you
>>> need to change the file format and add lyx2lyx reversion routines.
>> And see lib/doc/Development.lyx for some info about that.
> PS In this case, it will not be possible to preserve output when
> reverting to an older format, since we do not have any construct (like
> ERT for DocBook) that could possibly allow that. So the reversion will
> simply involve deleting the new param. (And the forward conversion will
> involve adding a default value.) This need not be done in the same
> patch. Sometimes, it is not even done by the same person. E.g., I'd be
> happy to do it for you in this case.

All that said (and checking with other devels): If the lyx2lyx is not
included in a given commit, should LYX_FORMAT be updated in that commit?
Or should that only be done when the lyx2lyx is committed? If we did it
earlier, then LyX would complain quite a lot.

Riki