Re: Bug in ox.el

[Qiang Fang <godblessfq@gmail.com>]

>> Does this issue happen with "ox-odt.el" bundled with Org? If so, could
>> you provide an ECM?

The issue happen with list-table in the unofficial ox-odt, list-table enables
list in tables, it's very cool.

>> The standard version of org has a lot of limitations.
> Please report them, and, if possible, help fixing them.

Most problem I reported are fixed in this repo:
https://github.com/kjambunathan/org-mode-ox-odt

And I think there is no one more capable and willing to fix issues related to
ox-odt than the original author.

It will benifit more people if we can include it in the official org-mode.

Can anyone tell me whether if my approach will work:
The author of ox-odt gives me his code as a gift, and it becomes mine, the I can
do everything with it, right?

On 9/13/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Qiang Fang <godblessfq@gmail.com> writes:
>
>> The standard version of org has a lot of limitations.
>
> Please report them, and, if possible, help fixing them.
>
>> In case you won't check the issue because of it not copy right. The
>> complete bug
>> report is:
>>
>> "Lisp nesting exceeds ‘max-lisp-eval-depth’" exceeded, when using
>> cookies with List Tables.
>
> Does this issue happen with "ox-odt.el" bundled with Org? If so, could
> you provide an ECM?
>
>> org-export-table-cell-alignment uses org-export-data to infer cookies of
>> some
>> columns. I think, it should use other mechanisms like
>> org-element-interpret-data
>> (may be).
>
> I disagree. For example
>
>   | @@html:<b>text</b> 1.2 |
>
> doesn't express a number with `org-element-interpret-data', although it
> is a number when exporting, i.e., to LaTeX.
>
> There is only one way to know if the cell is going to be a number during
> export: effectively exporting it.
>
> Regards,
>
> --
> Nicolas Goaziou
>