Test & rate, I'll rest now

I'm thinking of implementing a simple formatter for HTML entities in file and folder names. It would handle unsupported characters by converting them. This might sound too nerdy, but why not?

For example, you generally can't use these symbols in a name: ?, :, *, |, /, \, <, >, "

But if you type their HTML entity (like ? or ?), the formatter would replace it with the corresponding Unicode symbol (e.g., "?").

So basically:
[ SHOW NAME ] EPISODE X: NAME
would be reformatted to:
[ SHOW NAME ] EPISODE X: NAME

As I mentioned some months ago, these «formatting» tricks are intended genuinely for enthusiasts.

I could also enhance the default renaming mechanism to automatically convert characters like "?" into their HTML entities right after renaming. This integrated solution would save users from having to look up these codes on the internet. It also deprecates the renaming error entirely.

right now it supports only 3 characters (idk others that can be used)

I'll remove some additional action info in the snackbar UI, that usually makes the message unreadable at all. Currently it shows the message like this:

Failure:

Unable to delete this video.

Success:

*File name* has been permanently deleted.

If the file name is long, rest of the message disappears due to the preset max amount of lines (e. 2).

Future version

Failure:

The video could not be deleted.

Success:

The video was permanently deleted.

I like to keep people informed about upcoming changes :p

Imagine deprecating API 31/32 and making the app to work only on API33 (Android 13) and up

so now we can make snackbars rounded

bro, i just woke up and thought they're the same person lmao

I have updated the sorting logic to ignore whitespace (such as spaces between words or numbers) for more precise results. It also now supports locale-aware sorting, which properly handles accented characters according to alphabetical standards.

Whitespace removal prevents incorrect lexicographical order. For instance, «A 1» would be sorted before «A» due to the spacing between word and number. Stripping whitespace ensures the sort is based on the intended alphanumeric characters.

Example:

A -> A
A 1 -> A1
ABC -> ABC
A BC -> ABC

(Upper cases first)

P.S. I'm still trying understand how it works so it'll be implemented as an experimental feature (you won't be able to toggle it off :D)

Please, note that the proper alphabetical sort depends ON SYSTEM/APP language.

instead of numeric reference it'll use named reference