grammar checker not showing up
// Please enter a detailed description of the issue
// Description of the issue:
the grammar checker does not show up
I deleted the preference file and rebooted with no success.
When I start up Marked 2 I am offered to buy the extension. "Restore purchase” then works, but the menu does not show up.
Before deleting the preference file and rebooting, the grammar proofing menu was grayed out, but visible. Now it is simply not there.
Thank you for your help and keep up the good work (I do like Marked 2!)
// Please enter a list of steps required to reproduce the issue
// Steps to reproduce:
1.
2.
3.
// If applicable please attach a sample document that causes the issue for you.
// Configuration (do not edit)
Marked 2 922 (Direct)
OS X Version: 10.11.6
---
additionalMathJaxConfig:
allowPageBreakInCode: 1
bookTxtIsLeanpub: 0
codeIsPoetry: 0
collapsibleHeadlines: 0
convertGithubCheckboxes: 1
convertYAMLToMMD: 0
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: swiss
defaultProcessor: MultiMarkdown
enableMiniMap: 0
excludeBlockQuotesFromCounts: 0
excludeFootnotesFromCounts: 0
excludeVerbatimFromCounts: 0
excludeCaptionsFromCounts: 0
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: 1
h1IsPageBreak: 0
h2IsPageBreak: 0
hrIsPageBreak: 0
includeMathJax: 0
limitTextWidth: 0
minimalJavaScript: 0
outlineModeExtensions:
permissionGranted: 0
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFooterFirstPage: 0
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: 1
removeMetadataForPreview: 0
removeYAMLHeaders: 0
scrollToEdit: 1
shouldDetectCritic: 1
shouldHighlightMarkupErrors: 0
shouldLoadCritic: 0
syntaxHighlight: 0
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Brett on Aug 27, 2016 @ 03:20 PM
If you've previously run the MAS version, see if the folder ~/Library/Containers/com.brettterpstra.marked2 exists.
If it does, go ahead and trash that whole folder, restart, and see if
the issue resolves.
It also could be a failure to properly store the preference/license files. This can be a result of disk errors, so opening Disk Tool and running Repair on the main HD can often fix the issue.
Let me know if that helps.
-Brett
2 Posted by francesco.cavig... on Aug 28, 2016 @ 05:32 AM
I ran Disk Utility / First Aid, and thereafter started Marked 2.
It asked twice to add the spelling and grammar check, the program
recognized the “restore purchase” command, but did not show the menu.
Then I started the program again and, automagically, grammar errors were
marked in the document although the menu was greyed out.
If it helps understanding the issue, now Marked 2 also starts when I open a
file in Multimarkdown composer, which did not happen before.
There was no ~/Library/Containers/com.brettterpstra.marked2 folder.
Now everything is working and the grammar checker has a cool interface.
By the way, which languages are included (was it “multilingual”?) I did not
expect it would work with Danish, but it does not seem to work with German
and Italian. Can’t complain for 2 dollars ;-) and I needed it mainly for
English.
So everything ends well, thanks Brett for a wonderful piece of software!
Have a nice Sunday
Francesco
—-
Francesco Caviglia
Hejdesvej 10A
8270 Højbjerg
Support Staff 3 Posted by Brett on Aug 28, 2016 @ 01:50 PM
The multilingual features use a detection feature to choose a language with a supported system dictionary. Did it appear to not realize it was Danish at all? If you want to attach a sample document I could see what language Marked thinks it is.
-Brett
4 Posted by francesco.cavig... on Aug 28, 2016 @ 02:25 PM
Hi Brett,
Here are three ultra-short files, respectively in German, Italian and
Danish.
The proofing tool marks spelling errors as of they were in English
(curiously, the Danish file receives one grammar suggestion that could make
sense, but it is hard to tell).
When writing in Multimarkdown Composer I have a spell checker, so this is
not a big problem.
But if your grammar checker does undestand other languages, this would of
course be great, even more after Word has messed up with grammar checking
in 2016 version.
Best
Francesco
—-
Francesco Caviglia
Hejdesvej 10A
8270 Højbjerg