Re: [irsg] how to upload minutes in markdown format?

[Bob Hinden <[e-mail]>]

Hi,

> On Aug 2, 2021, at 10:15 AM, Paul Kyzivat <[e-mail]> wrote:
> 
> On 8/2/21 12:55 PM, Carsten Bormann wrote:
>> On 2021-08-02, at 18:16, Paul Kyzivat <[e-mail]> wrote:
>>> 
>>> I don't get it. The problem isn't with the bits in the file.
>> There is more than one problem.
>>> The problem is that MacOS insists on reporting that a .md file has content type octent-stream. IIUC, if it would simply report it as text/plain then all wood be ok.
>> The content-type is sent by the browser.
>> We probably have different browsers, and nobody takes care of reporting which browser is being used when things fail.
> 
> I've tried Firefox and Chrome.

For what it is worth, I had no uploading issues using MacOS 10.14 using a .md file directly from Codimd, or after I edited the file with emacs.  I was using Chrome (92.0.4515.107) at the time.

Bob

> 
>> I have never been able to get any of my browsers to upload the right media type (text/markdown), so I can’t help with that part.
>> They all do send text/plain (well, Chrome sometimes text/html).
>> To get there, you probably have to open a directory with an .md file in it in Finder, single-click that file, and CMD-I.
>> Choose a markdown presentation application (I use Marked) or text editor (Geany?) of your choice under “open with”, then click “change all”.
> 
> I've tried that. I have .md associated with textedit.
> 
> Even so, when the extension is set to .md Finder Get Info (CMD-I) reports the Kind:Document, whereas it reports .txt as Kind:text.
> (AFAICT MacOS doesn't report literal mime type. Do browsers derive mime type from Kind?)
> 
>> All that said, I stand by my recommendation for keeping sanity:
>> Get “Raw HTML” from CodiMD and upload that.
> 
> That will be my fallback.
> 
>>> Lacking a fix for that problem, can we have datatracker recognize .md.txt as indicating an intent to upload markdown? The tools are already doing a workaround by recognizing .md as markdown even though the actual content type being sent is text/plain.
>> Sounds good to me.
>> You'll still will have the problem with different interpretation of line breaks about which there was some discussion at tools-discuss; the little tool de-gfm was written as a workaround until the Great Unified Datatracker Markdown Solution is implemented.
> 
> I haven't encountered that problem yet.
> 
> 	Thanks,
> 	Paul
>