Recognize periods as word breaks

[TheQwerty]

I'd have to agree with Mesh. I think more than the period is needed.

Another option to maintain your dot-only use could be to implement triple-clicking which would select just the base or extension.

[admin]

; All characters listed between double quotes will be considered word boundaries for all renaming purposes
WordBoundaryCharacters= " _()."

That's a possibility. But for now I wouldn't mind finding a choice that suits most users. So, does everybody agree on " _()." as word boundaries?

[Mesh]

That's a possibility. But for now I wouldn't mind finding a choice that suits most users. So, does everybody agree on " _()." as word boundaries?

If we're looking for a catch-all solution for the moment, it probably makes more sense to reverse the parameters and simply say any character that's not "a-z" (case insensitive) and "0-9". That would be more accurate and catch the characters we might not initially think of.

I can't think of any character outside of the "a-z" and "0-9" range that *wouldn't* be a word seperator of some sort.

[admin]

That's a possibility. But for now I wouldn't mind finding a choice that suits most users. So, does everybody agree on " _()." as word boundaries?

If we're looking for a catch-all solution for the moment, it probably makes more sense to reverse the parameters and simply say any character that's not "a-z" (case insensitive) and "0-9". That would be more accurate and catch the characters we might not initially think of.

I can't think of any character outside of the "a-z" and "0-9" range that *wouldn't* be a word seperator of some sort.

I can do that. Agreement?

[avsfan]

Sounds good. I typically use spaces and dashes "-" as word separators, so that would work great for me.

[ivan]

I can do that. Agreement?

Yes, I think any character/symbol outside of those ranges should be considered as a word break (including spaces of course).

[admin]

I can't think of any character outside of the "a-z" and "0-9" range that *wouldn't* be a word seperator of some sort.

Well, I can: á, ü, ñ ...
Looks like it's easier to collect the potential word breakers in file names:

Code: Select all

(){}[].,;- !§$%&=+#_

[/size]

That should cover it more or less...

[ivan]

That should cover it more or less...

Here are a few more...

Code: Select all

~^*/\|

[/size]

[Mesh]

I can't think of any character outside of the "a-z" and "0-9" range that *wouldn't* be a word seperator of some sort.

Well, I can: á, ü, ñ ...
Looks like it's easier to collect the potential word breakers in file names:

Code: Select all

(){}[].,;- !§$%&=+#_

[/size]

That should cover it more or less...

Damn. I forgot about those. Maybe the INI route is the easiest way after all. Well, if you're going with a static and uneditable list to start with, I'd probably add "<>" and M-Dashes.

[j_c_hallgren]

But are all the chars listed above valid within file names? Just wondering...I'm not 100% sure if all those are.
And if it's done via INI setting, then a user could decide if they wanted a char to be treated as separator or not...in my case, I use the "$" and "#" as 'normal' chars, as in "M$ - Update xxxx" as abbrev for Microsoft.

[admin]

But are all the chars listed above valid within file names? Just wondering...I'm not 100% sure if all those are.
And if it's done via INI setting, then a user could decide if they wanted a char to be treated as separator or not...in my case, I use the "$" and "#" as 'normal' chars, as in "M$ - Update xxxx" as abbrev for Microsoft.

Me too. $ and # should probably be left out for most people. But or now I put them all in:

Code: Select all

.:,; _-~(){}[]<>|/\^°*?!§$%&=+#"'

[/size]Then we can see which ones to drop.

I will make it configurable later.

[j_c_hallgren]

So what happend when combinations of these occur in a set, as in "M$ - fix #123765"? Does it get considered as one break? So that, for now, the "$ - " isn't treated as four breaks...

[admin]

So what happend when combinations of these occur in a set, as in "M$ - fix #123765"? Does it get considered as one break? So that, for now, the "$ - " isn't treated as four breaks...

As four breaks currently. Hmmm, I should change this maybe...

[ivan]

Me too. $ and # should probably be left out for most people. But or now I put them all in:

Code: Select all

.:,; _-~(){}[]<>|/\^°*?!§$%&=+#"'

[/size]Then we can see which ones to drop.
I will make it configurable later.

Thank you for adding those characters, but please enable them to be recognised as word breakers throughout the program. It really needs to work for Rename Special --> Capitalization.

[Mesh]

So what happend when combinations of these occur in a set, as in "M$ - fix #123765"? Does it get considered as one break? So that, for now, the "$ - " isn't treated as four breaks...

As four breaks currently. Hmmm, I should change this maybe...

Well, what I was originally envisioning was something like this:


If we're starting from the left side and hit Ctrl-<Right>, the cursor would stop before the next non-break character that occurs after a break character. This would have prevented the behavior j.c. brought up.