Raj Patel

These should be invisible until you need them, and none of them should require an account or a network call. A slug is a URL fragment, so the characters that are legal in a URL, legal in a path segment, and safe on every filesystem are three different sets, and a generator should tell you which set it is targeting. Transliteration of accents is a policy choice rather than an algorithm, and a name with two reasonable spellings cannot be transliterated back to the original. Collisions are the other half. Two articles can reduce to the same slug, and the options are to append a discriminator, to fail loudly, or to silently overwrite. Only one of those is safe, and it is worth stating which a tool does. Counters are simpler but have the same definition questions as the word count section, and I point there rather than restating. Formatting utilities, by which I mean wrapping, trimming and fixing whitespace in a field for a form, have one rule: never trim silently. A field the user filled in should not lose characters because the tool decided they were unnecessary. Everything here runs on your device, which for text processing is not a performance decision so much as a privacy one. Where a tool has to make a decision a person would have made, I would rather it refused and asked than guess quietly. A utility that guesses is a utility that surprises somebody at the worst moment. I would also keep the count of words separate from the count of characters, because a limit written for one is usually enforced against the other.