Fix issues with vim.org vimlogo.svg

[Shay Hill]

Great logo, but the SVG file was in rough shape. I fixed the issues but had to make some minor changes. These are detailed in the README.

This version is made in Python/Vim. Where possible, I tried to infer and recreate the steps followed by the original designer.

If this SVG file were maintained on GitHub, I would create a pull request. Here it is for consideration.

ShayHill/vim_logo: Vim logo similar to the logo on vim.org (github.com)

[Christian Brabandt]

Shay,
Honestly, I don't understand half of what you detailed in the Github
Readme 🙈 but I cannot see a difference between the README logo and the
output/vim_logo.svg. I suppose this is a good sign :)

I'd like to hear a few more opinions, and if I don't hear a lot of
complaints, I happily include it in the Vim repo. Let me know, what
parts I should include (I suppose the source not sure about the tests).
You can also create a PR against the Vim repo.


Thanks,
Christian
--
take forceful action:
Do something that should have been done a long time ago.

[Shay Hill]

Thank you. The cosmetic differences at low resolution are minor. The important changes are in the construction. Those internal differences are important if you ever want to cut vinyl stickers, make some variant, render a large image, or make additional changes algorithmically. Quality problems *may* be why so many people have re-created the logo for Wikipedia and other projects. In my opinion, all of those variants lack the charm of the *real* Vim logo.

IMO, only the SVG file itself should go into the repo. I'm happy to maintain the Python code that created it, but there are *many* ways someone might want to update the logo in the future, and learning / updating my codebase would be the least straightforward way.

I will create a pr if you let me know where you'd like to put the SVG file--the file is plain text.

[Christian Brabandt]

Shay

On Fr, 26 Jan 2024, Shay Hill wrote:

> Thank you. The cosmetic differences at low resolution are minor. The
> important changes are in the construction. Those internal differences
> are important if you ever want to cut vinyl stickers, make some
> variant, render a large image, or make additional changes
> algorithmically. Quality problems *may* be why so many people have
> re-created the logo for Wikipedia and other projects. In my opinion,
> all of those variants lack the charm of the *real* Vim logo.
>
> IMO, only the SVG file itself should go into the repo. I'm happy to
> maintain the Python code that created it, but there are *many* ways
> someone might want to update the logo in the future, and learning /
> updating my codebase would be the least straightforward way.
>
> I will create a pr if you let me know where you'd like to put the SVG
> file--the file is plain text.

Shay, thanks so much. If you could create a PR that will play the logo
file to the runtime directory? That would be prefered, we already have
the other logos there so it should be fine. And please also include it
in the Filelist (along with the others, that are already there).

If you want, you can link your repo in the commit message or in an
accompanying readme for reference.


Thanks,
Chris
--
I'm serious about thinking through all the possibilities before we
settle on anything. All things have the advantages of their
disadvantages, and vice versa.
-- Larry Wall in <1997090323...@wall.org>