Here's the 'other' TahrPup stamp: <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M42 56l-3 7m-4 0l3-1v4l-3 4zm-6 4l3-1v7l-3 3zm-6 0h3v13l-3 2zm-6-2l3 1v17l-3-2zm-6-5l3 2v14l-3-2zM5 48l3 5v15l-3-4zm40-7V21M41 4l3 9v36l-3-11zm-6 2l3-1v30l-3-...

Not as small in size as I hoped it would be, but it's as good as it gets. Here's the TahrPup stamp: <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M49 64c11 0 11-15 0-15-9 0-10 15 0 15zM23 86c0 8 10 8 13 8 16-1 39-30 40-32 0-21 11-19 12-25...

Another doggie stamp for those interested: <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M80 25l4 3c2 1 1 2 2 3s6 3 6 4c0 2-3 3-5 3-3 0-3-1-8-1-2 4-3 10-3 11l-1 5-1 2c0 4-2 7-2 8 0 14-5.455 16.242-2 27 2 1 2 1 3 1s2 1 2 2c-1 1-2 1-3 1h-3l...

Here you go trio! The stamps are now aligned to the bottom like the quirky stamp.

Try this Tux version. It shows normal in my browser preview window. <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M53 87c-3-10 8-11 13-11h5m-3-55c0-3-1-6-3-8m0 29v-5m3 8V17m3 31V23m6 43l-5-30m16 21l-18-9M28 21c0-3 1-6 3-8m0 29v-5m-3 8V17m...

Okay, gotcha! Good to know about the stroke-color as well. The tux svg is strange. After I optimize it, I get a big T shape when I see it in the browser preview window when I want to open it, but then when I open it in the browser it looks fine. I've tried another way of optimization with a program ...

Quirky stamp: <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M40 66c16 16 45 7 51-14H49m24 19c4 2 6 5 8 8m-21-5c9 4 12 7 14 11m12-13c-2-2-4-4-6-5m1-5v-4m-5 0h10m-5 5l7-8H74zm1 3c-5-3-10-8-11-14M30 68l11-7m-9 10l14-13-14 5zm-6-11l3 1v12l-3 ...

@solo, thanks but it doesn't work that way. The fill is done within the gui, not the actual stamp. Pls revise it to the same uniformed structure like the others. Okay, I'll remove the fill statement then. <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> ...

Awesome Trio! Here's a revised tux stamp that accepts a fill. <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M53 87c-3-10 8-11 13-11h5m-3-55c0-3-1-6-3-8m0 29v-5m3 8V17m3 31V23m6 43l-5-30m16 21l-18-9M28 21c0-3 1-6 3-8m0 29v-5m-3 8V17m-3 31V...

Here's a little bonus stamp: <svg xmlns="http://www.w3.org/2000/svg" width="96" height="96"> <path d="M68 21c0-3-1-6-3-8m0 29v-5m3 8V17m3 31V23m6 43l-5-30m16 21l-18-9M28 21c0-3 1-6 3-8m0 29v-5m-3 8V17m-3 31V23m-6 43l5-30M8 57l18-9m15-8l7 7 7-7c-3-3-11-3-14 0zm9.5-8...

Okay, that's good to know. Here's my revised version. A line thickness of 3 means the design becomes more simple in structure. That is to say that some lines that are used as filler are no longer needed. So the bonus is that the fatdog logo is now less than 1Kb in size. <svg xmlns="http://www.w...

Trio, is the line thickness of 3 a hard requirement as well? And fills are not possible?

P.S: Fatdog looks pretty good, apart from the tail. I'll post another version today.

Still not completely optimized, but a whole lot smaller. You have to understand, the more complex a design is the more gridpoints you need to snap the nodes and nodehandlers to, if you want good optimization and good accuracy. One gives way to the other in any other circumstance. <svg xmlns="ht...

That is going to be a bit difficult Trio. The logo itself, as you can see, is not square. I could try and fit it in a 96x96 grid, but then the line thickness would have to be 1. I will be while.... Okay, quick and dirty: <svg xmlns="http://www.w3.org/2000/svg" width="96" height=&...

It's not too difficult. I took a shot at it, and I came up with this <svg xmlns="http://www.w3.org/2000/svg" width="254" height="204"> <path d="M88.5 6.997c9-2 20.74-4 38-4 45 0 65.38 9.533 88 26 5.655 4.117 14.507 12.66 19 17 8-16.5-5-30-27-30 27-28 61 18.5 38 47 ...

This is pretty standard code for svg but it doesn't work in your app. <svg width="96" height="96"> <circle cx="50" cy="50" r="40" stroke="#444" stroke-width="3" fill="none" /> </svg> Smokey, very simply put, you execute...

@solo you cannot get libs from other puppy? Well, the problem is that every version of librsvg before 2.36 is potentially open to exploits. However, if I wanted to update librsvg to a later version than 2.36, like 2.40, then I run against at least 5 dependencies that require updating for it to func...

Really great stuff trio!

The problem for me, as I explained in a previous post, is my librsvg version, which is the library used for rendering svg's.
Precise Puppy runs librsvg version 2.36, which has problems.

I realize it's a bit of a weird request, since I'm not able to succesfully run your wallpaper maker on the Puppy I use, but I am very much interested in what it is capable of now, so I'd like to ask if it would be at all possible to post a sample wallpaper image. Because it seems like you are liftin...

How about this; an on-line in-browser Woof-ce gui frontend, which allows users to instantly create their own invidually tailored Puppy iso, by means of having them make choices according to their own preferences and requirements. You no longer have to work yourself through a myriad of different Pups...