CopperSpice Forum

Hi Mauricio, We have resolved the issue you reported in the latest version of DoxyPress and we have been able to run your project successfully on our Windows 7 64-bit machine. Please give DoxyPress 1.2.9 a try and let us know how things work for you. Please do continue to let us know of any enhancem...

Hi Mauricio, Thank you for your kind words and your detailed bug report. This should help us track down the issue. We appreciate your interest in our project. We are speaking at a C++ conference in a week and we are in the final preparation. We will make sure to look at this issue as quickly as poss...

Thank you for your report.

You mention trying the following syntax: This syntax makes sense and should be allowed, but is not currently supported. I have filed a ticket to support this case:

http://redmine.copperspice.com/issues/31

Thanks for the suggestion.

Barbara is going to look into this and we will make some changes so that this menu item links to the correct documentation online.

Hi jdjd, The doxypress binary package expects to use the packaged version of clang, rather than individual files. Instead of extracting the individual libraries, can you try running: apt-get install libclang-3.7-dev libllvm3.7 Once those packages have installed, you should not need to add any additi...

Hello Jurrien, Thank you for looking at CopperSpice. Android support is definitely on our radar but we do not currently have an ETA. As for iOS support, the situation is more complex from a legal standpoint. CopperSpice is licensed under the LGPL, so end users must be allowed to re-link any CopperSp...

We have found and resolved this issue. The resolution of this warning will be released in 1.2.5, scheduled for release in December.

Thank you for your report!

Have you been able to reproduce this issue with a test case you can share? We have been unable to reproduce the issue as described.

I'd like to confirm what encoding your input files are in, and what encoding your browser has detected for the HTML output. We strive to support UTF-8 on input and output however there may still be some code that is not unicode aware. Andrew is correct that the ± HTML entity is more widel...

Just for reference, this issue was resolved earlier this year.