Thomas Worthington wrote:
Is anyone actually working on fixing the font problems (ie, no styles except the very basic ones)? This is a total show-stopper for professional use. If no one is working on it, is there a guide to how to start on working with the Inkscape code, submitting patches etcetera?
Hi Thomas,
AFAIK nobody is working on it. I hope you can improve things! It is really appreciated a lot :-) I assume you are working on windows. Although badly out of date, you can find some hints here: http://inkscape.modevia.com/win32_inkscape_org/win32buildnotes.html I cannot access the wiki at the moment, I think there is a page there that has more up to date information. Here is a brief list of how to get inkscape built: 1. Get the code from SVN, using for example TortoiseSVN. Checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk 2. At http://inkscape.modevia.com/win32libs/?C=M;O=D you can download the latest library packages. You need gtk210-070527.7z and mingw-4.2.0-070518.7z or anything newer. Unpack them (for ease you can unpack them to c:\gtk210 and c:\mingw but it should not matter) 3. Check the contents of mingwenv.bat (inkscape root dir) to see whether the directories are correct. 4. Go to cmdline and to the inkscape dir and enter mingwenv.bat g++ buildtool.cpp -o btool.exe btool 5. An inkscape dir is now created there and you have built your own inscape! (note that if you change a lot of includes (i.e. dependencies), you should delete build.dep before running btool again; if that doesn't work you must do 'btool clean' and then run btool again.)
TortoiseSVN can easily create patches that you can submit. Note that you get SVN commit access when 2 of your patches are accepted :-) If you have more questions, you can mail me any time; although these weeks I will probably not be able to respond.
Cheers, Johan