Re: [EXTERNAL] Question about Codimd for w.g. minutes

Bob Hinden <bob.hinden@gmail.com> Thu, 29 July 2021 18:30 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0523A145F for <wgchairs@ietfa.amsl.com>; Thu, 29 Jul 2021 11:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfKQGorFoLhx for <wgchairs@ietfa.amsl.com>; Thu, 29 Jul 2021 11:30:42 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 826733A13D5 for <wgchairs@ietf.org>; Thu, 29 Jul 2021 11:30:40 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id d131-20020a1c1d890000b02902516717f562so4672087wmd.3 for <wgchairs@ietf.org>; Thu, 29 Jul 2021 11:30:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=duT8MXTCAvafaJc4DV9tKardNSeJjRmjMqjm2muozeU=; b=hHjWOXOnrJjFM5qm8wY5laNl/CxpJSD18q0J5NiOj/kHM9/R5a/uOKZQAOYw2ZHp6K odw7FU9SuyOi1jbSPZSUt39g74vRt0NWk/3ODBSTiu1gZd4gANd2HGBLYjMOvZXR0LrW ia+DSUKX616ocywJyz8xLnlo3alC1oURHPQAnUmcOptbonav8DC/6d/nerDfTFIhPPVf 519kEFNRcuisZrs3al4Mvr81eltviY4OuLOScfIZvsoFY1+lmVCZC3NRi0laxSE2cu3e C60FsCeJkTRlNsH/+o6fQynR4ijb6pMl+/L7xcVj6boW9HCT5xa5IrGwR5YthKQ2Tjhe PF8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=duT8MXTCAvafaJc4DV9tKardNSeJjRmjMqjm2muozeU=; b=i8ddHXJJH9ejyZCluWMyZy44IyHP2HG5wa72b3eP3RGi2C9eKRVBYp90ttaXIxE1XR Ot5cvWianzv2Jy+SG2wy6FtaQpwzNeKnNSoPglpJHp9kPaPnrKgus2mFfVDAXXbhskhH cwks0KVX239USSHQdc2hSF7RDY4q8ECSH0syyFdyNDof9LbjaYKHWbwQSgdbrKsEG0Zr SK4hb4UmB4TxpZZxzjorpB9cxXnLKd6icEjeaiu76a0W160N6g3zgwXkA+Xw8kxEmd0s eENUcgn3W461k4GTsKuDiaunVk6lp5EDQygcmFnXI8bv5vXX1goWMivyKv6ZkP47zzqs +9YA==
X-Gm-Message-State: AOAM530QZJM6w60s/p/s4uJQQ/Fej03TfKY48dQqmPvVjjrKfeBKBE64 0ERnsVgpPu4Erg0Rszzn00A=
X-Google-Smtp-Source: ABdhPJy8vlD67sZpVVpktoIHEkQGFTtEZHlGrHbV7Ut1x5w7G9Ka4fboYTYkAJcX9i/Di3aKad5KUQ==
X-Received: by 2002:a7b:c089:: with SMTP id r9mr16153879wmh.149.1627583438348; Thu, 29 Jul 2021 11:30:38 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:659:904e:d830:2ae7:6ebd? ([2601:647:5a00:659:904e:d830:2ae7:6ebd]) by smtp.gmail.com with ESMTPSA id z5sm9089792wmp.26.2021.07.29.11.30.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jul 2021 11:30:37 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <CDFB76F4-58DC-4B1E-827B-E17DBA7CBC2B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_212A52CF-225D-4A94-8FE1-6EBFA39BCE60"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Subject: Re: [EXTERNAL] Question about Codimd for w.g. minutes
Date: Thu, 29 Jul 2021 11:30:33 -0700
In-Reply-To: <CAJU8_nXevwOYaGvZdWWfEcKqNnfnHNzFK-PMv-PYTW-R8v12nw@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>, Working Group Chairs <wgchairs@ietf.org>
To: Kyle Rose <krose@krose.org>
References: <2A3CF02D-ACAC-440E-87FC-DD247C9DF0CA@gmail.com> <2B94E2D4-20E8-4E10-8A10-321F6E4C22FA@nbcuni.com> <8178CA4F-3AC1-4C01-91DF-B3864D23183F@gmail.com> <0D4DA368-BE52-4D51-986B-389CDDE7D680@nbcuni.com> <CAJU8_nWzmWiELMwme6P=r5DygZotEHAAP3A+HA3+SQLbd5DSMA@mail.gmail.com> <36687D77-F596-43A1-BD85-AC60B381BB3A@gmail.com> <62B18365-90F0-4773-8DEF-ABE9DE1A85F4@nbcuni.com> <CAJU8_nXevwOYaGvZdWWfEcKqNnfnHNzFK-PMv-PYTW-R8v12nw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/jKPUAseqrUtwDTjBtjqA5pD2gOw>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 18:30:47 -0000

Kyle,

> On Jul 29, 2021, at 11:10 AM, Kyle Rose <krose@krose.org> wrote:
> 
> Interesting. I think CodiMD is rendering incorrectly, because markdown intentionally ignores single newlines: if CodiMD wants a line break, it should insert *two* newlines (a paragraph break) or two spaces at the end of a line (line break) to get that effect. I would avoid the issue entirely by using bullets to delineate elements.

According to this:  https://www.markdownguide.org/basic-syntax/

Two blank lines creates a paragraph.   Two spaces creates a line break.   As it says, hard to see in a editor.

Also, there doesn’t seem to be a to create bullet lists without a symbol before the text.   I will turn everthing into paragraphs.

Bob

p.s. Now I know more about markdown than I wanted to know.


> 
> Kyle
> 
> On Thu, Jul 29, 2021 at 1:47 PM Deen, Glenn (NBCUniversal) <Glenn.Deen@nbcuni.com> wrote:
> Bob,
> 
> I see the wrapping problem at times as well when reading the minutes from datatracker.
> 
> Here'e the raw ADD@110 minutes from CODIMD.  https://codimd.ietf.org/notes-ietf-110-add  which formats fine.
> 
> Here's the datatracker version: https://datatracker.ietf.org/meeting/110/materials/minutes-110-add-202103091530-00.md which has wrap problems.
> 
> 
> The Datatracker version does preserve markdown coded links correctly, but the text lines are being wrapped together.
> 
> Could this be a typing problem coming out of datatracker?     Datatracker does recognize that it's a markdown file as I'm accessing it via the "markdown" version link in tracker and it has a .md extension.
> 
> -glenn
> 
> 
> On 7/29/21, 10:38 AM, "Bob Hinden" <bob.hinden@gmail.com> wrote:
> 
>     Kyle, Glenn,
> 
>     I gave downloading the markdown and uploading that to the Datatracker.  That works, but the discussion are getting wrapped when I open the link in Safari and Crome.  For example:
> 
>     Toerless Eckert: Very nice. Any experience from ECN experimental? Gorry Fairhurst: ECN is standards. Second generation of ECN. Unable to help. Gorry Fairhurst: Original is currently proposed standards. Toerless Eckert: I think we could be consistent on that. You made it experimental because you don't want to explore some things? Gorry Fairhurst: Original ecn appears to be more unexperimental. We can do whatever 6man wants us to. Geoff Huston: Not everybody can do it overnight. It effects every router along the path. The real question is that how partial deployment will impact. Bob Hinden: We expect there will be mixed implementations for a while. Gorry do you want to say more? Gorry Fairhurst: Not replace the PMTU discovery. If you have some routers that can discover, then
> 
>     In Codimd it displays fine with appropriate line breaks.
> 
>     I have tried several ways to capture the markdown (download, copy and paste), all have the same results.
> 
>     Suggestions?   I could do an editing pass to fix this, but would prefer to avoid that.
> 
>     Bob
> 
> 
>     > On Jul 29, 2021, at 10:09 AM, Kyle Rose <krose@krose.org> wrote:
>     >
>     > I download the markdown and then upload it to the data tracker. The 111 MOPS minutes, for instance:
>     >
>     > https://datatracker.ietf.org/doc/minutes-111-mops/
>     >
>     > It requires your browser/OS to understand and present the markdown mime type when uploading, which has led to some frustration (and confused attempts at helping) in the past.
>     >
>     > Kyle
>     >
>     > On Thu, Jul 29, 2021 at 12:59 PM Deen, Glenn (NBCUniversal) <Glenn.Deen@nbcuni.com> wrote:
>     > Hi Bob,
>     >
>     > More cut and paste into a new local notes.md file out of the codimd notepad which are marked up with markdown, but yes.
>     >
>     > -glenn
>     >
>     > On 7/29/21, 9:42 AM, "Bob Hinden" <bob.hinden@gmail.com> wrote:
>     >
>     >     Glenn,
>     >
>     >     To clarify, so you download Markdown and then upload that to the Datatracker?
>     >
>     >     Bob
>     >
>     >
>     >
>     >     > On Jul 29, 2021, at 9:15 AM, Deen, Glenn (NBCUniversal) <Glenn.Deen@nbcuni.com> wrote:
>     >     >
>     >     > Bob,
>     >     >
>     >     > I've done a light cleanup - both for English and markdown - and then upload them.   Since I also create the WG agenda as markdown when making it, this goes as the seed for the cotimd notes ahead of the meeting the result is the notes are then all in markdown along with working links etc.   that live in the notes document and work for future readers.
>     >     >
>     >     >
>     >     > -glenn
>     >     >
>     >     > On 7/29/21, 8:48 AM, "WGChairs on behalf of Bob Hinden" <wgchairs-bounces@ietf.org on behalf of bob.hinden@gmail.com> wrote:
>     >     >
>     >     >    What’s the best practice to convert and/or publish minutes taken with codimd?   I have managed to so something in past meetings, but usually try a few things.
>     >     >
>     >     >    Is there a best practice?  What do you do?
>     >     >
>     >     >    Bob
>     >     >
>     >     >
>     >
>     >
> 
>