X-Git-Url: https://gitweb.michael.orlitzky.com/?a=blobdiff_plain;f=README;h=db832277dce48aa7272d9b55afe60ac09f147966;hb=refs%2Fheads%2Fmaster;hp=7df72d2ef5334df9ec61e431418b2e46c58714c4;hpb=83f5680b39a1b77b24bdbce414354625be558bcf;p=libsvgtiny-pixbuf.git diff --git a/README b/README index 7df72d2..db83227 100644 --- a/README +++ b/README @@ -1,3 +1,5 @@ +libera te tutemet ex inferis + == Overview == This package builds a GDK Pixbuf Loader for the SVG format that uses @@ -32,10 +34,10 @@ The blessed solution to this problem is to use librsvg: That package builds a pixbuf loader that can be plugged into GTK, allowing it to import SVG files into a GdkPixbuf, and everything is -great. Until January 3rd, 2017. On that day, librsvg-2.41.0 became the -only dependency of GTK that requires Rust, which in turn requires -LLVM. The rest of GTK (and its dependencies) are written in C or -C++. This has several downsides: +great. Or was, until January 3rd, 2017. On that day, librsvg-2.41.0 +became the only dependency of GTK that requires Rust, which in turn +requires LLVM. The rest of GTK (and its dependencies) are written in C +or C++. This has several downsides: * Rust is big and slow to compile * LLVM is big and slow to compile @@ -44,7 +46,7 @@ C++. This has several downsides: security vulnerabilities [0]. It's not feasible to keep the old librsvg around forever, because that -will *also* result in security vulnerabilities. Which brings us to... +will ALSO result in security vulnerabilities. Which brings us to... == Why == @@ -52,28 +54,41 @@ Because if you have a problem with any of the bullet points above, then you need to replace librsvg if you want to keep using GTK. And, * libsvgtiny is written in portable C - * libsvgtiny is actively maintained - * libsvgtiny is already packaged on a few distributions as part of the - netsurf browser + * libsvgtiny is still maintained; there are no open security + issues + * libsvgtiny is already packaged on a few distributions as part of + the netsurf browser == Caveats == -This is a REPLACEMENT for librsvg, and cannot be used alongside it -(the filenames and mimetypes clash). - The main downside is that libsvgtiny isn't as robust as librsvg. It renders some things wrong, or a bit uglier than its counterpart. These are in theory all fixable upstream however, and you will help the -netsurf browser by doing so. Regardless, it more or less works. +netsurf browser by doing so. + +One especially relevant shortcoming is that libsvgtiny doesn't handle +