Codeberg/Design
Archived
23
51
Fork
You've already forked Design
4

Separate optimized vs. inkscape icon designs #86

Closed
opened 2023年11月15日 12:26:57 +01:00 by circlebuilder · 4 comments

I noticed that the /logo/icon/svg are Inkscape designs, and they carry a lot of extra baggage. On supertinyicons.org there's a codeberg.svg of only 436 bytes in the blue variant, but not in monochrome (white).

It may be better if both optimized and inkscape designs (with filename extension _inkscape) would be available.

The online SVGOMG optimizer can be used with preferred settings to process the Inkscape designs.

I noticed that the `/logo/icon/svg` are Inkscape designs, and they carry a lot of extra baggage. On [supertinyicons.org](https://supertinyicons.org) there's a [codeberg.svg](https://github.com/edent/SuperTinyIcons/blob/master/images/svg/codeberg.svg) of only 436 bytes in the blue variant, but not in monochrome (white). It may be better if both optimized and inkscape designs (with filename extension `_inkscape`) would be available. The online [SVGOMG](https://jakearchibald.github.io/svgomg/) optimizer can be used with preferred settings to process the Inkscape designs.
Collaborator
Copy link

Personally, I'm not particularly interested in the race to the bottom of SVG filesize, (especially if there isn't an excessive misuse that got out of hand).

#80 Covered a certain case, if you can come up with a logo that is smaller but changes nothing other than the file size. I'm down to accept updates. If you want to propose an update please make sure that colors and exact position of all paths are 100% the same (not only in your favorite browser but on applications like Inkscape and the most browsers).

Personally, I'm not particularly interested in the race to the bottom of SVG filesize, (especially if there isn't an excessive misuse that got out of hand). https://codeberg.org/Codeberg/Design/issues/80 Covered a certain case, if you can come up with a logo that is smaller but changes nothing other than the file size. I'm down to accept updates. If you want to propose an update please make sure that colors and exact position of all paths are 100% the same (not only in your favorite browser but on applications like Inkscape and the most browsers).

The consideration was mostly about smaller sizes of images to save energy and get slightly better page load times for those on slow connections. Logo's are used in many, many places, so it adds up. A basic run of SVGOMG for instance by a SVG noob like me, on codeberg-logo_horizontal_blue.svg brings down its size nearly by half (9.2kb --> 5.3kb).

codeberg-logo_horizontal_blue-optimized.svg

The consideration was mostly about smaller sizes of images to save energy and get slightly better page load times for those on slow connections. Logo's are used in many, many places, so it adds up. A basic run of SVGOMG for instance by a SVG noob like me, on [`codeberg-logo_horizontal_blue.svg`](https://codeberg.org/Codeberg/Design/src/branch/main/logo/horizontal/svg/codeberg-logo_horizontal_blue.svg) brings down its size nearly by half (9.2kb --> 5.3kb). ![codeberg-logo_horizontal_blue-optimized.svg](/attachments/27f111d0-6931-4a71-82d4-95342ced5398)
Collaborator
Copy link

I don't feel like we need to care about optimization of resources others may put to use. I care about the resource being correct, in terms of exact color and position values as well as met-information more than a few saved bytes. If somebody wants to optimize it – most probably the best approach is: taking into consideration what the specific usecase is, removing all redundant information.

I'm not willing to maintain or come up with this kind of optimizations but am not opposed to people putting in the effort and contributing it.

I don't feel like we need to care about optimization of resources others may put to use. I care about the resource being correct, in terms of exact color and position values as well as met-information more than a few saved bytes. If somebody wants to optimize it – most probably the best approach is: taking into consideration what the specific usecase is, removing all redundant information. I'm not willing to maintain or come up with this kind of optimizations but am not opposed to people putting in the effort and contributing it.

I highly appreciate your work! Fully understand 👍

I highly appreciate your work! Fully understand 👍
Commenting is not possible because the repository is archived.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
Kind: Breaking
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Maintenance
Kind: Public Relations

Design relevant outside of Codeberg
Kind: Question
Kind: Security
Kind: Testing
Kind: Web Design
Part: Color Palette
Part: Design Kit

Codeberg Design Kit
Part: Fonts
Part: Logo
Part: Navbar

Codeberg's navigation bar
Part: Themes

Gitea themes
Priority: Critical

The priority is critical
Priority: High

The priority is high
Priority: Low

The priority is low
Priority: Medium

The priority is medium
Reviewed: Confirmed

Something has been confirmed
Reviewed: Duplicate

Something exists already
Reviewed: Invalid

Something was marked as invalid
Reviewed: Wontfix

Something won't be fixed
Status: Blocked
Status: Completed

Work is complete
Status: Help wanted
Status: In progress

Work is in progress
Status: Needs feedback

Feedback is needed
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Design#86
Reference in a new issue
Codeberg/Design
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?