Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new icon for bulk rename #208

Open
philipzae opened this issue Apr 13, 2020 · 4 comments
Open

new icon for bulk rename #208

philipzae opened this issue Apr 13, 2020 · 4 comments

Comments

@philipzae
Copy link

With the generic file manager, thunar and bulk rename all sharing the same icon, its difficult to distinguish them apart and instead a dedicated icon for bulk rename should be made.

We can take the existing thunar icon, remove the home from it and maybe add an 'A -> B' on the folder.

preview

@ochosi
Copy link
Member

ochosi commented Apr 14, 2020

I would only use letters in icons as scarcely as possible. Please keep in mind that not everyone uses Latin characters or LTR direction.
So this surely won't look/feel nice to everyone...

@philipzae
Copy link
Author

Even if users of other languages don't use latin characters, most people are aware of them, so using them as symbols to illustrate an action isn't problematic. We currently have english alphabets for Fonts and Dictionary icons.

By the way, i've worked with designers of LibreOffice's various icon themes. :D

@marcosins
Copy link

If letters are a problem, maybe you could use the i-beam pointer to convey text manipulation.

Some references:

Theme Icon Name
Oxygen actions-edit-rename.svg
Yaru yaru rename source-symbolic.svg

A quick mockup i did mixing Oxygen and Current Thunar icon. For 16x16 it could use only the I without the textbox:
mockup

@philipzae
Copy link
Author

The i-beam pointer looks like an I and likely would be misunderstood as one as well. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants