@Chris - I had the same issue with wma_ fonts (matlab appear to have renamed their fonts at some point, and illustrator seems to demand that the specified font is installed on the system even if it is embedded in the file??).
I solved the problem by [using Mac OS X], by installing TTX and using it to rename my cmr10 and cmmi10 system fonts as mwa_cmr10 and mwa_cmmi10 (and then installing these new fonts). For step by step instructions, see: http://www.fontgeek.net/blog/?cat=7
I also ended up installing FontForge and replacing some of the glyphs in cmmi10, which were a bit wonky in my version (e.g., triangles instead of decimal points)
Prima facie, this looks well written and well documented. It seems to give results that are highly correlated with, but slightly from, various websites (all of which agree with each other). For example:
ans = 2.5549
Whereas the following all give it as 2.549
The difference is small though, particularly at large N, and any fault may lie with the websites rather than this function (unsure). Any explanation for this difference would be much appreciated.
thanks a lot for this great tool. I recently used it in a project on the windows platform and was very happy with it. However, I will now do a project on a linux platform and unfortunately I get parse error during post processing. I have boiled it down to the following:
My test m-file is very simple:
c = a+b;
and when I run MatlabDocMaker.create, I get the following error in warnings.log
mtoc++ postprocessor messages:
/home/widhe/git/solar/matlab/qrt_toolbox/doc/foo_8m.html: PARSE ERROR
< matlabtypesubstitute, c > </td><td class="memItemRight" valign="bottom"><a class="e
If I remove the return value like this:
c = a+b;
everything works as expected.
I have also tried to run the failing m-code on windows without any problems (exactly the same configuration files etc), which leads me to think this is a linux problem.
I compiled according to the instructions on http://www.morepas.org/software/mtocpp/docs/install.html. During make install I get similar parse errors (I think the documentation is build using mtocpp during make install, is that correct?). Anyway, after make install, make test seems to work:
widhe@fluffy:build$ make test
Test project /home/widhe/install/mtoc++/mtoc++_1.5/build
Start 1: MTOCPP_TEST
1/2 Test #1: MTOCPP_TEST ...................... Passed 0.11 sec
Start 2: MTOCPP_DOXYTEST
2/2 Test #2: MTOCPP_DOXYTEST .................. Passed 0.03 sec
100% tests passed, 0 tests failed out of 2
Total Test time (real) = 0.14 sec
I'm running ubuntu server 12.04
mtoc++ version 1.5
doxygen version 1.8.7
ragel version 6.7
gcc version 4.6.3
Any help greatly appreciated!
Hey, very nice tool, BUT:
It does not work if you declare methods of classes with spaces between the braces.
function myFun ( in1, in2 )
I often do this for better readability so maybe you could consider taking this into account.
Very nice tool.
A question though: I have a number of functions that forward their (optional) arguments via varargin like:
% varagin: optional parameters
% a1: argument 1
% a2: argument 2
Works nicely but mtoc++ inserts a 'Required Parameters for varargin' before the a1, ... list. Is there a way to make it print 'Optional parameters for varargin'?