Re: [docbook-apps] Better rendering for programlisting

[David Cramer <david@thingbag.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/05/2012 10:38 AM, davep wrote:

>> 1. Stick with what we have now. 2. Use the table solution and
>> accept the limitation that all lines must always be the same
>> height.
> 
> Why is this an issue Norm? How often in a fixed width font do users
> want exponents/Drop caps etc?

The callouts cause the lines that contain them to be a little higher
than the others, causing the line numbers to become out of whack. If
you have more than a couple of callouts, the code listing ends up
extending beyond the line numbers and obviously the line numbers
aren't accurate.

>> I'm open to suggestions on 3, but I'm not likely to figure it out
>> myself.
>> 
>> Thoughts? Other suggestions?
> 
> You've obviated the line numbers by putting content in col 2... why
> not finish the job and put co in col 3?

But what if the user wants to put the callout somewhere other than the
end of the line? If you do that, you should just abandon callouts and
refer to line numbers from a list below the code listing.

> Then I could cut/paste?

That should be hard requirement for html outputs.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPpcR1AAoJEMHeSXG7afUhXKIH/1SyaZPW2wna9n9ljdoDHHar
+7rrfuFZpwPsmhh8rtlIK6x7nGOTXOmMV71Q3BCdS0g0+TUlbmoqmeu5CjLHjf9+
w+9iK6qd0e7acWtym2hOClZqy11XoF5K/00DZAx3h3K2+7izumx45SKQwAtc/dES
QiuyAEjcC5fh6KHMoIFXg4aaAMPCrloPKaznpgfv6GT6WA4rvwmhvjmqfvggYNkU
UeTLKXUFLBO8XiJum4vHVW9nQqE/Cwhdu62RLqUGslzK23oJKVUM8UZLvJdmtWnQ
73yhf5DfepliU8VQNPvN+n/JYse3z78S89NzlBE0j3++GBVA2+BBxGpNJqQsCDY=
=wPhz
-----END PGP SIGNATURE-----