Spell check....?

Boring I know, but oh so useful…it cant surely be that hard to include?


Where do you expect to see spell check work?

Uhhh…how about when the user placed text in the file via the text command?

Actually I cant think of anywhere you wouldn’t want spell check.
Typically, you’d use it, not necessarily because you cant spell, but, like what is happening right now while I’m creating this post , to pick up mistakes and typos…
Especially if you create construction and or presentation documents, no matter how well they are presented, a spelling mistake or typo just spoils the the whole thing.
Likewise, even in the notes command, a spell check, with a user dictionary, would over time build up a set of specialised set of discipline specific terms and words, correctly spelled, which you could copy and paste into other documents with confidence.
I do this often ie I write myself notes to keep track of design decisions, things I need to watch, info I have collected that is relevant to the task and so on, and then I use some of that text in emails or notes on construction drawings etc.

Why wouldn’t rhino have spell check? What not to like about it? Its a standard tool that I’d expect in any program that can create text…


Having never looked into it, I don’t know what it takes to implement spell checking. And given that our UI is written in at least four different programming languages, I’m concerned that getting spell check “everywhere” could be very time consuming.

On the other hand, if there were 3 or 4 or 10 places that would make a real impact on your work, the project might become more manageable.

That’s why I’m asking you to think about where spell check would really benefit your work.


Spellcheck in
Textobjects/dimensions first they are used to annotate layouts etc. and as such are the main area where texts are visible and meant to he read by others. And these type of texts are meant to convey written descriptive information often in the form of sentences and paragraphs.

Second dots

Third…all other text fields that are meant for descriptive sentences.

Probably when a spellchecker is implemented it would be fairly easy to have a tool to collect most strings present in the document and pass them through the checker. As means to check non realtime.

Imo Never should a spellchecker work on things like object names layernames etc.


From my naive point of view it seems that in the best spirit of OOP a fundamental text editor which incorporates the OS’s spell checker could be developed and then used anywhere and everywhere Rhino takes in text. What’s the flaw in this thinking?

How many languages does it need to support and which ones?

We could support English, French, German, and Spanish “relatively” easily. Other languages would require more work.

Maybe in Rhino v2050 you can support this

sorry, couldn`t resist. :wink:

HIq vItlhutlh vIneH

Hi Steve.
Are there no open dictionary formats we as users could import? Much like with mozilla products and libreoffice where I can download a dictionary file and “install” it.


I just pointed out what could be relatively easy to implement. Of course there are plenty of other options that we could spend a large amount of time on :smiling_imp:

Ok, got it, sorry.
My thinking was that in any case there must be a dictionary list somewhere.

So simple thinking made me guess in basis it is just replacing one list with another.