On Sat, Nov 7, 2020 at 11:24 PM Per Bothner wrote:
>
> I checked in some css tweaks for the DomTerm manual to make use
> of the latest makeinfo changes.
>
> If you're concerned that ': '
> is verbose I can look into using JavaScript to remove the colon.
> (If you're fine with the currently-checked
On Sat, Nov 07, 2020 at 03:24:20PM -0800, Per Bothner wrote:
> I checked in some css tweaks for the DomTerm manual to make use
> of the latest makeinfo changes.
>
> If you're concerned that ': '
> is verbose I can look into using JavaScript to remove the colon.
> (If you're fine with the currently
I checked in some css tweaks for the DomTerm manual to make use
of the latest makeinfo changes.
If you're concerned that ': '
is verbose I can look into using JavaScript to remove the colon.
(If you're fine with the currently-checked-in code I won't bother.)
One more issue related to definitions
On Sun, Nov 01, 2020 at 08:37:48AM -0800, Per Bothner wrote:
> On 11/1/20 7:10 AM, Gavin Smith wrote:
> > The colon is still present in the category, as I mentioned in
> > my other message.
>
> That colon is way ugly, but it seems easy to fix - see attachment.
The result cannot really be translat
On 11/1/20 9:40 AM, Gavin Smith wrote:
On Sun, Nov 01, 2020 at 08:37:48AM -0800, Per Bothner wrote:
On 11/1/20 7:10 AM, Gavin Smith wrote:
The colon is still present in the category, as I mentioned in
my other message.
That colon is way ugly, but it seems easy to fix - see attachment.
I gue
On Sat, Oct 31, 2020 at 09:26:30PM +, Gavin Smith wrote:
> I read an explanation online of how it worked a few days ago; unfortunately
> I cannot find it again now.
Found it:
https://django-sphinxdoc.readthedocs.io/en/latest/change_appearance.html
> To only show the headings’ “¶” sign if you
On Sun, Nov 01, 2020 at 08:37:48AM -0800, Per Bothner wrote:
> On 11/1/20 7:10 AM, Gavin Smith wrote:
> > The colon is still present in the category, as I mentioned in
> > my other message.
>
> That colon is way ugly, but it seems easy to fix - see attachment.
I guess so, although it makes the HT
On Sat, Oct 31, 2020 at 03:16:26PM -0700, Per Bothner wrote:
> On 10/31/20 2:26 PM, Gavin Smith wrote:
> > Feel free not to consider it if you find implementing your desired
> > functionality enough, but there has also been discussion of outputting
> > an "anchor" at def items to provide a link tha
On 11/1/20 7:10 AM, Gavin Smith wrote:
The colon is still present in the category, as I mentioned in
my other message.
That colon is way ugly, but it seems easy to fix - see attachment.
Note I prefer rather than because it helps makes the output
well-formed XML, which I think is useful. (Th
On Fri, Oct 30, 2020 at 05:05:28AM -0700, Per Bothner wrote:
> dt.synopsis span.category { float: right; padding-left: 2em; }
> dt.synopsis span.category:before { content: "[" }
> dt.synopsis span.category:after { content: "]" }
> dt.synopsis span.category-suffix { display: none }
As of commit 2d2
On Thu, Oct 29, 2020 at 03:46:23PM -0700, Per Bothner wrote:
> The html output for definitions only allows for very limited css styling.
>
> As an example of the kind of styling it would be nice to enable, in my Kawa
> and
> DomTerm manuals I move the "category" to the right margin,
> as you can
On 10/31/20 2:26 PM, Gavin Smith wrote:
Feel free not to consider it if you find implementing your desired
functionality enough, but there has also been discussion of outputting
an "anchor" at def items to provide a link that could be copied:
https://lists.gnu.org/archive/html/bug-texinfo/2020-0
On Thu, Oct 29, 2020 at 03:46:23PM -0700, Per Bothner wrote:
> The html output for definitions only allows for very limited css styling.
>
> As an example of the kind of styling it would be nice to enable, in my Kawa
> and
> DomTerm manuals I move the "category" to the right margin,
> as you can
On Fri, Oct 30, 2020 at 05:05:28AM -0700, Per Bothner wrote:
> On 10/30/20 12:13 AM, Gavin Smith wrote:
> > I think it's worth supporting this with CSS if all it needs is adding
> > some element classes to the output.
>
> Note that adding descriptive class names isn't just for styling - they
> cou
On 10/30/20 6:34 AM, Patrice Dumas wrote:
On Fri, Oct 30, 2020 at 05:05:28AM -0700, Per Bothner wrote:
On 10/30/20 12:13 AM, Gavin Smith wrote:
I don't think there is a strong reason to not use non-standard attributes:
It's fully supported by javascript and css. There are a couple of minor rea
On Fri, Oct 30, 2020 at 05:05:28AM -0700, Per Bothner wrote:
> On 10/30/20 12:13 AM, Gavin Smith wrote:
>
> I don't think there is a strong reason to not use non-standard attributes:
> It's fully supported by javascript and css. There are a couple of minor
> reasons
> (validation becomes more co
On 10/30/20 12:13 AM, Gavin Smith wrote:
I think it's worth supporting this with CSS if all it needs is adding
some element classes to the output.
Note that adding descriptive class names isn't just for styling - they
could be useful for searching or (say) extracting only all the definitions.
On Thu, Oct 29, 2020 at 03:46:23PM -0700, Per Bothner wrote:
> The html output for definitions only allows for very limited css styling.
>
> As an example of the kind of styling it would be nice to enable, in my Kawa
> and
> DomTerm manuals I move the "category" to the right margin,
> as you can
The html output for definitions only allows for very limited css styling.
As an example of the kind of styling it would be nice to enable, in my Kawa and
DomTerm manuals I move the "category" to the right margin,
as you can see examples of here:
https://www.gnu.org/software/kawa/Composable-pictur
19 matches
Mail list logo
