From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa3.mentor.iphmx.com (esa3.mentor.iphmx.com [68.232.137.180]) by sourceware.org (Postfix) with ESMTPS id 14C223890419; Fri, 4 Jun 2021 07:55:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 14C223890419 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mentor.com IronPort-SDR: drI6ZmvvDOemb2f9Dx5/sMt1zSrzy788idrW5m57DSLxfUNQdKtTaItxLNMqXlZeSXCBmbI21o HsydGMA5xU/CEPDdvsHQ2w8BOT1iDBCv1vyXQlFFyWZCoZdtTs6ZlejwmUDg89mXRccxBboVAX /BcUUAv4A0+bXH/PvuUOy4hfAvDoQt7AOW6VwRUcKKqjNMXaAHlFZWMRspTko++ITMM13LAQJZ V7FJNWlrc5LFjkZ3wS4Dfoii3DCENZbP5VkFRhtltLkKYziNksl52q7MyF850RxAWKgivw8OgH R38= X-IronPort-AV: E=Sophos;i="5.83,247,1616486400"; d="scan'208";a="61993254" Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa3.mentor.iphmx.com with ESMTP; 03 Jun 2021 23:55:14 -0800 IronPort-SDR: BWqcuIb/eY/oiu8oAD51M38UqtulSjkPHp73+J97sj6JVOJJrsWeJNuPjdoUhhapB63YIKL3r6 O2A+S052uY3j/sBz/boi+DYpwNM45FI/u+YofE1eKa7gjQNjCZQz44CxgyMzKdnxwCnldrffic tGnOq9//bS7zyoNqzcRp4Fe7oioMLTZ7xh0zppSlTVLqOYcYGhOBUHEeKb1s0TsxKBm2mnPzax sX/clnIDpEcp2LLhOt3tz2D0bOjS9EmltCFiXdU2+PTQ33IE488sA6S3CqlxKOpwmP+XjvREZ+ rE4= Subject: Re: RFC: Sphinx for GCC documentation To: =?UTF-8?Q?Martin_Li=c5=a1ka?= , CC: GCC Development References: <1446990946.2994.192.camel@surprise> <1a22bc37-3d48-132f-a3d5-219471cd443c@suse.cz> From: Tobias Burnus Message-ID: <7366de44-aece-e53a-42ca-65f59407ec04@codesourcery.com> Date: Fri, 4 Jun 2021 09:55:07 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: <1a22bc37-3d48-132f-a3d5-219471cd443c@suse.cz> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: SVR-IES-MBX-08.mgc.mentorg.com (139.181.222.8) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, KAM_EU, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org 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: Fri, 04 Jun 2021 07:55:26 -0000 Hello, On 13.05.21 13:45, Martin Li=C5=A1ka wrote: > On 4/1/21 3:30 PM, Martin Li=C5=A1ka wrote: >> That said, I'm asking the GCC community for a green light before I >> invest >> more time on it? > So far, I've received just a small feedback about the transition. In > most cases positive. > > [1] https://splichal.eu/scripts/sphinx/ The HTML output looks quite nice. What I observed: * Looking at https://splichal.eu/scripts/sphinx/gfortran/_build/html/intrinsic-proced= ures/access-checks-file-access-modes.html why is the first argument description in bold? It is also not very readable to have a scollbar there =E2=80=93 linebreaks = would be better. =E2=86=92 I think that's because the assumption is that the first line cont= ains a header and the rest the data * https://splichal.eu/scripts/sphinx/gfortran/_build/latex/gfortran.pdf If I look at page 92 (alias 96), 8.2.13 _gfortran_caf_sendget, the first= column is too small to fit the argument names. =E2=80=93 Admittedly, the curren= t gfortran.pdf is not much better =E2=80=93 it is very tight but just fits. I don't kno= w how to fix this. * I note that we write before the argument index, that those are without -/= -- prefix but that's not true. Something to fix after the conversation. * The syntax highlighting for gfortran is odd. Looking at @smallexample: - intrinsic.texi: All Fortran examples (F90/free-form) - gfc-internals.texi: 4x Fortran, 4x C, 3x plain text - gfortran.texi: Shell, Fortran, C, plain text. - invoke.texi: 4x Shell, 2x C, 4x Fortran Does not seem to be that simple, but it would be nice if at least all in intrinsic.texi would be marked as Fortran. Actually, I do not quite understand when the output is formatted a C (wrong= ly or rightly) as Fortran (rarely but correctly) as plain or in some odd forma= tting which randomly highlights some examples. Possibly also an item for after the conversion. Tobias ----------------- Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 M=C3=BCnchen R= egistergericht M=C3=BCnchen HRB 106955, Gesch=C3=A4ftsf=C3=BChrer: Thomas H= eurung, Frank Th=C3=BCrauf