Hi, 2016-10-28 13:09 GMT+02:00 Andreas Tille <andr...@an3as.eu>: > Hi, > > I really want to update cimg since a long time, missing several upstream > releases but I cimg does not build due to #836168. In the bug report it > was also suggested to use sphinx as doxygen replacement but I'm not sure > how sensible this might be since upstream is using doxygen. > > Since there is no real progress with doxygen (3 RC bugs no relevant > trafic) I seriously consider droping the doxygen documentation for cimg > at all and recommend users to live with the online documentation. I do > not consider this a good solution but if cimg will not be uploaded soon > this will also affect opencv transition. > > What do you think about the "droping documentation since it breaks the > package build" idea?
In a similar situation I worked around the issue and preprocessed the broken latex input to fix the unescaped characters. Cheers, Balint
