Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNbwJ-0000Ez-4R for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Sep 2020 13:14:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kNbwG-0001dN-Fz for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Sep 2020 13:14:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNbwG-0001dG-7w for pgsql-bugs@lists.postgresql.org; Wed, 30 Sep 2020 13:14:32 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNbwD-0005tY-O9 for pgsql-bugs@lists.postgresql.org; Wed, 30 Sep 2020 13:14:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=mH3SCeJzpeut0MMtIjb6M213kt1Tdwr8IV7AZzBTJi8=; b=j9T1Jh+55OCz+GqqKaf4nxw4v2 lhQqON04OXmeP/yPPANOajt3nHXxy6bnqpLwgMtj+hFcNFaNyb1ZSBcZWNuAKEE1t0lfGVmsM/hx4 ZQ/DOBoE76riL79vaX2oqER9ArfEGdp/RI+1/cWbR9f1KWQUk0KC/CQch8jx3a4p6Mmc=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1kNbwB-0006ud-70; Wed, 30 Sep 2020 15:14:27 +0200 Date: Wed, 30 Sep 2020 15:14:27 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Daniel Gustafsson Cc: valentin.baert@everysens.com, PostgreSQL mailing lists Subject: Re: BUG #16640: Documentation table formatting issue Message-ID: <20200930131427.GA22291@depesz.com> Reply-To: depesz@depesz.com References: <16640-2ea18d259b1d57be@postgresql.org> <0CB3642C-084C-4751-9513-934323D02116@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0CB3642C-084C-4751-9513-934323D02116@yesql.se> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Sep 29, 2020 at 12:26:46PM +0200, Daniel Gustafsson wrote: > > On 29 Sep 2020, at 00:14, PG Bug reporting form wrote: > > > Hello, > > I have noticed that in the documentation of Postgresql 13 on the website for > > example at https://www.postgresql.org/docs/13/functions-json.html the table > > are all messed up. > > Compared to the same table in the previous version > > https://www.postgresql.org/docs/12/functions-json.html > > This was an intentional change, made in order to better fit wide content. I didn't notice it before - is there any change this change could be rolled back? Previous layout makes the information trivial to see and easy to diff visually between doc versions. New version, in my opinion, is much worse when it comes to readability. Best regards, depesz