From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: shr: alt text truncation
Date: Fri, 05 Nov 2010 09:22:59 +0100 [thread overview]
Message-ID: <yb0sjzgji1o.fsf@dod.no> (raw)
In-Reply-To: <m3lj58o9x8.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> I added the limit because of tables, really. :-) I found that in my
> test cases, the alt texts were typically the thing that took up most
> space, because it's not uncommon to have obnoxiously long, but
> nonsensical alt texts, and when rendering tables, this made many of
> them somewhat unreadable.
Couldn't you keep them out of the width calculation for the table
columns, but let them expand to the width determined by the other cells
in that column?
Or is that what you tried, that looked bad?
next prev parent reply other threads:[~2010-11-05 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 0:53 Katsumi Yamaoka
2010-11-05 1:07 ` Lars Magne Ingebrigtsen
2010-11-05 8:22 ` Steinar Bang [this message]
2010-11-08 20:32 ` Lars Magne Ingebrigtsen
2010-11-09 8:39 ` Steinar Bang
2010-11-09 17:49 ` Lars Magne Ingebrigtsen
2010-11-09 22:00 ` Ted Zlatanov
2010-11-09 23:00 ` Steinar Bang
2010-11-09 23:12 ` Rupert Swarbrick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yb0sjzgji1o.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).