why would you expect "Test the Title: The NYC Song"? word separators are just word separators. they are only custom addition to spaces. and it's senseless in this case because there is an already space after the colon. what i can do is add new parameter "override all exception after chars". or change the meaning of the existing last parameter (which seems useless anyway) to this.
What I mostly meant by 'I would expect', is that it would be desirable to have it work this way from a linguistic point of view.
(and I assumed that's what this parameter was intended for. But I now realise that I misunderstood that)
From a linguistic point of view:
You can have titles such as:
the waltz: the first part
or
an adventure - a beginning
For parameter 2 (lower_case_words), you would set the words a, an, and the to be lower-case.
That would give you:
The Waltz: the First Part
and
An Adventure - a Beginning
(correct?)
But for English titles it should be:
The Waltz: The First Part
and
An Adventure - A Beginning
(I think?)
So I guess I was (wrongly) assuming that parameter 2 (word_separators) was checking for separator character+space.
But I now understand it is not, and it is meant for words like Non-Stop.
My misunderstanding.
----
I am not sure about this new 'overrule' parameter. Would this make it possible to do what I described above?
Would it perhaps be better to have a parameter named something like 'sentence_connector' instead?
(native English speakers, please propose a better term for this?)
One that will work identical to word_separator, but internally adds a space to the separator?
This parameter is only needed because it must be able to overrule any lower_case_words.
Since as you said, it is unnecessary for all others.
edit:
If you agree with this, perhaps change 'word_separator' to 'word_connector'?
Then there would be:
word_connector
sentence_connector
Seems better, more descriptive to me?
