tag:support.multimarkdown.com,2013-02-12:/discussions/problems-v4/2761-unable-to-open-document-created-with-mmcMultiMarkdown Software, LLC: Discussion 2019-12-23T19:01:31Ztag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-25T21:58:53Z2019-12-23T19:01:30ZUnable to open document created with MMC<div><p>MacOS: Mojave 10.14.2, but also seen with High Sierra<br>
Product: MMC 4.5.1 (87)<br>
Version: 4.5.1</p>
<p>Steps to reproduce:</p>
<ol>
<li>Lauch MMC<br></li>
<li>Select [New Document}<br></li>
<li>Enter text "This is the text."<br></li>
<li>Select File > Save<br></li>
<li>In dialog box enter "Text", accept standard .mdd extension<br></li>
<li>Select File > Quit<br></li>
<li>Relaunch MMC<br></li>
<li>From the DB, note that the "Text.mdd" document is not associated to MDD - the icon is generic (file attached)<br></li>
<li>Select "Text.mdd" and click "Open"<br></li>
<li>A DB is presented to the user stating "The document “Text.mdd” could not be opened."</li>
</ol>
<p>Note that the document. can be opened with a regular text editor or Textedit without error. The only option to create new document is to open a version 3 document in 4.5.1 and rename it... Is it possible to downgrade to version 3?</p>
<p>Thanks,</p>
<p>Marcelo Marchetti</p></div>marcelo.marchettitag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-25T22:15:05Z2019-12-23T19:01:30ZUnable to open document created with MMC<div><p>Note that creating the document with BBEdit and saving with MMD extension, all works fine, including the correct icon association.</p></div>marcelo.marchettitag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T00:18:12Z2018-12-26T00:18:12ZUnable to open document created with MMC<div><p>Marcelo,</p>
<p>Sorry you're having trouble. That's unusual.</p>
<ol>
<li>
<p>You say that you use the extension "mdd". I assume you meant to type "mmd"? "mdd" is not an extension used by Composer.</p>
</li>
<li>
<p>Assuming you meant "mmd", use the Terminal to run <code>mdls yourfilename.mmd</code> with one of your files. Send me a copy of the results. You should get something like this:</p>
</li>
</ol>
<p>kMDItemContentType = "net.daringfireball.markdown"<br>
kMDItemContentTypeTree = (<br>
"net.daringfireball.markdown", "public.item", "public.text", "public.data", "public.content", "net.daringfireball.markdown", "public.plain-text" )</p>
<p>If you have another program that is modifying the UTI system incorrectly, it could cause the file to not be openable by Composer. The <code>mdls</code> command can help offer information about what macOS <em>thinks</em> the file is.</p>
<p>Let me know what you find, and we can go from there.</p>
<p>Fletcher</p>
<p>--<br>
Fletcher T. Penney<br>
Manager, Founder<br>
MultiMarkdown Software, LLC<br>
<a href="mailto:admin@multimarkdown.com">admin@multimarkdown.com</a></p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T00:41:03Z2019-12-23T19:01:30ZUnable to open document created with MMC<div><p>Apologies, I meant .mmd… To make sure that I was not doing this myself, I reopened MMC and created a new doc. I noticed that when saving a file the extension mdd is added automatically. See the picture I am enclosing. This is what happens by default.</p>
<p>However, if I re-select [MultiMarkdown Text Document] in the File Format drop down list, the extension is now set to .md instead of .mmd as per the picture below.</p>
<p>I followed up on your request in point 2 below with Terminal and the output is pasted below. I think that the issue is that MMC is picking *.mdd instead of *.mmd by default or *.md.</p>
<p>Regards,</p>
<p>Marcelo</p>
<p>kMDItemContentCreationDate = 2018-12-26 00:29:51 +0000<br>
kMDItemContentCreationDate_Ranking = 2018-12-26 00:00:00 +0000<br>
kMDItemContentModificationDate = 2018-12-26 00:29:51 +0000<br>
kMDItemContentType = "net.multimarkdown.text"<br>
kMDItemContentTypeTree = (<br>
"net.multimarkdown.text", "public.text", "public.data", "public.item", "public.content", "public.plain-text" ) kMDItemDateAdded = 2018-12-26 00:29:51 +0000<br>
kMDItemDateAdded_Ranking = 2018-12-26 00:00:00 +0000<br>
kMDItemDisplayName = "Testing with Fletcher....mmd"<br>
kMDItemFSContentChangeDate = 2018-12-26 00:29:51 +0000<br>
kMDItemFSCreationDate = 2018-12-26 00:29:51 +0000<br>
kMDItemFSCreatorCode = ""<br>
kMDItemFSFinderFlags = 0<br>
kMDItemFSHasCustomIcon = (null)<br>
kMDItemFSInvisible = 0<br>
kMDItemFSIsExtensionHidden = 0<br>
kMDItemFSIsStationery = (null)<br>
kMDItemFSLabel = 0<br>
kMDItemFSName = "Testing with Fletcher....mmd"<br>
kMDItemFSNodeCount = (null)<br>
kMDItemFSOwnerGroupID = 20<br>
kMDItemFSOwnerUserID = 504<br>
kMDItemFSSize = 25<br>
kMDItemFSTypeCode = ""<br>
kMDItemInterestingDate_Ranking = 2018-12-26 00:00:00 +0000<br>
kMDItemKind = "MultiMarkdown Text Document"<br>
kMDItemLastUsedDate = 2018-12-26 00:29:51 +0000<br>
kMDItemLastUsedDate_Ranking = 2018-12-26 00:00:00 +0000<br>
kMDItemLogicalSize = 25<br>
kMDItemPhysicalSize = 4096<br>
kMDItemUseCount = 3<br>
kMDItemUsedDates = (<br>
"2018-12-25 05:00:00 +0000" ) kMDItemUserCreatedDate = (<br>
"2018-12-26 00:29:51 +0000" ) kMDItemUserCreatedUserHandle = (<br>
504 )</p></div>marcelo.marchettitag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T00:52:50Z2018-12-26T00:52:50ZUnable to open document created with MMC<div><p>Did you change the Files preferences? Composer won't pick <code>mdd</code> unless you tell it to. It's not an extension that Composer "knows."</p>
<p>So if you change the extension to "md" (or "mmd"), does it open properly? The mdls information that you included suggests that the file you included information from is working correctly. The "net.multimarkdown.text" Content Type is the right one, and you can see below that the "public.plain-text" which means that macOS knows this is a text file (because of the UTI that Composer provided.) The filename of "Testing with Fletcher....mmd" suggests that "mmd" (not "mdd") should work.</p>
<p>Fletcher</p>
<p>PS> FYI the "known" extensions that Composer uses are md, txt, mmd, mdown, markdn, markdown, text, ft</p>
<p>--<br>
Fletcher T. Penney<br>
Manager, Founder<br>
MultiMarkdown Software, LLC<br>
<a href="mailto:admin@multimarkdown.com">admin@multimarkdown.com</a></p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T00:57:22Z2019-12-23T19:01:30ZUnable to open document created with MMC<div><p>I did not change the file preferences — at least not knowingly but it is probably that I must have done it. I reset the preferences to “mmd” and order is restored… Thank you for bearing with me. I think that the mystery is resolved.</p>
<p>Thanks,</p>
<p>Marcelo</p></div>marcelo.marchettitag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T01:31:29Z2019-12-23T19:01:31ZUnable to open document created with MMC<div><p>One last question: what is the extension for MMC? *.mmd or *.md? My MMC seems to be using both.</p></div>marcelo.marchettitag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T01:57:06Z2018-12-26T01:57:06ZUnable to open document created with MMC<div><p>I had double checked the code, and I don't see any way that Composer could have entered mdd into the file preferences without the user doing it. Never say never, and all that. But I don't see how it's possible.</p>
<p>Glad that did the trick! Let me know if you have any further trouble!</p>
<p>Fletcher</p>
<p>--<br>
Fletcher T. Penney<br>
Manager, Founder<br>
MultiMarkdown Software, LLC<br>
<a href="mailto:admin@multimarkdown.com">admin@multimarkdown.com</a></p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/467117322018-12-26T01:58:14Z2018-12-26T01:58:14ZUnable to open document created with MMC<div><p>Technically it doesn't matter. Some prefer one, some prefer the other. It will work with any extension that maps to a text file via a valid UTI.</p>
<p>The built in ones are md, txt, mmd, mdown, markdn, markdown, text, ft</p>
<p>F-</p>
<p>--<br>
Fletcher T. Penney<br>
Manager, Founder<br>
MultiMarkdown Software, LLC<br>
<a href="mailto:admin@multimarkdown.com">admin@multimarkdown.com</a></p></div>Fletcher