W dniu 2014-02-19 15:42, R.J. Baars pisze:
In fact, I suggest only lowercasefull stopUppercase should be reported.
I don't think so. There might be numbers at the end of the sentence,
brackets, parenthesis, uppercase proper names etc. We deal with zillions
of cases via our sentence breaking
Daniel Naber wrote thus at 06:18 PM 19-02-14:
This rule will cause new false
alarms for words like X.Org.
If it's only when the first character after the dot is in cap, then it's okay.
Otherwise, we've a lot to deal with: .com, .exe, .org, .uk, .txt,
.net, .my, .tv...
kb
Daniel,
I don't know how to add it myself.
Could someone do it for me?
Thanks!
Kind regards,
Marco A.G.Pinto
---
On 19/02/2014 10:18, Daniel Naber wrote:
Hi,
I have added a rule that finds an error like this.Note the missing space
at the start of this
In fact, I suggest only lowercasefull stopUppercase should be reported.
Ruud
Daniel Naber wrote thus at 06:18 PM 19-02-14:
This rule will cause new false
alarms for words like X.Org.
If it's only when the first character after the dot is in cap, then it's
okay.
Otherwise, we've a lot to
On 2014-02-19 12:07, Kumara Bhikkhu wrote:
If it's only when the first character after the dot is in cap, then
it's okay.
Otherwise, we've a lot to deal with: .com, .exe, .org, .uk, .txt,
.net, .my, .tv...
It depends on what the sentence detector detects as a sentence. At least
for
On 2014-02-19 14:22, Marco A.G.Pinto wrote:
I don't know how to add it myself.
Could someone do it for me?
Done.
Regards
Daniel
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the
That seems reasonable. Anyway, time will tell if the current
implementation is okay.
kb
R.J. Baars wrote thus at 10:42 PM 19-02-14:
In fact, I suggest only lowercasefull stopUppercase should be reported.
Ruud
Daniel Naber wrote thus at 06:18 PM 19-02-14:
This rule will cause new false
