링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Fortran FORTRAN wkjhxdd
But it is OK for me, wkjhxdd is the only spell error on the above line. Isn't that spell checking your browser rather than the forum?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Try a right-click on the misspelled word to see whether there is an option to add it to the Dictionary.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Thanks app4619 and Kevin. I didn't realize the spell checker is whatever the browser supports. I thought something had changed at the forum since I only noticed the red squiggly thing below Fortran while using Google Chrome on a newer PC at home this weekend whereas I mostly access the forum from the work computer which has a standard issue of IE9 from the IT folks without the spell checker turned on.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
It's your browser. Microsoft Office products also are 25 years out of date here. The forum doesn't have a spellcheck feature. I'll see if I can report the Chrome issue to Google.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Steve Lionel (Intel) wrote:
.. I'll see if I can report the Chrome issue to Google.
That'll be cool - it looks like base dictionary in Google Chrome has en entry for FORTRAN and it'll be great if they're open to adding Fortran!
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
While we are on spell checking, I would like to address the issue of auto-correcting.
Please, please, turn off the auto up-casing of i as it is a real pain in the butt to fix all the low-case i's in code examples. I do not mind it low-case singular i is red-tagged. Up-casing I makes it difficult to disambiguate from l (you see any difference between I and l ?).
Jim Dempsey
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Auto-upcasing? I have not seen that except in Word. This forum doesn't do that on its own.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I I I I I I I I
All above type in lower case.
What do you see when you type a series of lower case i's with space surrounds?
Maybe this is an IE 11 thing.
Jim
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Jim,
It must be due to the browser: the up-casing doesn't occur with IE 9 on the work computer I use nor with Google Chrome on a newer personal laptop.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Jim, if you can ever determine how to stop MS products from doing their arrogant and ignorant auto-upcasing-or-downcasing thing, please let me know. I seemingly turned off all those annoying features in Excel, but still it messes up stuff like MPa (mega pascals) every time I enter it into a cell.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
i i i
Click the tool gear icon | IE Options | Programs | Manage add-ons | Spelling Corrections
Then uncheck enable spelling corrections.
*** However, this does not resolve having spelling corrections, without upcasing i
Currious.... unchecking spelling corrections for this entry worked before entering text.
rechecking later did not restore spell checking. I will leave page and come back.
(edit return to page)
I I I I
Restored
Jim Dempsey
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
MPa is noted as spelling error, but not auto-upcased
whereas do I=1,10 i was up-cased.
??? now the Comment form in arbitrarily switching between upcase and not upcase...
To upcase or not to upcase, that is the question...
Jim Dempsey
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Repeat Offender wrote:
... I seemingly turned off all those annoying features in Excel, but still it messes up stuff like MPa (mega pascals) every time I enter it into a cell.
Totally agree about all the annoying features in Excel. But I can put up with anything EXCEPT the scientific stuff, especially notations - that's a no-no for me!! So I'd to do something about MPa and I did the following in Office 2007 (hopefully it works in higher versions of Office too):
- Go to Excel Options -> Proofing and click on "Autocorrect Options"
- On the Autocorrect tab, click on Exceptions
- Click on the "INitial CAps" tab and add MPa to Don't correct: list in addition to a whole bunch of other labels such as mW for milliWatt, MW for megaWatt, etc.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
jimdempseyatthecove wrote:
MPa is noted as spelling error, but not auto-upcased
whereas do I=1,10 i was up-cased.
??? now the Comment form in arbitrarily switching between upcase and not upcase...
To upcase or not to upcase, that is the question...
Jim Dempsey
Jim,
It is not upcasing per se with Microsoft Office products (and I assume that is also true with Internet Explorer 10 and higher), but case conversions. Microsoft Excel (up to version 2007 for sure) will change MPa to Mpa, unless told otherwise (see my comment above this one).
Re: source code snippets you provide, I suggest you use the "code" link provided by the forum: not only will you then avoid the case conversion issue, but the code becomes easier to read with syntax highlighting, etc.
do i = 1, 10 a(i) = b(i) + c(i)*d(i) end do
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
It was up-casing in the code window when typing not when pasting.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
jimdempseyatthecove wrote:
It was up-casing in the code window when typing not when pasting.
Hmm... that is strange indeed - I didn't think the long arm of the (Microsoft) law would extend to the code window!!
In Google Chrome, when I type a wrongly spelled word in the regular Comment window, I get the red squiggly line underneath. But if I'm in the code window under Plain (Text), no spell checker seems active. So I was thinking the code window may be under the control of Intel Forum where other browser rules may not apply - may be not.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
i i i i i !!!
Success: http://www.askvg.com/how-to-disable-built-in-spell-checker-feature-in-internet-explorer-10-ie10/
It turns out that it's the OS ('Doze 8.1) and not Internet Explorer (11) at fault. Excel was to blame for MPa, though: it has a totally lame feature that 'corrects' two initial capitals so it requires extra effort to disable it. Like I want all my megabytes to be changed to millibits or all my possessives (its) to be changed to contractions (it's) so everyone can tell what a fool I am for using MS products. I just noticed that pretty much everything in Excel has also been deprecated so we are supposed to throw out everything we know and start out from scratch again.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
"Excel has also been deprecated so we are supposed to throw out everything we know and start out from scratch again."
This is why i am still using Excel 2003, I doubt if anything of much use has been added in the last decade or so.....
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
app4619 wrote:
"Excel has also been deprecated so we are supposed to throw out everything we know and start out from scratch again."
This is why i am still using Excel 2003, I doubt if anything of much use has been added in the last decade or so.....
@app4619,
It is not just that nothing of use has been added to Excel since the 2003 version, but a few things that worked well in Lotus 1-2-3 from the very beginning and which were so-so in Excel effectively stopped functioning: one example is the ability to add error bars on X-Y types of charts.
@Repeat Offender,
I agree with your sentiment completely when it comes to many of the annoying aspects of Microsoft products, especially Office versions. But I'm not sure I understand what you mean by "everything in Excel has also been deprecated "! Care to elaborate further? Thanks,
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I was looking for the syntax of statistical functions like NORMSDIST, STDEV, TINV and they were deprecated. On further inspection most of the others were not. I can't believe what MS does to their products at each iteration. Ranting and raving are unseemly on technical forums so I will stop at that.
