From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) by sourceware.org (Postfix) with ESMTPS id 390BA385AC2D for ; Tue, 16 Nov 2021 09:31:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 390BA385AC2D Received: by mail-wr1-x432.google.com with SMTP id d5so36256963wrc.1 for ; Tue, 16 Nov 2021 01:31:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W7ECc8aj0gpWi67prV9GVWvCChOn2DeeiQAdhtP64WU=; b=UOPcCAJ9vzDg3Sf6GazZ0f7LR8JRquD8R9WfNEJf/uxPNSgGkcPukzCr7xxlZibXP/ zMMIHVhBA0ESnPEBeGiBSJEDeX92uaALJhf/XDjqk39uN2p00pcnOg0/yeCAp/WiMUdt RMulmUB84USL9OTlLW4WZn1Ga/+lHCF1UbadJdFwwbalsaP/khQ7l2/toL2eWkClPVTv cFtigTbSZidQiOy+cJtDgaMCxcxV0ZGZNkw3B5m9+mCJ3yC1NlsyKtN917E8qCneKpvk c0jZ/2Ve2NJ4tsoGQGXJOlnqAAsm0E5tCPVwj5Q6dbEOMOcJZiyg8cyaFiC+qoTbWA0c JoAg== X-Gm-Message-State: AOAM532/OKXJUoOTFWCz0w2pkZXQIU8FCCYQ4gbHDzxTWUMSkoysdMbS awVZ/Dxle7aASR29QxKJNlA4UfQyD/4G8D14pnQ= X-Google-Smtp-Source: ABdhPJxzYGeZgvPwiUN949+Y/JT5eK/5L25ivPKyTUcQ2Y4cmq+2eXUWY1AOOXfzT0Lemqv4rSvnVypiAx4Z0dCXS70= X-Received: by 2002:adf:f04d:: with SMTP id t13mr7409334wro.324.1637055071256; Tue, 16 Nov 2021 01:31:11 -0800 (PST) MIME-Version: 1.0 References: <56a1a945-608e-0e5e-7610-c35481abb980@gmail.com> In-Reply-To: <56a1a945-608e-0e5e-7610-c35481abb980@gmail.com> From: Jonathan Wakely Date: Tue, 16 Nov 2021 09:30:59 +0000 Message-ID: Subject: Re: ISO C3X proposal: nonnull qualifier To: "Alejandro Colomar (man-pages)" Cc: Joseph Myers , "gcc@gcc.gnu.org" , cfe-dev@lists.llvm.org X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2021 09:31:14 -0000 On Mon, 15 Nov 2021, 21:15 Alejandro Colomar (man-pages) wrote: > My intention is that the final PDF to be sent to the committee > will have those diffs. > But I have no clue of how to do that kind of things, > so for an initial draft to discuss on, > before even presenting it to the committee, > I think my "native" language for writing technical documents > will be easier. > > Also, > I'm curious, > do you do those diffs usually by hand? > Yes. Just highlight text in red and green, with strike through or underlining. If you write the paper in LaTeX you can use macros like: \definecolor{addclr}{rgb}{0,.6,.6} \definecolor{remclr}{rgb}{1,0,0} \renewcommand{\added}[1]{\textcolor{addclr}{\uline{#1}}} \newcommand{\removed}[1]{\textcolor{remclr}{\sout{#1}}} \renewcommand{\changed}[2]{\removed{#1}\added{#2}} I mean, you can't diff(1) a PDF, can you? :) > Aside: see diffpdf, which is packaged by some distros.