Re: Unicode UTF-8 table formatting for psql text output
От | Peter Eisentraut |
---|---|
Тема | Re: Unicode UTF-8 table formatting for psql text output |
Дата | |
Msg-id | 1255689495.16715.9.camel@fsopti579.F-Secure.com обсуждение исходный текст |
Ответ на | Re: Unicode UTF-8 table formatting for psql text output (Roger Leigh <rleigh@codelibre.net>) |
Ответы |
Re: Unicode UTF-8 table formatting for psql text output
Re: Unicode UTF-8 table formatting for psql text output |
Список | pgsql-hackers |
(HTML mail to preserve formatting; let's see if it works.)<br /><br /> I like the new Unicode tables, but the marking ofcontinuation lines looks pretty horrible:<br /><br /> <tt> List of databases</tt><br /><tt> Name │ Owner │ Encoding │ Collation │ Ctype │ Access privileges</tt><br /><tt>───────────────┼───────┼──────────┼───────────┼───────┼───────────────────</tt><br/><tt> pl_regression │ peter │ LATIN2 │ cs_CZ │ cs_CZ │</tt><br /><tt> postgres │ peter │ LATIN2 │ cs_CZ │ cs_CZ │</tt><br /><tt> template0 │ peter │ LATIN2 │ cs_CZ │ cs_CZ │ =c/peter</tt><br /><tt> ╷ ╷ ╷ ╷ ╎ peter=CTc/peter</tt><br /><tt> template1 │ peter │ LATIN2 │ cs_CZ │ cs_CZ │ =c/peter</tt><br/><tt> ╷ ╷ ╷ ╷ ╎ peter=CTc/peter</tt><br /><tt>(4 rows)</tt><br/><br /> This looks more like a rendering mistake than something sensible, and also it doesn't actually helpthe viewer to tell what lines are continued, which was the original purpose.<br /><br /> On a side note, I don't reallyunderstand why the access privileges need to be broken up over multiple lines. There is plenty of space left on theline.<br /><br /> Note that the above is close to a default setup, so that is what many people will see by default fromnow on.
В списке pgsql-hackers по дате отправления: