From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Feature request: HTML table formatting Date: Fri, 13 Apr 2007 06:23:16 +0200 Message-ID: References: <461D6C86.2060601@gmail.com> <6ab5c96fc04df1271f2c5ddb8ba171c3@science.uva.nl> <461E7F1A.5070802@gmail.com> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HcDNu-0000SK-7h for emacs-orgmode@gnu.org; Fri, 13 Apr 2007 00:27:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HcDNt-0000Ru-KF for emacs-orgmode@gnu.org; Fri, 13 Apr 2007 00:27:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HcDNt-0000Rr-F1 for emacs-orgmode@gnu.org; Fri, 13 Apr 2007 00:27:41 -0400 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HcDJe-0000pk-FW for emacs-orgmode@gnu.org; Fri, 13 Apr 2007 00:23:18 -0400 In-Reply-To: <461E7F1A.5070802@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Daniel J. Sinder" Cc: Matej Cepl , emacs-orgmode@gnu.org On Apr 12, 2007, at 20:48, Daniel J. Sinder wrote: > > I think rejecting vertical rules as a matter of style is a mistake. > Whether you consider org-mode tables to be a markup or a > spreadsheet, it's peers -- HTML, LaTeX, Gnumeric, Excel, etc. -- > will all produce tables with vertical rules if asked to do so. I'm > wary of tools that enforce style. I'd prefer to read the style > guide and then decide for myself (that is, use it as a *guide* not > an edict). Fair enough. > However, if vertical rules are too clunky, difficult, > time-consuming, or low priority to implement, that's an entirely > different matter that I can fully understand. As I said, I don't want to have a special separator for this, implementation would be very cumbersome and I'd like to be able to have ! as a character in a table field. Maybe something like a special #+FORMAT line above the table to set special formatting directives. - Carsten