Sorry, I didn't mean to take this discussion off-list.

Thanks, I get it now. The fact that both error messages have that "</td>" tag 
does make you wonder if the two issues are related. But I agree it's worth reporting on the bug 
tracker.


On 1/27/2020 11:13 PM, Dirk Dickmanns wrote:
|Adding "&nbsp;" or whitespace and some additional text correctly removed the appended 
||"|</td>" from the target name in the error message, but still the (now correct) \copybrief 
target is not found.||
||
||
||You are right, its not related to cross-references and yes, my problem 
started in 1.8.16.||
||
||
||Sounds like I should report it as bug...||
||
||
||Thanks,||
||
||
||Dirk
||

On 1/27/20 3:24 PM, DonM wrote:
Not sure what you mean. Both this thread and the thread you started (\copybrief 
for \file not working after 1.8.15?) discuss the failure of copybrief to copy 
the brief text. It has nothing to do with cross-references.

Adding `"&nbsp;"` does correct the problem of copybrief not copying text in a 
markdown table. I did not test it in a file description.

I believe the two threads report different problems. Failure in a markdown 
table occurs starting with version 1.8.17. It works correctly in 1.8.16. Your 
problem of copybrief in a file description fails in 1.8.16.

On 1/26/2020 10:31 PM, Dirk Dickmanns wrote:

Thanks for the hint, DonM, I see the "|</td>" at the end of the refs as well.|

|Adding "&nbsp;" or whitespace and some other text corrected this, but to no 
avail, the refs remain broken.|

|It happens both inside and outside of tables.
|

Dirk


_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Reply via email to