Re: [platform-text-dev] spell checking issue in property files

[Daniel Megert <daniel_megert@xxxxxxxxxx>]

Maybe I was not clear enough: there is
only a JDT specific engine so far. There are plans to move general parts
to the Platform (see bugzilla for the bug) but that has not yet happened.

Dani

From:	Eugen Paraschiv <hanriseldon@xxxxxxxxx>
To:	Eclipse Platform Text component developers list <platform-text-dev@xxxxxxxxxxx>
Date:	22.07.2011 10:32
Subject:	Re: [platform-text-dev] spell checking issue in property files

---

Sure, the consistency of the experience is important as
well, but this is a clear cut use case where the defaults are problematic.
Would it make more sense to have a JDT specific tab in settings for Spelling
(Java-Editor-Spelling or similar) and the general one (General-Editors-Text
Editors-Spelling), so that the option could be configured generically (as
off) and overridden specifically for Java (as on), where, as you say, makes
more sense?
The issue of consistency is important, but so is user experience, and at
the end of the day, it's the attention to these little things that make
or break the experience. It may take some more change than simply switching
of a default (adding this new preference instead of overriding the default),
but this use case (where an error in a log4j.properties file went unnoticed
in Eclipse yet a colleague spotted it in 2 seconds with IDEA) is an option
to improve the experience and focus on these little yet important things.
Thanks again for the feedback. 
Eugen. 

On Fri, Jul 22, 2011 at 11:21 AM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
What you see is the JDT specific spelling
engine and there all uppercase makes a bit more sense. Changing the defaults
after many years would not be nice. 

Dani

From:	Eugen Paraschiv <hanriseldon@xxxxxxxxx>
To:	Eclipse Platform Text component developers list <platform-text-dev@xxxxxxxxxxx>
Date:	22.07.2011 10:16
Subject:	Re: [platform-text-dev] spell checking issue in property files

---

No problem. I wasn't aware that the option exists. Now that I am, I think
this should be the default - the user experience would make more sense
that way. If the user has some special kind of document where the uppercase
words should not be checked, then that is a special case and the option
can be activated, but the standard use case should just work out of the
box, without any special configuration from the user, and the standard
user likely does want spell checking to work with upper case words as well.
Does this make sense? 
Thanks for the quick feedback. 
Eugen. 

On Fri, Jul 22, 2011 at 11:08 AM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote: 
Sorry Eugen, 

I misread it. This works if you unselect to ignore uppercase words ('Spelling'
preference page). 

Dani

From:	Eugen Paraschiv <hanriseldon@xxxxxxxxx>
To:	Eclipse Platform Text component developers list <platform-text-dev@xxxxxxxxxxx>
Date:	22.07.2011 09:59
Subject:	Re: [platform-text-dev] spell checking issue in property files

---

The only problem is that the the word was ERORR (one R in the middle, two
Rs at the end), so my guess is that is should be reported as an problem.
I understand your point about the list, I will take this to the forum,
sorry about the untargeted question. 
Eugen. 

On Fri, Jul 22, 2011 at 10:56 AM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote: 
Error and error are correct words. ERROR is not, like ErRoR isn't too.

Please not that this list is for developers of Platform Text. If you have
a question, then you should use the forums. 

Dani

From:	Eugen Paraschiv <hanriseldon@xxxxxxxxx>
To:	platform-text-dev@xxxxxxxxxxx
Date:	22.07.2011 09:53
Subject:	[platform-text-dev] spell checking issue in property files

---

I'm seeing an issue with spell checking in property files. The following
line doesn't report any kind of errors: 
log4j.rootLogger=ERORR, AppLog
Shouldn't the ERORR word by reported as a mistake? Should I raise a bug
for this?
Thanks. 

Eugen. _______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev



_______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev

_______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev



_______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev

_______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev



_______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev

_______________________________________________
platform-text-dev mailing list
platform-text-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-text-dev