less/less.js

[Feature Proposal] Better-optimized SVG encoding than URL-encoding and base64

Open

#3,105 建立於 2017年9月22日

在 GitHub 查看
 (1 留言) (3 反應) (0 負責人)JavaScript (16,977 star) (3,517 fork)batch import
good first issuelow priorityup-for-grabs

描述

I just came across this article which is relevant to Less w/ data-uri encoding: https://codepen.io/tigt/post/optimizing-svgs-in-data-uris

Basically, there was a discussion in the past about base64 vs. URL encoding for SVGs. (See: #2250 and #2184) There are a few additional optimizations in URL encoding that can make the encoding even smaller, as discovered by the research on that article. This is an improvement since URL-encoding by itself can inflate the output greater than base64 encoding.

貢獻者指南

技術棧
javascriptcss
領域
performancebuild system
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of Less .data uri() functionKnowledge of URL encoding vs base64Ability to read Less source code
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Examine the current data uri encoding implementation in Less's source code (likely in lib/less/functions/data uri.js). Review the discussions in #2250 and #2184 for historical context. Study the techniques described in the linked article (codepen.io/tigt/post/optimizing svgs in data uris) to understand potential optimizations. Implement a new encoding strategy that chooses the most compact representation between URL encoding, base64, and other optimized URL encoding methods, then submit a pull request.
[Feature Proposal] Better-optimized SVG encoding than URL-encoding and base64 · less/less.js#3105 | Good First Issue