You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to how most image formats (WEBP, AVIF, PNG, JPG, GIF, etc) have an icon association to depict that they are images, could there please be a conventional icon for localization files?
By default, this icon would be associated with formats like:
XLIFF (*.xlf)
TMX (*.tmx)
Fluent (*.ftl)
PO (*.pot / *.po)
etc
Some extensions may choose to reuse the icon for custom formats. Other broader file formats (like *.json) that extensions know to be a language file in the context of the libraries/stack used may use the icon as well.
I think this is something that would have to be added to https://github.com/jesseweed/seti-ui, the default file icon font used by VS Code. From there we may have to do more work to actually render it where appropriate. @isidorn may have more details there since we've talked about new icons in Seti before.
Yes, I think that is all there is to it. Adding to the seti built-in theme.
But I would not add this right away, I suggest we keep this issue open to gather more user feedback.
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Similar to how most image formats (WEBP, AVIF, PNG, JPG, GIF, etc) have an icon association to depict that they are images, could there please be a conventional icon for localization files?
By default, this icon would be associated with formats like:
*.xlf
)*.tmx
)*.ftl
)*.pot
/*.po
)Some extensions may choose to reuse the icon for custom formats. Other broader file formats (like
*.json
) that extensions know to be a language file in the context of the libraries/stack used may use the icon as well.Related
The text was updated successfully, but these errors were encountered: