Letter case: useful cleanup, not automatic copy editing
An all-capitals list can be made easier to read in seconds. That does not automatically restore the correct spelling of names and brands. Decide which change you want, and keep the original when its spelling matters.
Case is not a feature of every script
Arabic has no uppercase/lowercase distinction, so Arabic text may remain unchanged while embedded Latin words change. Case conversion is neither translation nor spelling correction.
Some mappings depend on language. Turkish pairs i with İ and ı with I. The same visible input can therefore produce a different correct result under a different language setting.
References: Unicode Standard — Case mappings and language-sensitive casing
A title-shaped result is not a style guide
Capitalizing word beginnings is a useful first pass for a list or heading. It does not know which connecting words your publication keeps lowercase or how a product name uses mixed capitals.
Review names and acronyms afterward. API can become Api, and iPhone can become Iphone. Those are predictable mechanical transformations, not editorial recommendations.
Changing back may not recover the original
A mapping such as ß to SS loses information: lowercasing SS does not restore the original letter. Review before replacing an important source copy.
Use case conversion for ordinary display text, not passwords, filenames or program values whose case may matter. ToolRoof uses the interface language for casing; it does not automatically identify each word’s language.
References: Unicode Standard — Case mappings and language-sensitive casing
Example: city names and a heading with an acronym
Uppercasing istanbul izmir in Turkish gives İSTANBUL İZMİR. In English it gives ISTANBUL IZMIR. The difference in dots is a language rule, not a font fault.
The word-initial capitals mode turns iPhone API into Iphone Api. That can be a helpful first pass for ordinary text, but a published heading still needs those names restored to their intended spelling.