From ooo-dev-return-1574-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Mon Jul 4 18:00:31 2011 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3E51D68AD for ; Mon, 4 Jul 2011 18:00:31 +0000 (UTC) Received: (qmail 64407 invoked by uid 500); 4 Jul 2011 18:00:31 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 64217 invoked by uid 500); 4 Jul 2011 18:00:30 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 64209 invoked by uid 99); 4 Jul 2011 18:00:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 18:00:30 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net designates 76.96.27.243 as permitted sender) Received: from [76.96.27.243] (HELO qmta13.emeryville.ca.mail.comcast.net) (76.96.27.243) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 18:00:22 +0000 Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta13.emeryville.ca.mail.comcast.net with comcast id 3tas1h0031smiN4ADu003U; Mon, 04 Jul 2011 18:00:00 +0000 Received: from [192.168.1.9] ([67.180.51.144]) by omta20.emeryville.ca.mail.comcast.net with comcast id 3u1P1h00t36gVt78gu1SVE; Mon, 04 Jul 2011 18:01:26 +0000 Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Dave Fisher In-Reply-To: <793280.43338.qm@web161422.mail.bf1.yahoo.com> Date: Mon, 4 Jul 2011 10:59:56 -0700 Cc: ooo-commits@incubator.apache.org Content-Transfer-Encoding: quoted-printable Message-Id: <7FCB326A-6DE0-4759-84D3-4048E0C30F5D@comcast.net> References: <20110704152224.7ECFE2388994@eris.apache.org> <5589495C-C188-43B3-812A-36C509A032E9@comcast.net> <325204.78804.qm@web161423.mail.bf1.yahoo.com> <0F49D7AD-21D8-44A2-8886-C6882496587B@comcast.net> <469839.67695.qm@web161427.mail.bf1.yahoo.com> <5B636A12-7783-4E59-A66B-F69F109C74B6@comcast.net> <793280.43338.qm@web161422.mail.bf1.yahoo.com> To: ooo-dev@incubator.apache.org X-Mailer: Apple Mail (2.1084) On Jul 4, 2011, at 9:39 AM, Joe Schaefer wrote: >>> Perhaps you can describe "why" you need to do this? >>=20 >> Yes. not everyone has a big screen like you. A lot of people have = learned that=20 >> eye fatigue is aggravated by reading long lines. >=20 > That isn't useful feedback. Useful feedback would be something like: > the table columns break the text into two rows on whitespace-separated = text. > Or is it the reverse, that you *want* them to break into two rows ( > in which case you have a bug because that's not what happens on my > screen)? OK. I could have stated my issue more carefully. There are two different = points here. One is overall and the other is specific to this case. (1) Overall we should all agree that we design our web content to look = in a narrow window like a laptop. Ten years ago this would be about = 600px. Now I think we should work towards 800px. Then pages work on = Tablets, Laptops, etc. (2) The intent is for the shorter data in the first three columns to not = wrap - while the last column is very free-form. When not given widths I = find that html layout gives too much space to this content. I now have it controlled by adding   to the longest text in columns = two and three. The fourth column only wraps for three people on my 13" = laptop and the table looks like it was done by a professional. >=20 >>> Would simply using   between the text words resolve this? >>=20 >> Perhaps, so. I'll be experimenting with the headers. But for me = knowing pixels=20 >> is a little easier than counting   >=20 > No that's not what I meant for you to do. What I meant was, look at = the > longest entry in each column and replace the separating whitespace in > that one entry with  . If your problem is columns breaking = prematurely > this will resolve it. Yes, this is what I did on my second try. Admittedly this moves the = problem. A real solution would modify markdown. This is something to = think about. >>>> Maybe someone should enhance markdown extras. >>>>=20 >>>> http://michelf.com/projects/php-markdown/extra/#table >>>>=20 >>>> All it can do is control the alignment. Width control ought to be = allowed,=20 >>=20 >>>> either that or an id / class tag to actually tie it in with = specific css. >>>>=20 >>>> | Item | Value | >>>> | ------200 | --:100| >>>> | Computer | $1600 | >>>> | Phone | $12 | >>>> | Pipe | $1 | >>>>=20 >>>> Thoughts? >>>=20 >>> You do realize that the CMS allows you to do arbitrary things with = the =20 >> markdown, >>> including preprocessing it before sending it off to the templating = system. =20 >> Also >>> the python markdown parser is extensible, so if you prefer going = that way=20 >> and >>> contributing code to infra we can add a custom extension for = everyone to=20 >> use. >>=20 >> Yes, I do. I am currently thinking about the OOo webcontent and = conversion of=20 >> the html. >=20 > We have an xslt file somewhere in the conversion-utilities directory > that converts tables to markdown-style tables, if you decide to go = that way > (and I strongly recommend you do). It's currently embedded in the > anakia stuff but can easily be extracted. Yes. A pointer to existing scripts is great. If you would give me the = full repos path I'll take a look this week. You may have noticed that we've started with a webcontent fetch in = ooo/trunk/tools/dev/. >> There will be thousand of pages, but hopefully not too many = patterns. >>=20 >>=20 >>=20 >>>=20 >>>>=20 >>>> Otherwise I really don't see why it's wrong to have the html = table here. >>>=20 >>> If you had examined the content of the table you might have noticed = how=20 >> bloody=20 >>=20 >>> awful >>> the html was (filled with unmatched tags). What you have now is = far more=20 >>> maintainable >>> in a collaborative context- humans make terrible html parsers. >>=20 >> Agreed. Not everyone has written lexers and parsers. >>=20 >> I'm just frustrated by the movement of the controls. >=20 > Change happens. ;-) And when two committers are in the same place discussion happens for all = to see! Regards, Dave