You are not logged in.
In the Case rule, the Force case fragments section requires us to define all variants of the acronym.
For example, if I have entered STP or KPI, it will not work on the words stps and kpis to make them STPs and KPIs.
The original cases do not change at all.
Desired: The plurals of the acronym should be handled well.
Offline
Two potential problems:
1) Conflicts between an abbreviation and a plural form of another abbreviation, i.e. ABCs and ABCS, if we consider that both ABC and ABCS are valid abbreviations.
2) Handling trailing "s" is relatively easy, but what about other languages?
Offline
2) Handling trailing "s" is relatively easy, but what about other languages?
Actually there is no need to provide for specific additional letters for each language. I quoted "s" for English as most likely case. In the other languages, it would be different (e.g. "en" for German). It really does not matter. The idea is to provide an option whether to capitalize the partially match.
Offline
Actually there is no need to provide for specific additional letters for each language. I quoted "s" for English as most likely case. In the other languages, it would be different (e.g. "en" for German). It really does not matter. The idea is to provide an option whether to capitalize the partially match.
I presume a lot of abbreviations could be found in the middle of other words, where they shouldn't be treated as abbreviations, so simply unticking the "Whole words only" option woudn't work well.
I think the only capable solution is to either define all plural forms in the abbreviation list, or all only "s" at the end of abbreviations. I would much prefer the former approach.
Offline
Is it possible to highlight the partial matches with a different color text?
Then the user can quickly glance through all and decide.
If required, he can press SPACE to disable renaming for that file only.
(or press F2 and fine-tune the name)
Last edited by narayan (2018-10-12 16:15)
Offline