the default cairo backend always creates confusion .. so changed the default backend to native one , and user has to set ECTOR_BACKEND=cairo to use cairo backend
Until we do have a proper test suite that make sure we do match SVG specification, we can't switch to our own backend as cairo already proved they can do SVG support and we haven't. If you just rename, default to freetype as it was before, it would be as accurate and I would accept that patch.
If you want to make our freetype based one the default, we need a test suite. Also I am pretty sure we are not following SVG specification correctly at the moment as a bug open by @vtorri is still not closed/investigated.
so what to do with this? abandon? i assume so - not ready yet. need more tests. even so ft outline rendering may not match ciaro pixel for pixel but that's kind of ok. we need to ensure its correct or not for sure.
imho, if cairo backend has bugs that the native one has not, and if it is not maintained anymore, it should just be dropped
we have too much dependencies and the EFL should be simplified (less configuration, less code to maintain)