Nicu Buculei wrote:
Haakon Meland Eriksen wrote: 1. Fonts to paths == none-text, thus not indexable or searchable in a > browser, and well ... not fonts. I think this is a NO-NO. The text should stay as text and not be converted to path, eventually the search engine will support and index it (and on top of that, converting a lot of text to paths will make the file size huge).
I agree. If you take a look at my example site at http://far.no/svg/, you will notice that only titles and menu items are paths. This is an artistic choice. I find those fonts fun and in tune with the vivid colours and childlike simplicity of the rest of page and Inkscape itself. I think you will agree your solution is technically correct, but not artistically correct. I have done what you recommended in the past, but I find it uninteresting and backwards, and I will not endure it any longer. Typefaces are drawings and should be treated as part of the overall composition, not as "just text". Imagine Leonardo painting "Mona Lisa" today using SVG, and then the engineers came and told him: "Listen, you really can't have this Mona object in there. It's not standard. It's the smile, you see. It's not supported on most operating systems, so we suggest a fall back solution with a cow, and if that's not supported then a piece of lettuce." I doubt embedding fonts is the way to go, if it was, why isn't it used?
- Honouring Z-order.
This is a bug in the browser and should be fixed by the browser.
Ah, good. Another problem is browser zooming with CTRL and + or CTRL and -. If you try this with Firefox 2.x, you will notice that only the text become bigger or smaller, not the rest of the SVG design.
- Text is not treated as text by Firefox, which means you cannot search > and more seriously - you cannot select and copy (being mindful of > copyright or copyleft).
Yeah, the search does not work, but I believe the feature will be added to Firefox once it will be needed enough.As for select and copy, sure, it would be nice to have, but license-wise for the time being, the workaround of looking at the source and copying from there is not that bad.
You and I know this workaround is possible, but we are the minority. The majority report will be quite different: this sucks.
Cheers, Haakon